| We moved this page to our Documentation Portal. You can find the latest updates here. |
Question:
Using FFMPEG instead of Adobe.
Environment
OnApp CDN
Answer:
If you would like to use FFMPEG to publish a stream, you can use the following commands:
ffmpeg -re -i dummy.mp4 -f flv rtmp://username:password@fms_URL:80/P"CDN_Reference"/mystream
For example:
ffmpeg -re -i dummy.mp4 -f flv rtmp://P404130149:mtXsvYDwQQ@404130149.publishstream.worldcdn.net:80/P404130149/streamname
Note:
In case of external publishing point, Use-of-external-publishing-point the customer should have the RTMP URL "rtmp//xxxxxx.xxxx.com/live/streamname1", first (URL must start with "rtmp//xxxxxx.xxxx.com/live" (for example) ). And, "streamname1" is the name of the stream defined in the ffmpeg command during the streaming in the command line on the CentOS system to the external publishing point. This URL (from the external publishing point) should be playable. And, only after that, you can try to re-stream it using our CDN network.
After that, you should create a Live stream resource from UI and insert "rtmp//xxxxxx.xxxx.com/live/" to the "Main External Publishing Location".
As a result, your CDN URL should be similar to the following example: http://video.yourdomina.net/414746811/_definst_/streamname1.m3u8 ("streamname1" is the stream name, mentioned in the ffmpeg command)
Additionally, please, pay attention to the known limitations:
(1) wowza only supports re-streaming h264+aac to HLS/HDS. (2) For HLS/HDS restream, only wowza rtmp origin is supported