Відео

I'll look at it. What do you have in mind when you imagine random, in terms of number of points, diversity of points, curves, etc?

ha! thanks for pattin' the back :) let me know how it works for you if you use it or ideas you've got to improve it. 🎉

hey thanks! i agree :) the controller is a Keith McMillen K-Board Pro 4. One thing I thought to include in the video but didn't was to use the Expression Control device to map the MPE features of the K-Board (such as Slide) to the global duration / amount in ScratchBacker. That's fun too!

Yeah boyeeeee! 🎧

Oh make sure you try version 4. Many many improvements. I should maybe take this video down? github.com/zsteinkamp/m4l-Knobbler4 ua-cam.com/video/1SvkGQ3_K8k/v-deo.htmlsi=hd5J0bwOHzW09HqE

Yeah go for it! :)

thanks :) Not 100% sure, but I'd guess perhaps you could code something in TouchOSC's scripting language to simulate the moving balls. It's possible to move the balls via OSC commands, but that would be slow and unreliable. XY pads are part of the normal TouchOSC kit. It would be possible to construct a layout of XY pads, with each axis of each pad mapped to a parameter. You would need some dedicated way to trigger the param-to-axis mapping though, since touching an XY is ambiguous about what axis you're interested in mapping. If you dig into this, let me know what you come up with! zack@steinkamp.us

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. :)

Rad advice, thank u! May I send some candidates your way for feedback?

Thanks! Any suggestions for future topics or ways to improve the video?

@@zsteinkamp a looper with Glitch/ambient built in fx?

Or a device randomizer :)

Mission accomplished! Thanks :) Any ideas for future topics?

​@@zsteinkamp Oh, don't ask me that or I'll make a list so gigantically huge that your eyes will bleed (; But seriously: I started with Max to make my own "Expression Control" device, one that offers more control over Velocity and Keytrack modulation and that is precise enough to be used during live playing (Expression Control seems to "miss" a lot of data). Also, I pretend to make it polyphonic, so it can really be called "Expressive". So that's what I want. However, I've learned a lot with your WavScope video, not only about how to iterate and idea and make it better, but also about navigation, usability and a bunch of other little droplets of information you threw in there. Like the fact that you can cmd+click and avoid a thousand switches between presentation and patching modes (; Meaning: Whatever you come up with I'll be happy because I vibe with your teaching style.

Aww thanks :) I do enjoy it. Ideas for the next one?

My pleasure! I only have Live 12 now, so could you try it in 11 and give it a shot? Easiest way is to download a .zip here: steinkamp.us/music-tools, extract it, and drag it into the set.

Agreed! Would love to hear what you can come up with it.

Cool idea. I'll look into adding a "time factor" knob, perhaps to go from 0.1x to 10x? Or did you have something else in mind?

@@zsteinkamp Nothing too particular in mind, but def under 200%, if not under ~110%. Seemed like it could be cool to have some echos come in a little early some a little late, or one or two a little late followed by speeding up rapidly.

@@peterlaar Ahh! Ok cool then. Now I get it. :) Makes perfect musical sense. I'll have a look.

@@peterlaar Want to give this a try? github.com/zsteinkamp/m4l-TapPanZeit/raw/refs/heads/main/frozen/TapPanZeit-v8.amxd

@@zsteinkamp Cool, will check it out! Played around a little with the previous version, super cool.

This is gonna be fun for modular jams

@@josealejandrogarciarojas1115 I'd love to hear the results!

Curious to hear what you come up with!

Hi @morizanova! It uses the newest version of TouchOSC.

Oh yeah! Have you used one? I'm curious how well they work in practice.

Something I'll think about. I have a Push2, so that handles those duties for me better than I'd want to code up for Max/TouchOSC. Or do you envision features that are different than Push?

@@zsteinkamp It would be nice to have everything in one app (TouchOSC) now I have to use another app to fire up clips. Thanks for another update, Knobbler4 is great!

@@zsteinkamp i just think with the intelligent mapping and hot cues to go through the session youre just a few features away from a full ableton control solution for ipad, and a lot of the other options are no longer being developed. food for thought!

@@screenwhirlpool Yes indeed! Something to ponder for sure. Perhaps it just starts with Play/Record/Stop buttons, then loop, punch in/out, tempo, ......... :D

Hey @pieterdesmijter420! Help me understand some details of what you're asking. If you have a MIDI knob assigned to a parameter, turning the hardware knob would update the slider/value on the Bluhand tab if that device was selected, or if you had mapped the parameter to a Knobbler knob on the screen, then it would also update. Is that what you had in mind? It's bi-directional. If the parameter value in Live is updated (no matter how -- MIDI control, mouse control of on-screen knob in Live, automation in Live, etc), then the new value is sent to the iPad.

@@zsteinkampmy bad sorry. I was wondering of it would be possible to run the software on an arduino or any other hardware and have a display above each physical knob to show parameter name etc. That would be really awesome 😀

@@pieterdesmijter420 Ahh yes ... I have thought about dedicated hardware as well. Since it uses the OSC protocol and it is documented in the GitHub repo [1], it is possible for anyone to make it. My plan is to first develop a dedicated iOS app, eliminating TouchOSC, then perhaps the next phase is a piece of hardware. We shall see! [1] github.com/zsteinkamp/m4l-Knobbler4/blob/main/OSC-API.md

@@zsteinkamp hmm I might have a go with one knob to see if I can get it to work 😀

@@pieterdesmijter420 Happy to hear about what you do! zack@steinkamp.us is my email.

I don't have a Push3 so I'm not sure, but the little bit of looking that I did about it makes me pessimistic about support at this time. Give it a try if you have one and let me know. The issue that I suspect is that Push3 does not yet support the [udpsend] and [udpreceive] objects in Max, which Knobbler relies on for the OSC communication with the iPad. Confirumation from a Push3 owner would be good though!

Yes indeed! That was one of the primary design goals. Switching projects should be 100% seamless. Let me know how it works for you once you try it.

@@zsteinkamp I just did a reopen so far and it works.. Too tranced out to leave this piece to try 🙂. What is the process for replacing existing mappings in the same project? Or adding another tab of controls (user configured preferably). which is a...

request. I did open two projects and they were opened correctly mapped, but it seems I had to move a fader or two to handshake with Live to actually control my devices.

@@SwamiLove Oh interesting. I wonder if you used a USB connection if that initial lag would be different. Home wifi networks can be unpredictable. github.com/zsteinkamp/m4l-Knobbler4/blob/main/USB.md

@@SwamiLove There are two tabs now. What sort of controls did you have in mind? You can play with the .tosc layout and change the sliders to dials or something, or move things around. As long as the names, events, and scripts are not changed it will work.

lol 🎸

Thanks Andrew! Happy to hear your feedback or ideas to improve it. :)

Glad to share! Let me know how it's working for you.

Oh yeah I didn't mention that in the video. You can still use your mouse or other means of controlling parameters you've mapped to a Knobbler slider. 👍Thanks!

I believe it is "Pepe le Pew Pew".

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?

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 > <

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.

Mission Accomplished!

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 .

Yes indeed it is! I forgot to put it in the doc. Thanks for the reminder :)

​@@zsteinkamp got it. awesome work as always!

I'm happy to hear about your experiences with it and what you make with it!

Hey @_CRiT_hits_ thanks! Simulscrub is one (big) track in the song. The drums, synths, etc are additional tracks. The sample loaded into SimulScrub is a full performance of "In C" by Terry Riley. Link is in the description. :)