All of you have given us so much great feedback over the last several months since Millicast launched, and one thing we heard more than anything else was “the quality is great, the latency is unbelievable, but how can I use it with my RTMP encoding workflow?”
Although our core mission is to help pioneer the future of real-time video streaming, and we love the idea of “pure WebRTC”, we understand many of you today use encoders or software that cannot output WebRTC streams. So we have bridged the gap: Millicast now supports RTMP ingress, and automatically upscales it to a full WebRTC stream with simulcast / ABR support, and the audio tracks also get upscaled thanks to the high quality Opus codec.
Millicast RTMP Ingest Requirements
RTMP has been the de-facto standard protocol for publishing live streams for many years. It’s not very complex, and our aim was to keep it that way. There is nothing to do beyond changing the RTMP publishing URL and stream name/ID in your encoder.
Now when you manage your stream tokens in your Millicast dashboard, you will see “RTMP publish URL” and “RTMP stream name”, which is all you need to set up your encoder! And … Voila!
We also provide some best encoding practices and guidelines in our docs.
We hope you enjoy this new feature. As always, please feel free to email us at hello@millicast.com with any feedback, questions or concerns.
Stay tuned for more updates this summer, and some great announcements prior to IBC 2019.
Cheers,
-Millicast
