GoodSync

What's new in this version:

vMix 21.0.0.60
- Added support for alpha channel when using XSplit VCam
- Improved performance when using API to update multiple text fields


vMix 21.0.0.59
- Added support for alpha channel when using XSplit VCam
- Improved performance when using API to update multiple text fields


vMix 21.0.0.58
- Fixed GPU render time issue when using the List input after a long period of time


vMix 21.0.0.57
- Fixed login issue with Twitch
- Added workaround for issue with codecs that don't correctly support more than 4GB of memory
- Fixed frame offset issue during Replay transitions
- Fixed ColourCorrectionReset shortcut not correctly resetting Gamma
- Fixed issue with VST3 plugins that have duplicate names
- Fixed issue with FFMPEG recording 29.97p in EU
- Fixed vMix Social issue when Windows region set to Turkey


vMix 21.0.0.56
- Fixed issue with ButtonPress activator on the APC Mini
- Fixed List tab not refreshing when saving Video Delay clips to a list
- Added error messages describing when Camera or Microphone access is disabled in Windows Privacy settings
- Improved compatibility with new NDI support in Skype


vMix 21.0.0.55

- Recalibrated skin tone line in Vectorscope for better accuracy
- Added new recommended Periscope streaming quality presets

Fixed some issues with new Kona HDMI card and added support for the following modes:
- Up to 4K60 on Input 1 + 2x HD on Input 3 and 4
- Up to 4K60 on Input 1 + 4K30 on Input
- Up to HD60 on Inputs 1,2,3 and 4


vMix 21.0.0.53
- Fixed support for streaming to Facebook Groups
- Fixed auto creation of Facebook streams when description was left bank


vMix 21.0.0.51
- Fixed issue logging in to Facebook with Two Factor Authentication in some countries
- Updated Facebook permissions to support latest security requirements for Groups
- Fixed issue where vMix Call return video freezes or becomes garbled when changing sources
- Fixed rare error that may occur when closing vMix on slower systems


vMix 21.0.0.50
- Improved recording quality in Replay when using 1080p sources
- To enable, select 200 Mbps as the bitrate before adding the replay session to vMix
- Previously 200 Mbps would only have an effect on Interlaced sources
- Relaxed video format restrictions with AJA capture devices

New rules are as follows:
- All outputs must be in the same "clock family". (29.97/59.94 or 50/25)
- Port 1 must be in same clock family as outputs if used as an input channel
- Ports 2+ will accept any input format
- Fixed some rare issues with AVI codecs


vMix 21.0.0.49
- Change log not available for this version


vMix 21.0.0.47
- vMix Diagnostics is now included with install and can be found from the "hamburger" menu in vMix or in the start menu
- Detects any background applications that may interfere with the graphics card causing errors, flickering and performance issues
- Fixed replay bug when trying to play back incomplete events
- Fixed issue where PTZ Optics ZCAM provider did not appear in PTZ dropdown list


vMix 21.0.0.45
- Fixed issue with SetAudioFade when used with List input
- Improved CPU usage accuracy
- CPU/GPU warnings are now disabled by default
- Can be enabled under Settings -> Performance.
- When disabled, will still be reported in the logs to help assist our support team


vMix 21.0.0.44
- Additional bug fixes for Sony BRC series VISCA over IP support
- Will now no longer attempt to reconnect to Facebook streams that have expired


vMix 21.0.0.43
- Improved performance of local desktop capture on desktop PCs
- Added support for Sony BRC series PTZ cameras using VISCA over IP
- Fixed issue with audio only NDI outputs not appearing


vMix 21.0.0.42
- Fixed memory issue with VST3 plugins, especially with latest Windows 10 update
- Video frame delay now supported on NDI and VLC inputs
- Added "Custom Multi-Bitrate" dropdown option in streaming destinations.
- This allows custom URLs and Stream Keys for each stream without using separate streaming instances for each which may cause problems with some CDNs
- Fixed issue in vMix Social where Overlay was sometimes triggered before content in title had been updated