Love the borders feature in 24! One note. The thickness of the border seems to be effected if that layer is zoomed. So it's a complete guess to get consistent borders with varying zoomed layers. Ideally a thickness of 10 shouldn't change with the zooming of the input. If that makes sense?

If you open an input and go to Positions (where some custom values have been entered for Zoom, Pan, etc. then close it and then do the same on another input, the values shown for some of the custom values will incorrect (will be from the previous values of the other input). This happens when going from layer to layer on the same input I believe.

It may only happen if you change a value (then go to another layer, it will show the value you updated where the value of the new layer is not correct)...I'll have to pay closer attention. It is very common though when editing layer positions.

If you can't replicate, let me know and I'll screengrab it.

I tried to recreate this and the only minor bug I found is with the Zoom value if a layer's Zoom X and Zoom Y are different.
Set Layer 1 Zoom X to 0.5 and Zoom Y to 1.5.
Set Layer 2 Zoom to some random value.
Go back to Layer 1 and the Zoom slider is disabled and centred but the value is retained from Layer 2
The value for Zoom is also enabled and can be edited but doesn't affect anything.
None of this causes any issue but it would be clearer if the zoom value was disabled and set to something like a hypen or blank.


Seems to be working as normal here.

Bug:

When a replay being event is played while you're working inside the attached replay window and you want to go to the audio mixer tab, the replay event starts to play again at the beginning.

I had this error twice on a live production today.

We are not able to replicate this behavior, sounds like something might have changed in your setup.
You can drop us an email and send a support report in vMix if you would like us to take a further look.

Another slight error:

I am using one Vmix machine to playout graphics with alpha channel and send them to a hardware video mixer.

It's possible to fade-in those graphics and videos, but not possible to fade them out, when noting else is underneath the them.

It just makes a cut, when using the fade transition.

It would be great to also have fade out in this case.

Regarding the behaviour of global/local script management.

If a Setting already contains a global script named "Test", and a Preset containing the script "Test" is opened, you end up with two "Test" scripts.
My suggestion is that the user instead gets a warning, asking to keep or overwrite the global script. For keep, perhaps also ask if include it with a different name.

When Presets are opened, I would expect checkboxes not only for all the Inputs, but also for the scripts.

I noticed that Local scripts are differentiated in the Scripts editor by bold typeface. A differentiation is necessary, but I think it would be easier for the user to have each script marked with a "L" or "G". As it is now one has to know and remember that bold means local.

It is not possible to remove a Local script, it must first be made Global. Not sure why that is so.

I also noticed that the new functionality with Local scripts is not documented in the Help.


On a side note, related to the FR where this idea of Local scripts perhaps originated. There some of us would like to see the possibility to also Export/Import scripts.

vMix 24.0.0.42 beta released

https://cdn.vmix.com/download/vmix24preview.exe

* Included over 300 new title templates, including titles, social and stingers.
* Data Sources will no longer load on startup from previous session. They will load only when opening a preset.
This can be turned back on via Settings -> Options if needed
* SRT outputs will no longer start up automatically if used in previous session. They will start only when opening a preset.
This can be turned back on via Settings -> Options if needed
* Updated SRT library to latest 1.4.2 release
* SRT options in External menu now show hostname/port to help identify outputs. Outputs that have not yet been configured are now disabled in the list.
* Audio mixers were not hiding correctly when using category search feature
* Bad NDI sources can sometimes have too much audio leading to memory leak, vMix now puts an upper limit on how much audio it can receive.
* Improved performance when loading recent titles list where titles are on a no longer connected network share
* Hidden stinger transitions from Mix input since they are not supported
* Production Clock did not support fractions in hour offset, this has now been corrected.
* ReplayStopEvents was not showing channel dropdown
* API XML now includes gainDb value
* Vimeo API updated to support recent changes
* Fixed replay playback stopping when switching tabs (such as to audio mixer).
* Fixed number on audio mixers not allowing three digit numbers.
* Fixed Alerts showing FTB alert even after the option is disabled in Settings.

This update is expected to be the last beta fore final release. We have looked through the forum feedback and fixed all outstanding bugs we are aware of.
There were many other reports based on misunderstandings of how features are intended to work, so these have not been "fixed" as such.
If you still believe your report is valid, please submit again the bug here.

Regards,

Martin
vMix

I think this one is still valid, because it worms one way, but not the other way around.

Oh damn sorry... Didn't See this Post because I just saw your Post with the Version Update.

And yes, I totally understand that and Also thought that this is the problem.. But the weird thing is that it worked when transitioning in