Sub 37 feature suggestions - firmware updates

[bartleby]

also:

midi cc dump/snapshot:
in addition to sysex dumps, it might be useful if all phatties could also send their current buffer preset as a midi cc/nrpn dump. provided that cc/nrpn parameters are the same on all phatties, this might make it possible to send little phattie presets to your sub phatty or sub 37 and vice versa. of course, it would only cover the parameters that the two synths invovled have in common, but it seems better than nothing. does this make sense at all?

global/tuning scales:
shouldn't this be a per preset setting rather than a global one?
personally, i don't often use different scales, but i could imagine that some people might like to play one song in one scale and another in a different one without having to dive into the global menu...

[lushr]

I understand the desire for the display to show the setting of every knob, but this is a feature of the voyager and was never going to be a feature on the sub 37. The lack of panel space means the lights the LP had to show settings weren't going to be an option either.

This synth cost me $2000 thanks to the extra shipping to Australia, but it isn't going to have every feature under the sun, BPM is essential to working with other instruments (in my view) but if you want to know the settings of the presets, then the editor will be coming out soonish, or you can export the Sussex files and have a read of them. Personally I just twiddle the knob to see where it was before I messed with it. And if I don't want to mess with a preset I've written I save a copy.

[bartleby]

ok, here is one more: unleash the lfos!

i appreciate how the second mod bus and the generous amount of mod destinations are a great step forward compared to the lp and sp. they open up a great variety of modulation options. hey, they are why i bought this synth - the first time i bought a modern moog.
however, what bugged me while exploring my new s37 yesterday, was how the two lfos are hardwired to the two mod busses. for example, if you select the filter eg as your modulation source for mod bus 1, lfo 1 will just run idle and not modulate anything. what a waste!

so here is what i would suggest: instead of hardwiring the lfos to the mod busses, give them direct links to some of the most common lfo mod destinations. just as the two envelope generators are hardwired to be a filter and a vca eg, make the two lfos usable as an osc and a filter lfo independently of the mod busses.

here is a quick & somewhat conservative hack showing how this might be achieved with the exact same hardware controls that the s37 already offers, just repurposing/relabelling some of them:



so i moved the mod source switch from the rotary switch in the lfo section to what used to be the osc1/2 switch of the mod bus. it now switches the mod source between the lfo and whatever you like to set it to in the pgm menu instead - just like before. but now, the lfos can still modulate osc1/2 (lfo 1) and filter cutoff/resonance (lfo2) indepenendtly from the two mod busses. so you'd essentially gain two additionall, lfo-specific mod busses!

the rotary switch now just sets the lfo waveform, with the one extra position available. as an additional lfo waveform, i would suggest sample&glide, to nicely complement the sample&hold wave.

maybe this could be an idea for phuture phatties, like the upcoming post-tribute s37? and us tribute pioneers might berhaps get some alternative panel overlay to install on our phatties?

(just phantasizing, of course. after all, moog music are encouraging us to come up with suggestions. if this one is going to phar, just phile it under phan phiction )

[bartleby]

also, i think it would be nice if in the arp/seq section, the 'back/forth' button would also work for the sequence, not just for the arpeggiator.

[gencomprodukts]

also, i think it would be nice if in the arp/seq section, the 'back/forth' button would also work for the sequence, not just for the arpeggiator.

Great idea! + having shuffle would be pretty cool.

[ImNotDedYet]

Some sort of visual representation of current knob/parameter value differences from preset values would be immensely helpful!

Also, I upgraded my firmware to 1.0.2 last night successfully without bricking it, thankfully. There's also a tunings sysex file in the zip. Can I just open that file in C6, load and send it at any time or is timing of loading that file crucial?

Thanks!

[_DemonDan_]

There's also a Tunings sysex file in the zip. Can I just open that file in C6, load and send it at any time or is timing of loading that file crucial?

I probably wouldn't do it in the middle of a update but, after you've updated the Sub 37, you can send that SysEx file at any time.

It will load 12? (I'm not near my Sub 37 at the moment) tuning scales into the TUNING SCALE sub menu in the GLOBAL menu.

The normal tuning can be found at slot #1.

[ImNotDedYet]

Thx DemonDan!

[PatMcM]

also, i think it would be nice if in the arp/seq section, the 'back/forth' button would also work for the sequence, not just for the arpeggiator.

Great idea! + having shuffle would be pretty cool.

These would definitely be great additions, in my excitement over the Sub 37 I had imagined these behaviours were actually going to be available for launch.

[greenborder]

Hi guys, I've had my Sub 37 for two days and loving it so far. A couple of things I'd like to see, or perhaps somebody can point me to currently existing functionality / tricks I am not aware of:

* A quicker way to enter preset names, possibly via the computer via a USB connection.
* A way to select modulation depths of the hidden parameters more efficiently. I mean the velocity, aftertouch amount etc, now you have to hold a button for a while which can be a bit cumbersome, I'd prefer to use one of the dials (for instance the arp speed dial) while in this menu to change the active parameter.

Also I feel the aftertouch takes a lot of pressure to fully engage. I saw in the manual there's some calibration routines for this that I can try, but do others have the same experience?

Thanks!

[Amos]

you have to hold a button for a while which can be a bit cumbersome, I'd prefer to use one of the dials (for instance the arp speed dial) while in this menu to change the active parameter.

Already possible
Try the Fine Tune knob while editing; it does data entry instead of Fine Tune while an editable value is selected on the LCD.

it's worth adjusting the aftertouch to your own playing style; especially if you're using the Fine Tune to adjust numbers, it's easy to make adjustments on the Pressure calibration page until the aftertouch feels better to you.

[greenborder]

Great news Amos, I suspected some trick was available

[Rufus the Dog]

Just got my Sub37 last Friday and starting to play. I don't find the keyboard an issue 'kept for velocity.

Already have a Little Phatty Stage II and a Sub Phatty and have been waiting for the Sub 37 since it was announced at NAIM.

Anyway the one feature that the Little Phatty has (and my Nord Lead 4 and Mopho X4) is to be able to see or at least read the current setting for a parameter. That along with precise setting of the BPM would be my top two

My third, and it has already been mentioned is to turn of the blinking arp led when not in use. I find I am always dialling the rate knob down to minimum when I am not using it


R.

[mmarsh100]

One feature I would like to see is a separate data store for sequences (and maybe arps as well) It's cool to be able to save sequences per patch, but I would like to play the same sequence on different patches.

[_DemonDan_]

One feature I would like to see is a separate data store for sequences (and maybe arps as well) It's cool to be able to save sequences per patch, but I would like to play the same sequence on different patches.

I think an "Import Seq from Preset" would do the trick nicely, thus eliminating the need to create a new category of savable data objects.

What, specifically, would you want saved separately about an Arp? It's just a knob setting and a couple of buttons. Or am I interpreting your "maybe arps as well" request incorrectly?