Actions11
- Filters and Effect Actions
- Metadata Actions
- RTMP Restreaming Actions
- Transcoding Actions
- Video Processing Actions
Overview
The node provides functionality related to FFmpeg operations, including RTMP restreaming. Specifically, the "Start Restream" operation under the "RTMP Restreaming" resource allows users to stream a media file to a specified RTMP URL. This is useful for scenarios where you want to broadcast or restream video content from a media source to an RTMP server, such as live streaming platforms or custom streaming servers.
Practical examples include:
- Streaming a pre-recorded video file to a live streaming service.
- Redirecting or restreaming a media input to multiple RTMP endpoints.
- Automating live broadcasts by feeding media files into RTMP streams within workflows.
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. While the exact structure is not detailed in the provided code, typically it would include status information about the streaming process, such as success confirmation, error messages if any, and possibly metadata about the stream.
If the node supports binary data output (e.g., processed media files), it would be included in the output's binary fields, but this is not explicitly shown here.
Dependencies
- Requires an API key credential for FFmpeg-related services (referred generically as an API authentication token).
- Depends on FFmpeg functionality exposed via an external service or API.
- The node internally uses a router module to delegate execution to specific action handlers, including the restream action.
Troubleshooting
- Invalid Media Input: If the media file input URL or binary field name is incorrect or inaccessible, the restreaming will fail. Ensure the media source is valid and reachable.
- Invalid RTMP URL: Providing an incorrect or malformed RTMP URL will cause connection failures. Verify the RTMP endpoint format and availability.
- Authentication Errors: Missing or invalid API credentials will prevent the node from executing FFmpeg operations. Confirm that the required API key or token is configured correctly.
- Timeouts or Network Issues: Streaming requires stable network connectivity. Network interruptions can cause the restream to stop unexpectedly.
- Error Messages: The node may throw errors related to FFmpeg processing or streaming failures. Review error details in the node execution logs to identify issues.