[FIXED] CV mapping screen values slightly incorrect

[trevormeier]

Firmware 2.01A

On a new project, sending C0-C1-C2-C3 out of CV1 and then reading CV1 in the mapping screen produces values that are slightly incorrect. The result is when using the CALC P2NT pitch > note mapping about 50% of the octave notes are off by a semitone (usually lower, e.g. B1 instead of C2).

The linked video shows an example: apattern with programmed notes, the result of the CALC P2NT and the CV1 input on the mapping screen.

https://drive.proton.me/urls/ZMG037ZEEC#Oz7RX4L34iCD

[mgd]

Firmware 2.01A

On a new project, sending C0-C1-C2-C3 out of CV1 and then reading CV1 in the mapping screen produces values that are slightly incorrect. The result is when using the CALC P2NT pitch > note mapping about 50% of the octave notes are off by a semitone (usually lower, e.g. B1 instead of C2).

The linked video shows an example: apattern with programmed notes, the result of the CALC P2NT and the CV1 input on the mapping screen.

https://drive.proton.me/urls/ZMG037ZEEC#Oz7RX4L34iCD

Have you calibrated your input?
If you have then maybe the P2NT function does not round but truncate. That would explain the observed behaviour. You may wish to also output/show the result of the first row of the mapping. That would show the values read from CV1.

Kind regards
Michael

[trevormeier]

Firmware 2.01A

On a new project, sending C0-C1-C2-C3 out of CV1 and then reading CV1 in the mapping screen produces values that are slightly incorrect. The result is when using the CALC P2NT pitch > note mapping about 50% of the octave notes are off by a semitone (usually lower, e.g. B1 instead of C2).

The linked video shows an example: apattern with programmed notes, the result of the CALC P2NT and the CV1 input on the mapping screen.

https://drive.proton.me/urls/ZMG037ZEEC#Oz7RX4L34iCD

Have you calibrated your input?
If you have then maybe the P2NT function does not round but truncate. That would explain the observed behaviour. You may wish to also output/show the result of the first row of the mapping. That would show the values read from CV1.

Kind regards
Michael

These errors occur when reading from the Track 1 CV1 output (not the CV1 input). So it's all internal math on the NerdSEQ.

[XORadmin]

Firmware 2.01A

On a new project, sending C0-C1-C2-C3 out of CV1 and then reading CV1 in the mapping screen produces values that are slightly incorrect. The result is when using the CALC P2NT pitch > note mapping about 50% of the octave notes are off by a semitone (usually lower, e.g. B1 instead of C2).

The linked video shows an example: apattern with programmed notes, the result of the CALC P2NT and the CV1 input on the mapping screen.

https://drive.proton.me/urls/ZMG037ZEEC#Oz7RX4L34iCD

Have you calibrated your input?
If you have then maybe the P2NT function does not round but truncate. That would explain the observed behaviour. You may wish to also output/show the result of the first row of the mapping. That would show the values read from CV1.

Kind regards
Michael

These errors occur when reading from the Track 1 CV1 output (not the CV1 input). So it's all internal math on the NerdSEQ.

The thing is that you read the real values that are going to the output after calibration. I will fix that in the upcoming version. However, playing notes,, reading pitch values from it and convert back to notes seems a bit overflow to me. Just read back the note values instead and it should be fine.

[XORadmin]

The problem was in the Pitch2Note function which didn't have a proper range to 'snap' to the correct note.
As workaround until the next version just add 9 to the CV value and it will be fine, too.