OS 2.0.4: vel/at-modulation has to be reset manually to 127 in user bank.

[ko-bra]

It seems as if the latest 2.0.4 update sets the newly added velocity/aftertouch modulation to zero on patches in the user bank, which means most of them sound wrong.

But it'simply a matter of holding down VELOCITY/AFTERTOUCH and use the INC/DEC to set it back to 127, as they were before the update.

And then the patches come back!

[HockeBocke]

That's not my experience ....   The patches I'we checked is up to 127 .....  All of them   

Cheers !

[LPF83]

That's not my experience ....   The patches I'we checked is up to 127 .....  All of them   

Same, it starts at 127 for me.   Wondering if this means there is a way to have it default to 0?  I find the most usable setting between 20-40, so it would be much faster for me to tweak from 0 up on each patch.

Really wish this was a global setting rather than per-patch, but I understand the arguments for having it per patch as well... so not complaining, just glad its there

[HockeBocke]

The only thing I'm confused over now is that when trying to save the edited patch, lets say
FLT / LFO set to 050, when pressing RECORD and Program Number  the edited number 050
goes up to 127 again .....   

What do I do wrong ?   


Cheers !

[LPF83]

The only thing I'm confused over now is that when trying to save the edited patch, lets say
FLT / LFO set to 050, when pressing RECORD and Program Number  the edited number 050
goes up to 127 again .....   

Same again...   Q compensation saves with the patch but the AT and VEL setting values do not.
So I guess we can look forward to a patch.  Still I'm just happy to be able to use AT at all, turning it off altogether has been one of those things that I just learned to live with, I accepted it for "doing what the vintage ones do".  So even while we wait for the patch I'm still stoked about the update.  It would really help speed of workflow if I had the option to start at 0 and go up instead of 127 down though.

[HockeBocke]

Seems like whatever I do the AT settings don't stick to the patches OR elsewhere   
It is back to 127 all the time after pushing any button .....

According to the update instructions it can to be stored "per program" .......   

[Qwave]

The new Velocity and Aftertouch amount parameter is only stored per patch, if you set it to this in the new Global Page 3 Button 3 settings. It is described in the to thread here (the one we are not able to send replies to). It work here fine. And all my own patches default to 127 on the Velocity and Aftertouch amount. So they do sound like the used to sound before the update. I started changing it one by one to the more playable value of 30 to 40 for most sounds.

[Quatschmacher]

The new Velocity and Aftertouch amount parameter is only stored per patch, if you set it to this in the new Global Page 3 Button 3 settings. It is described in the to thread here (the one we are not able to send replies to). It work here fine. And all my own patches default to 127 on the Velocity and Aftertouch amount. So they do sound like the used to sound before the update. I started changing it one by one to the more playable value of 30 to 40 for most sounds.

The global 3 button 3 is Q compensation. There is no global setting for the per-program velocity level.

[MARTELLO]

not my experience, everything ok and setted at 127 ;
Cheers

[solitud]

I cannot store aftertouch and velocity amount values on my own presets created on firmware 2.0.1.
After save the values jump back to 127.
However I can change and save values on the duplicated FACTORY presets in the user banks and also on new INIT patches created with RECORD+PRESET.

[LPF83]

I cannot store aftertouch and velocity amount values on my own presets created on firmware 2.0.1.
After save the values jump back to 127.
However I can change and save values on the duplicated FACTORY presets in the user banks and also on new INIT patches created with RECORD+PRESET.

That's an interest observation -- I have no idea how things work behind the scenes but it sounds like the data structure of a patch had new attributes defined that weren't present in old patches, so maybe some sort of conversion needs to take place.

[g3o2]

That's an interest observation -- I have no idea how things work behind the scenes but it sounds like the data structure of a patch had new attributes defined that weren't present in old patches, so maybe some sort of conversion needs to take place.

That’s a reasonable assumption, however, why would there be cherry picking of the “factory-user” presets over any other user presets?

[LPF83]

That's an interest observation -- I have no idea how things work behind the scenes but it sounds like the data structure of a patch had new attributes defined that weren't present in old patches, so maybe some sort of conversion needs to take place.

That’s a reasonable assumption, however, why would there be cherry picking of the “factory-user” presets over any other user presets?

They have an opportunity to update the factory presets as part of the OS updates, where as they don't know what other user presets are on the target synth.  Just a guess.