Hey, So I've only been making electronic music for 19 years and just bought my 1st midi controller, an old Korg Nano Kontrol. I get quick mapping MIDI parameters, but for the life of me I can't get the document switcher to switch documents reliably via MIDI.
What I want is to load document 1, play it, do some stuff, and then when I'm done hit a button on my controller to go to document 2. And then iteratively work through the documents list in my Document Switcher / .AMS file - i.e. when I'm finished playing document 2, hit the same button I've mapped to switch documents, move on to document 3, do stuff with MIDI in there, hit that same button to move on to document 4, etc.
Can someone kindly step me through how to do that?
Oh yeah, I'm on Windows 7 if that's something to consider...
> I can't get the document switcher to switch documents reliably via MIDI.
I'm not super familiar with the capabilities and limitations of the Nano Kontrol. But the way document switcher mapping (and also preset mapping) work in AM is that AM expects to be sent a different CC,PC or Note velocity value for each document slot (or preset, or in 2.2 also metasurface snapshots).
Usually this would mean a separate button on your controller for each message, and hence document/preset/snapshot that you want to switch. You seem to be asking about using one button to send lots of different messages. Or perhaps, one button to execute a "next document" or "increment" command.
AudioMulch doesn't currently support interpreting a single button press as an increment/decrement operation, although it is a worthwhile idea that I would like to explore in 2.3. For now, if it is possible at all, you need to find a way to get the Nano Kontrol to execute the increment operation and send a different CC value each time you press the button, or use one button for each value document, assuming the Nano Kontrol can be programmed that way.
On Windows I often find that MIDI OX is a useful tool for understanding what your MIDI controller is sending:
Does this make sense? Do you understand enough about how the MIDI protocol works to know what I'm talking about? -- It is something we are thinking about at the moment: do people understand how MIDI works enough for the AM UI to make sense?
Thanks for the speedy reply. I found it totally clear. Regarding your questions in the last para, I've used MIDI a lot for years - I don't know how typical that is of Mulch users.
I was looking for a way to jump to the next document but I guess given there's no onscreen equivalent I was being a bit hopeful to think I could do it via MIDI. I'll investigate my options.
I've just mapped the Document Switcher to a knob instead of a button and can see now how it's working. It is quite glitchy / unpredictable, though. Turning the knob to far right / maximum value doesn't necessarily load the last document in the set, which seems odd to me.
That's with no configuration beyond quick mapping, I may be able to do something to improve it. I'll keep tinkering.
> Turning the knob to far right / maximum value doesn't necessarily load the last document in the set, which seems odd to me.
The knob will most likely span the full range of 7 bit MIDI values (0 - 127, or 1 - 128 depending on how you count it). That would correspond to switching between the first 128 slots in the document switcher grid. There is no way to scale the mapping for the document switcher (or presets) so as you can see, the current situation is not suited for mapping preset/document switching to a knob. It is most suited to mapping one button per document -- often you'd do this via program change messages.
Ah right, gotcha. I can configure the buttons as you describe with the standard software for the controller, by the looks of it, but I'll play with MIDI-OX and things to get more familiar.
The brave old world of controllers! ;)
Program Change increment/decrement can be set up via Bome's Midi Translator http://www.bome.com/products/miditranslator
Can't seem to find the specific thread I have seen it explained in the forum over there but do know that I have come across it when looking for myself.
I'm definitely in favour of having increment/decrement functions for Document/ Presets/ Snapshots.
If you're familiar with PureData you could also use that to make one button act as multiple buttons using MIDIYoke to input it into AudioMulch.
You would just have to set it up to count the number of times you hit the button and modify what it does each time. This would be very simple to set up.
Thanks for the extra suggestions bods!
I've never got into PD but have done a bit of (non-musical) programming so am hopeful it wouldn't be as scary as some make it out to be.
Anyway, will investigate...
I found it to be really easy to get into on a low level.
It also has a similar graphical display to AudioMulch in that you connect objects from output to input in a canvas on the screen.
If you already know some programming you should be in with a head start as PD uses many of the same basic principles as any programming language just with a graphical interface rather than blocks of text.