#530

Am I right in assuming that you can’t actually save an mlr session? I’m using the Preset save on the norns, but it only saves settings for each track, not any recordings or actual clip points? I don’t mind, I just need to approach mlr differently if I know a funky session can’t be restored exactly as I left it, between sessions.

1 Like
#531

Re saving, I believe that is correct

1 Like
#532

pset saving is on the list for the revision.

5 Likes
#533

nice would love to be able to switch presets via button press, not sure if that is already possible. I used to use on my old mlr. would switch all my samples. also a second page with all the controls + MORE PATTERN RECORDS!!! WOOT! MLR on steroids .

1 Like
#534

Any arc plans, while we’re talking and all? :blush:

5 Likes
#535

Might have something for you here @tehn

I’m getting fatal crashes twice in one week now, both in mlr. Not entirely sure it’s mlr-related, cause the repro (which isn’t 100% by any means, just the least common denominator when this has happened) is in the params menu.

Anyway, here’s what happens. I got a pretty heavy mlr session going. Four tracks, at least, both times this happened. Two or three patterns going and they’re pushing it - reversing, bouncing pitch up and down, stuff like that. Quant is turned on. Samples are fairly long, loops between 8 to 32 beats, resized and split up heavily.

So when I’m in the param menu, frantically scrolling (yes, frantically, I mention it because it might be related) up and down for whatever purpose - adjusting the pan on a sample, fixing a slew, whatever - I get a crash.

One of those crashes where K3 - K2 - K1 won’t help.

Mlr keeps on playing but the grid freezes exactly where it was at the time of freeze. Norns is unresponsive, nothing works. But the show goes on :slight_smile:

Also, both reverb and compressor is on. Reverb is subtle but the compressor is pretty active.

This has happened twice in one week now. Both in mlr, both when lots of stuff have been going on, both in the params menu as I’ve been browsing it for whatever reason.

I realise the repro isn’t solid and I got nothing from maiden (the norns is literally dead), but maybe it’s part of a puzzle as you’re working on updates.

#536

@circuitghost More or less the same thing happened to me yesterday twice when using Cheat Codes (@dan_derks). If I remember correctly I was also scrolling around in the param meny while stuff was playing (using loaded samples). One time I remember I was trying to load a sample into the 3rd bank. Had to push the white button both times

Don’t know if this is related at all though

1 Like
#538

That mirrors my experience exactly, only different script. White button saved the day, though it was scary as I’ve been told that to use that one, is like calling out Voldemort by name :slight_smile:

It does feel a bit like a good old memory kind of crash. Not perhaps a leak, but certainly a lot going on at the same time, RAM-wise or similar, and there’s just not enough temporary space to handle it all.

#539

I am getting these crashes now very often, and the k3-k2-k1 has never worked for me. I’ve had norns freeze up on Cheat Codes, meadowphysics and Orca (and both the libraries and norns are up to date).

#540

next time you play can you first open maiden so you can see any error messages and post them here?

1 Like
#541

I’ll do some extra digging for leaks. Its plausible. But audio continues yes?

1 Like
#542

Yep, no told soft cut the end is nigh, so it keeps on playing, and we love it for it :blush:

#543

Got another one, related to clock -

Mlr only transmits clock on startup, not when you’re actually changing it as you play. First, I figured, oh well. Then I tried a few other scripts, and mlr is the only one I use, which behave like this.

Start norns. Observe the tempo set in the clock. Say it’s 140.

Notice whatever external midi device you use, to take sync from norns / mlr. Works just fine. In my case, a Keystep Pro which sends midi and sequences to a Prophet 12.

Go into mlr. Do some live sampling mayhem, or load a clip. Doesn’t matter.

Then go, “Ahm, maybe this is a 132bpm track after all.”

Change your tempo in clock. Notice how your external midi devices don’t respond to this clock change, and how this is different from at least Animator, cheat codes and grey hole.

I can see how tempo change during an mlr session can cause problems, and reasons to commit to a bpm as you start your session … but more likely, it feels like a bug to me.

#544

thank you for the reports, will investigate

1 Like
#545

Regarding the crash, I’m seeing that others are getting it too, in other scripts.

It seems the common denominator is that the script is playing something while you scroll quickly through options, most typically settings in the param menu.

Related to draw update in relation to memory handling, maybe? Haven’t had this crash again so nothing from maiden yet.

1 Like
#546

I will try to replicate the freezing, but how do I get the error message if it happens? Is it the journalctl -b command in Maiden that I use in order to get the logs?

#548

shiny newbie here – MLR working well but can’t get clips to load either.
were you able to figure it out?
I can naviagate to the .wav file and “load” it but nothing appears in the track

Eric

#549

have you tried any of the audio files included in the norns install?

#550

yes - I tried several. I can select one and screen returns to the “clip” screen.
thanks
Eric

#551

are you on the newest norns update, and the newest mlr version?

last i checked it’s working here. i’ll open it up again now