#449

I’m having a similar problem with MLR and LEVELS see here @marcus_fischer

2 Likes
#450

Can anyone point me into a direction how midi mapping is supposed to work, e.g. in MLR?
It seems like noone is using a Launch Control, but I would be curious if it is user mistake on my side or Norns and the Novation Launch Control just don’t play too well together. Unluckily I just do not have another knobby USB midi controller at hand to “try again”. Thanks!

1 Like
#451

I can confirm this is also happening here, also with a Qunexus.

#452

@marcus_fischer @sno update just about ready that fixes TAPE to it’s earlier state. also fixes midi/grid collision issues

will get a midi routing tutorial up.

be aware that some midi controllers (especially those with encoders) send out delta positions, ie +1 -1 when knobs are turned. this will not map correctly without some intervening software.

4 Likes
#453

Ah, ok, Thanks!
Also, if there is a list of “known to work” controllers, it would be good to list these… I would really love to be able to map some stuff in MLR and Glut for quicker access.

2 Likes
#454

anything that sends out a standard 0-127 value cc will work. and on the todo list is a feature for translating incremental cc’s like endless encoders where the controller itself doesn’t create a proper mapping (the op-1 doesn’t map cc’s properly, for example)

2 Likes
#455

Hey @tehn, I installed the update this morning and I’m still having problems w/ Levels and basically getting any audio into any of the norns scripts that accept external audio sources.
If I plug my OP-1 into Norns and bang away on the keys, I can hear the audio coming through just fine but nothing registers on the Levels page. No input is shown and the sound I hear is not effected in any way by where the knobs are set in output, input or mon. it all comes through at the same volume.
I have rebooted a number of times and nothing seems to help.
Any ideas on what’s going on? thanks!

#456

@marcus_fischer i’ll triple-check now and try to figure out a quick-fix for you

edit: indeed, mine is working fine. can you try loading “awake”, shutting down, boot up, then load “jah/shifty” and let me know if the monitor/levels don’t work still?

FYI the input knob on LEVELS is not functional… i totally forgot to hook this up

#457

Will you be updating the update (so to speak) to fix this?

#458

Damn. Still no luck.
Another thing is the L/R inputs are each only going to the L/R side of the headphones even if monitoring is set to mono. It’s like anything I plug in is just bypassing levels and other scripts and is just going straight back out.

#459

ok. i’m writing up a guide to do a full disk wipe/restore. thanks for your patience

@bobbcorr it’ll get in the next update :slight_smile: https://github.com/monome/norns/issues/544

2 Likes
#460

You’re the best, @tehn - I promise if you keep standing up the updates, I’ll keep applying them :smile:

2 Likes
#461

Thanks brian!!
(20 characters)

2 Likes
#462

Would it be useful to check alsamixer to see if input levels are set properly?

alsamixer should be there on the system, shouldn’t it?

#463

alsamixer is controlled by service startup, and has no control for the input gain level or routings. https://github.com/monome/norns-image/blob/master/config/norns-init.service#L21

#464

Ah right… darn. A shot in the dark there (having had problems like this on various RasPi audio projects).

#465

What’s the recommended way of assigning an action to a MIDI CC or multiple CCs within a script?

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

-- process incoming midi
mo.event = function(data) 
  tab.print(midi.to_msg(data)) -- shows you all the incoming data
    if data[1] == 176 then -- this is the status message for a CC on channel 1
     -- do stuff with value from data[2]
    end
end

full list of midi status bytes here

1 Like
#467

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
Friends of norns: gear, accessories, etc
Friends of norns: gear, accessories, etc
#468

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