ok guys…
i need an idiots guid to the 16n and MLR.
and i do mean IDIOT’s guide…
:stuck_out_tongue:

do i need to connect the microUSB for power or does it just power it from the norns USB connection?

norns saw the device at first without the microUSB power but then while i was making adjustments i deleted it from the list of MIDI devices. i then could not get it back since it would not show up in the MIDI device list until i powered norns completely off with SLEEP and then powered back up.

it is currently connected to norns with the standard miniUSB and without the microUSB power.

there are NOT any options on the parameters page that i can see that would allow me to connect a fader/controller to a parameter.
all i see is the variable settings for each parameter.

running latest OS for norns and latest MLR.

am i missing something?

thanks for any help!!!

1 Like

just the connection to norns is required.

  • make sure that your 16n is connected to norns.
  • make sure that it is listed and selected in the devices/midi menu.
  • navigate to the mlr parameter menu.
  • hold key1 to bring up the pset save/load/midi mapping page.
  • navigate to midi-cc mapping with enc2
  • use enc3 to turn midi-cc mapping on.
  • release key1

you can now use enc2 to scroll to the param you want to map. press key3 to select the param you wish to map, then move the 16n slider. mapping accomplished!

to exit the mapping menu, and return to mlr, just press key1.

hope this helps! :sweat_smile:

4 Likes

Could you use MLR with a MIDI 128 controller (not monome Grid)?

No, the main interface is written specifically for the grid. You could, however, use bits of the code and build something similar.

1 Like

THANK YOU THANK YOU THANK YOU!!!

got it working just now!

oooo…neato…

1 Like

ok…
ran into a small issue.
the 16n sends CCs 32-47.

so FADER 3 sends CC #34 which is Breath Control.

for some reason MLR or norns will not respond to #34.

i tested every fader as well as hooked the 16n to the mac and launched the app MIDI Monitor to make sure everything was working.
(i thought i had a defective 16n for a second)

is there a fix for that?
or…do i need to figure out how to change the CC that the 16n sends?
(which i have no idea how to do)
:stuck_out_tongue:

edit…
so i looked into it…and yeah…that’s a bit of work to update it.
probably will break if i do it.
:expressionless:

i did a quick test this am. fader 3/ cc 34 works fine for me with mlr… could there be a problem with your 3rd fader?

1 Like

I think I’ve run into this as well with my 16n… occasionally one fader won’t register when trying to midi map norns parameters to it (various scripts, not isolated to MLR). 16n plugged directly into laptop has no problems midi-mapping all faders, so don’t think there is a build issue. The odd thing though for me is that these issues don’t occur every session–a lot of the time everything works fine, but then on next boot up it can reoccur. One workaround was to manually map midi CCs, rather than learning, but never really got to the bottom of it…

1 Like

Can confirm here too. Been awhile since I’ve paired the 2 together, but turning both off and on again (once or a few times) seemed to eventually fix it.

1 Like

well…
i had contacted Michigan Synthworks and he suggested checking the 16n with a MIDI scanner.

everything shows up fine on there.
here’s a screen shot of fader 3.

after seeing the other responses…i will try it again in a few mins now…

edit…





oh frack!
i accidentally hit Button 3 on norns and discovered the LEARN function for MIDI CC!!!
i know i rush into this stuff but i did not see anywhere that there was a MIDI CC “LEARN” function.
i was assigning them by hand like i do on most of my noiz gear.
:stuck_out_tongue:
NOW…fader 3 (CC# 34 BREATH) works perfectly!

Thank you for the help guys!

1 Like

another episode of LATE NIGHT NOIZ FOR LATE NIGHT FIENDS thanks to the help of getting me going with the 16n…using it on a norns with MLR and another norns using MANGL:

https://www.facebook.com/Astrogenic.Hallucinauting/videos/2386198834953481/

thanks!

3 Likes

So the prelim docs 404 when clicked. I know a lot of docs have been moved around, where does this live now?

Has anybody used the midi start/stop? I’ve not been able to figure that out…

I had trouble too. Was trying to send midi clock from the opz and send a clock out of crow. Crow worked fine but norns didn’t respond to the midi clock and the opz was selected in devices.

looking at the current state of the code, I don’t believe MLR takes incoming clock. midi sync appears to just send clock out.

I don’t see any midi start/stop events in the code.

just an FYI on an error…

while using MLR…norns seems to lock up after ten or 15 mins…

MLR keeps running.
in fact i was controlling it from a grid and using a 16n for another installment of LATE NIGHT NOIZ FOR LATE NIGHT FIENDS:
https://www.facebook.com/Astrogenic.Hallucinauting/videos/2525487354202464/

the main screen of Audio Outs and Ins was displaying but i could NOT get back to the MLR program display.

in fact…i just woke up norns (the display went to sleep) to check on it again…and it will navigate through the system screens (audio, tape, system, parameters) but it just will not go back to the MLR program.

my guess is screen redraw is throwing some error, maiden REPL should reveal a thing

2 Likes

Is anyone able to record a perfect loop of ansible kria using the crow clock outs and mlr?

Here’s an example of what I’m trying to do:

  1. create a 16 step sequence on kria, clocked by crow
  2. start a 16 step loop on the “cut” page in mlr, and manually start and stop recording for that loop.

The loops never seem to run at the same speed. Im guessing its because clock is based on the quantize param, but I’m not sure how it could work differently.

2 Likes

do you have quantize and tempo mapping enabled?

1 Like