I have one on order…will update when i get my grubby little mitts on it.

Hello there,
I noticed that my 16n doesn’t seem to reach full midi values (127) at the maximum throw of the faders. has anyone else had this issue?
I saw three posts on the GitHub w/ no resolution https://github.com/16n-faderbank/16n/issues/26

any help would be appreciated.

1 Like

I’ve noticed this happening depending how it’s powered. I had it plugged into my computer via a hub and that was enough to lesson the voltage it was operating with, which I think in turn affected the max midi value.

weird… Via computer or via norns the result is the same.

Have you tried a different usb cable and did it just start happening?

I’ve been experiencing the same issue. Just built mine, new firmware. This occurs when plugged in to my norns or the computer. I will test with a different wire just to check.

If, for example, I’m using this with mlr on norns, my max levels are .97 regardless of the wire.

Seems like a calibration routine is in order

1 Like

i believe that these values (in config.h) can be adjusted to narrow the min/max range.

47%20PM

sounds like max is out of range, so decreasing that value slightly should help…

2 Likes

I apologize if this has already been asked, but is it possible to control a DAW and Modular at the same time?

EX: Faders 1-8 controlling parameters in ableton and faders 9-16 controlling CV on a eurorack?

Yep, it totally is.

You’d connect the voltage outputs of 9-16 to your CV inputs on eurorack. You can use the MIDI outputs of channels 1-8 in your DAW, either via the hardware MIDI, or via USB.

Powering it from your computer’s USB whilst connecting it to Eurorack should work, but there’s an upper bound to the current a computer can supply over USB, and if you run into issues there, powering the 16n over USB and using the minijack MIDI out might be a safe bet.

2 Likes

yes. Any fader will give values simultaneously on USB-Midi, CV out, I2C out, mini-jack MIDI.

3 Likes

Are there hex files available to update the 16n? Or is the only way of updating to compile?

I’m running into some errors and am not sure if I’m doing this right or have a setting inside of the Arduino application wrong. I do see the error for multiple midi libraries but need some help


/Applications/Arduino.app/Contents/Java/arduino-builder -dump-prefs -logger=machine -hardware /Applications/Arduino.app/Contents/Java/hardware -tools /Applications/Arduino.app/Contents/Java/tools-builder -tools /Applications/Arduino.app/Contents/Java/hardware/tools/avr -built-in-libraries /Applications/Arduino.app/Contents/Java/libraries -libraries /Users/prnts/Documents/Arduino/libraries -fqbn=teensy:avr:teensy31:usb=midi,speed=120,opt=o2std,keys=en-us -ide-version=10810 -build-path /var/folders/yl/f4y5029521qf_0nfc3w7zh_h0000gn/T/arduino_build_488581 -warnings=none -build-cache /var/folders/yl/f4y5029521qf_0nfc3w7zh_h0000gn/T/arduino_cache_387006 -verbose /Users/prnts/Music/Hardware Backups & OS/16n-master/firmware/_16n_faderbank_firmware/_16n_faderbank_firmware.ino
/Applications/Arduino.app/Contents/Java/arduino-builder -compile -logger=machine -hardware /Applications/Arduino.app/Contents/Java/hardware -tools /Applications/Arduino.app/Contents/Java/tools-builder -tools /Applications/Arduino.app/Contents/Java/hardware/tools/avr -built-in-libraries /Applications/Arduino.app/Contents/Java/libraries -libraries /Users/prnts/Documents/Arduino/libraries -fqbn=teensy:avr:teensy31:usb=midi,speed=120,opt=o2std,keys=en-us -ide-version=10810 -build-path /var/folders/yl/f4y5029521qf_0nfc3w7zh_h0000gn/T/arduino_build_488581 -warnings=none -build-cache /var/folders/yl/f4y5029521qf_0nfc3w7zh_h0000gn/T/arduino_cache_387006 -verbose /Users/prnts/Music/Hardware Backups & OS/16n-master/firmware/_16n_faderbank_firmware/_16n_faderbank_firmware.ino
Using board 'teensy31' from platform in folder: /Applications/Arduino.app/Contents/Java/hardware/teensy/avr
Using core 'teensy3' from platform in folder: /Applications/Arduino.app/Contents/Java/hardware/teensy/avr
Detecting libraries used...
/Applications/Arduino.app/Contents/Java/hardware/teensy/../tools/arm/bin/arm-none-eabi-g++ -E -CC -x c++ -w -g -Wall -ffunction-sections -fdata-sections -nostdlib -fno-exceptions -fpermissive -felide-constructors -std=gnu++14 -Wno-error=narrowing -fno-rtti -mthumb -mcpu=cortex-m4 -fsingle-precision-constant -D__MK20DX256__ -DTEENSYDUINO=148 -DARDUINO=10810 -DF_CPU=120000000 -DUSB_MIDI -DLAYOUT_US_ENGLISH -I/Applications/Arduino.app/Contents/Java/hardware/teensy/avr/cores/teensy3 /var/folders/yl/f4y5029521qf_0nfc3w7zh_h0000gn/T/arduino_build_488581/sketch/_16n_faderbank_firmware.ino.cpp -o /dev/null
Alternatives for i2c_t3.h: [i2c_t3]
ResolveLibrary(i2c_t3.h)
  -> candidates: [i2c_t3]
/Applications/Arduino.app/Contents/Java/hardware/teensy/../tools/arm/bin/arm-none-eabi-g++ -E -CC -x c++ -w -g -Wall -ffunction-sections -fdata-sections -nostdlib -fno-exceptions -fpermissive -felide-constructors -std=gnu++14 -Wno-error=narrowing -fno-rtti -mthumb -mcpu=cortex-m4 -fsingle-precision-constant -D__MK20DX256__ -DTEENSYDUINO=148 -DARDUINO=10810 -DF_CPU=120000000 -DUSB_MIDI -DLAYOUT_US_ENGLISH -I/Applications/Arduino.app/Contents/Java/hardware/teensy/avr/cores/teensy3 -I/Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/i2c_t3 /var/folders/yl/f4y5029521qf_0nfc3w7zh_h0000gn/T/arduino_build_488581/sketch/_16n_faderbank_firmware.ino.cpp -o /dev/null
Alternatives for MIDI.h: [MIDI@4.3.1]
ResolveLibrary(MIDI.h)
  -> candidates: [MIDI@4.3.1]
/Applications/Arduino.app/Contents/Java/hardware/teensy/../tools/arm/bin/arm-none-eabi-g++ -E -CC -x c++ -w -g -Wall -ffunction-sections -fdata-sections -nostdlib -fno-exceptions -fpermissive -felide-constructors -std=gnu++14 -Wno-error=narrowing -fno-rtti -mthumb -mcpu=cortex-m4 -fsingle-precision-constant -D__MK20DX256__ -DTEENSYDUINO=148 -DARDUINO=10810 -DF_CPU=120000000 -DUSB_MIDI -DLAYOUT_US_ENGLISH -I/Applications/Arduino.app/Contents/Java/hardware/teensy/avr/cores/teensy3 -I/Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/i2c_t3 -I/Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/MIDI/src /var/folders/yl/f4y5029521qf_0nfc3w7zh_h0000gn/T/arduino_build_488581/sketch/_16n_faderbank_firmware.ino.cpp -o /dev/null
Alternatives for ResponsiveAnalogRead.h: [ResponsiveAnalogRead@1.1.0]
ResolveLibrary(ResponsiveAnalogRead.h)
  -> candidates: [ResponsiveAnalogRead@1.1.0]
/Applications/Arduino.app/Contents/Java/hardware/teensy/../tools/arm/bin/arm-none-eabi-g++ -E -CC -x c++ -w -g -Wall -ffunction-sections -fdata-sections -nostdlib -fno-exceptions -fpermissive -felide-constructors -std=gnu++14 -Wno-error=narrowing -fno-rtti -mthumb -mcpu=cortex-m4 -fsingle-precision-constant -D__MK20DX256__ -DTEENSYDUINO=148 -DARDUINO=10810 -DF_CPU=120000000 -DUSB_MIDI -DLAYOUT_US_ENGLISH -I/Applications/Arduino.app/Contents/Java/hardware/teensy/avr/cores/teensy3 -I/Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/i2c_t3 -I/Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/MIDI/src -I/Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/ResponsiveAnalogRead/src /var/folders/yl/f4y5029521qf_0nfc3w7zh_h0000gn/T/arduino_build_488581/sketch/_16n_faderbank_firmware.ino.cpp -o /dev/null
Alternatives for CD74HC4067.h: []
ResolveLibrary(CD74HC4067.h)
  -> candidates: []
/Users/prnts/Music/Hardware Backups & OS/16n-master/firmware/_16n_faderbank_firmware/_16n_faderbank_firmware.ino:23:24: fatal error: CD74HC4067.h: No such file or directory
Multiple libraries were found for "i2c_t3.h"
compilation terminated.
 Used: /Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/i2c_t3
Multiple libraries were found for "MIDI.h"
 Used: /Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/MIDI
Multiple libraries were found for "ResponsiveAnalogRead.h"
 Used: /Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/ResponsiveAnalogRead
Using library i2c_t3 in folder: /Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/i2c_t3 (legacy)
Using library MIDI at version 4.3.1 in folder: /Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/MIDI 
Using library ResponsiveAnalogRead at version 1.1.0 in folder: /Applications/Arduino.app/Contents/Java/hardware/teensy/avr/libraries/ResponsiveAnalogRead 
Error compiling for board Teensy 3.2 / 3.1.

Yes, hex files are available from the releases page.

1 Like

Was hoping after going to 1.34 the acceleration of the faders would be fixed but it still seems to be the same. At the top and bottom of the throw the values move slowly but then accelerate to a much more sensitive throw. Is everyone else experiencing the same thing on their 16n?

That’s… Very strange.

Over MIDI? Over i2c?

Do you have log faders installed, rather than linear?

Definitely over midi. My build was done by Michigan synthworks so I really don’t know what type of faders they are. I haven’t tested over cv. I don’t really have a way to monitor it visually

1 Like

Ah. You should speak to MSW - I believe there was a period where they may have shipped devices with log faders in. There are ways to resolve this, but I think that may be down to a component issue.

I reached out and you were right. I’m going to send it back for a fix. Thanks for your replies!

I feel like of late I’ve given some bad tips that I’ve had to withdraw :slight_smile: I will share this, and if anyone knows why this might be ill-advised, please speak up.

I have a 16n I just built last night. I do not have a TXb. However, I do have an Intellijel case with midi jacks built in. I also have a couple of stereo 3.5mm-to-midi cables that I made to use with my 0 Coast (which was 2nd hand and came without its original cable).

The Intellijel case has a midi out jack which routes directly to 3 pins. In this photo midi out is the center jack, and the three connector pins are on the right.

By doing continuity tests with my multimeter, I was able to figure out that if I plug my cable into the midi out jack, tip ring sleeve on the 3.5mm jack corresponds to the left center right pins on the internal midi out respectively. Since the 16n i2c is tip ring sleeve = SDA SCL GRD, it was straightforward to wire those midi out pins to my Teletype backpack.

I haven’t done extensive testing yet, but Teletype reads the faders just fine this way. My midi cable is rather long, so I might fashion a just-long-enough version of the cable to improve communication, if that seems necessary.

If you have a 3.5-to-DIN midi cable from Arturia, just note that those are wired differently. You would probably just have to swap the position of SDA & SCL coming out of the 3 pins of the Intellijel midi out, though I would do continuity tests to confirm that.

I’m psyched though, since TXb’s are currently hard to come by, and I wasn’t looking forward to sneaking some i2c wire between panels to get my 16n talking to Teletype. This is a bit more elegant.

4 Likes

See my post directly above…if you’re not using the MIDI out on your case, you can probably use that for i2c.

1 Like