Here's the use case:

- User presses one button which creates two clips (one from Angle 1 for X seconds, and then a second clip from Angle 2 for a shorter duration)
- User presses another button to select & play those two clips back to back

However, I don't think the second part is... possible, with current vMix 27 shortcut functions. ReplaySelectLastEvent will indeed select the last event, but ReplaySelectPreviousEvent does not ADD to the selection: instead, it single-selects that previous event alone. The only multi-select shortcut function is ReplaySelectAllEvents as far as I can tell. And using that for my use case would require me to move all other clips from the current bin every single time I make clips which is... not a great solution.

The only other possible way to even technically accomplish this would be ReplayPlayEventsByID, but as I don't have a way of obtaining those IDs in external software (I'm working in Companion), I don't think that's possible either for my use case.

I'm posting here just to make sure I am not missing something in my Shortcut Function Reference adventures.

Yeah, that's... kind of an insane amount of overhead for what amounts to a rather simple Mouse & Keyboard use case. I would really love to sit down with vMix development folks and help them understand how replay actually gets used by different projects/subject matters. The extensibility of vMix in general allows it to be adapted to punch WAY above its weight class against other solutions. And that just doesn't quite hold true for the replay portion specifically (which I think I can say after building & using Companion configs on ~100 shows with it).

I'm probably going to go the route of "move everything to another bin when clipping the new goal, and then play out all from current bin after making the two new clips"