![]() ![]() ![]() When I noticed the cache filling up I started thinking about what the switch is doing. I found out that the switch is uploading with 4,5mbit when I set the quality to 4,5 mbit. Problem solved! Or at least, problem moved! Every step of the way we've gotten confirmation that we do, in fact, know what we're doing, but so far that hasn't solved any of our problems. Our entire system is set at 1080p30 for consistency. OBS is set at 5Mb/s, and we've mostly be trying to test the ATEM at the 'Streaming Med' profile for 4.5Mb/s. We've checked the network/port configurations, and even moved the ATEM to the OBS Comp Ethernet that streams fine and the ATEM seems to be having issues. It finally started working last week, but regardless of streaming quality set in the ATEM, it still fills the cache (not to mention what's going out is extremely poor quality), even though we're able to stream out OBS at full quality with no issues. It took a few weeks to get the RTMP stream to handshake/stream to BoxCast (we tried multiple different resets of the Streaming.XML file, with BoxCast's help/confirmation that our code was correct from the start, as well as a few other integrator friends we know just to get some other minds on it). We're currently troubleshooting the same issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |