User Details
| Username: |
sblakely |
| Website: |
None provided |
| Facebook: |
None provided |
| Twitter: |
None provided |
| Soundcloud: |
None provided |
| Account Status: |
enabled |
| Member since: |
Jan 17 2015 |
| About sblakely: |
|
| (report this profile) |
|
Devices by sblakely
Total Downloads: 174
Comments by sblakely
Comments
This website uses cookies.
Clicking “Accept” means you consent to your data being processed and you’ll let us use cookies and other technologies to process your personal information to personalize and enhance your experience.
Click “Close” to deny consent and continue with technically required cookies that are essential for the website to function.
So the use case is flexible set flow.
I have a group of tracks containing four or five control tracks.
With ClyphX, the clip name contains instructions - play this, adjust that etc.
By setting an option in ClyphX, only the unmuted track commands get actioned.
So for each Scene, I can have different outcomes based on which track is not muted - play next scene, loop this scene, jump to chorus, jump to bridge, hold on the solo until I am ready, jump to the end. Using an FCB-1010 footpedal mapped to the track mute buttons, I can rearrange the set elements as I perform.
From a programming perspective, it's a finite state machine with tracks in the exclusive group acting as the "state" variable.
I have another set of Python extensions to ClyphX that allow me to record on the fly into layered clips - like looping, but with the ability to undo and change tempo. That bit isn't working so well yet, but I'll revisit it soon.