Page 1 of 1

Sub 37 Panel Mode: Preset settings not persistent

Posted: Thu Aug 01, 2019 3:13 pm
by fwilleke
Hello,

it's been quite some time since I posted here, as I'm still very happy with my Sub 37.

However, I noticed a problem recently: While in Panel Mode, I press + hold the PRESET/EDIT button and edit some of the settings. For example, I like the pitch wheel to go up +2 and go down -12. I also activate the EXP. ATTACK options for both envelope generators. This alway worked, but since some time, those settings are often forgotten after switching the synth off and on again.

I looked through the manual and online resources, but couldn't find anything about how to store those settings as standard for PANEL MODE. I was always under the impression they would get stored automatically, but it seems they aren't.

Firmware 1.2.0, by the way (can't find updates anymore, where do I get them?)

Thanks in advance for help!

Best greetings,
Frank

Re: Sub 37 Panel Mode: Preset settings not persistent

Posted: Wed Aug 07, 2019 2:53 am
by fwilleke
Nobody has any idea how and when the Panel mode stores its settings?
Or is it just vacation time and nobody reads this?

Re: Sub 37 Panel Mode: Preset settings not persistent

Posted: Tue Sep 17, 2019 4:12 am
by till
Guten Morgen Frank!

Version 1.2.0 is the newest available.

https://api.moogmusic.com/sites/default ... load_0.zip

The Sub37 is in the SYNTHESIZERS -> LEGACY PRODUCTS section of the moogmusic.com navigation at the left side.

But I can't help you on the main problem of yours, as I own no Sub37.

Re: Sub 37 Panel Mode: Preset settings not persistent

Posted: Mon Oct 14, 2019 4:30 pm
by Razzia
I’ve had similar issues, but not necessarily with panel mode. I think it had to do with setting mod wheel modulation depth, and I’d set a value to 100 then a minute later the sound wouldn’t be behaving as expected, so I’d check in the lcd and mod depth would have changed by several points. I never did figure out what caused it. It was within a week of getting my sub and I just assumed there was some interaction that i was unaware of and unintentionally triggering