XSplit Broadcaster did not shut down properly

If XSplit Broadcaster was shut down improperly or unexpectedly, you can use the Select Presentation window for some basic troubleshooting. If the shut down occurred after adding a new source to a scene, it is recommended to load a backed up presentation, a previously saved presentation, or to create a new presentation. 

If the error occurs after adding the source another time, please make sure to document any error messages and immediately seek out assistance from our support team at support.xsplit.com.

Recommendation for Primary Monitor Setup

On desktop machines which has a monitor connected to both Nvidia/AMD discrete graphics and Intel on board Graphics card, it is recommended to always connect the Primary monitor directly to the Discrete GPU.

To review which GPU is currently connected to the primary monitor (Win 8.1 or Win 10), right-click desktop and select “Screen Resolution”. View which monitor is the primary by looking at which screen has the added icon group. You will also find a text telling if the selected display is your main monitor. Check to see if that monitor is connected to the Nvidia/AMD GPU, if not then you can change this in two ways:

1. If you wish to keep the position of the actual monitor assigned as the primary monitor, then go ahead and simply change the wiring so that the DVI or HDMI input on that screen is connected to the Nvidia GPU.
2. Alternatively, you can click on the secondary monitor, make that primary by checking the checkbox to make it your main display and ‘apply’ settings. But doing it in this way will switch your main view monitor.

XSplit Broadcaster Software Information

Your stream or recording was limited by performance or affected by network issues. This following sections will help you understand what and how to change to ensure your stream is uninterrupted and set to the best possible quality.

We are currently working on gathering baseline data to establish the guidelines. This page will be updated regularly – please check back soon.

The XSplit Team

Introducing Adaptive CBR in XSplit Broadcaster V2

This blog post will introduce you to the newest XSplit Broadcaster V2 feature, adaptive bitrate!

Adaptive Bitrate is a new feature in XSplit Broadcaster 2.4+ available for CBR streams (currently only for x264 codec). If enabled, the bitrate will automatically change when network conditions fluctuate. For example if your upstream bandwidth changes midstream, XSplit Broadcaster will try to match the current available upstream bandwidth to prevent constant frame drops, and if more bandwidth becomes available later, then the system will readjust to target your set CBR bitrate.

Hopefully this feature will be able to address bandwidth fluctuation problems often experienced by user on ADSL connections.

What does it mean to “drop frames”?

When the bitrate output by the encoder is higher than your actual upstream bandwidth, frame dropping is a common known technique to temporarily lower the bitrate and avoid building up a long queue/delay. In technical terms we often talk about dropping frames before or after the encoder. If CBR bitrate settings is applied to the encoder then dropping frames before the encoder does not help much, so instead we drop frames by dropping parts of the encoded bitstream in the RTMP send/output queue. By doing it in this way we also ensure that local recordings of a live broadcast remain intact.

Hence, if your CBR bitrate settings is higher than your actual upstream bandwidth at any time, then we will allow the send queue to grow, but will eventually cut part of the bitstream corresponding to a full GOP (group of pictures) – this is the time when you will see dropped frames (in bulk) corresponding to the number of frames that we cut.

This process will continue until your upstream bandwidth can again keep up, but unfortunately there may be prolonged periods where frame drops will continue. The experience for viewers will look like small stop/resume with pieces of your stream missing. Depending on the streaming service/server and how ingest and buffering is handled, you may never see the actual stops, but there will still be small pieces missing, – gaps if you will.

What is adaptive CBR?

Adaptive CBR is one of our newest features in XSplit Broadcaster 2.4+ that we hope will improve and streamline your streaming experience. Previously, you were allowed to change your bitrate manually while streaming if you saw you were dropping too many frames and suspected that your bandwidth had decreased. Since this can be hard to monitor and even harder to change during intense broadcasting sessions, we have developed adaptive bitrate to deal with this issue before you suffer  stream drops at an inopportune moment.

What does adaptive CBR do?

Adaptive CBR monitors the delay of the send queue and if the queue grows above a certain threshold then the adaptive CBR function will decrease the bitrate to slightly below the last known bitrate. Once the stable bitrate is found, adaptive CBR will continuously check to see if the bitrate can be increased back closer to the original setting or if the bitrate need to be further lowered. This loop function continues during your broadcasting and will help to ensure that you do not experience dropped frames.

Needless to say that lowering the bitrate also lowers the quality, and large changes in upstream bandwidth over short periods of time can still result in dropped frames or very decreased quality of your stream. Magic can only take you so far -:), so your internet provider need to take you the rest of the way.

How to enable Adaptive Bitrate

  1. Go to your Broadcast Plugin. For example Twitch, head to Twitch Properties.
  2. Under Video Encoding Section, click on the Gear Icon to open Video Encoding Setup WindowXSplit Broadcaster Twitch Properties
  3. Make sure to enable ‘Strict CBR’ first and then check on Adaptive CBR.XSplit Broadcaster Video Encoding Setup
  4. Click OK to save the Settings.

Now you can broadcast without having to restart your stream or manually having to reconfigure settings when the going gets tough.

It’s still an experimental feature but please give us your feedback in the comments below!

Deleting faulty DirectShowSpy registry key

Some users that use a 3rd party tool called DirectShowSpy may encounter errors when logging in to XSplit.

This can be caused by a fault registry key that is introduced when DirectShowSpy is registered to intercept Filter Graph initialisation — Filter Graph is used by XSplit. The faulty DirectShowSpy registry key is usually caused by DirectShowSpy program begin relocated after registration.

To workaround this situation, XSplit1 detects the presence of HKEY_CLASSES_ROOT\CLSID\{E436EBB3-524F-11CE-9F53-0020AF0BA770}\TreatAs registry key2 when it fails to initialise Filter Graph and exits when it is found. In this case, user must manually correct the DirectShowSpy registration or delete3 the registry key. Only after either is done can XSplit be restarted.


  1. Implemented in XSplit Broadcaster v2.2. In XSplit Gamecaster, this workaround will be implemented in v2.3.
  2. For 64 bit Windows, the registry key is HKEY_CLASSES_ROOT\Wow6432Node\CLSID{E436EBB3-524F-11CE-9F53-0020AF0BA770}\TreatAs
  3. Deleting this registry may require special/full permissions. Read here on how to do it.

XSplit Broadcaster Memory Usage

XSplit Broadcaster is currently only available as a 32 bit application, but on both 32 and 64 bit Windows 7+ operating systems. We do have a 64 bit version in the pipeline, but before we publish this, we want to make sure that it is compatible with all 3rd party integrations. For example, several capture cards’ integrations lack 64 bit support and we are working with manufacturers to extend 64 bit support. One of the limitations of 32 bit applications is the amount of OS memory that each 32 bit process can use. If LARGEADDRESS space aware manifest is not used, then the limit for an application is 2GB. If LARGEADDRESS space aware manifest is used, then the limit is extended to 3GB on a 32 bit OS and 4GB on a 64 bit OS.

The default configuration of XSplit Broadcaster (as of version 2.2) is to only address up to 2 GB (please note this is different than the memory usage reported by task manager). This can cause issues for users who have very complex presentations. If you are encountering such issues, then it is advisable to reconfigure XSplit Broadcaster to run with the LARGEADDRESS space aware manifest is used, or the 3GB-aware version of XSplit Broadcaster. The following guide will direct you on how to set this up.   
To run XSplit Broadcaster using the 3GB-aware exe, please follow the instructions below:
 
1. Open the XSplit Broadcaster application folder. This is normally located in C:\Program Files (x86)\SplitmediaLabs\XSplit Broadcaster\
2.  Backup XSplit.Core.exe by renaming it to XSplit.Core.exe.bak
3. Go to the folder labeled “3GB-aware” and move the XSplit.Core exe into the main program folder.
4. Run XSplit.Core.exe.
Starting with XSplit Broadcaster 2.3, LARGEADDRESS space configuration will be the default and users will no longer have to perform the above workaround. So far we have found no problem in using LARGEADDRESS space configuration, but it is still considered experimental so please report any issues you encounter to xsplit.com/support