working on the midi study now.

presently best way to use midi cc is to map it to a parameter using the parameter menu.

hold KEY1, scroll down to mapping, set to on. release KEY1. scroll to parameter to be mapped. KEY3 to learn. move midi thing. exit midi mapping mode same as you entered.

5 Likes

jumping ahead, here’s a better way:

-- connect to port 1 (which is set in SYSTEM > DEVICES)
local mo = midi.connect(1) 

-- process incoming midi
mo.event = function(data) 
  d = midi.to_msg(data)
    if d.type == "cc" then
     -- do stuff with d.cc (cc number) and d.val (incoming value)
    end
end
6 Likes

fantastic!

but for the kids at home, pls note this change (as the above will syntax error):

if d.type == "cc" then

2 Likes

thanks @okyeron!! typing too fast

Not sure if this is posted elsewhere. Did some searching but didn’t find anything.

Just purchased a norns with the most recent run. I don’t have a grid or arc. I do have a teletype.

Will I be able to get somewhere with just a midi keyboard/sequencer? Feel free to link if this was brought up elsewhere.

1 Like

yep, plenty to do without grid. it’s long but the Approaching thread is worth going through.

edit: more specifically to your question, here (and this was before more non-grid scripts were added): Approaching: norns

1 Like

I haven’t experienced any major issues with the latest update, save for one I’ve been able to replicate twice now: if I connect my USB drive to the third slot from the right (looking straight down at Norns), the light on the key itself flickers rapidly and Norns freezes up. If I disconnect the USB key, Norns immediately becomes responsive again.

Edit: I originally thought the problem was specific to a single USB port, but I’ve able to replicate the issue now with a couple of them.

Started to notice that my Norns is monitoring sound inputs a bit off balance with more passing though the right channel.

I tested through the headphone out and the main outs with the same result. I started noticing while running MLR that after I would finish recording source material that when it started to play back it would balance itself out.

Has anyone else experienced this? Seems to be it would be software related as it’s behaving the same on both the headphone out and main outs.

The only place inside Norns that I thought may fix this was in the Audio settings under aux input pan settings but it had no affect.

**edit - upon further investigation if I go into the Audio settings and turn the monitor down to -inf db I get sound just coming in through the right channel. I’m guessing when I reboot it will be fixed but don’t want to test just yet as I’ll be losing my buffers

A reboot fixed the issue.

Quick question: how do I force power off? I’m locked up in the wifi screen and cannot exit or select anything (although I can scroll through the Off, Hotspot, Network options).

The little button on the bottom should do it for you.

2 Likes

Thanks! I must have missed something. Wasn’t obvious to me.

Echoing this. Jumped into the new update today to do some studying and I kept getting freeze-ups and and even one where it refused to boot at all. I usually put my USB drive in that third port, but removing it and everything works as expected.

Is there a way to map midi to the reverb controls?

Also, it would be rad if you could chose the transposition interval so that it would step thru 2nd 3rd 5th or octaves.

See here for midi cc mapping:

1 Like

Hi there - I have all older grids (because they are so beautiful) and wondering if anyone is using monobrights grids with Norns, especially with mlr. Any insight on experiences would be incredibly helpful.

i have a gray scale 128 that i’ve been using with norns, especially mlr. the only thing thats tricky is the 'reverse" column on page 1. i just put a very small piece of tape on the top of the grid to allocate myself. that row lets me know what clips are playing in reverse while also showing me the 4th pattern recorder button. mlr works great with the gray scale 128 in my opinion. its incredibly intuitive and fun to use.

1 Like

New Norns owner here. I’ve been running MLR through its paces. Just sampling one or two tracks at a time and letting it run for 15-20 minutes to see how stable it is. Regrettably, the sound engine reliably craps out after that same amount of time: a “pop” and then Norns is no longer able to process or produce sound. The interface still works: I can select another program, Awake for example, but no sound is emitted. Running the latest software version. Hard rebooting naturally rights everything.

What’s the consensus on MLR’s stability? Not quite ready? Or am I missing something?

unfortunately there might be some sort of regression which affected stability. i’m looking at it now.

previously i ran mlr for hours and had no issue with it live in a high-pressure situation.

we’ll get it back to stable this week, i’m sorry for the trouble.

1 Like

New Norns user here.

I have a E-MU XMidi1X1 Midi interface that I use to connect my sound interface and the Norns. Norns recognizes the interface in SYSTEM>DEVICES>MIDI but doesn’t seem to respond to any MIDI events. I’ve tried Passerby to test the MIDI (nothing) and then wrote some test code to see if it was detecting any MIDI events and it did not. Does anyone know a reason why this interface wouldn’t work? What are recommended ways to get MIDI into Norns from a desktop DAW?

Thanks!

I was able to set up the Digitakt and control parameters. I think it’s based on which script you’re running. For example, in Rebound, if you go to Parameters and then hold KEY1, you’ll see:

  • load
  • save
  • midi-cc mapping off

Change it to ‘on’ and then let go of KEY1 to return to the Parameters. You should now see a list of options. If you highlight ‘cutoff’ for example, and click KEY3, it will say (learn), then turn a knob or something on your midi controller.

This worked for me. I hope I explained that well enough.

4 Likes