ATEM Mini Pro Slow Upload Speed

I’m doing some YouTube streaming testing and the upload speed being reported by the Mini Pro is only .2 Mbps. YouTube is also flagging the low speed. Once it climbed to 4.5 Mbps but quickly dropped back. Steaming quality on Mini Pro is set to Highest 9 Mbps setting.
The Mini Pro is connected via cat 6 to the Comcast cable modem.
Speed Test from my desktop PC on same wired network is 183 Mbps down/ 28 Mbps up.

Tim


Sent from my iPhone using Tapatalk

The value is not representing the general uploading speed but the data uploaded and that value is not fixed and depends on the content you are uploading (as I see from my own tests).

If you are streaming a fixed picture, an slide of a presentation for example, you will see that the value is low.

If you put a video with with a lot of action then the value will rise.

Try that

Pd. I had the same concern like you

I'm having a similar challenge, including the Mini Pro flashing the "on air" light and the feed dropping completely. I'm not a technical expert, but this has utterly baffled me. Any guidance is greatly appreciated.

Situation:
1. Video content fed to ATEM Mini from Sony FS5, A7II, playback content from Video Assist.
2. Ethernet cable fed from MacBook Pro to ATEM Mini using Internet Sharing (exactly as set up in the launch video). Have also tried hardwired router with the same results.
3. Launched ATEM Software; ATEM Mini Pro connects fine.
4. Run Internet speed test to verify upload speed is averaging 20+ Mbps
5. Confirm YouTube stream key in ATEM Software
6. Press "On Air"
7. "On Air" begins flashing; shows 0.4 Mbps upload speed. Cache fills after 2 minutes and unit shuts down.

I've tried this on all of the stream settings with the same result. Even reprogrammed the XML to create a "streaming base" setting at 2Mbps, which did the same thing, so I restored the original XML file.

After all this, I pull the plug, connect via USB-C using OBS, and the stream connects fine to YouTube (as fine as it can on a new Mac; I still get dropped frames, etc.).

Certainly, this can't be normal behavior. Any suggestions on troubleshooting?

Don’t use Cat-5 cables! That could be the cause.

Im having similar issues. Using the usb output into OBS seems fine but we'd ideally want to use the built in encoder and the ethernet port to stream to facebook via stream key.
When using the ethernet connection for streaming, we're only getting roughly 1 frame per second and the audio is awful. Our upload speed is fine, ranging from 12-20 mbps. Also selecting the lowest quality on the ATEM software.
We have tried both sharing internet over Ethernet with macbook and using ethernet from a switch for both macbook & ATEM.
If anyone has any help, that would be much appreciated!

We have tried both sharing internet over Ethernet with macbook and using ethernet from a switch for both macbook & ATEM.
If anyone has any help, that would be much appreciated!

What about the above mentioned suggestions regarding cables and firewall settings?

Don’t use Cat-5 cables! That could be the cause.

Hello,
What is the issue with using cat-5 cables? Can you elaborate on that point a bit more?
Thank you.

Don’t use Cat-5 cables! That could be the cause.

Hello,
What is the issue with using cat-5 cables? Can you elaborate on that point a bit more?
Thank you.

To be honest, no. But our IT specialist told me to and since then things worked, and that guy is the mother of all nerds. He dreams in binary code.

Cat 5e cable only gets 2.5-5 gig transmission bandwidth, cat 6 can get up to 10 gigs.
Cheers

Cat 5e cable only gets 2.5-5 gig transmission bandwidth, cat 6 can get up to 10 gigs.
Cheers

Thanks Danny!

Resurrecting this thread.

Did anyone ever get to the bottom of this problem as it appears to be exactly the same problem I am experiencing.

Thanks,

I second that resurrection. I was having that issue intermittently. Now it happens constantly. All CAT 7 high end cables. All static IPs. All computers and phones stream perfectly at 6.0mbs on same wired ethernet network. Only the ATEM has this issue. And it's driving me insane. Changed out 6 different cables. 3 Different routers. It is 100% an ATEM Mini Pro issue. Please someone help. Thanks.

Hey folks.

I have the Atem Mini Extreme ISO.

Had this issue during a Wedding Live Streaming on Youtube. The local was in the middle of the mountains, no 3G/4G. Only the local internet. However: Some details must be noted.

1) The local internet link was varying between 10-18 mbps upload speed. Enough for streaming medium or high.
2) We started the Live transmission. Streaming High. It worked fine for some good 20 minutes. The first videos were a countdown and a Pre-wedding. Both made by myself, with a bitrate of 5 mbps - good enough for Youtube live. Everything held fine, no dropouts. Also we advised the few people present (8 people) to not use the local wi-fi.
3) Then, we fired up the same-day-edit video, that was edited in the last 24 hours, and rendered 1 hour before the LIVE transmission. One thing we didn't check -> the BITRATE. Later we saw that It was rendered at 20 mbps. When we started playing this video, the ATEM Extreme buffer started to increase, to 50, 70, 90%, until it went to FULL. And minutes later, people started to warn me that the streaming was freezing.
4) When this video finished playing, we started with the Live feeds from the 3 local cameras (Sony's A7 III), and the buffer kept FULL.
5) We stopped the live streaming and restarted it at Streaming LOW. No avail. It kept the buffer at FULL.
6) We then decided to record everything on an external drive, and upload it later. So we did.
7) One IMPORTANT aspect: we were told that there was a strong rain at the internet provider, which may have caused the link going down.

I made some tests later here at home, trying to replicate the connection limitations, by connecting the ATEM to a cheap repeater/access point, which in turn connects to my home wi-fi. This would give about the same 15 mpbs average upload speed, with a good chance for some dropouts. Tested streaming Low, Medium, High, HyperDeck Low, HyperDeck Medium. Only then I got the buffer to get full again - on HyperDeck Medium. I was streaming the same 'same-day', 20 mbps video. At the best cost/benefit output in my view - Streaming High - the ATEM's data rate indicator was at 9.90 Mb/s maximum. The resulting streaming video at Youtube was pretty solid, good quality.

The conclusion? As you can see, several moving parts which make not that easy to direct point the cause. The ATEM was connected to the router via a CAT6 cable on both cases.

My recommendations after this experience:
1) Render your videos at 5 mbps for streaming, just in case. The culprit, all indicates, was the link itself, later confirmed by the locals. But having a 20 mpbs video doesn't exactly helps.
2) Record everything for later upload if the link fails - do not try to reconnect - just a waste of time.
3) For ISO customers, record individual cameras as well. The client usually asks for a 'teaser' later on.

Just my 2 cents.

I was having an issue with the upload speed and increased our Internet service to 1Gb down and 40 up (the maximum we can get), replaced the switch, the modem, cables, etc. and still had an issue. I restored an older setup file (.xml) and found that my speeds went up from 0.3 Mb/s to 6.9 Mb/s. I was in the process of recreating the setup when I discovered that for some reason the 'Quality' dropdown below the stream key on the Output tab was not displaying a selection. I selected Streaming High and immediately the stream increased from 0.3Mb/s to 6.9 Mb/s. I was able to pinpoint that the change in the setup occurred after I installed version 8.6.4 and remained even though I uninstalled it and installed 8.6.3. I hope this helps someone else.

I used the same solution that K.R. Davidson mentioned. Somehow, the quality wasn't selected on my streaming source. I could paste in the key and get a low broadcast speed for the past few weeks. By setting it to high quality, the speed is back to normal, and I feel like a fool for not realizing the switcher settings were the problem instead of my internet connection.