The RTMP URL format of specifying a username and password before the hostname ( is really just an ffmpeg convention and does not actually reflect the way username and password authentication information is sent via the RTMP protocol. It is possible to tunnel RTMP sessions over HTTP, although this is not that widely used by most streaming providers: None of these is really an HTTP authentication mechanism (such as HTTP Basic or HTTP Digest authentication) as the RTMP protocol is different from the HTTP protocol. Swallow wrote:I have no experience with DaCast but if DaCast support RTMP authentication format which is just HTTP authentication format, you can include username and password into the url.Ĭode: Select all I mentioned in another thread, there are different forms of authentication that can be used with RTMP, including URL query parameters and Adobe RTMP authentication (as an initial step of the RTMP protocol):

This could be a local server running Nginx (or similar), or a public RTMP forwarding service like restream.io Other than using the USB webcam output with OBS (or other streaming software), the other workaround I am aware of is to stream through an intermediate RTMP server which does support RTMP authentication. Ethanw wrote:I'm just awaiting a chat with the DaCast team to confirm but while I'm waiting, has anyone had confirmation that there is no way around with with the mini pro? I realllllly don't want to loose the MV and have to use the HDMI to go to my hardware encoder.According to other people that have gotten in touch with DaCast support, there is no way to turn-off username/password authentication for their RTMP streams.Īnd since the ATEM Mini Pro doesn't have a way to configure RTMP username/password authentication, it's not really possible to go direct from the ATEM Mini Pro to DaCast at the moment.

Blackmagic design atem mini pro