I am struggling with this as well. Huge difference between input and what’s recorded in MLR. Did you ever find a workaround?

found a bug

when holding alt to start and stop tracks in CUT view, the grid has issues lighting up again when you start it from the same “slice” if you move one slice left or right it normally lights that track back up.

2 Likes

i was just setting this up with some midi cc mapping to my 16n and noticed that there is no entry for “overdub” in the script parameters section from which one does said mapping.

i am hoping that i might find some help hacking that item into the list. even if that means temporarily replacing another item in the list (such as record level) - whatever is the easiest way to make this mod :slight_smile:

1 Like

So, in softcut, feedback/overdub is called pre_level. In mlr, I think the params you are looking for already exist, and are named

1pre
2pre
3pre
etc...

edit: just checked and these are midi mappable

2 Likes

ah thanks for clarifying - i didn’t know what “pre” was referring to.

2 Likes

That took me a while to figure out too.
With that parameter under fader control MLR becomes an awesome seamless overdubbing/looping delay machine

8 Likes

yeah - it’s pretty incredible!
has your experience with midi cc control over mlr been without bugs?
i spent most of a day last week with it working perfectly, but this morning i got a complete lock up of norns (though audio kept going) and had to do a hard reboot. oddly, it wouldn’t respond to 16n after a reboot. testing with ableton showed 16n as a device, but with no outgoing midi. i re-flashed the firmware and was able to get it working with ableton and mlr again.
also, i’m noticing a lot of jitter with mlr values mapped to the 16n - but when i map things in ableton there is no jitter.
wondering if this jitter is somehow connected to the crash.

dang, sorry.

if there is a laptop nearby, i’d always recommend trying to login (via serial or ssh) and do a clean shutdown (sudo shutdown 0). this is to save your filesystem from corruption.

for debugging, it would also be great to see what crashed: journalctl -b if you haven’t rebooted since the lockup, journalctl -b -1 if you’ve since rebooted.

wowee zowie! that’s not great.

1 Like

am i correct in understanding that i’d only be able to do this if i had the wifi nub attached and norns connected to my wifi network prior to the freeze?

is there a way to get this info over ftp? i haven’t learned about serial/ssh interfacing yet…

am i correct in understanding that i’d only be able to do this if i had the wifi nub attached and norns connected to my wifi network prior to the freeze?

nah, you can use the serial port. attach mini-usb from laptop to norns device port, screen 115200 /dev/ttyUSB0 (or whatever the correct device name). this will give you a crummy little terminal but it’s enough to shut down if nothing else.

if audio is running but menu/whatever seems frozen, then almost certainly the system is basically fine but something has got stuck or crashed in lua or matron. (we’d of course like to know what - hunch is something with midi driver. the fact that the 16n has itself become borked makes me suspicious and think i should get my own 16n [or equivalent] to test.)

is there a way to get this info over ftp?

if you just rebooted, something like this on the norns:

journalctl -b -1 > ~/log.txt

then if you get your norns online, you can transfer that from another host with

scp we@norns.local/home/we/log.txt ~/log.txt

(btw, i dont’ happen to have norns in front of me ATM so haven’t tested exactly - caveat emptor… also, the proper linux gurus (e.g. @simonvanderveldt) will surely have better ideas about getting service logs with a minimum of unrelated junk. the command above should dump everything from the last boot, which is way too much but we can always sift through it.)

1 Like

ok i was able to ssh in via wifi, tried journalctl -b -1

> 192.168.1.40 ~ $ journalctl -b -1 
> 
> Specifying boot ID has no effect, no persistent journal was found

That is the same with me. The midi on my 16n is problematic. It worked like a dream at first but now won’t work. It shows up on my computer and in Norns but no messages can be sent. Sometimes it starts working again and other times it won’t. :sob::sob::sob:

interesting. i’ve used 16n with midi a lot (via ableton) with no issues.
recently i switched i2c to “master” mode for direct use with the er-301… i wonder if i that is connected to this issue. when i just reflashed the 16n firmware i disabled i2c master mode and it’s working fine (so far!).

have you tried reflashing the firmware to get midi working again?

ok sorry for the red herring, I’ll work on the correct invocation

2 Likes

teeny bit of portasound and mlr-ing from my trip to norns

6 Likes

Yes. That would be so great.

1 Like

Can anyone explain to me how to use midi sync? Struggling to find an answer through the thread. Ideally would like to tempo sync mlr with Ableton. Sorry for repeating a question that seems to have been asked 1000 times - just seems like i’m missing something here. (And maybe a better question is whether or not a solution through ableton link has been generated??).

3 Likes

Does anybody have a method of using the original GrayScale Grid 128 with this (circa 2010)?

@kin.sventa uses a non varibright I’m fairly sure

1 Like

Oh dang! Through code adjustment? I’ll send him a message. Thanks!

1 Like