I thought I'd share a very short experiment with the new control busses and midi input in tidal 1.7 - this immediately reactive control is something that I really missed when I first started getting into tidal, and I didn't have the patience to plumb the setup externally.
I'm twiddling knobs on a novation launchkey mini, mapped to djf, squiz, room and size respectively
I'm going to assume you mean a typing keyboard (as opposed to an instrument keyboard)? it sounds super cool! would love to see a worklog once you get going
haha yeah you're right! should have specified
yeah I'll definitely post something when I get to it exam period is almost over so I'll have some free time coming up soon
Aweesome! yeah, I always missed that continuos control of params, and now that I can do it, I realized that using the 'faders' on my launchpad mini aren't as smooth as I thought (you can really listen the steps!!)
Hi @cleary could you explain how you assign Tidal parameters to your midi knobs controller in your example? Syntax seems different depending on parameter ?
Thanks.
It says listen to midi CC #21, regard the incoming values as a Float (cF), and superdirt does some magic in the background to convert the 0-127 value range to be read as 0-1 instead, and set the initial value at 0.5
This is the shorthand version - listen to CC #23, no default initial value (the same 0-1 range magic is in place):
# roombus 3 ("^23")
This is more complicated because squiz doesn't operate in a 0-1 range - in fact 0-1 squiz is not applied at all, it doesn't kick in until values > 1
# squizbus 2 (7 * "^22" + 1)
I actually can't remember why the maths employed here was chosen... it could do with some validation, but the rationale is based on squiz being ranged in a non-standard way
Thanks a lot @cleary that's clear now.
Second question, I don't understand how tidal maps this CC with rigth midi controller.
I added that in Supercollider to declare my komplete keyboard in order using its knobs:
MIDIClient.init;