Velocity AMP - patches nearly silent when active?

[ANZV]

Hi all -

This has been nagging me since first buying my Prophet desktop last year. When I have Velocity AMP activated, patches are nearly silent when playing them with my various midi inputs (both a Native Instruments keyboard and an Ableton Push 2).

I believe there are per-patch Velocity AMP settings now, but I'm wondering why exactly this is happening in the first place, and if there's a global setting that would correct it?

Is this an issue with the Prophet? Is there something on the midi side that I should be investigating?

Welcome any ideas here. Thank you!

[Analog Prophet]

Hi all -

This has been nagging me since first buying my Prophet desktop last year. When I have Velocity AMP activated, patches are nearly silent when playing them with my various midi inputs (both a Native Instruments keyboard and an Ableton Push 2).

I believe there are per-patch Velocity AMP settings now, but I'm wondering why exactly this is happening in the first place, and if there's a global setting that would correct it?

Is this an issue with the Prophet? Is there something on the midi side that I should be investigating?

Welcome any ideas here. Thank you!

Hitting the keys with full velocity is equal with no velocity setting. It would cause gain issues if it was the opposite.

Sounds like your velocity curve to extreme at the Prophet and/or your controller.

I believe the velocity can be set by patch but I might mix that up with the OB-X8 - please check the documentation.

[g3o2]

Yes, I believe since version 2 velocity amount can be set per patch. Have a look at this thread:
https://forum.sequential.com/index.php/topic,6295.0.html

In 2.0.4 there may be currently a bug regarding the storing of this setting though.

[ANZV]

Yes, I believe since version 2 velocity amount can be set per patch. Have a look at this thread:
https://forum.sequential.com/index.php/topic,6295.0.html

In 2.0.4 there may be currently a bug regarding the storing of this setting though.

Thank you both. It looks like this may be a bug or an issue with third party patches (or both?).

When I hold the velocity button on a Factory patch and go to the +/- buttons, the value showing is 127. When I hold the velocity button on certain third party patches, the value showing is 0. So it seems like the default value should be 127? And that the issue is def on the Prophet side with these third party patches vs. on the midi side.

I could go through each patch and fix this, then re-save to my Soundtower library, but I guess i'll just do it on a case by case basic during usage. Thanks again!

[Starkstrom]

Yes, I believe since version 2 velocity amount can be set per patch. Have a look at this thread:
https://forum.sequential.com/index.php/topic,6295.0.html

In 2.0.4 there may be currently a bug regarding the storing of this setting though.

Thank you both. It looks like this may be a bug or an issue with third party patches (or both?).

When I hold the velocity button on a Factory patch and go to the +/- buttons, the value showing is 127. When I hold the velocity button on certain third party patches, the value showing is 0. So it seems like the default value should be 127? And that the issue is def on the Prophet side with these third party patches vs. on the midi side.

I could go through each patch and fix this, then re-save to my Soundtower library, but I guess i'll just do it on a case by case basic during usage. Thanks again!

In my experience it’s best to keep the velocity scaling at 127. When lowering the velocity depth Sequential choose to scale the maximum envelope level down for both the filter and amp envelope instead of scaling the minimum envelope velocity value up as most other synth do. The result is that presets often sound quite and also dull - in terms of cutoff frequency- when the velocity depths is lowered.

[Analog Prophet]

Just a thought: Some users complain very loud output of P5/10 rev 4 (not an issue to me), maybe that is related to not getting to low output when use velocity amp?

[ANZV]

Wow yes, I think you're both right! I often just turned this off entirely on those quiet patches, and then the output was super loud! These patches play muuuch better when I manually tweak the vel scaling to 127.

I only wish there was a way to make this a default setting. Or that I could tweak it via the SoundTower editor (I don't see a way to do this). My Prophet desktop module is unfortunately situated out of arms reach right now, so it's not ideal to be going across the room every time I go to a new patch.

[dr.sax]

Did you see that someone posted all the factory patches with the velocity set to 127 in sysex format on the forum. Perhaps this helps you.

[ANZV]

Did you see that someone posted all the factory patches with the velocity set to 127 in sysex format on the forum. Perhaps this helps you.

Thanks! I did see this. I manage everything through Soundtower, so I guess I could load it there.

Has there ever been any word/acknowledgement from Sequential on this? It's kind of an insane (and insanely annoying) bug to go unaddressed for so long.

Would be really helpful if there was some sort of global lock/override on this setting that would keep it at a preferred level no matter what patch is loaded. Even being able to dial in "127" with the patch keys would be a big win. Having to wheel over to my module and sit there watching numbers go up, every time I change a patch... 

[gus]

Did you see that someone posted all the factory patches with the velocity set to 127 in sysex format on the forum. Perhaps this helps you.

Thanks! I did see this. I manage everything through Soundtower, so I guess I could load it there.

Has there ever been any word/acknowledgement from Sequential on this? It's kind of an insane (and insanely annoying) bug to go unaddressed for so long.

Would be really helpful if there was some sort of global lock/override on this setting that would keep it at a preferred level no matter what patch is loaded. Even being able to dial in "127" with the patch keys would be a big win. Having to wheel over to my module and sit there watching numbers go up, every time I change a patch... 

Yes, we are aware of this issue and we hope to have an updated public OS out in the very near future. Apologies for any frustration with this, we know this most recent release has been in beta for (far) too long.

[ANZV]

Did you see that someone posted all the factory patches with the velocity set to 127 in sysex format on the forum. Perhaps this helps you.

Thanks! I did see this. I manage everything through Soundtower, so I guess I could load it there.

Has there ever been any word/acknowledgement from Sequential on this? It's kind of an insane (and insanely annoying) bug to go unaddressed for so long.

Would be really helpful if there was some sort of global lock/override on this setting that would keep it at a preferred level no matter what patch is loaded. Even being able to dial in "127" with the patch keys would be a big win. Having to wheel over to my module and sit there watching numbers go up, every time I change a patch... 

Yes, we are aware of this issue and we hope to have an updated public OS out in the very near future. Apologies for any frustration with this, we know this most recent release has been in beta for (far) too long.

Amazing news!! Thanks for letting us know. Is this release strictly bug fixes or are we going to see some new functionality too? Excited!

[gus]

Did you see that someone posted all the factory patches with the velocity set to 127 in sysex format on the forum. Perhaps this helps you.

Thanks! I did see this. I manage everything through Soundtower, so I guess I could load it there.

Has there ever been any word/acknowledgement from Sequential on this? It's kind of an insane (and insanely annoying) bug to go unaddressed for so long.

Would be really helpful if there was some sort of global lock/override on this setting that would keep it at a preferred level no matter what patch is loaded. Even being able to dial in "127" with the patch keys would be a big win. Having to wheel over to my module and sit there watching numbers go up, every time I change a patch... 

Yes, we are aware of this issue and we hope to have an updated public OS out in the very near future. Apologies for any frustration with this, we know this most recent release has been in beta for (far) too long.

Amazing news!! Thanks for letting us know. Is this release strictly bug fixes or are we going to see some new functionality too? Excited!

We don't disclose this sort of thing, but I will say that we log all bug and feature requests. Support scrubs the forums for requests, but it always helps to blast them directly to us (support@sequential.com) so we can add +1's to existing requests for priority.

[dr.sax]

New beta OS is released . Should have this fixed. Will try tonight

[ANZV]

New beta OS is released . Should have this fixed. Will try tonight

Did this actually get fixed? I still have this issue with basically any third party patch sets. It is maddening.

If I open a patch via SoundTower, manually correct the velocity from 000 to 100, then re-save the patch bank -- the issue persists when I reload the bank. SoundTower is not capturing this value change.

What can be done? It is such a vibe killer to have to manually tweak this every time I switch to a new patch.

If there is a way around this, please let me know.

[Jpro600k]

Adjust Velocity and Aftertouch Depth
Hold the VELOCITY or AFTERTOUCH buttons
Press Inc/Dec buttons to adjust the depth

For save your preset
Press and hold the Velocity and Aftertouch button,
press the Record button, and press the preset number.

Now you can save successfully.
Even if the power is turned off and then turned on again, the value is retained.

point)
Press and hold the Velocity and Aftertouch button

**********
Is the OS you are using the latest version?
Newest Prophet 5/10 Main OS 2.1.0 and Panel OS 1.1.3

**********
My Prophet-10 Tracks
https://soundcloud.com/jpro600-k/solitude
Instruments: SEQUENTIAL PROPHET-10 Rev.4