#480

Score. Thanks for that.

3 Likes
#481

Question on jitter - I’m seeing it a bit in testing my build today.

Do I need to update the ResponsiveAnalogRead library in any way for this fix?

I’ve tried the 1.34 hexes and recompiling myself, but still getting jitter

some midi monitor output
19:23:06.556 From 16n Control 1 38 126
19:23:06.560 From 16n Control 1 43 126
19:23:06.561 From 16n Control 1 33 126
19:23:06.563 From 16n Control 1 39 126
19:23:06.595 From 16n Control 1 39 127
19:23:06.598 From 16n Control 1 33 127
19:23:06.602 From 16n Control 1 43 127
19:23:06.615 From 16n Control 1 38 127
19:23:06.717 From 16n Control 1 32 127
19:23:08.048 From 16n Control 1 32 126
19:23:08.074 From 16n Control 1 38 126
19:23:08.074 From 16n Control 1 43 126
19:23:08.092 From 16n Control 1 39 126
19:23:08.092 From 16n Control 1 46 126
19:23:08.092 From 16n Control 1 33 126
19:23:08.096 From 16n Control 1 36 126
19:23:08.150 From 16n Control 1 34 126
19:23:08.153 From 16n Control 1 47 126
19:23:08.177 From 16n Control 1 37 126
19:23:08.177 From 16n Control 1 42 126
19:23:08.276 From 16n Control 1 45 126
19:23:08.471 From 16n Control 1 45 127
19:23:08.477 From 16n Control 1 37 127
19:23:08.478 From 16n Control 1 42 127
19:23:08.495 From 16n Control 1 47 127
19:23:08.504 From 16n Control 1 34 127
19:23:08.514 From 16n Control 1 36 127
19:23:08.514 From 16n Control 1 46 127
19:23:08.517 From 16n Control 1 33 127
19:23:08.517 From 16n Control 1 39 127
19:23:08.522 From 16n Control 1 43 127
19:23:08.534 From 16n Control 1 38 127
19:23:08.562 From 16n Control 1 32 127
#482

awesome! where did you find the fader caps?

#483

You can manipulate the parameters for RAR to fit your build and how you want the 16n to behave.

Changing those parameters will manipulate the easing and whether or not the values should “sleep”. The initial tunings worked well for my prototype builds, but given different component tolerances and voltage sources, you may need to tweak them a bit. Also, the new addition of the setActivityThreshold call on line 111 may have “detuned” the jitter reduction of the algorithm.

Instructions on the parameters are here:

If you play with it, let us know what works for you. I’ll peek at it too when I get a moment.

2 Likes
#484

It took my a while to actually get this completed. I had the PCB and BOM back in February, but only just got the panels, standoffs and fasteners last week. The only thing I wish was that the grey switch caps were a little darker.

image
2D6C9123-9DF0-4826-9DA1-8438DBF9B351.jpeg1440×1079 147 KB

2 Likes
#485

trying to solve a weird 16n + norns bug…

will be working fine for many mlr sessions. then one day:

(A) norns/mlr shows no response to 16n

or, if it is working

(B) norns/mlr will at some point visually stop responding, while audio continues. sometimes after a long wait i’ll be able to regain control over the UI - other times a hard reset is my only option.

my solution?

reflash the 16n firmware. works every time!

no idea what’s going on or how that fixes it…

#486

To clarify - this is usbmidi from 16n to norns? And… using midi learn from 16n to control various params?

Random guess - I wonder if you’re getting flooded with midi messages (jittery fader values maybe?) and somewhere in MLR they get all bogged down.

Does just unplugging/replugging (power cycling) the 16n make any difference?

#487

yes & yes

i have wondered the same thing. i haven’t tried the latest firmware yet - will run that for a while and see if it comes back.

sometimes - but mostly no. it’ll get to a point where i’ve rebooted both the 16n and norns a few times, and relaunched mlr with no luck. a reflash to 16n firmware will set everything straight again.

#488

These right angle cables may be helpful for folks like me who need to tuck their 16n close to something behind it.

Tendrils right angle cables

#489

How sturdy is this case and does it hold the 16n tightly enough?

Thanks.

#490

That won’t work with i2c as they are mono cables.

#491

I use a stereo cable that’s one right angle end, one straight end. In bright red with metal ends just so I never confuse it for my normal patch cables. :slight_smile:

2 Likes
#492

I don’t know about i2c, I’m only using the 16 cv outputs from the 16n…

#493

Ah, ok. In the past, there have been some folks using mono plugs with i2c and it caused some confusion. That will work fine for the CV outs, yes.

1 Like
#494

Its fairly rigid and 16n doesn’t move when its closed

1 Like
#495

Just tried my 16n for the first time as a midi controller and although Ableton live receives the midi signal on the top right corner, when I try to map it to a parameter, it’s doesn’t move it at all.
Anyone experienced this, I might be missing something really simple but I’m not figuring it out.

#496

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

Enjoy!

2 Likes
#497

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.

1 Like
#498

and so my day was saved. Thank you

1 Like
#499

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 ?