Boxee video choppy7/27/2023 ![]() ![]() The only variable I didn't take into account was streaming to both RTMP stream at the same time. YouTube handled 1080p video like a champ, but with a fear Facebook was running into problems downscaling our video I ran it at 720p as well. I tried streaming to Facebook in both 7 (for some reason our max supported resolution went down).Įverything was run at 30fps, with varying framerates. So here I've attached/linked some videos. I also ran the same tests with OBS software to determine where the issue lied, and to my surprise, OBS performed perfectly with smooth video. Not sure if I've been looking at it too long, or if the choppiness really is still there.=, but I can tell you it definitely was there on Facebook while live. Especially when there is only a team of 5 people here, once a week.ĬraigS Ran a myriad of tests today. The only cause I could think of is limited network bandwidth, however I think it impossible for us to be saturating a business gigabit connection through Verizon FIOS while running through gigabit switches the entire way. Yes, streams, it was happening on both YouTube and Facebook (both RTMP streams). Let me know if you have any more insight on this. None of the variables have changed, yet after 5 or so weeks of amazing success, we fall flat on our faces again, but this time with 5 times the viewers. I will try updating and running a test stream now, but I don't understand what would cause it to randomly fail like this. I did see that there was an update for Wirecast today, but I didn't have time to update before the stream. Now here we are, just over a month into using the new Decklink Duo 2 and I just had to stream to our entire congregation (online service because of the pandemic) and show them a video that's rubber-banding for an hour and a half. Please share your thoughts.ĬraigS and Ob coc so I wish I could say the new capture card fixed all of our problems, but it was short lived. The newer ATEM Television Studio HD's (they don't seem to sell our model anymore) support 3G-SDI which is capable of handling the bandwidth for 1080p video which might resolve all of our issues. Not sure if all of this made sense, or what you knowledge level of deinterlacing is, but spending about 20 minutes on google I got about this far. This would explain why the problem seems to get worse at times as the algorithm has trouble with certain frames. Now it is also possible the Wirecast might be taking in 1080i, although it's reported as 59.94 fps so I'm unsure, and the problem lies in Wirecast's deinterlacing. A poorly implemented motion compensation algorithm would interfere with natural motion and could lead to visual artifacts which manifest as "jumping" parts in what should be a stationary or a smoothly moving image. Motion compensation needs to be combined with scene change detection (which has its own challenges), otherwise it will attempt to find motion between two completely different scenes. Sometimes with a poor deinterlacing algorithm implementation, according to this wikipedia article So since the ATEM Switcher is outputting video at 1080i, the Elgato is probably trying to "deinterlace" the video, or combine the "fields/half frames" as I understand it. This is due to the limitations of bandwidth on its HD-SDI interfaces which can't support the bandwidth needed for 1080p (only up to 1080i). I believe Wirecast sees the Elgato HD60 as a 1080p source, however our ATEM Television Studio (the older model) only supports 1080i. So after doing some research today, I think the problem lies in the "deinterlacing process". Please follow these instructions EXACTLY.See how it looks in Live Broadcast Area (do not stream or record).In Wirecast select Layout Show Live Only. ![]()
0 Comments
Leave a Reply. |