2.04 Aftertouch / Velocity settings not getting saved

[Jaxigally]

This *was* working initially, and now whenever I try to save a program, the aftertouch and velocity sensitivity gets reset to 127. Is this a known bug? Is there some hidden setting somewhere I flipped accidentally?

[Jaxigally]

Well, resolved for now... It was only happening for program 111, and when I copied it somewhere else, modified the sensitivity, modified it successfully in the new spot, and then copied it back to 111... everything worked. In fact, now I can just edit it normally in program 111 and it works.

[Jaxigally]

Just FYI for anyone else that runs into this. I heard back from support, and it is a known bug that happens after the OS update should be fixed in the next OS update. Until then, the workaround is basically to do what I described.

[obelisk]

Just FYI for anyone else that runs into this. I heard back from support, and it is a known bug that happens after the OS update should be fixed in the next OS update. Until then, the workaround is basically to do what I described.

I've been troubleshooting some issues with loading Conforces patch presets, and discovered any of the patches with velocity button engaged were not playing properly. Going back to version 2.0.1 fixed the problems, so be careful loading older patches with them incorrectly loading.

[Starkstrom]

Well, resolved for now... It was only happening for program 111, and when I copied it somewhere else, modified the sensitivity, modified it successfully in the new spot, and then copied it back to 111... everything worked. In fact, now I can just edit it normally in program 111 and it works.

I found that some of my programs have this problem with Aftertouch. Unfortunately copying the programs to different memory slots as described above doesn’t solve the issue in my case. By any chance, did anybody come across a different workaround?

[Starkstrom]

Well, resolved for now... It was only happening for program 111, and when I copied it somewhere else, modified the sensitivity, modified it successfully in the new spot, and then copied it back to 111... everything worked. In fact, now I can just edit it normally in program 111 and it works.

I found that some of my programs have this problem with Aftertouch. Unfortunately copying the programs to different memory slots as described above doesn’t solve the issue in my case. By any chance, did anybody come across a different workaround?

Maybe interesting for some… I found a workaround, albeit one that's a bit cumbersome:
- While the program with the described issue is active, match all rotary knobs using the dot in the three digit display as a reference
- Turn off 'Preset' and match all push buttons
- When done 'Preset' on or off should sound identical
- With 'Preset' off save the program to the same slot
- Now you can adjust velocity and aftertouch to your liking and save / recall the program as expected

[spacesoul]

It's getting really disappointing: It's been a year since the last update and bugs are not  eliminated by Sequential ...

Adjusted level for Aftertouch & Velocity is not getting saved.
Also the "workaround" to alter some parameters like Cuttoff and than saving is not working for me. I always get the same full blast value of 127 when changing the program and return to the one I´ve just saved.

When is the update coming?

[BardicPerspiration]

It's now October 2024 and these bugs are still around. But at least we have a new P10 with lacewood now, I guess? 

Is there ever going to be another firmware update?

[dr.sax]

It's now October 2024 and these bugs are still around. But at least we have a new P10 with lacewood now, I guess? 

Is there ever going to be another firmware update?

Hopefully the guy who did the firmware is still employed in the company. Changing the wood of the case is no brain surgery 😜

[BardicPerspiration]

So, for anyone interested: I contacted Sequential asking if there's still a fix and/or P5/P10 firmware coming and received a prompt and friendly response letting me know that a) the same three-person software engineer team that's been in place for many years is still in place and b) that updates to the P5/P10 OS are being worked on, though no release time frame was mentioned. I'm just glad to hear they still have people working on it.

[dr.sax]

So, for anyone interested: I contacted Sequential asking if there's still a fix and/or P5/P10 firmware coming and received a prompt and friendly response letting me know that a) the same three-person software engineer team that's been in place for many years is still in place and b) that updates to the P5/P10 OS are being worked on, though no release time frame was mentioned. I'm just glad to hear they still have people working on it.

This is good to hear.