Multi-IO Expander

[Inkog]

My Multi-IO should be here tonight! I'll design and post up a .stl file for 3d printing a cover for the I2C ports once it arrives.

[diffrentstrolks]

Good point; ordered!

Last question-- the edit encoder on my expander is loose/wobbly and there is a soft "click" or bump if I press down on the knob. For comparison, I'm using the Klavis CalTrans and NE Sinc Iter eurorack modules which have endless encoders that are very firm (i.e. the posts don't move if I nudge them with a finger) and have a hard "click" when pressing on them, which operates as a button press.

The Midi-IO knob seems to work fine, but I'd just like to know if it is meant to feel loose or should it be firm like my comparison modules?

Thanks

It’s not a button but only an encoder. What do you mean with wobbly? Is the shaft wobbly? 
The cap is just pressed on the button but shouldn’t be too lose.

Thanks. Yes, the shaft is a little wobbly (i.e. there is movement left/right/up/down if nudged with a finger). It isn't significant, but also not firm/stationary like other modules and synths with encoders that I have on hand for comparison.

Also pushing on the knob from the top has a bump that "feels" like a very soft button/switch, but understood that it is an encoder only.

I'm currently dealing with a different module that has a loose potentiometer shaft that is causing audio to cut in/out when it is touched; the shaft of that potentiometer feels similar to the Multi-IO encoder shaft. That said, I'm not seeing any glitchy/jumping values when touching the Multi-IO knob, so we're probably ok?

Thanks again

[kriskeyman]

I have F8R successfully controlling probability of Midi track 1, note column 1. However, with slider at max, the value often goes to 63 instead of 64. This is true for all sliders on the F8R when assigned to the same.

I have attempted modifying the json file for the F8R to lower the 'max' value of the sliders, but the issue persists... 63 is just hit earlier when moving the slider up, but rarely hits 64 unless I'm going from 0.

Moving slider from 0 to max sometimes hits 64.
Moving slider from ~40 to max rarely hits 64, but often only goes to 63.

Is there anything I can look to modify so that max slider always hits 64?

Thanks!

[XORadmin]

I have F8R successfully controlling probability of Midi track 1, note column 1. However, with slider at max, the value often goes to 63 instead of 64. This is true for all sliders on the F8R when assigned to the same.

I have attempted modifying the json file for the F8R to lower the 'max' value of the sliders, but the issue persists... 63 is just hit earlier when moving the slider up, but rarely hits 64 unless I'm going from 0.

Moving slider from 0 to max sometimes hits 64.
Moving slider from ~40 to max rarely hits 64, but often only goes to 63.

Is there anything I can look to modify so that max slider always hits 64?

Thanks!

You can look up in the mappings what values are being generated. Mainly if it does reach FFF. And you could add a simple calculation to it and change the range yourself.
I got to check the 16n here but as far as I remember I could reach the full values.

[XORadmin]

Good point; ordered!

Last question-- the edit encoder on my expander is loose/wobbly and there is a soft "click" or bump if I press down on the knob. For comparison, I'm using the Klavis CalTrans and NE Sinc Iter eurorack modules which have endless encoders that are very firm (i.e. the posts don't move if I nudge them with a finger) and have a hard "click" when pressing on them, which operates as a button press.

The Midi-IO knob seems to work fine, but I'd just like to know if it is meant to feel loose or should it be firm like my comparison modules?

Thanks

It’s not a button but only an encoder. What do you mean with wobbly? Is the shaft wobbly? 
The cap is just pressed on the button but shouldn’t be too lose.

Thanks. Yes, the shaft is a little wobbly (i.e. there is movement left/right/up/down if nudged with a finger). It isn't significant, but also not firm/stationary like other modules and synths with encoders that I have on hand for comparison.

Also pushing on the knob from the top has a bump that "feels" like a very soft button/switch, but understood that it is an encoder only.

I'm currently dealing with a different module that has a loose potentiometer shaft that is causing audio to cut in/out when it is touched; the shaft of that potentiometer feels similar to the Multi-IO encoder shaft. That said, I'm not seeing any glitchy/jumping values when touching the Multi-IO knob, so we're probably ok?

Thanks again

I am pretty sure you are fine. Those are not the cheapest encoders and I expect them to have a long lifecycle.
And if there is an issue some day then I will fix it!

[diffrentstrolks]

Good point; ordered!

Last question-- the edit encoder on my expander is loose/wobbly and there is a soft "click" or bump if I press down on the knob. For comparison, I'm using the Klavis CalTrans and NE Sinc Iter eurorack modules which have endless encoders that are very firm (i.e. the posts don't move if I nudge them with a finger) and have a hard "click" when pressing on them, which operates as a button press.

The Midi-IO knob seems to work fine, but I'd just like to know if it is meant to feel loose or should it be firm like my comparison modules?

Thanks

It’s not a button but only an encoder. What do you mean with wobbly? Is the shaft wobbly? 
The cap is just pressed on the button but shouldn’t be too lose.

Thanks. Yes, the shaft is a little wobbly (i.e. there is movement left/right/up/down if nudged with a finger). It isn't significant, but also not firm/stationary like other modules and synths with encoders that I have on hand for comparison.

Also pushing on the knob from the top has a bump that "feels" like a very soft button/switch, but understood that it is an encoder only.

I'm currently dealing with a different module that has a loose potentiometer shaft that is causing audio to cut in/out when it is touched; the shaft of that potentiometer feels similar to the Multi-IO encoder shaft. That said, I'm not seeing any glitchy/jumping values when touching the Multi-IO knob, so we're probably ok?

Thanks again

I am pretty sure you are fine. Those are not the cheapest encoders and I expect them to have a long lifecycle.
And if there is an issue some day then I will fix it!

Sound good; thank you, Thomas!

[stimulusfunctions]

New Multi-IO expander is here. Now begins the long journey with MIDI which I've.. never actually used before, hah. I have a couple of questions.

1. Is there a quick simple routine I can do to just.. check the multi io expander is working? I have it hooked up, I've updated my NERDSeq firmware. I can get to the various screens for it. I am not certain if I need to set something up for the encoder knob to work. The X, Y, and Z buttons do not light up when I push them. The encoder knob on any screen I'm on is currently not causing anything to happen. Note that I *do* see the expander power on when I turn my rack on, and the three X, Y and Z lights light up.

2. If anyone out there has a crash course for getting the Multi-IO expander set up to send the correct MIDI output for triggering the 16 pads on the BitBox, that would be amazing. If no one does then after I figure it out, I'll write one myself in case it would be useful.

[XORadmin]

New Multi-IO expander is here. Now begins the long journey with MIDI which I've.. never actually used before, hah. I have a couple of questions.

1. Is there a quick simple routine I can do to just.. check the multi io expander is working? I have it hooked up, I've updated my NERDSeq firmware. I can get to the various screens for it. I am not certain if I need to set something up for the encoder knob to work. The X, Y, and Z buttons do not light up when I push them. The encoder knob on any screen I'm on is currently not causing anything to happen. Note that I *do* see the expander power on when I turn my rack on, and the three X, Y and Z lights light up.

2. If anyone out there has a crash course for getting the Multi-IO expander set up to send the correct MIDI output for triggering the 16 pads on the BitBox, that would be amazing. If no one does then after I figure it out, I'll write one myself in case it would be useful.

1:

You got to enable the Multi-IO in the NerdSEQ Setup Menu. SHIFT+SETUP -> MIDI Expander, change this to Multi-IO. Leave the menu. It might be possible that you got to restart the NerdSEQ once.

[stimulusfunctions]

New Multi-IO expander is here. Now begins the long journey with MIDI which I've.. never actually used before, hah. I have a couple of questions.

1. Is there a quick simple routine I can do to just.. check the multi io expander is working? I have it hooked up, I've updated my NERDSeq firmware. I can get to the various screens for it. I am not certain if I need to set something up for the encoder knob to work. The X, Y, and Z buttons do not light up when I push them. The encoder knob on any screen I'm on is currently not causing anything to happen. Note that I *do* see the expander power on when I turn my rack on, and the three X, Y and Z lights light up.

2. If anyone out there has a crash course for getting the Multi-IO expander set up to send the correct MIDI output for triggering the 16 pads on the BitBox, that would be amazing. If no one does then after I figure it out, I'll write one myself in case it would be useful.

1:

You got to enable the Multi-IO in the NerdSEQ Setup Menu. SHIFT+SETUP -> MIDI Expander, change this to Multi-IO. Leave the menu. It might be possible that you got to restart the NerdSEQ once.

That is indeed the step I missed! Looking forward to a weekend with this now.

[kriskeyman]

I seem to be getting an unfortunate buzzing computer noise when using the Device USB connection on Multi-IO. Using the MiDI expander before, never had this issue. I can work around this by using the TRS MIDI on the Multi-IO expander, which has no issue. But what would cause this? I’d prefer to use Device USB connection.

I’ve also tried different USB cables and the issue occurs with all.