OSC Note-On Reset

Hello, does anyone notice any difference when NOTE-ON RESET in the Osc section is on or off? To me it doesn’t make any difference. Seems like it‘s not working (I know how it should sound eg in unison in reset mode or with FM)

Moog music has today come back to me and they said that indeed, this setting has no effect, even not on their Moog Ones over there. They will address that in a future update.

So there i am reading along and i’m like, that’s nice … “They will address that in a future update” and i start to move on to another post when it hit me, i’m like, WHAT? WAIT!, did you write “They will address that in a future update” They promised a Future Update?

OUTSTANDING!!!

For a while there we started thinking that we had become part of … the forgotten ONES.

hope dies last :slight_smile:

haha. believe it or not this feature was why I got this synth in the first place. Nice one moog, your OS is full of bugs and shortfalls. It all seems so good on paper and then instead of working on my project I’m chasing my tail trying to get non-existent features to work.

This could just mean that they take that option away because it’s broken.

For all of us, who can’t imagine what we miss:

My Prophet XL with
https://soundcloud.com/noisebit-2/prophetxl-2-oscilllators-saw-with-wave-reset

and without Wave-Reset (that’s equal to NOTE-ON Reset)
https://soundcloud.com/noisebit-2/2-osc-saw-without-wave-reset

I recorded a sequence with 2 OSC SAW. At bar 20 I switched
to HARD-SYNC OSC1->OSC2. I detuned the frequency of OSC2 to -7.
OSC compensation is set to OFF.

Both Oscillators start at the same level. I found my workaround (or solution).

https://soundcloud.com/noisebit-2/moog-sync-moog-one

Niceeeeeeee, very cool riff!!!

Indeed they are. I know that the 1.5 firmware is in beta and have been int for quite som weeks. I think it is a matter of…patience!

Well, the ProphetXL uses digital oscillators, where this is easy. I actually don’t know of an example of VCOs “note-resetting” properly. I guess Moog One is the first.

Moog One does (at the moment) almost always reset oscillators by default. What you are hearing in your example is (from sec 20) the single OSC2 playing. All you have done, by lowering the frequency of the synced osc, is to make the saw wave slightly quieter and unsymmetrical. Just imagine your saw, getting restarted before it has reached it’s lowest point.

After some messaging with moogmusic back and forth, we have found the following problems:

  • moog one does reset the oscs most of the time anyways
  • the end of the release phase seems to cause the oscs to reset

As a work around (if you DON’T want the oscs to reset) you can use another env to replace the amp env via the mod matrix (screenshot attached). Here a video where I demonstrate what’s going on. At 0:42 you can clearly hear the osc-reset spikes when release is shortened.

https://www.dropbox.com/s/hqgi81rrv9m7nkm/Moog%20One%20Note%20On%20Reset%20with%20ENV%20Release.mov?dl=0
Mod Matrix Replace Env.png

Hi,

Do you know if the problem has been fixed? I’m on v1.5.0 firmware vers. and I have exactly the same problem (very annoying…).

I presume that only a firmware upadate could fix this, but its weired that a so piece of art like the moog one suffers from such a ridiculous bug…