Multi-IO Expander

[XORadmin]

Thanks for providing this project.

Loaded the project. No sound from the distingEx. Looking into it it basically does what I had tried myself (so not only a stupid user error ).

How would I do the loopback test?
Connect I2C A with I2C B is the easy part. Which settings on the NerdSEQ?

Kind regards,
Michael

Indeed, connect the 3 lines to each other.

Use only 1 pullup to 3.3V (doesn't matter which one...you can try also to swap to the other one on a 2nd test).

Load the project and play the pattern. Both LED should flash and in the mapping screen you see the 'loopback' reception in the first line 000 466 6AA B99.

If that works, try the other way around (set the I2C Port A to 16n->NS and port B to out. Change in the track setup to B-SC.CV)

I've tried that and neither do either LED flash, nor do I see any change in the first line in the mapping screen. I tried both A -> B and B -> A (with changed track setup). I verified that the 3 cables are correctly connected to their corresponding pins. Pull-up removed on B and 3.3V on A.

I then swapped the MIDI cable to see if that makes any difference - none visible.

What I also realized: How do I actually check that the NerdSEQ "sees" the Multi-I/O expander?
At one point I completely removed the MIDI cable between the two and AFAICT everything looked and behaved the same w/r to booting and looking into menus etc.

Kind regards,
Michael

Maybe a silly question... did you enable the Multi-IO at all?

[mgd]

Maybe a silly question... did you enable the Multi-IO at all?

The utterly embarrassing answer is:
It was on DIN / TRS-A. After changing that all my previously failed tests work:
 - Loopback
 - Triggering Poly Wavetable on distingEx
 - reading fader from F8R

Only unexpected behaviour was that the fader movement was only visible in the first row of the mapping screen when the cursor was on the line where the respective fader was read. When I watched the Variables Window they never changed their value.

Is there something special to be set/adjusted for the variables to be updated in realtime?

Anyway, sorry for all the noise...in the end it was a PEBCAK type error.

Kind regards,
Michael

[XORadmin]

Maybe a silly question... did you enable the Multi-IO at all?

The utterly embarrassing answer is:
It was on DIN / TRS-A. After changing that all my previously failed tests work:
 - Loopback
 - Triggering Poly Wavetable on distingEx
 - reading fader from F8R

Only unexpected behaviour was that the fader movement was only visible in the first row of the mapping screen when the cursor was on the line where the respective fader was read. When I watched the Variables Window they never changed their value.

Is there something special to be set/adjusted for the variables to be updated in realtime?

Anyway, sorry for all the noise...in the end it was a PEBCAK type error.

Kind regards,
Michael

Ah hehe...

I'm sorry for you that it took so long.

Good that it works. And the question is, how does your mapping line look like?
I hope like this:

Code:

SC.CV xxx   >   SETV   V  A   SRC 

[circulant]

First of all, amazing update to the firmware, and an incredible new module with the Multi-IO. This has made me rearrange my modules and incorporate my 16n F8Rbank into the case and learn I2C connections. Well done XOR! This is a very fun and challenging addition to an already impressive sequencer/mini-computer.

I have a question regarding the 16n F8R via I2C on the Nerdseq and applying mapping. I have a fader assigned to control pitch on CV1, and it connects correctly (awesome) however it increases the pitch amount drastically. By the time the fader position reaches 1/4 of the full sweep, the note change goes from C-2 through A-8. Is there a way to spread this note change over the entire length of the fader throw?

[XORadmin]

First of all, amazing update to the firmware, and an incredible new module with the Multi-IO. This has made me rearrange my modules and incorporate my 16n F8Rbank into the case and learn I2C connections. Well done XOR! This is a very fun and challenging addition to an already impressive sequencer/mini-computer.

I have a question regarding the 16n F8R via I2C on the Nerdseq and applying mapping. I have a fader assigned to control pitch on CV1, and it connects correctly (awesome) however it increases the pitch amount drastically. By the time the fader position reaches 1/4 of the full sweep, the note change goes from C-2 through A-8. Is there a way to spread this note change over the entire length of the fader throw?

Thanks a lot! 
I would first check in the f8r calibrations if it is calibrated well. Normally it should have a full range from zero to full with a little offset at the ends. 
In the mapping you can look up which values it generates and that should go from 0 to FFF. 
It is possible to manipulate the incoming data so it will be corrected and uses the full NerdSEQ range. But I would first check if and why the f8r is not using the full data range.

[circulant]

First of all, amazing update to the firmware, and an incredible new module with the Multi-IO. This has made me rearrange my modules and incorporate my 16n F8Rbank into the case and learn I2C connections. Well done XOR! This is a very fun and challenging addition to an already impressive sequencer/mini-computer.

I have a question regarding the 16n F8R via I2C on the Nerdseq and applying mapping. I have a fader assigned to control pitch on CV1, and it connects correctly (awesome) however it increases the pitch amount drastically. By the time the fader position reaches 1/4 of the full sweep, the note change goes from C-2 through A-8. Is there a way to spread this note change over the entire length of the fader throw?

Thanks a lot! 
I would first check in the f8r calibrations if it is calibrated well. Normally it should have a full range from zero to full with a little offset at the ends. 
In the mapping you can look up which values it generates and that should go from 0 to FFF. 
It is possible to manipulate the incoming data so it will be corrected and uses the full NerdSEQ range. But I would first check if and why the f8r is not using the full data range.

Thank you, I am indeed getting the full data range for the faderbank from zero to FFF in the mapping, and the full range when checking the online calibration (including midi).
Once plugging everything back in the problem still persists (using a Vector Wave and a Basimilus Iteritas Alter for testing). I changed the offset coming from the Nerdseq from 10v to +-5v, however this did not fix the issue.

 I checked the calibration of CV1, and now it appears that the CV1 is not outputting any CV (CV2 is). I will have to do more testing (maybe a reset, or start from a new project) and report back!

[XORadmin]

First of all, amazing update to the firmware, and an incredible new module with the Multi-IO. This has made me rearrange my modules and incorporate my 16n F8Rbank into the case and learn I2C connections. Well done XOR! This is a very fun and challenging addition to an already impressive sequencer/mini-computer.

I have a question regarding the 16n F8R via I2C on the Nerdseq and applying mapping. I have a fader assigned to control pitch on CV1, and it connects correctly (awesome) however it increases the pitch amount drastically. By the time the fader position reaches 1/4 of the full sweep, the note change goes from C-2 through A-8. Is there a way to spread this note change over the entire length of the fader throw?

Thanks a lot! 
I would first check in the f8r calibrations if it is calibrated well. Normally it should have a full range from zero to full with a little offset at the ends. 
In the mapping you can look up which values it generates and that should go from 0 to FFF. 
It is possible to manipulate the incoming data so it will be corrected and uses the full NerdSEQ range. But I would first check if and why the f8r is not using the full data range.

Thank you, I am indeed getting the full data range for the faderbank from zero to FFF in the mapping, and the full range when checking the online calibration (including midi).
Once plugging everything back in the problem still persists (using a Vector Wave and a Basimilus Iteritas Alter for testing). I changed the offset coming from the Nerdseq from 10v to +-5v, however this did not fix the issue.

 I checked the calibration of CV1, and now it appears that the CV1 is not outputting any CV (CV2 is). I will have to do more testing (maybe a reset, or start from a new project) and report back!

I think you should turn off the mapping with the CV output for the calibration as that might overwrite the output. Best is to do the calibration on an empty project after the NerdSEQ turned on (or after the soft-reset)
0-FFF for the input values is good and it should be around 800/2047 in the middle position. 
If the calibration is right then check if not maybe something else is manipulating the cv output as well.
All in all the 0-FFF input should create a ~ 0-10 / ~ -5+5 Volt.

[circulant]

I think you should turn off the mapping with the CV output for the calibration as that might overwrite the output. Best is to do the calibration on an empty project after the NerdSEQ turned on (or after the soft-reset)
0-FFF for the input values is good and it should be around 800/2047 in the middle position. 
If the calibration is right then check if not maybe something else is manipulating the cv output as well.
All in all the 0-FFF input should create a ~ 0-10 / ~ -5+5 Volt.

Nice, thank you. Empty project confirmed everything is calibrated well, I will continue troubleshooting my sequencing. Now in the i2c mapping from faderbank, the 'Note' out of cv1 seems to respond aggressively, the 'Pitch' seems to behave better, and Transpose' works perfectly.

[XORadmin]

I think you should turn off the mapping with the CV output for the calibration as that might overwrite the output. Best is to do the calibration on an empty project after the NerdSEQ turned on (or after the soft-reset)
0-FFF for the input values is good and it should be around 800/2047 in the middle position. 
If the calibration is right then check if not maybe something else is manipulating the cv output as well.
All in all the 0-FFF input should create a ~ 0-10 / ~ -5+5 Volt.

Nice, thank you. Empty project confirmed everything is calibrated well, I will continue troubleshooting my sequencing. Now in the i2c mapping from faderbank, the 'Note' out of cv1 seems to respond aggressively, the 'Pitch' seems to behave better, and Transpose' works perfectly.

Yes Note works also different and expect values between 0-120 = notenumbers. And the faderbank generates 0-4095. I will check it later on again as well.
Maybe you can share your project so I can take a look?

[circulant]

I think you should turn off the mapping with the CV output for the calibration as that might overwrite the output. Best is to do the calibration on an empty project after the NerdSEQ turned on (or after the soft-reset)
0-FFF for the input values is good and it should be around 800/2047 in the middle position. 
If the calibration is right then check if not maybe something else is manipulating the cv output as well.
All in all the 0-FFF input should create a ~ 0-10 / ~ -5+5 Volt.

Nice, thank you. Empty project confirmed everything is calibrated well, I will continue troubleshooting my sequencing. Now in the i2c mapping from faderbank, the 'Note' out of cv1 seems to respond aggressively, the 'Pitch' seems to behave better, and Transpose' works perfectly.

Yes Note works also different and expect values between 0-120 = notenumbers. And the faderbank generates 0-4095. I will check it later on again as well.
Maybe you can share your project so I can take a look?

Sure thing, here is the project, thanks for looking!