Feedbacks on - Speed Percentage - No of saved replays - No of remaining replays

[Fred-DTV]

Hi exeldro,

Thanks for this amazing plugin which helped me to create an amazing skatecontest here which looks like it has way more budget than it actually has 😅

We are using companion to control obs and the replays and I want to improve the workflow this year, that'S why I would like to show some info on my streamdeck about the replays:

1. The speed percentage
   We are currently doing slo-mo's through the half-speed shortcut, but I would like to be able to manually ramp it down and up. For this to work the operator would need to knoiw which percentage the video is at, at the moment.
   I am currently trying to add more hotkeys to your code for this (+/-5% to make it work with rotary knobs) but I don't understand how to add feedback variables...

2. Number of saved replays
   This would be another great feedback variable especially because there is a limit to how many replays your plugin can save. In the hectic of a live situation the operator sometimes doesn't count right and looses replays.
   (currently I am using a workaround for this but just counting button presses, which works fine, sothis is not super important)

3. Number of remaining replays, when playing
   This however would be a really important feedback variable, because this can tell the director when the replay is about to end.
   This would only need to be a number variable, as with the combination of 2. one can have an overview already.

Thanks a lot again for putting so much work into this!

[exeldro]

At the moment information like this can be set to a text source in obs using the Text Source and Text Format setting in the Replay Source. Maybe there is a way for you to display that text source on streamdeck buttons using companion?

[Fred-DTV]

Ahhh yes I didn't think of the %variables% anymore, as I deleted them from my source back when I implemented it for the first time.
They have everything I need to get them into companion, but to be able to use them properly I would need each stat in its own text source.

Would that be possible somehow?

(For now I will try to find a solution with a custom expression that splits the one big text-variable into multiple single ones in companion)