![]() ![]() I have 2 GB RAM on the development server. So, aĬouple of 12 second stalls in the middle of a two minute race is a bit I seem to see more dropouts when thereĪction in the shots (we’re wanting to stream live horse races). However, I get “stalled” segments about every 12 - 36 seconds, with the I start the encoder (Wirecast) and connect with Safari on an iPhone. Has anyone found a solution to this issue? We would like a way to fix the delay without adding a pre-input delay which would put our locally encoded files out sync. ![]() We also encode to disk in windows media format and audio and video are in sync in the resulting. We stream from Wirecast to EC2 instance of Wowza and audio is ahead of the video for all clients. We are experiencing the same problem with a similar setup. I’m pushing the stream out over TCP via wirecast, and have the UDP range open. Is there something I need to tweak in the AVSync config parameters, or is it something else? The delay problem doesn’t seem to be related to the encoder hardware as it does the same thing whether I do it from our stream producer system at the office using Osprey capture, over the T1s or from a DVCAM deck into my laptop at home via Firewire over my cable modem. We’re running rtplive and pushing a 500K (nominal) stream at 15fps. While this workaround generally works (and we need to make sure that any video content we play from within Wirecast is also delayed by 10 frames), at some point we’re considering offering a simultaneous Windows Media stream, which is perfectly in sync without the hardware audio delay. The biggest hitch we’re running into is that we have to delay our audio 330ms (10 frames) upstream of the encoder for it to arrive in sync at the client. If you do plan on recording a local copy of your content, especially if it's in HD 1080p, you may want to save your hardware encoding option for that (see Step 10, below) and not use it for the smaller Facebook 720p encoding.We’re using Wirecast to EC2, and generally we love how well it works. ![]() So if you use hardware for Facebook Live 720p encoding, you might not also be able to also use it for recording to disk, for example. Not all hardware encoding options allow more than one thing to use them at the same time. If you have CPU cores to spare and your minimal bandwidth is important to you, then software encoding may be the way to go however, for most streaming scenarios, hardware encoding is more than sufficient. If you are streaming dynamic, fast-moving content with multiple effects or scene changes then you might want to compare the hardware encoded quality against the software encoded quality for best results. The main tradeoff is that the bitrate will be higher and the quality might not be as good - although it’s rarely a noticeable difference. Using hardware encoding, when available, is generally a good idea as it will free up your CPU for other tasks. This is called "hardware encoding" or "GPU-Accelerated encoding." NVENC is made by NVIDIA and will be available if you have a NVIDIA graphics card installed in your computer. "Quicksync" is made by Intel and comes with many of its CPUs that have an integrated graphics card (on Macs it’s called "Apple H.264"). You won’t see these options unless you have these chips in your computer. "Apple H.264," "Quicksync" or "NVENC" use chips on your graphics card, also known as your GPU (Graphics Processing Unit) to encode and compress the video. This is sometimes called "software encoding." This generally allows the computer to make “smarter” decisions when choosing what information to include and what information to get rid of when encoding your video stream and allows it to maintain the best quality:size (bitrate) ratio. "x264" uses the computer’s Central Processing Unit (CPU) to do all the encoding. In the screenshot here, you can see that I chose between "x264" and "Apple H.264." On Windows, you might see "Quicksync" or "NVENC" in addition to "x264." Depending on the hardware in your computer you will see between 2 and 6 different encoding options based on these settings. They only allow (or recommend) 720 HD video in either 30 frames or 60 frames per second.īy default, Wirecast will limit you to Facebook’s preferred settings. On another note, if you don’t know what "encoding" means in relation to video and audio or live streaming, you probably will want to read this article.Īlthough you don’t necessarily need to change anything, we'll discuss it now, so you have an idea of what the settings do and how they work.įacebook is quite strict on the size and quality settings of any live video you stream to the site via the Live API. We cover Frequently Asked Questions, including what computer to use with Wirecast. If you don’t know what "quad core" means in relation to computers or why that matters with Wirecast, you should probably watch this video.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |