Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Velocity Settings not being saved #22

Open
xustafu opened this issue Oct 3, 2024 · 1 comment
Open

Velocity Settings not being saved #22

xustafu opened this issue Oct 3, 2024 · 1 comment

Comments

@xustafu
Copy link
Collaborator

xustafu commented Oct 3, 2024

Copy paste from user mail:

Si configuras las entradas CV como Velocity, estos ajustes sólo se mantienen mientras el módulo esté encendido. No se guardan cuando salvas la configuración en alguna de las 4 memorias de usuario o cuando salvas el archivo como SysEx en el ordenador. En la pantalla del módulo se puede ver el gráfico del voltaje entrante pero la nota asociada a ese banco siempre se envía con una intensidad de 127 independientemente del voltaje que se reciba. Si quiero usar esta función tengo que configurar de nuevo las 8 entradas CV manualmente cada vez que enciendo el módulo.

@BrufordRules
Copy link

More info on this issue:

If you configure CV input 1 from the device as Velocity for Block 1 and send the SysEx to the computer, the info about this input is correct:

F0 7D 32 11 10 25 01 01 0E 3C 28 00 00 00 00 3F 00 00 00 00 00 00 40 03 04 00 00 7F 00 00 10 10 10 78 00 00 7F 00 10 7F 7F 68 03 F7

Where the byte in bolt means target for velocity Block number 1 (see table below)

00 Off
04 Block 1
08 Block 2
0C Block 3
10 Block 4
14 Block 5
18 Block 6
1C Block 7
20 Block 8

But, if you save it as a User Config on any slot and then reload the patch again and send the SysEx to the computer, you can see the byte in bold is always 00. So any Velocity input does not have any block assigned as velocity target and the note velocity output is always 127.

F0 7D 32 11 10 25 01 01 0E 3C 28 00 00 00 00 3F 00 00 00 00 00 00 40 03 00 00 00 7F 00 00 10 10 10 78 00 00 7F 00 10 7F 7F 68 03 F7

I hope it can be solved in a future firmware.

Thanks in advance.

Alex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants