[FIXED] Mapping CV CV6 to CV16 not in tune

[kaspar]

Hi    Thomas,

I have a strange problem:

When i map a CV Out to a CV16 Out, the tuning is not correct.
   

When i use the CV out (from the nerdseq), it's fine. Even when i patch the CV Out to a CV IN and map that CV IN to a CV16 track it's also totally fine.
   

So, it's not a calibration issue, but something else..


Greets!!

[XORadmin]

Yes I see the issue and it is much more complex than you might think and it is related to calibrations and hardware.
In fact, every value you send to a CV output is calibrated and optimized and you get this optimized value as the 'CV' value in the mapping input.
So a C-4 for example generates a value for the DAC which differs for each CV output and it differs even more on the CV16 outputs since it comes from another hardware batch etc..
I can see if there is a compensation possible here in an easy way without involving too many calculations.

[kaspar]

Yes I see the issue and it is much more complex than you might think and it is related to calibrations and hardware.
In fact, every value you send to a CV output is calibrated and optimized and you get this optimized value as the 'CV' value in the mapping input.
So a C-4 for example generates a value for the DAC which differs for each CV output and it differs even more on the CV16 outputs since it comes from another hardware batch etc..
I can see if there is a compensation possible here in an easy way without involving too many calculations.

Thanks for the insight, Thomas..

yeah, crazy complex machine.. 

But why is it working with the CV inputs?  are they not measured, calibrated and optimized?

[XORadmin]

Yes I see the issue and it is much more complex than you might think and it is related to calibrations and hardware.
In fact, every value you send to a CV output is calibrated and optimized and you get this optimized value as the 'CV' value in the mapping input.
So a C-4 for example generates a value for the DAC which differs for each CV output and it differs even more on the CV16 outputs since it comes from another hardware batch etc..
I can see if there is a compensation possible here in an easy way without involving too many calculations.

Thanks for the insight, Thomas..

yeah, crazy complex machine.. 

But why is it working with the CV inputs?  are they not measured, calibrated and optimized?

The CV inputs are calibrated and read 0-10 V and generate a 0-FFF from that range which is what you want to have.

I did solve it already actually by calculating back in the mapping source so the factor calibration is out of it again. It works quite OK but not 100% as they are precision faults with calculation involved, too. But it seem to work mainly well. Next release which is coming up soon.

[kaspar]

Yes I see the issue and it is much more complex than you might think and it is related to calibrations and hardware.
In fact, every value you send to a CV output is calibrated and optimized and you get this optimized value as the 'CV' value in the mapping input.
So a C-4 for example generates a value for the DAC which differs for each CV output and it differs even more on the CV16 outputs since it comes from another hardware batch etc..
I can see if there is a compensation possible here in an easy way without involving too many calculations.

Thanks for the insight, Thomas..

yeah, crazy complex machine.. 

But why is it working with the CV inputs?  are they not measured, calibrated and optimized?

The CV inputs are calibrated and read 0-10 V and generate a 0-FFF from that range which is what you want to have.

I did solve it already actually by calculating back in the mapping source so the factor calibration is out of it again. It works quite OK but not 100% as they are precision faults with calculation involved, too. But it seem to work mainly well. Next release which is coming up soon.

Thomas, you are brilliant. nerdseq is pure joy, thanks!