Hi Patrick,

This is actually fixing a bug in 23, when a new event is created the timeline will switch to the frames of the mark in point when the event is completed.
As it is selected in the timeline. This naturally needs to stop playing any existing events.

If you want different behaviour you will need to use the A and B separately, as replay was never designed to edit events while playing back others on the same channel.

Regards,

Martin
vMix

Hi Martin

Thank you for your answer.

In my opinion this is a big step back in the main functionality of the replay system. I'm trying to argue this.

The most used function inside the irp is creating events. Operators not only create events if something is happening, they also create events if they think something could happen or if they are unsure what was happen. You're focused on the monitors and you have to be always ready to create an event as fast as possible, also during an already playing event. You never know how fast and what the director calls next.

With the 24 bugix regarding the "ReplayMarkInOutLive" shortcut, the 24 workflow doesn't reflect the above explanation: The operator has always to think first: Am I playing an event currently? Am I in the right channel mode? Only after this the operator can create an event. And this is not only restricted to A/B-Synced mode. Also in A and B channel, this decision has always to be felt first.

That's why I think the creation of events should never have an impact on a already playing events. And this task should be and stay as easy as possible.

And to be clear: More editing like trimming or add text tags is not necessary. In this case I agree that the operator has to switch the channel to A or B.

But I'm not only complaining :-), I also have an idea.

Why not let the shortcut "ReplayMarkInOutLive" only create the event, so no additional selection of the event and no switching to the first frame.
For selection and switching to first frame, the shortcut "ReplaySelectLastEvent" can be used.

Or better: Calling the shortcut "ReplayMarkInOutLive" checks first if an event is currently playing in the channel.
If yes, it only creates the event. If not, it creates and select the events.


Thanks for checking my idea (and hopefully to agree that the basic functions should be as easy as possible for the operators).

Best regards,
Patrick

you are totaly right, reading this would have helped :D

This error would appear to indicate your installation is corrupt and missing files.
Reinstall it after making sure the computer has been freshly started, all windows updates are installed and all programs are closed.

Stinger1 is a transition function, so you need to set the input there to the input you will be transitioning to, not the stinger input.

Regarding "Added right click menu to vMix Calls under Advanced to show blank frame when call disconnects"

This is a really nice improvement, but a few things might need clarification and perhaps fixing (no intention here for a feature request).

1. Feature not documented in https://www.vmix.com/hel...ex.htm?vMixCallMenu.html

2. Unclear what "blank frame" means. What I get is a black frame. Means that if that call is used on a Layer it will be black instead of transparent (which would be nicer, at least in our productions).

3. It takes a few seconds after the caller disconnects before the "blank frame" appears. Guess that has to do with necessary waiting time to allow for temporary dropouts.

4. If the producer/director disconnects the call using right-click Disconnect, that never results in a blank frame (v24.0.0.50). The problem here is that we cannot quickly do a manual remove of a frozen frame (before the blank frame is automatically showed by vMix.

Thanks,

/richard

Possible bug: Using v24.0.0.50

Audio from NDI (teams) stopped working shortly after the stream started. Restarted the system, reconnect NDI streams into vmix, the audio was fine. Started steaming and again the NDI audio stopped working. Rolled back to 24.0.0.46 and the issue went away. It may be related to NDI updates added in 24.0.0.47 but have not had time to test.

I use vMix Social on Overlay 3, with no problems. I have stuff on overlays 1 and 2, and they are not affected.

I'm using v24.0.50.

Hardware encoding/decoding is a system requirement for SRT in vMix, as per the documentation:

https://www.vmix.com/help24/SRT.html

In the bigger picture the particular issue I reported is perhaps not very important. Just wanted to tell if it perhaps was worth doing something about. If nothing else making it known to other users.

I do understand that in most situations hardware is needed, but I really do not want that enforced in vMix. In the curent use case I have I am only sending and receiving a low res/rate powerpoint for feedback to remote callers doing presentations. (webRTC is not an option).

Sorry if I misunderstood. Before posting I read "when available" at https://www.vmix.com/help24/SRTInput.html where it says

"Where supported" is somewhat confusing if hardware is a requirement, as outlined at https://www.vmix.com/help24/index.htm?SRT.htm I previously only read to