MIDI Controller assignment system…
In trying to make things both highly functional in a number of situations and modular, I’m wondering how folks who do this a lot deal with MIDI controller number assignments between parts of a patch. For example. if I build a patch that includes 5-6 other abstractions I’ve made (maybe as [bpatchers], do you have some kind of central system for assigning controllers to various parameters? I’m thinking about doing one but trying to think through how– maybe the [pattr] system and some pre-defined parameters in the patchers that can be sent MIDI controller assignments. Hope this is making some sense…
I would use the "set" message to [ctlin] wherever you have one, these number boxes can be preset with either [pattr] or [preset]. If you’re using [bpatchers] then use [pattr] to store different sets for each instance.
Personally I’ve been converted to holding the opinion that "every max patch should start with a pattrstorage"
This example uses a simple coll to map cc numbers to the elements you wish to control via their scripting names. The controlled elements are UI elements stored in bpatchers (embedded in the parent), though the basic idea works for any combination of child patchers/bpatchers/abstractions etc.
Pattrstorage (with a sprinkling of autopattr) gives you instant (and wireless!) control of all ‘scripted’ elements, as well as (optionally) feedback. This has the distinct advantage that all your midi io can be in one place (rather than distributed through various midiin/notein/ctlin throughout).
You’ll also cut down on patching time by not having to add send/receive pairs, or dig into patches to find the corresponding names (pattrstorage’s client window will give you the ‘path’ to all clients)
A final benefit is that as your then using the pattr system, adding preset capabilities to the patch later is painless.
Adapt this to ‘any patch’ should just be a case of deciding on your mapping (fixed or dynamic) and implementing it, then adding autopattr/scripting names to any patches you plan to embed in the top level patcher.
----------begin_max5_patcher---------- 1635.3oc6ZszaaiCD9ryuBBs6Q2BJJYKqrW1tONzCEXAVzSIEFzRzNrURTPh xMoE8+9xGRxR1T1xN1xcAbNvDSNjblONyvgeNe+tQVKXOSxs.2Cd.LZz2uaz HUWxNFU94QVw3mChv4JwrBXwwjDt0X8XbxybU++cbQDlS.AA.X0fzP0PrEe9 MNSp5bIKgmfiIpgdWFEGUMRRQLMIhvUajcCwyoeSItM7svMxxJ3UBW0aJlG7 DMY07LR.WaUHOGwj.SPxVO4B.rm8VH3SxY7i6tS1Ltm1dLIOGuhrisCA+psI a14HsYzwXy16wlQJ6zehr0A81IBadpzlKmhdU3ujRzxaYcRvQXC6noYau2Cz i0JbcUsvp1tshkQLL+zLkt7p+2TR.c4KfXbZpP6xAKdAfCCE+IPHdFkjC3LP .KJZLfl.3OQ.KYYw2+XxiIAA+xXPdPFMkKjWXfO8aUqeDMgDvJRTahqAHDdk hVr8mphPJCTblVE6bVQ0OlSTP0iV+tPsRK3wrPBv9QK.lK.0EEh7HBXcEgCV RHgKvAeArLiEC936AjHhbMyMBkN6BkH+qET5XqC+ba.kt1mHTlP9pvZ1AIyX RrJ+k3ELSghHuKowi5138U9OH0TASmsIqamYfFepYg5.Y9VD3yLZhIPw9RlV 9vfhqxuv26J.JEIohXISXB7p5nXOQ4h30CGEpLeh9Wm06vWRi3jr6uWdo1C1 eB3Ny.LY6cktQ2VgLN5jH9JGnKwM5ckvVCNl.D2WgeyRb.oSeIzwmw0oLQim NUq5CH3IlvcgZC1XzqwY0lW2vQcUt3rUkkUWeFsfkEJlU6Rg1fLuRy0FoSn3 1L5gDufDtiqkVIFUa3ijFDYMIKmxRZH8HqiYyDF3JQgPrrROVk.0Mv1BFwB9 hVyfUcFRVdbaGKkjrYFvxcYSSaIoIoYjbgyMlWZkM2YbQDet4fz1iW4yZbPi 9+irVkQCYIRkn0LkcWscOnBmaGTWJQBN0vj4LVzBb1ZZNcQDo0glvuFmPiEO FiS05CBVOOZbZFUWrTcejDrXMdRTppnN1VKkdj0FFIjrlFP9JMj+jZs1fVsd QYCmrVQbs5ee2csSrWgiCT7iMzqoD0YpvEbVprJxli1LBcVyA59PqqDW6Iat gnW2FiXJBVWZHR81zI9p2o0zEu6hBFWWbPCQE92bVFoAD2.iGYUdyldYbm0b pkCh9T0sM5TlpeT4Ma+W5rnmxYa6KXZezUoBlO3lLjmav8etMSkRCoedseaJ EFJfxtKfx8mHfBo3dQ6eeg.pvsrol4J1uGEpWPgwRz5xd8zQxPyLVbXVKFJL oSmG6yOln8Ab8OSXxlaGku7utFq61H1YplWVdfoJ7b9Irf2yQ8tsewXqabg9 STW45sCFotoUdoi3EUfVb4XB5tnuwz9fu6tjZKm9vFQ8P430jv4B0WrZyqYm Je6BnSwYB6Q7nf45RlZUeUI.0Ll.pNpDMyfpDFMJ5SsTzDpBHasNAQTgiZyW EJmrc4JLFLEBeMABcvYfjbSPLMj9lJRPMb1dQIYy8fzGnuP12omTprc0SJab dHli29bcaRZEEJUJ0tU29ExKsuRTDEEUTswhzI0jKrIylob7kqi8gVGT+VGj 40YK9N50R4zikpsVU6OdbgSad25Y2cV5IKBwxIF7hmdI8h851KdpSyW4BgGm abCFwF+54GaOvlQ1TmbkRpWhYPcskd8i3vSBQJDkGTXvx6A0WxseaZfLhFoY jkzm02oxxpKFgxIwky258u6OA+UFcMICH+y+nHWdKKvZrrgy.e.+7G92+wXe nMY55Er6zRqlWcQzd+t5TD862aG3R2zyNC2Z+zkLSeujWsuMVU4Y51I8p3iy GdHJjNbANYkIN+uRQttMJZU+0xue7Po9mcNb6n7d+q.AtCI+sCK8s2Xu8F6s awdKxUwdq+M1aeEr2h71C6svaj2di71aj2di71+GSdqRvlBUUvmRGk82trub VQVPMEI5h8AapiJTjaklTW6vC0AaMj4IZXXqqokukHkQS3szycJAsuZDpGZj TqsGLMxs0tYVilLnXzjdfQSGTMRRZ8AUIIy3C34lDAPGPkPvg04F1CeI4+3c CHLg5yQm+vBS18waZXO576gJI++HcHgIu9nS1CpN4zmiNGmgUm5ysbGal.DR +TFM0L9a9PKkU7geb2+grqpwJ -----------end_max5_patcher-----------
Thanks so much, this is *great* stuff. I was thinking along similar lines, willyc– I just have to get my pattr chops happening. I’ve gotten into a little and maybe not with the most straight-forward application, and got pretty confused. But I’ve got some resources, so it’s on the list to try again. I was not aware of these links, razzkazz, they are really interesting. I’d heard of Jamona but hadn’t looked into it. Many thanks!
Although I don’t have it packaged up in an easy to share way, you may want to look at how I do it in a finished product, in my Software Klee Sequencer: http://defectiverecords.com/klee (You can try it all in the demo, no need to purchase). You can also get a good idea of how it works in this YouTube demo: http://www.youtube.com/watch?v=ph5tFH1drlc
Under the hood, although the details are different, it’s basically doing similar thing to what willyc advises above…
how the coll keeps the data saved into an app?
It doesn’t – I allow the user to manually save the coll contents to a file, which they can manually load back into the coll later. That said, it would also not be too difficult to write the coll contents to a preference file, which were then automatically loaded back in when the app was restarted the next time.
Hey Dan, how did you do your "MIDI Learn" ability?
I’m a little foggy on the details now since it’s been at least 3 or 4 months since I built it, but basically:
* use hover to sense when mouse over an object (exclude objects that I don’t want to be able to map)
* move semi-transparent blue panel over the mappable object when hover’d over
* if click on that object (sensed using mousestate), then move different color (orange) semi-transparent panel on top of object to indicate "listening" mode
* now listen to ctlin for controller data
* when received, create a new custom ctlin object with correct CC and MIDI settings, using scripting, and connect it to object that was clicked on, also using scripting
* write data to coll and display in a jit.cellblock, allowing for save/retrieval etc…
Hope that helps some!