Thanks :) I'm glad you find use in them. Mostly r/showerthoughts, sometimes actual need in the moment when musicmaking. I love that I can just make something in Max and use it in Live right away. Bonus benefit to share with y'all. :)
Awesome thanks. I have the V2 bluhand working, but not the 'non-frozen' one (it only has 2 dropdown selections "music.local" & "iPad.local", but doesn't detect my Mac or other specific ios devices). I prefer to just connect it to OSCRouter app & farm-it-out, make bluhand 128. I'm wondering if maybe I don't have some (.json .js files? folders? etc) in the right places (if I'd need to that for 'editing')🤔 But this is amazing! Can't wait to work out a Knobbler routine.
I got it working :) Can I ask, is it 'overload' to just have the max osc addresses to be available up to 128? Because, for instance, using your first version, I made several extended TouchOSC Layout arrangements, with parameters split up into different object-amounts-per pager tab.. using all 128 for bluhand & 64 for knobbler. (Unfortunately I forget how I did that now though😕, using the non-frozen, .js files etc...I'm less savvy with M4L than TouchOSC). Having only 16 osc addresses per function (unless I find a workaround), I haven't been able to have 2 networked TouchOSC devices (like each showing different banks etc). I'd honestly want 128 of every function lol (just to know I had the addresses available for a .tosc layout) Other req: presets for knobbler 😍 How cool to have a 'collection' of our own collections :) Anyway, thank you Zack!
@@mthomas1091 Hey, your're definitely Knobbler's power user :) To get more slots for Knobbler sliders, you can duplicate the [bpatcher]s to get as many as you like there. Just make sure to update the 'args' property with an appropriate ID number. For Bluhand to have more than 16 params per page, you will need to change a couple of things. The `bluhand` patcher divides the number of parameters by 16 to get the number of pages/banks, so that "16" would need to change to what you'd like. The [poly~ finger 16] would need to change to reflect the new number (e.g. [poly~ finger 32]) and then inside of the finger.maxpat, there is an object that multiplies the bank number by 16 and adds the slider index to get the parameter index. That 16 would also need to be updated. I don't think you could have multiple TouchOSC interfaces to Bluhand on different pages though, since bank changes result in all sliders in the interface being updated. You could perhaps run multiple Knobblers, but you would need to change the receive port in the Knobbler device to something unique for each one. Happy to dig in more thru email! zack@steinkamp.us
Heya @claudiongleur -- I kind of suspect not. From Ableon's page here: help.ableton.com/hc/en-us/articles/8506527153308-Push-standalone-Max-for-Live-Device-Compatibility they mention: Connection Kit OSC Send Does not work. The OSC Send device in the Connection Kit uses the [udpsend] object in Max, and I suspect this is what is not supported on the Push3. Knobbler uses the same device to communicate with TouchOSC, and so I don't think it will work. But give it a try if you have Push3 and report back! I'll include the results in the README file with the project.
how are you storing mapped parameters in the m4l device? i was making a similar jsui device but without the tosc part for use with windows touch screens and just couldn't get the parameters to save after reopening a set. really cool device though
Hey @godboat. - Thanks for the Q. If you open the device for editing, then right-click one of the [bpatcher] objects (they are the 32 black rectangles with some text ("- - -") in each one) and choose "Object ... Open original knobSlot-bpatcher.maxpat, you will see a [textedit] object with a comment next to it. When a Knobbler slot is assigned, the path of the parameter it's assigned to is written into the [textedit]. Since it has its "Parameter Visibility" set to "Stored Only", then whatever the value is gets stored as a param, which are saved with the Live set. When Live loads a set containing the knobbler, the param system puts the value back into the textedit, who then emits the path value out its left outlet, which can then trigger everything to get set up to listen to and control that param. If you want more details, feel free to email me at zack@steinkamp.us and I can send screenshots or answer deeper questions. 👍
I just deeply tested your tool. It works overall very well on my setup (Ableton 11, PC) and TouchOSC (iPad). However, on TouchOSC, I use BUTTON objects in TOGGLE PRESS mode. This allows me to activate or desactivate MIDI filters on Midi tracks. These filters let me play in live with my synths if the MIDI filter is on, the MIDI signal goes to the synth and vice versa. This way, I can layer my synths in live. With TOGGLE buttons on TouchOSC, it’s very easy to press and turn multiple tracks on or off simultaneously. But with FADERS, this is impossible. Could you add this functionality to your tool ? For example, you could have 8 buttons at the top and 8 faders at the bottom. That would be amazing and allow me to fully use your tool. Also, I found a small bug: when you change the name of a macro or the name of the track in real-time, it’s not reflected on TouchOSC. However, when you reopen the Live Set, it works and refreshes correctly. Thanks.
Hey @alexandrebout4762 thanks for checking it out and sending your ideas and bugs! I'll have a look at the rename bug. I also found a bug where the color doesn't change on Bluhand if you change the track color, so there must be a common element there. I'll think about the button thing. One thing you could do in the short term, assuming your TouchOSC buttons are sending MIDI, is to add another tab to the Knobbler TouchOSC template for your buttons, or even modify the Bluhand tab to add your buttons. You could share that with me so I could see what you had in mind. Thanks again!
Fantastic tool ! exactly what I was searching since long time. will test it very deeply and go back to you for suggestions or bugs. TIA .
all your devices are incredible! you just have so many ideas, damn. where's all that inspiration for tools coming from? haha
Thanks :) I'm glad you find use in them. Mostly r/showerthoughts, sometimes actual need in the moment when musicmaking. I love that I can just make something in Max and use it in Live right away. Bonus benefit to share with y'all. :)
This is wonderful! Love it :)
Yeay 🎉. Can I ask, is this also working with Live 12.1 ?
Yes indeed! Using it with 12.1 now.
Awesome thanks. I have the V2 bluhand working, but not the 'non-frozen' one (it only has 2 dropdown selections "music.local" & "iPad.local", but doesn't detect my Mac or other specific ios devices). I prefer to just connect it to OSCRouter app & farm-it-out, make bluhand 128.
I'm wondering if maybe I don't have some (.json .js files? folders? etc) in the right places (if I'd need to that for 'editing')🤔
But this is amazing! Can't wait to work out a Knobbler routine.
I got it working :) Can I ask, is it 'overload' to just have the max osc addresses to be available up to 128? Because, for instance, using your first version, I made several extended TouchOSC Layout arrangements, with parameters split up into different object-amounts-per pager tab.. using all 128 for bluhand & 64 for knobbler. (Unfortunately I forget how I did that now though😕, using the non-frozen, .js files etc...I'm less savvy with M4L than TouchOSC). Having only 16 osc addresses per function (unless I find a workaround), I haven't been able to have 2 networked TouchOSC devices (like each showing different banks etc).
I'd honestly want 128 of every function lol (just to know I had the addresses available for a .tosc layout)
Other req: presets for knobbler 😍 How cool to have a 'collection' of our own collections :)
Anyway, thank you Zack!
@@mthomas1091 Hey, your're definitely Knobbler's power user :) To get more slots for Knobbler sliders, you can duplicate the [bpatcher]s to get as many as you like there. Just make sure to update the 'args' property with an appropriate ID number.
For Bluhand to have more than 16 params per page, you will need to change a couple of things. The `bluhand` patcher divides the number of parameters by 16 to get the number of pages/banks, so that "16" would need to change to what you'd like. The [poly~ finger 16] would need to change to reflect the new number (e.g. [poly~ finger 32]) and then inside of the finger.maxpat, there is an object that multiplies the bank number by 16 and adds the slider index to get the parameter index. That 16 would also need to be updated.
I don't think you could have multiple TouchOSC interfaces to Bluhand on different pages though, since bank changes result in all sliders in the interface being updated.
You could perhaps run multiple Knobblers, but you would need to change the receive port in the Knobbler device to something unique for each one.
Happy to dig in more thru email! zack@steinkamp.us
@@mthomas1091 Also, can you explain more what you mean by presets?
Cool
Will this work with Push 3SA?
Heya @claudiongleur -- I kind of suspect not. From Ableon's page here: help.ableton.com/hc/en-us/articles/8506527153308-Push-standalone-Max-for-Live-Device-Compatibility they mention:
Connection Kit OSC Send Does not work.
The OSC Send device in the Connection Kit uses the [udpsend] object in Max, and I suspect this is what is not supported on the Push3. Knobbler uses the same device to communicate with TouchOSC, and so I don't think it will work. But give it a try if you have Push3 and report back! I'll include the results in the README file with the project.
how are you storing mapped parameters in the m4l device? i was making a similar jsui device but without the tosc part for use with windows touch screens and just couldn't get the parameters to save after reopening a set. really cool device though
Hey @godboat. - Thanks for the Q. If you open the device for editing, then right-click one of the [bpatcher] objects (they are the 32 black rectangles with some text ("- - -") in each one) and choose "Object ... Open original knobSlot-bpatcher.maxpat, you will see a [textedit] object with a comment next to it. When a Knobbler slot is assigned, the path of the parameter it's assigned to is written into the [textedit]. Since it has its "Parameter Visibility" set to "Stored Only", then whatever the value is gets stored as a param, which are saved with the Live set. When Live loads a set containing the knobbler, the param system puts the value back into the textedit, who then emits the path value out its left outlet, which can then trigger everything to get set up to listen to and control that param. If you want more details, feel free to email me at zack@steinkamp.us and I can send screenshots or answer deeper questions. 👍
@@zsteinkamp wow! thank you so much. that's much simpler that what i was trying to do with the live mapping dicts and javascript >
I just deeply tested your tool. It works overall very well on my setup (Ableton 11, PC) and TouchOSC (iPad).
However, on TouchOSC, I use BUTTON objects in TOGGLE PRESS mode. This allows me to activate or desactivate MIDI filters on Midi tracks. These filters let me play in live with my synths
if the MIDI filter is on, the MIDI signal goes to the synth and vice versa. This way, I can layer my synths in live. With TOGGLE buttons on TouchOSC, it’s very easy to press and turn multiple tracks on or off simultaneously. But with FADERS, this is impossible. Could you add this functionality to your tool ? For example, you could have 8 buttons at the top and 8 faders at the bottom. That would be amazing and allow me to fully use your tool. Also, I found a small bug: when you change the name of a macro or the name of the track in real-time, it’s not reflected on TouchOSC. However, when you reopen the Live Set, it works and refreshes correctly. Thanks.
Hey @alexandrebout4762 thanks for checking it out and sending your ideas and bugs! I'll have a look at the rename bug. I also found a bug where the color doesn't change on Bluhand if you change the track color, so there must be a common element there.
I'll think about the button thing. One thing you could do in the short term, assuming your TouchOSC buttons are sending MIDI, is to add another tab to the Knobbler TouchOSC template for your buttons, or even modify the Bluhand tab to add your buttons. You could share that with me so I could see what you had in mind.
Thanks again!
@@zsteinkamp great idea, i'll do that ASAP . thank's .
is the manual rename feature still on this version?
Yes indeed it is! I forgot to put it in the doc. Thanks for the reminder :)
@@zsteinkamp got it. awesome work as always!