techtitch
Really not urgent, I'm hacking away, but maybe one for the backlog if we ever give you 5 minutes' peace.
I have mapped a button on my Seventy Two to `action_deck 1 ? swap_decks 1 3 : swap_decks 2 4`, to mimick the S11 invention. It absolutely rocks!
When I press it twice, eg, swap it to deck 3 then swap back again to 1, the needle drop zones on the sides of the 72 don't re-render and so are blank. (Oddly the cue points do.)
I have mapped a button on my Seventy Two to `action_deck 1 ? swap_decks 1 3 : swap_decks 2 4`, to mimick the S11 invention. It absolutely rocks!
When I press it twice, eg, swap it to deck 3 then swap back again to 1, the needle drop zones on the sides of the 72 don't re-render and so are blank. (Oddly the cue points do.)
Posté Wed 28 Oct 20 @ 1:10 pm
PhantomDeejay
The waveform data are sent once per track load and then firmware takes care of the rest.
Since swaping to deck 3 and then back to deck 1 does not reload the track, waveform data are not sent again.
We'll see if we can hack it somehow.
Since swaping to deck 3 and then back to deck 1 does not reload the track, waveform data are not sent again.
We'll see if we can hack it somehow.
Posté Wed 28 Oct 20 @ 8:13 pm
techtitch
Wow, how on earth did you reverse engineer that?! Really low priority, especially if this is the sort of thing that might be affected by a future firmware update.
Posté Thu 29 Oct 20 @ 10:10 am