I want to use Clyphx as a sequenced live looping tool, where xcues in arrangement view trigger action lists/snap actions to affect clips/device settings. It works really well, but there’s one issue; what to do if you make a mistake.
I’ve noticed that a company have sought to build this concept out as it’s own software, and the demand seems to be there for it as a tool. Check the link out below for more information: zenaud.io/
I think Clyphx can achieve much of same thing and more, but I have hit a wall with my workflow. I am looking for a way to create reference clips. Imagine ensuring you have a recorded version for every clip you’d be recording in real time, just as a backup in the event you stuff up your performance. This could then be mapped to an xcontrol and used only in the event you make a bad mistake. This would effectively delete and replace the specific clip with the reference clip. This is the way it is implemented in the previous mentioned software: youtu.be/zgmPAHuIrys I don’t think there’s a way to achieve something similar with the syntax already developed For Clyphx, but I was wondering whether anyone might have any ideas how to implement this as a custom user action? It seems to me that it would need a repository of reference clips, that are correctly inserted based on the arm status/playback position? I would love if it Stray were to take this on as an feature. I think you could capture a section of the live looping community with it, given the power and stability of Clyphx already.
Any assistance would be really appreciated, even if it’s that this isn’t really doable without significant dev.
You pose an interesting question as that is something that I considered as well after viewing the video.
One idea could be to have any tracks that might need to be replaced, prerecorded and disabled, running in parallel with the tracks that you're recording live. Then have a way to toggle between the two. Maybe a command, or command list, triggered via midi or clyphx, that would either activate said backup tracks and reroute all other commands/xclips to use the tracks that the backackups are on. You could in theory have an entire set of tracks running in parallel that could be toggled in case of an emergency.
After typing this out it sounds like it could get complicated, depending on how many backup tracks you'd have.
Post by rickywander on May 21, 2020 9:22:22 GMT -5
I would consider a LOADCLIP Action althought it creates a brand new track. Probably a User Action could do the task if it would be possible to load a clip into an existing track, instead of creating a brand new one.