I have a Novation LaunchControl (just one row of buttons with LEDs) and want to use the activators. When I set it up for LEDs to go green when in preview it works fine, when I set it up for LEDs to go red when in program it also works fine. But not when both are configured at the same time.
I understand that there's a little conflict because what happens if one input is in preview and also program? That leads to my next question, why is it possible to have the same input in pre and pgm and what's the sense of this? Blocking this would perhaps allow the use of green for pre and red for pgm with controllers having just one row of buttons/LEDs like the LaunchControl.

If using it like this a transition to pgm would be useful.

I just preview overlays without the background input but I understand that there are situations where someone perhaps really need this. Maybe it could be an option in settings?

Multiple activators per button is a challenge because who determines what the priority is for each?
If both preview and program are set to different colours which takes preference? In that scenario one would assume program has priority
but for other types of activator combinations it isn't always obvious.

For example, say we decide program has priority, then what happens if an input in program is selected later into preview as well?
Should it search through all the activators every time, find one that is already in output for the same midi led and therefore not do anything?

All this has the potential to introduce unexpected bugs and possibly CPU increases vs a simple one activator per button policy, so
how important is something like this?

Regards,

Martin
vMix

For me it is not that important. The buttons light up now which is a nice improvement.
I do not look that much at my panel anyway, so for me it was just an extra feature when looking trough the possibilities.
But I can imagine this being more important for ovinas, as that panel has one row.

Maybe a column that adds a number of preference would get this out of the way. So for program it can be set to 1 and preview to 2, shifting the job deciding what's best from you to the user, while remaining at one activator working per button at the same time. For my example I would set program to 2 and playing to 1 to get it to work.
Because vmix supports that much different controllers, I imagine this will be different for each one.

But I very much agree that stability goes before versatility, I would not like to have an activator crash my production indeed!

Seem to be getting a random System Freeze with latest Vmix 18 using XML Datasources
I have about 6 XML Datasources and after the recent update, I get a freeze where my Mouse and Keyboard are unresponsive
Only method to resolve was to restart manually to power button.

If I don't have any Datasources running system runs fine. Data works great before the random freeze that can occur after about 15 - 30mins.
Just wondering if a tick box for a data that only needs to be read once when it first loads with a refresh button. But for live data it
can check every 1000 secs as it does now. May help reduce system use. CPU and Memory has been good with 6 xml datasources running in the background.
Data is pulled from cloud CMS remotely via http://.....xml

Remember to add a activator rule of the button with the type Default, setting the LED of the button to off. This will turn off the LED when no other activator rules is matched in your Activators policy.

Is there any chance of making vMix remember where the list window was (when un-docked) ... everything else restores to its correct positions/monitors when I launch my vmix with my profile, except the list window.

Many thanks!

If the whole system is freezing this indicates a hardware issue of some kind, perhaps triggered
by the data sources. My guess is maybe there is an issue with the network card, though it does seem odd.

The new List functionality works extremely well. Thanks. The way to play individual clips is not intuitive atm. Could a help item be added to show the sequence to use. Un-select AUTO-NEXT; highlight required list item; Select PLAY OUT.

James,

Datasources does not have a timeout but each source runs independently in its own thread timer.
This means it will not interfere with anything else and won't queue up in cases where updates are taking along time.

It's actually very basic code, so if the whole system freezes, data sources is no more likely to cause this then say a browser
timing out visiting a web site is.

As for audio, if you heard the audio, how did you determine there was no master audio?
You can check the logs in Documents\vMixStorage\Logs to see if any audio mixer errors have been noted.

Regards,

Martin
vMix