New “loop forever” replay mode
The new Replays feature is cool, but it is missing a “loop forever” mode. I want to hit a trigger (e.g. latched) and have the sequence play forever until the trigger is hit again. At present a replay plays once and stops and you have to trigger it again to get it to repeat, even when trigger latching is on.
I assume a third replay mode of “loop forever while triggered” is wanted as a trigger mode.
The usecase is an “idle” state for the puppet. You can record an idle state (fidgeting etc) and and some other states (“frustrated”, “angry”, “tired”, “bored” etc) then when live streaming you just hit a key to change the state and the puppet keeps acting in that way until the state changes again. The replay might be like 20+ seconds long so it does not feel too repetitive.
tiko piet commented
I want this feature so bad....
david winn commented
We're still waiting for this Adobe. It can't be that hard to add this feature. Please.
Katherine Middleton commented
is there any movement on this? literally need it right now
Matthew Taylor commented
Yes please! This would be immensely helpful!
seth perciano commented
Just going to give this a *BUMP* Currently using performer mode preparing triggers for a Relaunch on my twitch channel with a puppet Made by GrifnMore. Until I can jump into a subscription I sadly cannot add a behavior. I am interested in getting a sub for Ch however so we will see.
Dan Tull commented
Where by "definitely on our list for the future", I mean something we agree would be cool and want to do, not that we have a specific plan on when or any implied promises about when.
I feel like a lawyer saying that, but I didn't want to set the wrong expectations, just express solidarity for the idea.
Dan Tull commented
Yes, replays are just begging for features along these lines (including a way to control which part repeats so you can have a start, a looped part, and a finish -- like a wave gesture that keeps waving until you let go). This is definitely on our list for the future. Right now the (cumbersome) workaround is to export the parts being replayed and use them to do the same thing with nested Cycle layers behaviors.