ATEM Mini pro direct RTMP streaming

Hello. I saw many information, that new ATEM Mini pro could direct stream to YouTube or Facebook. But there is any information about direct streaming to own rtmp server. Is it possible?

In the demo they show you can edit an XML file to add in any streaming services you want (your own as well).

Good to know. Our company usually streams to our own site.

Though it'd be nice to have this easily accessible via ATEM Software Control, rather than being a hack.

Simon : It was showed on video .. U can edit your own presets .. Thats ok .. Somebody who know whats need will configure it .. And user only select SERVER and Quality (low,mid, hight) in Atem Sofware Control ..
My question is , how will be quality .. Especially on low bitrate streams .. Old atem H264 recorder (or old ATEM TVS) was ok with high bitrates .. But quality was not acceptable in lowbitrate streams .. I was used MXlight , Load high bitrate from ATEM and recompress to lowbitrate to my WOWZA ..

It's not so much a "hack" as a one time XML coding change. You'd need to add the RTMP server and then the bitrate, frame size, fps and keyframe interval to it. Once you save the change it should be available as a preset.

Best,

David

Good to know. Our company usually streams to our own site.

Though it'd be nice to have this easily accessible via ATEM Software Control, rather than being a hack.

It's not so much a "hack" as a one time XML coding change.

Same thing.

I'm saying an addition to the software allowing the operator specify the URL for streaming, bitrate, frame rate, etc., along with the ability to save, recall and delete those presets would be a very welcome addition.

In other words, a GUI front end to hacking the XML. (You know, the way software normally works.)

While I don't disagree with you, for many that use the device they will probably only have to do it once. Plug in a couple more preset destinations and some lower bit rate encoding presets and then you can pull it up from the menu.

I would imagine that future releases of software will add this ability to do so. Judging by some of the responses on this forum people seem to want a lot more things when the value proposition to begin with is unbelievable at the price point. As Grant said in the presentation, if you merely bought it for use as an encoder it's a great value proposition on it's own.

Many asked for a multiview on the original and BM responded in kind. I'm sure they will look to up the game in the coming releases.

Best,

David

It's not so much a "hack" as a one time XML coding change.

Same thing.

I'm saying an addition to the software allowing the operator specify the URL for streaming, bitrate, frame rate, etc., along with the ability to save, recall and delete those presets would be a very welcome addition.

In other words, a GUI front end to hacking the XML. (You know, the way software normally works.)

[Gary Adams]

Hello Everyone. We wanted to post this information about setting up custom streaming services on the ATEM Mini Pro. As it was stated earlier, this is for advanced users with an understanding of how to edit and use XML files. There is a file called "Streaming.XML" that may be modified to change or add services in the ATEM Software Streaming menu. This file is located in the following places:

MacOS: /Library/Application Support/Blackmagic Design/Switchers/Streaming.XML

Windows: C:\Program Files (x86)\Blackmagic Design\Blackmagic ATEM Switchers\ATEM Software Control\Streaming.XML

These locations are in protected areas of the OS requiring administrater prividleges. When editing this file make a backup of the original just in case something is not working correctly so you can go back. Also note that many of the text editors that come native with the OS may not accurately edit these files and leave hidden control characters causing the file to not read properly. I would not recommend using notepad, wordpad, textedit or any word processor for this purpose. There are plenty of free apps that work just fine.

An experienced XML user will be able to easily identify the fields and make the necessary changes. With this file, you can edit, add or remove the existing choices in the ATEM menu. The available fields for each "Service" include URL, Server, bit rate and key frame interval. You can create several bit rate choices like the current High, Medium or Low. The file provides for the ability to assign two bit rates for each selection. The lower bit rate applies to lower frame rates of 30 fps and less. The higher bit rates would apply to above 30 fps. Once the file is changed and saved, it is necessary to restart the ATEM software. It is not necessary to restart the ATEM Mini Pro. Once a service has been loaded into the ATEM Mini Pro, it will be retained through power cycles until a new service has been loaded.

Sorry for the long text. I hope this helps. I'm sure there will be questions.

Regards, Gary

Here is the file :

Code: Select all

<?xml version="1.0" encoding="UTF-8" ?>
<streaming>
   <service>
      <name>Facebook</name>
      <servers>
         <server>
            <name>Default</name>
            <url>rtmps://live-api-s.facebook.com:443/rtmp</url>
         </server>
      </servers>
      <profiles>
         <profile>
            <name>Streaming High</name>
            <config resolution="1080p" fps="60">
               <bitrate>9000000</bitrate>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>6000000</bitrate>
            </config>
         </profile>
         <profile>
            <name>Streaming Medium</name>
            <config resolution="1080p" fps="60">
               <bitrate>7000000</bitrate>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>4500000</bitrate>
            </config>
         </profile>
         <profile>
            <name>Streaming Low</name>
            <config resolution="1080p" fps="60">
               <bitrate>4000000</bitrate>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>3000000</bitrate>
            </config>
         </profile>
      </profiles>
   </service>

   <service>
      <name>Twitch</name>
      <servers>
         <server>
            <name>Australia: Sydney</name>
            <url>rtmp://live-syd.twitch.tv/app</url>
         </server>
         <server>
            <name>Asia: Singapore</name>
            <url>rtmp://live-sin.twitch.tv/app</url>
         </server>
         <server>
            <name>Asia: Thailand: Bangkok</name>
            <url>rtmp://live-bkk.twitch.tv/app</url>
         </server>
         <!-- ... -->
      </servers>
      <profiles>
         <profile>
            <name>Streaming High</name>
            <config resolution="1080p" fps="60">
               <bitrate>8000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>6000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
         <profile>
            <name>Streaming Medium</name>
            <config resolution="1080p" fps="60">
               <bitrate>6000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>4500000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
         <profile>
            <name>Streaming Low</name>
            <config resolution="1080p" fps="60">
               <bitrate>4000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>3000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
      </profiles>
   </service>
   
   <service>
      <name>YouTube</name>
      <servers>
         <server>
            <name>Primary</name>
            <url>rtmp://a.rtmp.youtube.com/live2</url>
         </server>
         <server>
            <name>Secondary</name>
            <url>rtmp://b.rtmp.youtube.com/live</url>
         </server>
      </servers>
      <profiles>
         <profile>
            <name>Streaming High</name>
            <config resolution="1080p" fps="60">
               <bitrate>9000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>6000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
         <profile>
            <name>Streaming Medium</name>
            <config resolution="1080p" fps="60">
               <bitrate>7000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>4500000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
         <profile>
            <name>Streaming Low</name>
            <config resolution="1080p" fps="60">
               <bitrate>4500000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>3000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
      </profiles>
   </service>
</streaming>

Gary : I have questions :

1/ quality of recording onto HD is maded with the same selected preset/quality for streaming ?

2/ When U have PAL source (1080i50, 1080p50) and preset have 30 fps or 60 fps .. it will send as 30/60 ?

3/ How about deinterlacing ?

4/ How about audio encoding ? Bitrate ? Mono/stereo ? Will be adde later ?

Here we have the answer for the questions

https://www.provideocoalition.com/atem- ... -revealed/

[Gary Adams]

Now that I have mine up and running, I'll add that you can go lower than 3Mb/s. I'm running 1 on the simple service I use. The 3-70 is published in our documents so I'll leave it at that. There is some room to play for sure. It will be interesting to see what users run. Also, remember the names we use for the Quality settings are names. The Hyperdeck group has higher preset settings for better recordings, but you can stream and record at all settings assuming all the infrastructure allows. The Recording and Streaming (for Ethernet) rates are always identical. There is only one encoder. You can stream separately using a computer over USB but recording will not be possible then. The reason we show two bit rates is just to change the rate for lower fps. You don't have to do that, it is just a method we use since the quality will be similar. We do not have separate controls for audio streaming. The two channels ride along with the video in this case.

With the 8.2 software you will notice there is a new "Connections" selection in the main menu. Instead of selecting the ATEM switcher in Preferences, Connections provides selecting ATEM by name or IP Address. This will allow switching between ATEMs much faster.

I hope this helps. Stay safe. Gary

Gary : Thanx for answers .. What bitrate have audio ?

Since the audio is embedded in the Video, the audio bit rates should be the same as the video setting.
Cheers

Denny : but in XML is missing bitrate for audio..

Yes Roman, but isn’t the video bit rate setting also controlling the audio bit rate, since they are tied together? As there is only one encoder for both video and audio, which is controlled by the XML code.
While the video is being compressed for h.264 ins’t the embedded audio is normally an uncompressed WAV file, as the audio signal is so small compared to the video stream, or the audio bit rate is fixed, regardless of the video bit rate, which controls the level of video compression. This is an interesting question Roman, and you have me wondering also.
Cheers

With a firmware update, would the ATEM Mini Pro have the capacity to send the Multiview out via the USB or Ethernet instead? This would be amazing for a couple of reasons - to monitor the multiview on a laptop screen to have a small footprint of gear for some gigs, and to free up the HDMI OUT for either an AUX to send camera/powerpoint to a big screen or to record Program out to Prores.

Yes Roman, but isn’t the video bit rate setting also controlling the audio bit rate, since they are tied together?

NO .. Audio and Video is going embeded , but its still 2 streams .. Standard for streaming is H264 for picture and AAC for audio .. Or U can use uncompressed audio , mp3, etc .. codec as U want .. In MPEG era , we was used MPEG 1 or Mpeg 2 video and MP2 audio (mpeg audio layer2 ) .. Now is standard H264 or HEVC (H265) and complementary with this is AAC for audio .. AAC have multiple codecs formats too ..
In every encoder U are selecting bitrate for video .. Default is 3-8 mbps for HD/FHD signals .. And audio is 128-256kbps .. 128kbps is not very good (enough for AAC-HE) , do I normaly using 256 kbps .. Facebook want 128kbps, but 256kbps working .. Thats is my question , how is bitrate .. And it will be good , to have chance to edit it in XML too .. 128k is OK for discussion/talks .. But for music , concerts, etc we need more .. I preffer 256k ..

With a firmware update, would the ATEM Mini Pro have the capacity to send the Multiview out via the USB or Ethernet instead?

YEs .. It would be great to have chance select , what is going on USB out .. I really need to select Preview BUS into USB and HDMI out use as a PGM out on ATEM MINI ..

Gary : Do U think , that is doable in future updates ? Or USB out is directly connected to PGM ?

Yes! This device is so close to a perfect...my ideal set up would be:
- AUX out via HDMI
- Multiview available in software to view on laptop
- Preview Audio channels in solo, and audio mix monitoring via software
- Record 10bit Prores to disk (or high-bit rate H.264/H.265), while simultaneously encoding the livestream at lower bit rate

The hardware is short a headphone monitoring jack and a second HDMI out port, IMHO

Also, does anyone know if, with a firmware update, the Audio 1 or 2 inputs could be reversible? Given we can change the line/mic setting...does the hardware allow converting them to headphone out instead?

Yes Roman, but isn’t the video bit rate setting also controlling the audio bit rate, since they are tied together?

NO .. Audio and Video is going embeded , but its still 2 streams .. Standard for streaming is H264 for picture and AAC for audio .. Or U can use uncompressed audio , mp3, etc .. codec as U want .. In MPEG era , we was used MPEG 1 or Mpeg 2 video and MP2 audio (mpeg audio layer2 ) .. Now is standard H264 or HEVC (H265) and complementary with this is AAC for audio .. AAC have multiple codecs formats too ..
In every encoder U are selecting bitrate for video .. Default is 3-8 mbps for HD/FHD signals .. And audio is 128-256kbps .. 128kbps is not very good (enough for AAC-HE) , do I normaly using 256 kbps .. Facebook want 128kbps, but 256kbps working .. Thats is my question , how is bitrate .. And it will be good , to have chance to edit it in XML too .. 128k is OK for discussion/talks .. But for music , concerts, etc we need more .. I preffer 256k ..

Thanks Roman, I forgot about ACC, and you bring up a good point. It will be interesting to get the answers on this.
Cheers

- Record 10bit Prores to disk (or high-bit rate H.264/H.265), while simultaneously encoding the livestream at lower bit rate

As it was described .. THere is only one encoder .. So recording to disk and streaming use the same data ..

We wanted to post this information about setting up custom streaming services on the ATEM Mini Pro. This is for advanced users with an understanding of how to edit and use XML files.

THAT is the problem I would like to solve here, by making such changes possible within the GUI.

Eventually.

Hello! I did a custom setup for our ATEM mini pro, and got it to stream to castr. The settings do not seem to work correctly however, as all our streaming ends up as 1080p60 even on medium or low settings. I manually removed the 60fps options for high and medium to force a lower framerate, but it doesn't seem to work. Anyone got any ideas?

Code: Select all

<?xml version="1.0" encoding="UTF-8" ?>
<streaming>
  <service>
      <name>Castr</name>
      <servers>
         <server>
            <name>EU-West (London, UK)</name>
            <url>rtmp://uk.castr.io/static</url>
         </server>
      </servers>
      <profiles>
         <profile>
            <name>Streaming High</name>
            <config resolution="1080p" fps="30">
               <bitrate>6000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
         <profile>
            <name>Streaming Medium</name>
            <config resolution="1080p" fps="30">
               <bitrate>4500000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
         <profile>
            <name>Streaming Low</name>
            <config resolution="720p" fps="60">
               <bitrate>4500000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="720p" fps="30">
               <bitrate>3000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
      </profiles>
   </service>
   <service>
      <name>Facebook</name>
      <servers>
         <server>
            <name>Default</name>
            <url>rtmps://live-api-s.facebook.com:443/rtmp</url>
         </server>
      </servers>
      <profiles>
         <profile>
            <name>Streaming High</name>
            <config resolution="1080p" fps="60">
               <bitrate>9000000</bitrate>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>6000000</bitrate>
            </config>
         </profile>
         <profile>
            <name>Streaming Medium</name>
            <config resolution="1080p" fps="60">
               <bitrate>7000000</bitrate>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>4500000</bitrate>
            </config>
         </profile>
         <profile>
            <name>Streaming Low</name>
            <config resolution="1080p" fps="60">
               <bitrate>4000000</bitrate>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>3000000</bitrate>
            </config>
         </profile>
      </profiles>
   </service>

   <service>
      <name>Twitch</name>
      <servers>
         <server>
            <name>Australia: Sydney</name>
            <url>rtmp://live-syd.twitch.tv/app</url>
         </server>
         <server>
            <name>Asia: Singapore</name>
            <url>rtmp://live-sin.twitch.tv/app</url>
         </server>
         <server>
            <name>Asia: Thailand: Bangkok</name>
            <url>rtmp://live-bkk.twitch.tv/app</url>
         </server>
         <!-- ... -->
      </servers>
      <profiles>
         <profile>
            <name>Streaming High</name>
            <config resolution="1080p" fps="60">
               <bitrate>8000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>6000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
         <profile>
            <name>Streaming Medium</name>
            <config resolution="1080p" fps="60">
               <bitrate>6000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>4500000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
         <profile>
            <name>Streaming Low</name>
            <config resolution="1080p" fps="60">
               <bitrate>4000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>3000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
      </profiles>
   </service>
   
   <service>
      <name>YouTube</name>
      <servers>
         <server>
            <name>Primary</name>
            <url>rtmp://a.rtmp.youtube.com/live2</url>
         </server>
         <server>
            <name>Secondary</name>
            <url>rtmp://b.rtmp.youtube.com/live</url>
         </server>
      </servers>
      <profiles>
         <profile>
            <name>Streaming High</name>
            <config resolution="1080p" fps="60">
               <bitrate>9000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>6000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
         <profile>
            <name>Streaming Medium</name>
            <config resolution="1080p" fps="60">
               <bitrate>7000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>4500000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
         <profile>
            <name>Streaming Low</name>
            <config resolution="1080p" fps="60">
               <bitrate>4500000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
            <config resolution="1080p" fps="30">
               <bitrate>3000000</bitrate>
               <keyframe-interval>2</keyframe-interval>
            </config>
         </profile>
      </profiles>
   </service>
</streaming>

[Gary Adams]

Hello Fredrick. The fps is determined by the ATEM Mini Pro Frame rate in the Setup Icon on the software. Set that to the frame rate you want. The encoder doesn't change the frame rate. Setting a lower quality still will use the incoming frame rate to chose the bit rate. I hope that helps.

Regards, Gary

Can you change the encoder to stream at 1280x720?

Best,

David

Hello Fredrick. The fps is determined by the ATEM Mini Pro Frame rate in the Setup Icon on the software. Set that to the frame rate you want. The encoder doesn't change the frame rate. Setting a lower quality still will use the incoming frame rate to chose the bit rate. I hope that helps.

Regards, Gary

[Gary Adams]

Hello David. Thanks for your support of the forum. The encoding over the Ethernet is fairly simple. The resolution and frame rate is determined by the switcher setting. So it is always 1080p at the selected frame rate. Using the USB Web cam the image can be down converted to just about anything with software like OBS. You could also capture the HDMI output through a higher quality device if that is of interest.

Regards. Gary

Thanks Gary,

If I set the switcher to 720P 59.94 will the encoder match those settings?

Best,

David

Hello David. Thanks for your support of the forum. The encoding over the Ethernet is fairly simple. The resolution and frame rate is determined by the switcher setting. So it is always 1080p at the selected frame rate. Using the USB Web cam the image can be down converted to just about anything with software like OBS. You could also capture the HDMI output through a higher quality device if that is of interest.

Regards. Gary

Hello Fredrick. The fps is determined by the ATEM Mini Pro Frame rate in the Setup Icon on the software. Set that to the frame rate you want. The encoder doesn't change the frame rate. Setting a lower quality still will use the incoming frame rate to chose the bit rate. I hope that helps.

Regards, Gary

I see, then I understand the way it works. Thanks for your reply, Gary!

Best regards Fredrik

Hi Gary, is there a way to view the multiview on a computer over the USB or Ethernet? I’d like to keep the HDMI out free for 10bit recording.

And with a firmware upgrade, is it possible to incorporate separate audio monitoring? If program out always has program audio mix out, could the multiview’s attaches audio be switched between solo previewing of audio channels and the program audio? It seems crazy to have amazing fairlight processing but not separate monitoring.

Likewise, is it possible for the camera control panel to adjust non-BMCC cameras? So that as well as scaling, the HDMI inputs can have basic davinci color applied, to balance contrast, saturation, gain etc?

[Gary Adams]

Hello David. The ATEM Minis do not output 720p. Only 1080p. They will accept 720p and 1080i as inputs. All the ideas here will be passed along as feature requests to consider.

Regards, Gary

David, before the Mini can control a camera’s settings via HDMI, that camera has to be able to communicate with the switcher. To date, only the BMD Pocket 4K/6K Cameras with the new FW update can do this. BMD can not control how a Panasonic or Nikon Camera will work, nor can they create any FW updates for cameras they do not make.
Cheers

Thanks Denny - given that the ATEM Mini Pro seems to have Fairlight's EQ processing built in, I was wondering if the HDMI inputs had any basic image control processing (contrast/saturation/WB/gain etc) but I guess that capacity comes from the cameras themselves... Thanks!

Considering that FB only allows 1280x720 it would be helpful to allow it to encode that that.

Best,

David

Hello David. The ATEM Minis do not output 720p. Only 1080p. They will accept 720p and 1080i as inputs. All the ideas here will be passed along as feature requests to consider.

Regards, Gary

Considering that FB only allows 1280x720 it would be helpful to allow it to encode that that.

You can perfectly fine send 1080P50 to Facebook. It does it's transcoding at there servers.. We even streamed 4K to FB trough a Restream account because we went 4K to Youtube. FB does not care and handles it for you.

Daniel : I was sended 1080p into facebook and i had full log of error messages about it .. I was swtiched to 720p, for sure

We're having the same problem, Facebook fills the log with warnings that it's not happy about getting a 1080p stream. I had not understood that this was a limitation in the Mini Pro from the marketing material.

Best regards Fredrik

I've sent a 1080P to FB as well however until FB supports 1080P and higher it's senseless to send that signal to FB. It saves on bandwidth and doesn't rely on FB to scale for me. One thing I have found is that I see lots of people streaming and by the time the signal gets to the end viewer it's been scaled 4+ times. The best scenario is native in, native out. Second best is scale it once and be done with it.

Best,

David

Considering that FB only allows 1280x720 it would be helpful to allow it to encode that that.

You can perfectly fine send 1080P50 to Facebook. It does it's transcoding at there servers.. We even streamed 4K to FB trough a Restream account because we went 4K to Youtube. FB does not care and handles it for you.

Will the Pro save the custom RTMP Streams inside the unit, or would we need to Restore a saved XML file after each power cycle? And/or are the Streams part of the saved Startup State?

Hi all,

I have a question concerning Dacast streaming.
You need to enter a user/password together with with the URL and stream key.
Do you have any suggestions how to add that in the xml file if possible?

Best

Dominique

Game streamers can go 1080P60 to Facebook if they join the Level Up program. And when you have a Teradek streamer going trough Teradek Core. You can just go 1080P to facebook.

https://support.teradek.com/hc/en-us/articles/360045343334-Configuring-the-API-integration-for-streaming-to-Facebook-Live

Additionally, Facebook has whitelisted Teradek's API integration to allow a full 1080p stream to be shown to the audience when streaming from a 1080p encoder source.

Hi all,

I have a question concerning Dacast streaming.
You need to enter a user/password together with with the URL and stream key.
Do you have any suggestions how to add that in the xml file if possible?

Best

Dominique

I have the same issue. Asked DaCast and they said "Would suggest asking the encoder provider on how to stream on akamai settings" because they can't run the stream without the login and password...

With a firmware update, would the ATEM Mini Pro have the capacity to send the Multiview out via the USB or Ethernet instead?

YEs .. It would be great to have chance select , what is going on USB out .. I really need to select Preview BUS into USB and HDMI out use as a PGM out on ATEM MINI ..

Gary : Do U think , that is doable in future updates ? Or USB out is directly connected to PGM ?

I hope you don't mind me jumping in too. First time poster here.

Yes! Please! This is the main feature I'm hoping for. I haven't bought one *yet*, but to be able to preview everything on the laptop, and have a clean HDMI output feed for local 'broadcast/program feed' and stream, and record the full output to USB would be the dream. I've even been on the phone talking to a local rep and doing my research prior to purchasing about this exact functionality.

Hi all,

I have a question concerning Dacast streaming.
You need to enter a user/password together with with the URL and stream key.
Do you have any suggestions how to add that in the xml file if possible?

Best

Dominique

I have the same issue. Asked DaCast and they said "Would suggest asking the encoder provider on how to stream on akamai settings" because they can't run the stream without the login and password...

I have the same issue. Asked DaCast and they said "Would suggest asking the encoder provider on how to stream on akamai settings" because they can't run the stream without the login and password...[/quote]

Same question here! Any help?

BMD support said the authorization login and password can be added to the end of the stream url in the form of:

?rtmpauth=xxxxxx:yyyyyy

Where xxxxxx is the login and yyyyyy is the password.

Tried that but didn't work. Am I supposed to just add it to the end of the Stream URL? Or is there a specific way this needs to be added to the XML? Please help!

[Gary Adams]

Hello Jamie. There are two possible methods to do this. You would put this in the URL field. It is up to the service to allow one or both of these methods. Some do not. I would test this on OBS first to see if it works in the same way. I hope this helps. Stay safe.

rtmp:\\user_name:password@service_or_IP_address:port/publish_point

or

rtmp:\\service_or_IP_address:port/publish_point?rtmpauth=user_name:password

Regards, Gary

Hello Jamie. There are two possible methods to do this. You would put this in the URL field. It is up to the service to allow one or both of these methods. Some do not. I would test this on OBS first to see if it works in the same way. I hope this helps. Stay safe.

rtmp:\\user_name:password@service_or_IP_address:port/publish_point

or

rtmp:\\service_or_IP_address:port/publish_point?rtmpauth=user_name:password

Regards, Gary

Thank you Gary for responding. I sincerely appreciate it. I feel like I'm close but nothing has worked yet as if I'm missing just one bit of information, or I've written the URL wrong somehow. Is there someone there at BMD that specializes in this sort of thing, using the encoder with a service that requires authentication?

Also, in your response did you mean to make it "rtmp:\\user_name...." or should it be "rtmp://user_name...."?

Here's some additional info that might help. DaCast gives me the following info (I've taken out the numbers and replaced it with # just to be safe in this post)...

Stream URL: rtmp://p.ep######.i.akamaientrypoint.net/EntryPoint

Stream Name: dclive_1_150@######

Backup URL: rtmp://b.ep######.i.akamaientrypoint.net/EntryPoint

Login Details (I've replaced the numbers in this post with XXXXXX for the login and YYYYYY for the password to be safe):

Login: XXXXXX
Password: YYYYYY

So with that information, I feel like I've tried numerous combinations within the Streaming.XML file but it's still not letting the stream go through. Maybe I've entered it wrong. But does this info help YOU in helping me figure out how exactly to enter this into the XML? When I used a Teradek encoder before with DaCast, there was a box in their software for the Stream URL, Stream Key, and then an Authentication Login box and a Password Box. BMD doesn't have the authentication login box and password box.

Hopefully this info helps you in helping me find the correct way to do this. As for OBS, I've never used it before. Again, DaCast says their service works with all RTMP encoders, but they just require authentication. I'm hoping we can find a resolution with the info above.

[Gary Adams]

Apologize for the wrong slashes. I work with too many operating systems and command lines. The method your provider shows should be the right one for the URL. It's up to them to set how the login should be passed in a single line. I like to use OBS as a test setup because it will prove it the URL is good without involving the Mni at all. Worth looking into. Just to start at the beginning. Are you able to stream to You tube directly with the Mini using the default setup and your stream key? If that works, at least we know streaming is working. If you cannot stream to Youtube as a test, then your custom setup will not work because there is something else wrong getting in the way.

Regards, Gary

There are actually a few different authentication mechanisms for RTMP that have been used over the years.

1) Adobe authentication: This is probably the most common form of RTMP authentication which was originally added to Adobe's Flash Media Live Encoder (FMLE) as well as their Flash Media Server (FMS). This authentication mechanism is similar to HTTP Digest authentication and involves using a server-generated nonce string and password hash that are exchanged between the client and server during the initial RTMP connection.

ffmpeg uses the following URL format when supplying a username and password for Adobe-style RTMP authentication

Code: Select all

rtmp://[username:password@]server[:port][/app][/instance][/playpath]

It sounds like the ATEM Mini XML configuration file may be compatible with this URL format as well, but many other software and hardware encoders include username and password fields that are separate from the URL. This is because these pieces of authentication information are not actually sent to the server in the URL, but instead use the digest approach mentioned above. The URL format used by ffmpeg is just for convenience (and earlier versions of ffmpeg used separate pubUser and pubPasswd arguments.

Akamai, Wowza, and many of the other popular streaming servers and CDNs use Adobe-style authentication by default, but it is not the only option for RTMP authentication.

2) URL query parameters: The second RTMP authentication mechanism in widespread use involves sending the username, password, or other authentication information as parameters in the query portion of the URL. These are similar in format to HTTP URL query parameters, but applied to RTMP URLs.

The names of the authentication parameters may vary depending on the streaming server used. The rtmpauth=username:password format seems to be used by Nimble Streamer, while some other streaming servers use different URL query parameter formats. When using URL parameter authentication In Wowza, for example, it is common to use unnamed parameters in the query string (rather than the more traditional key=value pair):

Code: Select all

rtmp://[wowza-ip-address]:1935/live/?username&password

Since there is no fixed format for this style of authentication, the streaming server or CDN should specify the query parameter URL format that is expected.

Some form of encryption (such as RTMPS or RTMPE) is typically used in combination with URL query parameter authentication, because otherwise the username and password information would be sent in plaintext. This differs from Adobe authentication which uses a digest to avoid sending the password directly.

There are actually a few different authentication mechanisms for RTMP that have been used over the years.

1) Adobe authentication: This is probably the most common form of RTMP authentication which was originally added to Adobe's Flash Media Live Encoder (FMLE) as well as their Flash Media Server (FMS). This authentication mechanism is similar to HTTP Digest authentication and involves using a server-generated nonce string and password hash that are exchanged between the client and server during the initial RTMP connection.

ffmpeg uses the following URL format when supplying a username and password for Adobe-style RTMP authentication

Code: Select all

rtmp://[username:password@]server[:port][/app][/instance][/playpath]

It sounds like the ATEM Mini XML configuration file may be compatible with this URL format as well, but many other software and hardware encoders include username and password fields that are separate from the URL. This is because these pieces of authentication information are not actually sent to the server in the URL, but instead use the digest approach mentioned above. The URL format used by ffmpeg is just for convenience (and earlier versions of ffmpeg used separate pubUser and pubPasswd arguments.

Akamai, Wowza, and many of the other popular streaming servers and CDNs use Adobe-style authentication by default, but it is not the only option for RTMP authentication.

2) URL query parameters: The second RTMP authentication mechanism in widespread use involves sending the username, password, or other authentication information as parameters in the query portion of the URL. These are similar in format to HTTP URL query parameters, but applied to RTMP URLs.

The names of the authentication parameters may vary depending on the streaming server used. The rtmpauth=username:password format seems to be used by Nimble Streamer, while some other streaming servers use different URL query parameter formats. When using URL parameter authentication In Wowza, for example, it is common to use unnamed parameters in the query string (rather than the more traditional key=value pair):

Code: Select all

rtmp://[wowza-ip-address]:1935/live/?username&password

Since there is no fixed format for this style of authentication, the streaming server or CDN should specify the query parameter URL format that is expected.

Some form of encryption (such as RTMPS or RTMPE) is typically used in combination with URL query parameter authentication, because otherwise the username and password information would be sent in plaintext. This differs from Adobe authentication which uses a digest to avoid sending the password directly.

Wow, Dave, thank you. That's great info. I understood about 1/2 of it. I'm open to try anything at this point which is why I provided all the URL and Stream Key info a few posts back (taking out the numbers for security reasons of course). My hope is that there will be someone who takes that info and then says: "Here, try typing ______ into the URL part of the XML." The info you provided gives me hope but I'm a bit lost as to what to try writing next.

I will take the previous post's advice and try streaming to YT first just to make sure this thing is working correctly. Assuming it is, hopefully I can find a way to get it to work with DaCast.

NOTE: I'm looking for alternative CDNs that won't be strict with streaming events with music without flagging or cutting the stream. Just was hoping it would work with DaCast since their pricing fits our live stream load perfectly.

Either way, THANK YOU for your help.