That doesn’t seem normal. There isn’t dead space possibly at the beginning of the buffer is there? Are you preloading tracks or recording into the buffers?

I’ve been live recording into the buffers, in this case. Is there a way I can tell if there’s space at the beginning of the buffer?

does this seem to be better or worse with wifi on/off, by chance?

(“delay between button press and state change” sounds like an event loop / lua-side thing and not like a buffer / DSP-side thing.)

I’ve had wifi on, but switching it off doesn’t seem to make much of a difference.

After some more poking, this actually doesn’t look like an issue isolated to start/stop. I’ve just got general interface lag on almost all functions, except for changing the track focus, and starting/stopping recording.

Update: After power cycling Norns and re-recording some new stuff, the issue isn’t happening anymore. Is there a way that I can grab a sample of the process over serial if this happens again to help with possible debugging?

presently clip length max is set to 45 seconds. there are 7 clips available.

i can easily double this by using both buffers. the clips are spread out across the buffer at 45 second intervals— this is a constant var in the script and easy to tune.

3 Likes

I don’t think this deserves its own thread in the lib section.

The mlr64 2.0.1 for non varibright grids(should be easy to mod for all your varibright needs).

Column 3 on Rec/Speed view only lights up if it is “time mapped”, but still functions as a focus button as well(in addition to column 2).

mlr64.lua (22.1 KB)

11 Likes

Is midi sync currently working in mlr? I had previously in the 1.0 days synced tempo with my Octatrack with a usb to midi cable. I can’t seem to get it to sync now though.

oooo-weee!

ok MLR is working great!

question…does MLR send out a ton of MIDI info?

I have norns connected to MIDI through an old iConn USB to MIDI box thing.

the setup is with the Deluge sending out a master MIDI clock into a passive MIDI splitter and then to the Little Deformer 3 and then through the iConn box to norns.

my Little Deformer 3 would get a horde of MIDI data and then crash.

more testing tonight.

thanks for any help or info!

currently mlr sends clock messages but does not send start/stop messages, which some devices expect.

actually, there’s a typo on that line which prevents clock from being sent. should be midi_device:send not midi_device.send

trigger params for midi clock start/stop might be a nice addition to mlr?

4 Likes

Ah nice ok I don’t need it to send transport as much as I’d like to just sync the clocks up. Gonna try changing that line

**made the change and its syncing up now thanks

made a drawing for 128 grids as well. Not 100% happy with how this looks if anyone wants to do some adjustments I’ve added the illustrator file here as well.

mlr.ai (1.6 MB)

6 Likes

I would LOVE that. 20chars

What am I doing wrong? If I load a clip and play it back it slowly dies. It starts out at a good volume and slowly fades until it’s gone. I don’t have record on on that track. It also happened to a clip I recorded in, but not the other one I recorded in.

It’s as if I’m overdubbing silence, only… I’m not.

Is the overdub param in the rec/speed menu anything above 0.0? And is the rec button active(column 1)?

Nope. That’s why I’m confused.

Try repulling the script from git maybe?

I’ve not yet had a good look through the lua code for mlr but I did notice:

local FADE = 0.01

I’d also noticed my loops very slowly fading out but thought I was probably just imagining it. Might be worth changing the above to 0.00 and see if that makes a difference. It may well be unrelated!

that sets the crossfade time and should not influence overdub/erase level

(i have not run the script lately to verify that settings are as expected. you can monitor OSC from matron -> crone though…)

though i suppose if your xfade time is very long relative to the length of the loop, then loop beginnings could seem weirdly silent

1 Like

bug report (sorry, I don’t have a GitHub account)
This came about after some semi-random button mashing… if you hold Alt and Q then hit any of the three page keys the audio shuts off and does not come back unless you reload MLR.

Is there a way to have one input bypass mlr and have one input go directly to monitor? Most likely doing a gig this weekend and would love to have a dictaphone just running without any effect on one input.

2 Likes