We have created a playout server based on vMix. By using vMix through the API we can load clips, start them, perform all the things we want to do.
But since version 13 it is not stable anymore. After playing for a couple of days vMix crashes. The only thing we get is: vMix has stopped working. That's all. No messages in the windows log or whatever.
Version 12 was perfect. It played for over 2 months without restarting or whatever.

We checked the performance in regard to memory but that seems to be okay. We didn't change anything to our software. The only thing we did was upgrading vMix. Everything is running on a dedicated Windows machine used for nothing else. System updates are disabled.

Do you have a clue how to solve this?

Finally got some entries in de logs:

Foutbucket 94581754124, type 5
Naam van gebeurtenis: CLR20r3
Antwoord: Niet beschikbaar
Id van CAB-bestand: 0

Handtekening van probleem:
P1: vmix64.exe
P2: 13.0.0.142
P3: 53d10e91
P4: System.Windows.Forms
P5: 2.0.0.0
P6: 5397e03e
P7: 151f
P8: 18
P9: System.InvalidOperationException
P10:

Toegevoegde bestanden:
C:\Users\ctvplayout\AppData\Local\Temp\WER4F70.tmp.WERInternalMetadata.xml

Deze bestanden zijn mogelijk hier beschikbaar:
C:\Users\ctvplayout\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_vmix64.exe_a1dd95f9e8e9a6ad2eabd5e137778fb156104170_00000000_f846577f

Analysesymbool:
Opnieuw zoeken naar oplossing: 0
Rapport-id: 89ac019b-a4df-11e4-8266-e03f49471751
Rapportstatus: 1
Opgedeelde bucket: f6f005fb945a254dd02033fe99d71198

Hi Martin,

We have this error also in the 14.0.0.112 x64 version. Is there a newer version available?
After we upgraded to version 14 we started getting these crashes. We never had them with version 12. So we downgraded to 13. Same issue.
Now we are running 14 again (14.0.0.112) and issue still there.

But it occurs after let's say 3 - 4 days of operation. Never rightaway after launching vMix and starting to control it with our software (using the API).

Hi Martin,

We have about 8-9 inputs running. Our playout server software adds inputs and remove them after they have played. We use about 40 different clips now and the all come by several times before the crash occurs. It is not the same clip the crash occurs on.

The system is a clean Windows 8.1 install without any codecs added. But, we did install the AAC encoder because we need to stream to an Android App as well.

Input normally existing:
1. Colour: black
2. Channel logo: PNG file
3. A couple of XAML files for titles (4x)
4. 2 - 3 MP4 files (one that needs to be removed, one that's playing right now, one that is the next clip)

I hope this helps a bit...

I added one file and the following are reported:
- Audio Renderer
- Video Mixing Renderer 9
- Audio Processor
- Microsoft DTV-DVD Video Decoder
- Microsoft DTV-DVD Audio Decoder
and the path to the clip

Hi Martin,

The playout solutions is a client/server one. So you would need to setup a server and a client. Could be very timeconsuming since we don't have a manual ready yet.

However, we could give you access to the server here if that is something you would like to.
You need a VPN to our network, after that you can use a remote desktop connection.

Some more information that could perhaps we of interest:
1. We test with all shorter clips. Meaning that in a couple of days testing a lot of clips are loaded and removed through the API. Including the overlays shown.
2. While vMix is still in crash and waiting for a user to acknowledge closing down, the webserver is still active and accepting commands. We know this because in case of error our playout will send us a txt message.

If you would like access to our server, could you please pm me?

Hi Gerard,

Thanks for the info, that will give me something to stress test over the next few days and see what happens.

Regards,

Martin
vMix

I don't have the exact URL giving the internal server error. For now I tried this one:
http://127.0.0.1:8088/API?Function=SetText&Input=1ba9f30d-fc9b-4c3f-90e3-7a3be8841d98&selectedindex=8&value=

Giving a neat error: exceeds limits (I guess that's an okay message, but not the internal server error).
It could be that we send a DBNull (value), but how that would work out in an URL is a mystery to me.... :-)