I've noticed in the last couple versions the "last.vmix" preset isn't always representative of the actual last state or last saved preset. I have an automated vMix startup trigger that opens the last.vmix preset at a preset time to ensure it's up and running ahead of an event with what I had last worked on for that event. It seemed to be pretty reliable until a few months ago. When I first started noticing this, I thought it was me not making sure I had saved the last state of the preset I was working on or may not have made sure the right preset was the last opened and saved. But, when I started seeing things I know had changed and I had no other recently used presets (and could open the last saved preset and see was correct), I suspected something was up with the "last.vmix" preset.

We use the last preset functionality as part of our automation processes that make sure everything is on and starts streaming and recording on time. This is at my church, where the I'm really the only person familiar with vMix or any of the setup. So, I've setup Companion triggers and vMix scripts to handle a lot of the startup and shutdown steps. Obviously, using the last preset function has risks, but it generally works for our needs.

I'm happy to put in a feature request to ask for a specific change in how the last preset logic works. But, I thought I'd try to find out if there's an actual bug or something I can do differently to make it work better for my needs.


The other save state issue, is the panel that has the Audio Mixer and List tabs doesn't always automatically show itself when I re-open a preset. I haven't found anything consistent about this, yet. It's mostly an annoyance, since during an event I'm typically using vMPB and Companion to control vMix. Should I just submit a bug report on this one?


vMix 29.0.0.44
Windows 10 Pro