#396

Thanks for the offer! Let me make sure it’s not hiding somewhere on my workbench first

1 Like
Sixteen-N Faderbank
#397

I tried recompile with MINFADER 0, but I can’t see any change. When at 0, it’s still putting out a bit signal - seems as if it’s the same value as before.

I shut the LED lights to check if the code is compiled properly, so I guess it should be correct.

#398

I too cant seem to get MINFADER to output 0 even when the firmware is adjusted. Using i2c, via telexb, and polling FADER X with teletype. Ive tried setting MINFADER to negative values as well with no luck. When set around 200 the values get the lowest, but its still not 0.

Side note: The usb mini seems super fragile, im worried it might get ripped off the teensy oneday, does anyone know of a solution to fortify this connection…cables or adapters or something?

#399

You could try a MagSafe adapter maybe

2 Likes
#400

thanks! a break away adapter would feel much safer, Ill give it a shot.

#401

Yo, is anyone working on a variation of the fader bank that would fit in a euro format module?

2 Likes
#402

Hey guys!

Would be insanely cool with an option to define each faders output range (midi or i2c) individually. Any possible way to do this now? Couldn’t find anything about it in the config part of the code.

#403

Couldn’t you simply do that on the MIDI side, with scaling?

1 Like
#404

Thanks for chiming in - I’m not sure what you mean exactly?

#405

I was immediately thinking of doing it in Max/MSP with scale, but I’m sure there’s other utilities that can set the min/max CC or note range. Someone else might know the answer to that. I’d imagine it’s pretty simple in Ableton

#406

Yeah, I think in Ableton you can set this in Midi Mapping mode (CMD+M). Once you’ve mapped a 16n CC to a parameter, you should see options to set the min and max.

#407

Of cause there is a lot of options outside the 16n, depending on what you’re using it with.

However, I’m interested in an option for doing this on the 16n itself.

I am using 16n in a eurorack setup controlling two ER-301’s over I2C and other modules with MIDI to CV through a Cirklon sequencer. At the moment I’m using a Faderfox UC4 which has the ability to scale the outgoing MIDI from the faders. This is a great feature as you don’t necessarily have the possibiliy to scale outside the faderbank in all scenarios. It would save processing power and space :slight_smile:

#408

What is the clearance on the pcb+components? would it ever fit in a housing the same height as the arc/grid?

1 Like
#409

What would that look like, in your mind? To me, one of the benefits of 16n (admittedly, I don’t have one, but I really want one!) is its simplicity. Once you start adding a screen and encoder, things get considerably more complex and $$.

#410

the right angle jacks are right at 10mm

you might get a 2-3mm shorter panel height by doing a cutout for those jacks, but would look kinda interesting.

Problem then is your fader “tangs” would appear longer - not a problem with buchla nubs, but with regular fader caps they’d be floating far off the panel.

#411

Well, I’m just asking if individual ranges could be implemented as a config option in the code.

1 Like
#412

This is the fader used; its body is 7mm high. The PCB is 1.6mm thick. That’s the limiting factor in terms of height. The currently used jack sockets - which are cheap - are about 10mm high, and that’s how high the standoffs at the top are; you could definitely get that thinner with different jack sockets.

Getting it down to grid height is certainly doable, but not with the current BOM. If you changed the jack parts for something thinner (either SMT, or similar to the MIDI/I2C jack parts), that might get you there with standoffs. The milled case that the monome products use certainly helps in terms of mounting things more thinly.

#413

EDIT: I just saw that you wrote I2C, not midi :upside_down_face:
EDIT2: Looks like it should work anyway, since it’s mapped before the bit shifting.

I think it would be fairly easy. I don’t have a 16n myself, but looking at the firmware, what I would do is change the max value for the mapping here:
temp = map(temp, MINFADER, MAXFADER, 0, 16383);

to something like:
temp = map(temp, MINFADER, MAXFADER, 0, mapMax(i));

And then instead of having 16383 hard coded, make an array of your max values you can look up:
int mapMax[16] = {'max1','max2','max3',.......}

Of cause it wouldn’t be as dynamic as the faderfox.

1 Like
#414

They absolutely could.

I note that the initial MINFADER/MAXFADER scale is to do with scaling the input to reflect that it’s 0-3.2ishv, rather than 0-3.3v in range.

After that, however, it’d be possible to add a [16][2] sized array, with min/max for each fader read, and apply that scaling as the faders are each read. Around this line is the point to do the scaling. There are a number of ways of making the setting of that scale array tidy/neat.

2 Likes
#415

I was wondering about the faders you used, is it normal they don’t light up? or did I do something wrong :slight_smile:

1 Like