Millumin forum4/2/2023 ![]() I know this can rapidly become complicated if you have multiple timelines running in parallel and you want to track all the resulting states of previous events in concurrent timelines. ![]() I think a forward key with similar behaviors allowing to skip forward without timings, curves etc. Immediately recall finale state of previous cue.So if currently running Cue4 and I hit back arrow I would expect for the final state of Cue3 to be recalled and Cue4 to immediately begin playing again. On the other hand if score is already playing when I hit the back arrow I would expect it to simply jump back to the beginning of the current Cue and continue playing from there. ![]() Wait for user input before triggering next cue.Immediately recall final state of previous cue (without processing timings, curves etc).In my case, the ideal behavior if I’m currently in Cue4 (meaning that the various events or resulting state triggered by Cue4 are already in place) and I hit the back arrow while Score is in its stopped state would be to bring me back to the final state of Cue3 and wait for me to hit Go again. I guess the ideal behavior for the back key depends on the specific case but yes, you got the gist of it. Keep up the nice work, congrats for the forum and thanks! I’m wondering if I’m approaching Score with the wrong mindset and if there is another simpler way to achieve what I want? I first have to scroll back, click someplace before where I want to start, press space bar, wait for Score to stop on the next trigger and then press GO… This also does not allow me to easily go backwards. This works fine for only a few cues but it becomes quite tedious to program a show containing hundreds of cues with multiple edits, cutting/pasting/moving/reordering etc. I start playback in Score which halts when it encounters a trigger and waits there until the address value I specified for the trigger is != 0 (initiated by pressing the Go button in TouchOSC in this case). I’ve made a first attempt at this by using OSC triggers and configuring a TouchOSC interface with a GO button. where the user can advance through all the cues by tapping the space bar or using arrow keys. Similar to what can be found in software such as Dataton Watchout, Millumin etc. Given this context I think it could be quite useful to implement a simple keyboard or OSC driven cue advance mechanism to Score. going back and forth during rehearsals but generally going forward is better Cueing happen asynchronously meaning that the timing between cues varies from one show to another depending on how long the performers take to do their thing so an operator is usually waiting to trigger the cue manually. Cue 1 invariably leads into Cue 2 which in turn leads to Cue 3 etc. For such productions the timeline is usually pretty linear aka. ![]() I’m slowly discovering Score which I would like to use to drive a live production based on TouchDesigner through OSC. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |