(04-18-2024, 10:46 AM)XORadmin Wrote:

(04-18-2024, 10:19 AM)pnortnaomi Wrote:

(04-17-2024, 02:34 PM)XORadmin Wrote:

(04-17-2024, 12:21 PM)pnortnaomi Wrote: I just got the 16 trigger and the multi-io at the same time. I didn't have any expanders before. The multi-io lights up the midi triggers and is getting power, it just doesn't send to the Nerdseq. The Trigger 16 expander works well.

Edit - The multi-io setting in the menu saves between power cycles.

OK...did you try the cables? Remove and insert multiple times. And be sure you didn't insert it on the 'thru' port.

I removed the cables a few times and it worked. The new cables are pretty tight and it took 4-5 times unplugging and replugging. Thank you so much for your help.

The drum matrix in the trigger expander is so cool and the encoder has sped up programming considerably, however I never found the Nerdseq to be slow to program.

Previously I was sending midi sync from a Expert Sleepers Fh-2 and that worked great, but now I have an extra 2 ports in it to be used elsewhere.

Before the trigger 16 expander I was triggering 4 tracks from the Nerdseq to 4 mono drums in the Assimil8or leaving only 2 more channels for the rest of system. I was using clock dividers and and a Mimetic Digitalis and a Control Forge to sequence the rest of my modules, and even though I came up with unique sequences, I wasn't able to save the projects as a whole. The trigger expander has fixed this. Thanks

Very nice to hear!  Yes and it can be dirtyness as well on the pins and removing and inserting a few times scratches the dust off.

And very cool that all works out as you wanted to. Just fyi, you could also sequence all the local trigger outputs from a drummatrix even without the trigger expander using the I2C/Multi Track. Not that I don't want to sell Trigger16 :-) But I think it is all fair to say...and one can't have enough outputs anyways!

(09-11-2024, 05:52 PM)kriskeyman Wrote: Hello, I could use some help understanding the following.

I am attempting to set up F8R, CVM-8, and Sweet 16 MKII via I2C.

F8R (leader) connected to Multi-IO I2C-B on rear.
CVM-8 (leader) connected to Multi-IO I2C-A on rear.
Sweet 16 (leader) connected to Multi-IO I2C-A TRS on front.

Current I2C Settings…
I2C A Mode: 16N -> NS 17-32
I2C A In Address: Hex31
I2C B Mode: 16N -> NS 1-16
I2C B In Address: Hex31

… and of course CVM-8 & Sweet 16 are not playing nice with each other.

But I’m confused about this part in the manual explaining how to ‘use 4x 16N faderboxes on one I2C port’…
‘All the 16n got to be set in follower mode though and all need different addresses’.

Does this mean I need to modify the F8R, CVM-8, and Sweet 16 to all be in follower mode, but they will behave as if they are in leader mode (still as MIDI Out per se)?

Any advice on the best way to configure this so that all play nice together is greatly appreciated!

(12-05-2023, 10:43 AM)XORadmin Wrote: Lets start a new thread now it is out of Beta and available.

Note: All the basic stuff about connecting I2C and information you need is provided in the Installation Guide which came with the Multi-IO and in the currently Preliminary Manual for V2.0.

- 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.
- The Front I2C Port and Backside port A are the same and it uses the same Pullup
- Mostly use the 3.3Volt pullup or none if the other gear got already a pullup installed. You can start always without and see if it works reliably or if at all.
- ALWAYS turn all power off before you connect any I2C gear. That applies for the front and backside port
- The 16n and derivates (eg F8R) do scan for any I2C gear 10 seconds after its startup if they are set to leader mode. And if it missed that scan then it won't work. It is possible that it didn't scan the Multi-IO if the I2C port on the Multi was not configured for it. In that case you would configure first and then give the 16n a power cycle. Rule to follow: Use 16n -> NS then the 16n got to be in leader mode, Address to 31hex. If the 16n is set to follower mode then the NerdSEQ got to be set to NS -> 16n 1-16, the address is not important for it.
- No, a 2nd Midi Interface (TRA-A or classic Midi-IO) won't provide an additional Midi Port to the NerdSEQ.
- The encoder is not a push-button

(10-26-2024, 06:26 PM)Tuckles24 Wrote:

(12-05-2023, 10:43 AM)XORadmin Wrote: Lets start a new thread now it is out of Beta and available.

Note: All the basic stuff about connecting I2C and information you need is provided in the Installation Guide which came with the Multi-IO and in the currently Preliminary Manual for V2.0.

- 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.
- The Front I2C Port and Backside port A are the same and it uses the same Pullup
- Mostly use the 3.3Volt pullup or none if the other gear got already a pullup installed. You can start always without and see if it works reliably or if at all.
- ALWAYS turn all power off before you connect any I2C gear. That applies for the front and backside port
- The 16n and derivates (eg F8R) do scan for any I2C gear 10 seconds after its startup if they are set to leader mode. And if it missed that scan then it won't work. It is possible that it didn't scan the Multi-IO if the I2C port on the Multi was not configured for it. In that case you would configure first and then give the 16n a power cycle. Rule to follow: Use 16n -> NS then the 16n got to be in leader mode, Address to 31hex. If the 16n is set to follower mode then the NerdSEQ got to be set to NS -> 16n 1-16, the address is not important for it.
- No, a 2nd Midi Interface (TRA-A or classic Midi-IO) won't provide an additional Midi Port to the NerdSEQ.
- The encoder is not a push-button

Hello,

I have a NerdSEQ Multi-IO expander. Yesterday I used NerdSEQ with the Multi-IO expander and the Sega gamepad expander as I have for months now. Sega gamepad worked with no issues as usual.

Today I powered on with the gamepad plugged into the expander before powering on, like always, and NerdSEQ is not detecting the gamepad controller expander, therefore the gamepad is not working. I tried a firmware update with the same V2.01A firmware, turning off and on multiple times, debugging. I even unplugged the Gamepad Expander from the Multi-IO thru port and plugged in my original Midi IO expander to the Multi-IO Midi Thru port since the manual says that will provide gamepad usage. Despite this, neither gamepad nor original Midi-IO expanders are being detected by Nerdseq when plugged into the Multi-IO Midi Thru port. so i can't use my gamepad. 

I unplugged Multi-IO from NerdSEQ and plugged in the Midi-IO expander to the midi port on the back of nerdseq. It was not detected.

What should I do? I would really like to use my gampad expander and controller

(12-09-2024, 01:53 PM)Simontl Wrote: Hello. I am new to this community and the Nerdseq.

Is it acceptable to connect one source to the I2C Input A minijack on the front panel while simultaneously connecting another source to the I2C Input A pin connectors on the back?

Something like this:

ER-301 (follower) -> Nerdseq (i2c A - pin connectors)
Sweet Sixteen mkII -> Nerdseq (i2c A - minijack input)
Disting EX -> Nerdseq (i2c B pin connectors)

Thank you in advance.

(12-09-2024, 03:03 PM)Simontl Wrote: Oh okay, thank you very much!

Does this mean that I cannot utilize the minijack on the front?

How would you then go about wiring this together on the hardware side?