16n is a bank of faders [release thread]

eblomquist · 2019-09-13T02:28:18.647Z

Go into the preferences and turn on remote for it. I had the same thing last week.

Enjoy!

infovore · 2019-09-13T06:16:56.167Z

Yep, what @eblomquist said. In the midi config options make sure Remote is switched on for the 16ns input. This means it’s CCs will.work globally, not just for an armed track.

Foxhood · 2019-09-13T10:58:29.791Z

and so my day was saved. Thank you

baptiste · 2019-09-25T17:24:28.965Z

I just received my 16n, and trying to set the master flag still kills usbmidi with the 1.34 fw i’ve compiled. I didn’t check i2c connection yet.

Here is the output of the debug :

 16n Firmware Debug Mode
 Enabling i2c in MASTER mode
 MIDI[0]: 6
 i2c Master[0]: 866
 MIDI[1]: 6
 i2c Master[1]: 827
 MIDI[2]: 6
 i2c Master[2]: 770
 MIDI[3]: 6
 i2c Master[3]: 860
 i2c Master[4]: 114
 MIDI[8]: 87
 i2c Master[8]: 11189
 MIDI[9]: 89
 i2c Master[9]: 11393
 MIDI[10]: 64
 i2c Master[10]: 8298
 MIDI[11]: 60
 i2c Master[11]: 7680
 MIDI[12]: 14
 i2c Master[12]: 1843
 MIDI[13]: 24
 i2c Master[13]: 3082
 MIDI[14]: 113
 i2c Master[14]: 14580
 MIDI[15]: 87
 i2c Master[15]: 11240
 i2c Master[0]: 780

This shows up with the monitor window, but then nothing new appears.
Any tip ?

infovore · 2019-09-30T09:43:17.607Z

Hi gang.

So: it turns out there’s a bug in our master i2c code, which means everything hangs if an i2c device isn’t detected. This is what’s causing @baptiste’s problems, and this is also what’s causing problems I have been failing to solve for @marcus_fischer (to my shame) for months now. @okyeron has also been looking into this.

I’m just back from vacation and am slammed with work, but am nearly at a solution: I think the trick is going to be that before we try to send any i2c data in master mode, we make sure the device is connected to an i2c host, and I think there are ways of doing this. So I’m working on that now.

@baptiste, you’ve helped a lot!

infovore · 2019-09-30T10:13:09.814Z

OK, initial update: I think I have a fix for the i2c issue in this branch on github.

It definitely behaves correctly as a MIDI device when i2c master is on but no i2c devices are connected.

However, i don’t have any i2c devices to test it with to prove there is no regression. So: I’d like somebody to take this code, flash it onto a 16n, and then try to use a working i2c master rig. That might well be @okyeron or somebody else who understands that sentence.

(How the fix works: we detect 301/TXo/Ansible at bootup, and if they exist, and we’re in master mode, we send messages to them. If they don’t exist, we don’t send i2c messages to non-existent devices. Phew!)

If this looks good, it can be tidied up a bit and rolled into a new software release.

shellfritsch · 2019-09-30T17:16:15.217Z

well this explains why disabling master mode made my usb midi connection to norns much more stable!

will test this out soon and report back!

infovore · 2019-09-30T19:39:38.532Z

thanks! happy to help out with builds or zips. I’m also taking this opportunity to fixup some mess in the code.

baptiste · 2019-10-01T13:57:31.055Z

Happy to be helpful ! The midi_fix branch solved the issue indeed. I still have to test i2c connectivity with my ER-301 though

eblomquist · 2019-10-02T12:34:26.366Z

I got a 16n in September.

I plan for now to use it mostly for the cv outputs plus occasional midi, but not likely for the II use case.

Is there any need to update it at this point?

Thanks!

infovore · 2019-10-02T14:00:40.294Z

No. If your firmware is in FOLLOWER (or non-master, or whatever you’d like to call it mode), which normally is the default when you download the code, you’re fine to use MIDI and whatever. When there’s a genuine new release that’s tested, I’ll announce it.

okyeron · 2019-10-03T04:26:41.622Z

Quick testing tonight on @marcus_fischer’s faderbank…

I appear to have i2c traffic and usbmidi happening at the same time.

BUT - enabling DEBUG crashes things.

this bit of code has me baffled:

#ifdef DEBUG
  while (!Serial)
    ;
  Serial.print("16n Firmware Debug Mode\n");
#endif

infovore · 2019-10-03T09:38:42.776Z

OK - I will investigate that DEBUG issue in due course.

That line of code: Serial has been kicked off earlier, but may not have connected yet. Whilst Serial connection isn’t established, Serial itself is falsey. So the while loop runs until it’s Truthy, and then off we go.

What this makes me think is that if you don’t have a Serial terminal open, DEBUG mode might never kick off. I had ideas about neatly coralling Serial so it would only work in DEBUG mode, and I was possibly too clever for my own good. Will investigate when I’m tidying.

okyeron · 2019-10-03T14:59:32.088Z

FWIW - the crash with DEBUG i ran into was while the Serial Monitor was open (did not test with it closed).

Also - along with DEBUG I had LED turned on and it did not light up on the Teensy (and no output from i2c or usbmidi).

infovore · 2019-10-04T10:31:43.926Z

Got it. I’ve just pushed a fix to the i2c_midi_fix branch - it was that line you mentioned. Basically, if you’re in DEBUG mode, and your Teensy is set to MIDI+Serial, the board waits for a Serial connection (ie: for a console connection) on bootup. That means if there isn’t one, it loops forever, before the power light even gets turned on.

Removing the infinite while loop fixes this to no ill effect.

This sounds good. Next on my list is continuing the refactoring of the code, which is going alright.

Telestisch · 2019-10-13T15:03:30.407Z

Many thanks for this, just the confirmation I needed. Hope it confirms the queries of others who search for it too.

addamm · 2019-10-26T23:37:04.697Z

Apologies if this should be in a different thread but I’m planning on building a Fates and possibly a 16n. I’m curious if there are any scripts on Norns (or Orac) that people are using their 16n to play around with. I have a modular setup so 16n is appealing regardless and have seen the “I don’t plan on getting Grids, is Norns a waste?” question elsewhere on the forum. Mostly just curious as in my poking around I haven’t seen much of people integrating the two. It’s possible I’m just missing something, too. Thanks!

kasselvania · 2019-10-27T00:07:39.257Z

I’m currently about to get/build a 16n myself. While primarily for VCV Rack (and the eventual Euro Rack that I’m sure my GAS will force me to start building), I could see myself using the 16n a lot. Thing is, with the Norns, it’s a great tool to midi train for certain controls.

Some examples I’ve been thinking about (while not FULLY sure are all possible):

Controlling my awake pattern params when running in to my VCV builds. This way I can control note length and base volocity.

Bpm control for Meadowphysics. Would be sweet to speed up and slow down the cascading patterns as a way to blend between tracks (while loading new racks or queuing up equipment)

The beauty of the 16n being midi/CV/i2c (but mainly Midi on the Norns) is any param that has a midi learn function in the script can be mapped.

Happy patching! (Ps, where you getting your 16n from? You gonna make your own faceplate? Kit or PCB?)

Puscha · 2019-10-27T08:11:15.929Z

I can’t seem to find a link anywhere to the latest firmware and a guide to update. Can someone point me in the right direction? Thank you!

addamm · 2019-10-27T13:35:22.505Z

kasselvania:

The beauty of the 16n being midi/CV/i2c (but mainly Midi on the Norns) is any param that has a midi learn function in the script can be mapped.

Happy patching! (Ps, where you getting your 16n from? You gonna make your own faceplate? Kit or PCB?)

Yeah I suppose I need to dig into the scripts a little more and see how they work and can be interacted with (github is a nightmare for me for whatever reason).

May just get the pcb and panels from pusherman unless someone here on lines has spares.