Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
The node provides functionality to start RTMP restreaming of a media file. It takes an input media source (either a URL or a binary media file) and streams it to a specified RTMP URL. This is useful for scenarios where you want to broadcast or restream video content to live streaming platforms that accept RTMP input, such as YouTube Live, Twitch, or custom streaming servers.
Practical examples include:
- Restreaming a prerecorded video file to a live streaming platform.
- Redirecting a live stream from one source to multiple RTMP endpoints.
- Automating live broadcasts by feeding media files into RTMP servers.
Properties
| Name | Meaning |
|---|---|
| Media File Input | A valid media URL or the name of the input binary field containing the media file to stream. |
| RTMP Url | A valid RTMP URL where the media file will be streamed to. |
Output
The node outputs JSON data representing the result of the restreaming operation. The exact structure is not detailed in the provided code, but typically it would include status information about the streaming process, such as success confirmation, error messages if any, or metadata about the stream.
If the node supports binary output (e.g., processed media files), it would represent the streamed media or related data, but this is not explicitly shown here.
Dependencies
- Requires an API key credential for the underlying ffmpeg service or API.
- Depends on an external ffmpeg-based service or library capable of handling RTMP restreaming.
- The node internally uses a routing mechanism (
router.call(this)) to delegate execution to appropriate handlers.
Troubleshooting
- Invalid Media Input: Ensure the media input URL is accessible or the binary field name is correct and contains valid media data.
- Invalid RTMP URL: Verify the RTMP URL is correctly formatted and the target server is reachable.
- Authentication Errors: Confirm that the required API authentication token or credentials are properly configured in n8n.
- Streaming Failures: Network issues or server-side problems at the RTMP endpoint can cause failures; check connectivity and server logs.
- Timeouts or Unexpected Stops: Large media files or unstable network connections might interrupt streaming; consider splitting media or improving network stability.