Beside the current cue points, we could have ‘marker points’, or ‘points of interest’ or whatever you would name it. It is a point in the track with a name. It could be a simple label without any action like ‘Start vocal‘, ‘Chorus’ etc. That could be the start, then it could be later extended to add a trigger that gets fired when the marker is ‘hit‘. These actions could be extended over time and could be something like an action type and a value: ‘Beat jump + 16 beats‘, ‘Start video loop ‘my nice loop‘‘, “Trigger Soundswitch Scene ‘My nice scene‘“, ‘Loop 16 beats‘ etc etc. The actions types are fixed types defined by Algoriddim.
From my perspective this could solve quite a lot of items in the suggestions. It could be started simple and be extended over time.
Thanks for the suggestion @EwoutdeBoer. Interesting idea. I’ll share this with our devs for consideration. In the meantime, please use the blue Vote button at the top left of this page so we can gauge user demand for this feature. Thanks!
I would like to ‘separate these track markers‘ from hotcue’s. The reason is that my controller only has 8 pads and thus only 8 hot cues. When you add thinks like ‘Chorus‘ or ‘Vocal start‘ I clutter up my hot cues and for most tracks I would never want to use that hot cue. So I prefer labels only. These labels could later be ‘transformed‘ to triggers, to trigger more than just hot cues
@Slak_Jaw Good addition to my post. I was already using the second bank . The proposal for the trigger point has far more possibilities than ‘using cue points for labelling‘.
Great idea. However I would go straight to fire a trigger at the ‘track marker’. To stay within industry standards this could be an OSC or MIDI message
. The proposal for the trigger point has far more possibilities than ‘using cue points for labelling‘.
