I’m creating custom midi mappings in the editor with nonstandard values (trying to use the sub 37 as a template for my analog four) and I can get mappings mapped out, I can save to a preset, I can make them survive preset changes. But when I power cycle the sub 37 things are no longer mapped to where I set them. The drop down menus in the editor show the new mappings, but I have to map to a different control, then set back to the desired mapping for it to “take.”
Unfortunately no, that didn’t seem to do the trick. Even with patches saved and/or “map per preset” checked.
I’m not missing something obvious, like a “use custom mappings” setting somewhere in the system settings, am I?
Something did change since the update though: before, the editor would show the nonstandard mappings when you booted it up again even though the values hadn’t survived the sub’s power cycle. Now when you exit the app and restart the synth, the nonstandard mappings have been lost, just like before this release, but at least now the software is aware of the change: it displays the values that the synth is sending out exactly as they are. Unfortunately those aren’t the values we want
The mod wheel was also reassigned to send cc 38 after I saved my custom mappings, but that might be because ‘load preset mw’ was checked in the editor by default. I didn’t try to replicate that.
I double checked all of this with a midi monitor in max for live, btw, so I’m sure that it isn’t something attributed to the external synth I’m trying to control.
I haven’t tried all the various combinations, but just to give you an idea, these are the nonstandard mappings I’m attempting:
It appears that when you set a custom mapping in the editor, it is really saved in the hardware. If you turn off power to the Sub 37, close the editor, and turn on power to the Sub 37 again… the custom mapping is still there.
It appears there is some back-and-forth communication when opening the editor again, that is somehow setting the mapping back to default.
I’m digging deeper into this now.
Thanks very much for pointing it out! I anticipate a quick solution, just needs a little more investigation.
Oh ok that’s interesting. I was exiting the editor and then powering down the synth. I’ll try to shut the synth off with the editor running, then exit the editor, then see if I’m still sending nonstandard values after a power cycle.
I tried shutting the synth off after making my custom mappings and I found something interesting: more custom mappings survived the power cycle than survived when I was exiting the editor before turning off the synth, but not all of them survived.
I don’t have the full list of values in front of me, but I know that the following knobs maintained their remapped values: filter cut, filter res, filter drive, filter kb, osc1/sub/osc2/noise levels, keyboard octave buttons, and osc2 wave. The following lost their remapped values upon power cycle: osc1 wave (which is funny, given that osc2 survived), all the a/d/s/r knobs for both envelopes, filter EG amount (which is funny given that filter keytracking kept its reassignment).
we verified that the editor itself is resetting mappings due to a bug in v0.9.39; I anticipate this will be fixed in the next Editor beta when it’s ready.
Until then, probably best not to rely on custom CC mapping as using the editor Mapping page may reset your changes. Sorry about this! It will be fixed soon.
You caught what I said though, right, that some custom mappings don’t seem to stick regardless of the synth being turned on with or without the editor running?
Just wanted to make sure you guys aren’t testing it with only the same nonstandard mappings (eg just remapping filter cutoff and res). Like I say, some knobs seem to keep their new mappings while others have amnesia
I did and I’ll check this. I’m 99% sure it’s just an artifact of the same basic problem though; the custom-mapping system is no different than the default mapping system (the default mapping is just a preset set of “custom mapping” data really)… there’s nothing special about certain controls that should cause them to behave differently than any others when being mapped. But I will check.
Procedure I intend to use:
turn on Sub 37, connect USB, open editor.
go to Mapping tab, set some custom mappings.
disconnect USB so the editor can’t do anything to the Sub 37… then turn off Sub 37 and close editor
turn on sub 37 (with editor not running), connect USB… don’t open editor… just check MIDI CC assignments using MIDI monitor or MIDI-Ox.
confirmed, these all re-mapped and stayed re-mapped after turning the Sub 37 power off for a good several seconds and turning it back on again.
I did the mapping using the Windows stand-alone app connected to the hardware via USB… immediately after setting the mappings I wanted, I unplugged the USB without so much as clicking anywhere within the editor app.
I then plugged USB from the Sub 37 into a different computer which was not running the editor (just because I had a desktop and a laptop handy, there’s nothing crucial about this detail except making sure the Editor isn’t running anywhere while testing if the mapping persists).
I verified that all EG ADSR knobs were re-mapped (I used CCs 1,3,4,5 for Filter ADRS, and CCS 7,8,9,10 for Volume ADSR), then I turned off the power to the Sub 37, waited, turned it back on, and re-checked the CCs. Still custom mapped.
So the firmware seems fine… we just need to fix the editor so it doesn’t un-do your mapping work.
Hey thanks for the demonstration! Cool setup too, I can see why you want to get this working.
Can you fire up MIDI Monitor on your Mac and see what MIDI CC number the sub 37 is putting out for the Amp Eg Release, after the power cycle?
Looking at the code, there’s really no reason I can see that any mapping should ever not work, in the case where some mappings work. They are all handled exactly the same.
I’ll test on my side now, using Mac editor and DIN instead of USB, and report back.
Yeah I can do that tonight. I’ll monitor the cc’s sent via din as well as USB, although I can’t imagine those being different.
Should I test with the old firmware first before updating to the firmware that Gil just announced?
And yes: I know that “ostentatious midi controller” probably isn’t the biggest selling point of the sub 37 for most people, but the ergonomics on it are incredible and I’d love to have it working fully. Thanks for the compliment on my setup, Amos
