It would perhaps be a good idea the check that all the Settings are properly documented in the help.
For example, I just found that for Settings/Performance Graphics Adapter, Enable FlipEx on Full screen, and Memory Lock are undocumented. Of which I am curious about the two latter ;)

Thanks,

v16.0.0.108 Since upgrading I have been getting this error "Unhandled exception" on starting vMix on a win10 64bit install. Latest Windows build. Full error text below. If I quit the error message vMix will start normally next time. Any ideas?

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'SlimDX, Version=2.0.13.43, Culture=neutral, PublicKeyToken=b1b0c32fd1ffe4f9' or one of its dependencies. The system cannot find the file specified.
File name: 'SlimDX, Version=2.0.13.43, Culture=neutral, PublicKeyToken=b1b0c32fd1ffe4f9'
at fu.Show(Exception ex, String Source)
at fzzzzza.m()
at fzzzzza.l()
at vMix.frmSplash.b(Object a, EventArgs a)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].



************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll

---

vMix
Assembly Version: 16.0.0.108
Win32 Version: 16.0.0.108
CodeBase: file:///C:/Program%20Files%20(x86)/vMix/vMix64.exe

---

Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

---

System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

---

System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

---

System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

---

System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

---

WindowsBase
Assembly Version: 3.0.0.0
Win32 Version: 3.0.6920.8693 built by: QFE
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/WindowsBase/3.0.0.0__31bf3856ad364e35/WindowsBase.dll

---

System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

---

System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

---

System.Web.Services
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll

---

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

richardgatarski,

I am using a Asus GTX760 card with the latest drivers with vMix 108 and 3 monitors, but I am using windows 7.

I have tried to reproduce your problem using full screen but I am not getting them.

A couple of things to ask you:
what motherboard do you have? as I am using a Asus motherboard and it has a programme that controls the speed of the processor and the CPU, it is called EPU-6 Engine, when I have the EPU-6 Engine set to Auto vMix is very sluggish but when I set it to high performance vMix works great and videos run smoothly.

the other thing is are you using the ASUS GPU Tweak app that comes with the GTX760 to control the card? that can make a difference as it controls the speed of the card.

Oh okay,

I am using 3 1920 x 1080 monitors, and you would know if you were using the ASUS GPU Tweak app as you would have an shortcut icon on your desktop.

Good day. And sorry for my english.
Can somebody tell me, is Vmix16 work with encoder Teradec cube series correctly, or there may be problems with this equipment?
Thanks

The Terradec Cube is supported by vMix. If you have a single Cube (transmitter) you can bring it in via your IP network or via HDMI. On the network there is a slight delay (on my system) of 3-4 frames) on the low latency settings.

If you have a pair (transmitter/reciever) you bring it in as a normal input source viz HDMI. Again very low latency.

As mentioned above you can also use the Cube as you streaming/encoder in which case you take the output of your PC via HDMI into the Cube and have the Cube handle the processing and transmission of the signal to your CDN. To my mind however, that is an expensive way to go as vMix is very efficient as a streamer/encoder.

Possible "BUG" with vMix 16.0.0.114 and animated XAML titles.

I came across this in testing kayllastudio's recent sample contribution:

http://forums.vmix.com/d....aspx?g=posts&t=5664

I am not sure if this is isolated to my system or is related to a recent update to Windows 10 or simply a BUG, but none of the animated XAML titles I have tested (including the vMix lower thirds standard ones) are behaving "properly" when activated, either fullscreen or as a DSK Overlay (buttons 1,2,3,4). They do not animate "IN" automatically, but rather need to be "played" manually, otherwise, there is no visual until you remove the "Overlay" and the image appears and animates out appropriately.
The odd thing is, they will animate "IN" properly when used within the 'MultiView' feature, only there is no way to trigger an animate "OUT" from there that I am aware of (perhaps a feature request is in order for that).


Ice

As a general rule, the Performance settings are designed primarily for troubleshooting which is why many are not documented.
(Intended only for us to try and narrow down problems that come up during tech support).

The reason being the defaults almost always offer the best performance for the majority of uses
and in my experience tinkering with these settings can often make things worse.

In the case of FlipEx, its function is quite technical so the oversimplified explanation
is that it allows vMix to keep a small queue of video frames that Windows can pull from to display on screen.
This allows smoother video at 50 and 60 frames per second, where in the past you had to try and get the timing exactly
right to avoid dropped frames.

vMix can also submit a finished frame into the queue and move on straight away without waiting for a frame to be displayed on screen
hence why it also allows for reduced render times.

Enable FlipEX on Fullscreen
vMix has used FlipEx a long time now on Fullscreen and it works great most of the time.

Enable FlipEX on Previews
In the past few updates it has also been enabled for the main vMix interface on both the Preview and Output windows
and also the Input previews.

Problem is, having too many FlipEx boxes in a single window causes some problems on some systems.
Particularly having a large number of Inputs and then scrolling them will cause DWM to use up a lot of CPU.

So finally, in 114 the Enable FlipEX on Previews box will only enable it on the Preview and Output windows since they don't
use scrolling. The input previews work just like earlier versions of vMix 16 and earlier.

vMix 17

A whole new method of rendering the input previews is being added to vMix 17. This solves the scrolling problem
while simultaneously providing the smooth video benefits of FlipEx.

Does this mean that the fullscreen output has some latency when FlipEx on fullscreen is enabled?

Admin wrote

I did spend almost a day in total trying to isolate what caused the stuttering issues I had (reported above), including starting with a clean setting and preset. We did not have to problem, somehow it appeared a couple of months ago. I understand that the complexity of Windows, graphics drivers, display devices, and you name it makes it hard to maintain everything full proof all the time. In fact, I am impressed by how well vMix works, develops, and maintain stability.
Last Friday i simply disabled FlipEx on Fullscreen - and the stuttering went away totally during a full hour production. I will continue to experiment turning it on and off. But in my book, at least on this PC FlipEx cases stuttering.
Note again, the stuttering only appears (intermettently) on vMix's Preview and Output windows, not in the recording or in the stream. I still have to see if I get the same issue on other PCs.

Admin wrote

OK. May I humbly suggest you make a note of that in the Help and in the Settings tab. Perhaps also make a separate section clearly marked as "Debug specific" or something similar.

Thanks.