Trailer for S2 of A Lo…. Any advice on getting into adbo…. Playing StarCraft well without…. Customize Sidebar Post a Reply. Update 13th May XSplit have released a better x encoder in their update package.
The directions in this thread are no longer necessary, simply update to the latest XSplit version. I recently wrote a stream quality guide and lambasted XSplit for its lack of multi-core encoding which severely hinders performance on modern PCs that can execute 4 or 8 threads simultaneously.
I was intrigued since XSplit uses x, which is programmed to be multi-thread capable and decided to look into it further. Turns out XSplit ships with an old x encoder which either doesn't support multithreading or it is turned off by default. Thankfully due to the wonders of API compatibility, we can simply drop in a replacement encoder and get full benefit from multi-core systems! Here are two videos highlighting the difference, encoded with the exact same xsplit settings - same bitrate, same FPS, same quality - only the modified encoder.
Close XSplit. Download libx Rename libx Extract the new libx Now when you encode with XSplit, it will use as many cores as necessary for a good quality video. Obviously results will vary once you throw SC2 into the mix, but for those of you who use XSplit on quad core and especially i7 CPUs, this should allow you to greatly increase quality on your stream note that replacing this DLL won't actually improve quality by itself, it will allow you to set higher quality without running into single thread CPU limits.
I have re-hosted it on TL to ensure a safe download. Holy shit, were you full screen on quake? I would love to stream quake! No really though, this is amazing. This is huge. Thanks for your continued help for all of the up and coming streamers out there.
Thanks for this awesome find R1CH! Will be very interesting to test this out! Holy crap R1CH that is amazing. Although admittedly I never had any huge issues to begin with. Yeah it will help on any system quad core or higher. I noticed this greatly increases the size of the file, presumably it also affects bandwidth use? How will this replacement affect people who are already streaming near their max upload speed?
On May 09 Antoine wrote: I noticed this greatly increases the size of the file, presumably it also affects bandwidth use? One would wonder why the developers of such a popular program have not done this. So there's nothing to adjust with this change? Is it just smoother or the capabilities better? Also, do I have to readd this every patch? Thanks for this definatly gona use for my stream. On May 09 lynx. On May 09 Torte de Lini wrote: So there's nothing to adjust with this change?
Have you had any time to fiddle with the quality on xsplit? Im wondering how much of an impact it has. Would this be an improvement for a dual core machine?
Wow just downlaoded it gonna try it now, really awesome! Hardware requirements: AVerMedia capture card see list above , latest drivers. Note the capture cards cannot function as capture card and encoder at the same time. You need two cards to capture and encode in pure hardware, or combine capture mode with another available HW encoder. Back to Blog. Melvin Dichoso A basketball junkie, blogger, headphone enthusiast, aspiring chef, and traveler wannabe. Does social media and various other stuff for XSplit.
The reasoning here is simple — namely that a single frame at 25 FPS is more important than a single frame at 60 FPS when the overall target is to retain the same visual quality for both the 25 and the 60 FPS stream. For local recording it can still be desirable to control the maximum bandwidth used, so the UI in XSplit still allows the user to set a vbv-maxrate and vbv-buffer.
In the user interface of XSplit we only allow average quality mode as discussed above, since this is often a much more effective mechanism. However, for both main rate control schemes another supplementary rate control is often used and for successful live streaming with XSplit it is even required — the VBV rate control.
With quality based encoding you are assured of a particular quality but not a particular bandwidth usage. For live streaming it is important not to exceed your own available upload bandwidth, but also important not to exceed the download speed of viewers.
Streaming with a constant bandwidth is an option used by some encoders, but this rate control mechanism or lack thereof wastes bandwidths and often put larger requirements on quality of connection for both publisher and viewers. This basically means that the x encoder in XSplit tries to maintain a constant quality of the stream and can use less bandwidth in less complex or less important scenes. Hence your video bitrate can still exceed the discrete value of Kbps BUT you will not exceed Kbit during a 2 second period.
If you grasp this concept then you will also understand the flexibility that the vbv-buffer provides. It basically allows the encoder to look ahead on a series of frames and then choose to use a more bits to encode some frames in a sequence and less on others as long as the vbv-buffer is not exceeded. But here is what you now need to understand — the vbv-buffer is really a decode side buffer so it depends on the decoder which is mostly flash player in our case.
I hope this is all starting to make some sense! So this would mean that if flash player buffer with your provider was set to something like 10 sec then you would be able to really beef up my vbv-buffer size and in turn get same quality at lower overall bandwidth or better quality at the same bandwidth — Well , you would esentialy allow more liberty for the encoder to spike the bitrate when needed.
So you can expect that the XSplit team will have a dialog with our partners to see if we can actually get them to adjust their flash player buffer to match the VBV —buffer set in XSplit.
On this final note I wanted to get back to our local recording again.
0コメント