02-16-2021, 05:01 PM
(This post was last modified: 02-16-2021, 05:08 PM by mvdirty.
Edit Reason: T43 crappy photo addendum. :)
)
(02-16-2021, 04:52 PM)Bleep bleep Wrote: Its only a issue for the first step of the transposition pattern now wich is more acceptable, many thanks!
Yeah, for those use cases where self-patching is required (I actually have more going on in mine than just the T43 with one input into it, and so would need to continue self-patching even if NerdSEQ gained more transpose options) this physical loopback approach is always going to make for a bit of work related to timing.
I’ve been halfway tempted to do an experiment where I get one of my “control” tracks to intentionally run a tick (or few) ahead of everything else. There’d be some issues around track resync to the main clock but I’m tempted to play with the idea anyway since those might not prove to be too large or frequent of a problem and it could simplify the patterns driving that transpose input.
If I get around to trying that and have anything interesting to report I’ll try to reply back here with it. (If it ends up working well then oddly enough I’d probably end up not using any optional instant-transpose Thomas might theoretically add. For now: who knows.)
PS: The T43 photo on the vpme web site makes the module look like crap. The real module is actually quite nicely produced.