mlre

sonoCircuit · 2024-02-28T09:30:00.260Z

thank you everyone for your kind words! really looking forward to hear what you do with the new version.

I see you managed to answer some of your questions.

regarding clock options: clocking is tied to norns system clock so the options are internal, midi, crow, link. this does not include a reset option (as far as I know norns’ os does not include this option. it would need to be added per script.

bc3:

The manual appears to stop loading after page 25

you can download the manual on the GitHub page:

dl mlre manual2254×562 45.9 KB

or SMB into norns and grab the manual from dust/code/mlre/doc

ampism:

some of the Arc capabilities be assigned to a different controller

probably doable but I wouldn’t know where to start. happy to accept PRs.

Jordskred · 2024-02-28T11:11:17.057Z

sonoCircuit:

wouldn’t know where to start

@dani_derks included options for this (and op-z as arc) in cc2. just to be clear i don’t know anything about coding and what you guys do is absolute magic (!!) to me, i just know it is possible.

sonoCircuit · 2024-02-28T11:17:50.495Z

cool. thanks for the pointer!

Let me see if I can wrap my head around dan’s cc2 code (that seems like magic to me ).

McNUG · 2024-02-28T18:37:33.340Z

I’ve been diving into the update on shieldxl using combiner mod to use two monobrightness 64s as a 128. Loving the update. Amazing work. The documentation is fantastic.

I caught a bug. When I hit k1 and go to the norns main menu, then go to the norns TAPE page to try and record what I’m doing the grid semi-freezes up and things start acting weird. I lose things like led feedback for playheads, and access to the first mlre page by pressing the top left button. Audio keeps playing, but I essentially lose the grid. I can recreate this bug. I haven’t checked to see if Maiden is spitting out any errors.
Edit: Dang, you solved that very quickly! Bug Squashed.

xmacex · 2024-02-28T22:13:25.411Z

Congrats on the update! This is a fun script based on the little experience I have, and I should buy a grid

toga support broke

With Toga which was working before, I get error: init and the following message (abridged) periodically, about once per second:

Feb 28 21:54:46 norns ws-wrapper[1290]: #011/home/we/norns/lua/core/metro.lua:164: in function </home/we/norns/lua/core/metro.lua:160>
Feb 28 21:54:47 norns ws-wrapper[1290]: lua: /home/we/dust/code/mlre/mlre.lua:2611: attempt to call a nil value (global '_gridredraw_o')
Feb 28 21:54:47 norns ws-wrapper[1290]: stack traceback:
Feb 28 21:54:47 norns ws-wrapper[1290]: #011/home/we/dust/code/mlre/mlre.lua:2611: in global 'gridredraw'
Feb 28 21:54:47 norns ws-wrapper[1290]: #011/home/we/dust/code/mlre/mlre.lua:2655: in global 'hardwareredraw'
Feb 28 21:54:47 norns ws-wrapper[1290]: #011/home/we/dust/code/mlre/mlre.lua:2395: in field 'event'

If I install 1.3.6, Toga seems to work. I notice that g and a are global in the 2.0.0, they were local earlier.

sonoCircuit · 2024-02-29T10:49:35.254Z

thanks! can totally recommend a grid.

re toga:

yes, those variables are globals now. I moved the grid and arc code out of the main script to prevent a 5k loc monolith. I had a report where toga arc was throwing those same errors and I got to work if you do the following:

change the variable at line 100 to: arc_is = true
comment out lines 2471-2475:

-- detect if arc is connected
  for v in pairs(arc.devices) do
    if arc.devices[v].name ~= nil then
      arc_is = true
    end
  end

there might be a better way of arc-detection, but this worked for me so far.

sonoCircuit · 2024-02-29T10:55:33.915Z

McNUG:

combiner mod to use two monobrightness 64s

amazing! such a great mod. I need to try it someday.

thanks you very much for the bug report. experience the same thing here. need to investigate

edit: it seems it has to do with my global tape variable. as soon as textentry is opened in the tape module I get a stream of error messages about nil variables which point to anything with tape. so it should be an easy fix…

edit edit:

@McNUG fixed! → update via maiden.

P.M.FM · 2024-02-29T22:49:15.506Z

Such an amazing improvement that’s absolutely on my route. I am really just a user of NORNS have no clue about coding but I love all those interesting attempts to expand the ways to creat sound/music. I use MPCs as a starting point and time keeper and now this new version of MLRE just opens up so many new possibilities for me. Just started fiddling around a bit this evening and will dive deeper over the next days because I wanna use it in my live-performances just like CC2.
MegaRespect

Khenu_Singh · 2024-03-01T21:55:51.991Z

Hi All, I just got my Norns & Grid last week. I’ve been tinkering with MLRE, watching everything I can online & have printed and read through the manual a few times. I’ve also gone through most of the posts on this thread.

With a bit of tinkering, I have MLRE running in sync with Ableton via Link, which is sweet. I love the character and playability of MLRE, which has it’s own flavor in contrast to my Microcosm, Morphagene and conventional looping pedals.

A few questions:

how can I maximize the length of my MLRE recordings? I’m trying to record some longer guitar riffs (shorter, more textural material is more straightforward).

I’m not sure if I’m going about this right, but so far, I’ve set the tempo-mapping mode to “Resize” and the length to 32/4. There’s a “max” after this, which I don’t understand but nothing more than 32/4 - perhaps this is due to my butting against the max buffer length? On the Patterns Page, I’ve set the length to 32 bars. I think I’m confused about how all this correlates.

I’m not sure what the track reset does and when I might want to use this?
Is there a way to use a MIDI foot controller to start and stop the recording of material, and also to scroll through tracks. I have my Morningstar MC-6 set up to do so with my Microcosm, but would like to incorporate the Norns into this as well, to be hands free until I’m ready to put down the guitar and perform with the Grid.

Thanks!

Khenu

zfigz · 2024-03-02T05:32:05.028Z

Khenu_Singh:

how can I maximize the length of my MLRE recordings?

i think the maximum length that softcut allows for is 57s per buffer.

as for your other questions, there’s a variety of parameters (e. g. enabling/triggering record per track) you can map to midi ccs and there’s a nice explanation on what/how to use track reset in the doc of which i would recommend checking out, it’s incredibly thorough and well written:

mlre/doc/mlre user guide v2.0.pdf at main · sonocircuit/mlre · GitHub

sonoCircuit · 2024-03-03T18:39:12.682Z

Khenu_Singh:

how can I maximize the length of my MLRE recordings?

Yep, you’re right the jump from 32/4 to max is confusing and something I need to address in the next update. max refers to the max buffer length (57s) per track. why it stops at 32? I just didn’t think that far.

Khenu_Singh:

what the track reset does and when I might want to use this?

Track reset resets the play head position to the start point of the active splice after a specified number of beats. This is useful when you want to ensure that your tracks go back in sync and don’t drift when you change speed, direction, position etc. When track reset is enables the beat counter starts with track playback, so it’s best to use it in combination with track launch set to bar.

Khenu_Singh:

Is there a way to use a MIDI foot controller

Yes. As mentioned in the previous post (thanks @zfigz !) you’ll find a whole section under parameters whose sole purpose is for midi mapping.

lemme know if you have any more questions.

st_silva · 2024-04-19T22:13:37.612Z

I upgraded to v 2.0 (prev 1.3) and running into init issues. See description below:

When i start MLRE, norns it throws the message error: init and takes me back to home screen. In the terminal, I see the following error message, which spits out every 0.5 seconds or so (maybe faster). This message continues until I select a different script

lua: 
/home/we/dust/code/mlre/mlre.lua:854: attempt to perform arithmetic on a nil value (field 's')
stack traceback:
    /home/we/dust/code/mlre/mlre.lua:854: in function </home/we/dust/code/mlre/mlre.lua:851>

I took a quick look at the code, and it appears to point to this function in MLRE on line 854, but I’m not sure what it does or why. Any idea what could be going wrong? I loved using MLRE before and would really like to give V2 and the new features a spin

function phase_poll(i, pos)
  -- calc softcut positon
  local pp = ((pos - clip[i].s) / clip[i].l)
  local pc = ((pos - tp[i].s) / MAX_TAPELENGTH)
  local g_pos = math.floor(pp * 16)
  local a_pos = math.floor(pp * 64)
  -- calc positions
  track[i].pos_abs = pos -- absoulute position on buffer
  track[i].pos_hi_res = util.clamp(a_pos + 1 % 64, 1, 64) -- fine mesh for arc
  track[i].pos_lo_res = util.clamp(g_pos + 1 % 16, 1, 16) -- coarse mesh for grid
  if track[i].play == 1 then
    if track[i].pos_lo_res ~= track[i].pos_grid then
      track[i].pos_grid = track[i].pos_lo_res
    end
    if track[i].pos_arc ~= track[i].pos_hi_res then
      track[i].pos_arc = track[i].pos_hi_res
    end
    if track[i].pos_rel ~= pp then
      track[i].pos_rel = pp -- relative position within clip
    end
    if track[i].pos_clip ~= pc then
      track[i].pos_clip = pc -- relative position within allocated buffer space
    end
    -- display position
    grid_page(vLFO)
    grid_page(vTAPE)
    if (grido_view < vLFO or grido_view == vTAPE) then
      dirtygrid = true
    end
    if (gridz_view < vLFO or gridz_view == vTAPE) then
      dirtygrid = true
    end
    page_redraw(vTAPE)
  end
  -- oneshot play_mode
  if track[i].play_mode == 2 and track[i].loop == 0 and track[i].play == 1 then
    if track[i].rev == 0 then
      if track[i].pos_hi_res == 64 then
        stop_track(i)
      end
    else
      if track[i].pos_hi_res == 1 then
        stop_track(i)
      end
    end
  end

sonoCircuit · 2024-04-19T22:20:40.711Z

Hiya! The variables for tape or clip startpoints are returning nil for whatever reason and the math can‘t be done, hence the error. Please try to uninstall and reinstall the script and let me know if that helps.

JosueArias · 2024-04-20T05:32:36.278Z

Try renaming or moving the psets folder, I had the error:I it in the past when upgrading versions because the pset it loads on init

monkaiboy · 2024-04-20T13:30:36.543Z

Hi.

Relative newcomer to Norns and MLRE, but I’m really excited about it, and have been digging deep into the manual to get my head around this thing. I’m looking to use it for a live performace in 4 months, so I’m fully focussed on it at the moment

I’m primarliy using it in ‘synced’ mode, with a drum machine slaved off the Norns MID clock. It’s working well - here are my settings for reference:

Track Settings
tracklaunch: bar
tempomap: resize
trackreset: on
reset count: 8 beats

Tape Settings
splice length: 8/4
default splice length: 8/4

This is all good and works well. However I’ve hit an issue. When I clear the tape or the buffers, the splice length is reset to 4s. At first I didn’t realize this and just found the audio going out of sync (as 4s was only slightly different to 8 bars at my current tempo - 110 bpm)

Then I discovered ‘default splice points’ and thought that must be the solution, but setting this to 8 bars did not solve the issue.

So I looked at the code. It seems the issue is that when the buffer or tape is cleared, init_splices is called. This always sets the splice init_len to DEFAULT_SPLICELEN (4s), regardless of the default splice points

I hacked about a bit and was able to fix this by updating the default splice setting code to update the DEFAULT_SPLICELEN and DEFAULT_BEATNUM - but I don’t (yet) know the code well enough to have a feel for if this is the ‘correct’ solution

  if n == 2 and z == 1 then
    tp[track_focus].splice[track[track_focus].splice_focus].init_len = tp[track_focus].splice[track[track_focus].splice_focus].l
    tp[track_focus].splice[track[track_focus].splice_focus].init_start = tp[track_focus].splice[track[track_focus].splice_focus].s
    tp[track_focus].splice[track[track_focus].splice_focus].init_beatnum = tp[track_focus].splice[track[track_focus].splice_focus].beatnum
    
    -- set default splice length and beatnum from the default splice markers
    DEFAULT_SPLICELEN = tp[track_focus].splice[track[track_focus].splice_focus].l
    DEFAULT_BEATNUM = tp[track_focus].splice[track[track_focus].splice_focus].beatnum
    
    show_message("default   markers   set")

Feedback/thoughts/alternative workarounds appreciated.

Anyway, I’ll probably be posting more for advice etc as I progress on my journey, but in the meantime - thanks so much for this great tool!

Kai

zfigz · 2024-04-20T18:53:31.434Z

i recently bounced a bunch of old tracks down for use w/ mlre v2…still learning all the ins/outs, but here’s a quick lil video:

mlre v2 performance

sonoCircuit · 2024-04-20T19:10:00.333Z

@monkaiboy welcome to the forum! Glad you’re enjoying mlre so far and very cool you’re planning a live performance with it.

monkaiboy:

When I clear the tape or the buffers, the splice length is reset to 4s

Good call! Never occurred to me that when clearing the tape buffer it would be good to keep the splice lengths. If you clear an individual splice (ALT + REC_PAGE) the splice settings remain untouched. to change the behaviour all you need to do is comment out init_splices(i) on lines 560 and 570.

I’ll see that I’ll add a param to the next update and make init_splices optional.

monkaiboy:

I’ll probably be posting more for advice etc

great, feel free to reach out if you have any Qs.

@zfigz thanks for sharing! love the little setup you have there. just dl the 10min vid, very cool to see pset loading live in action

st_silva · 2024-04-22T14:05:07.020Z

Update: uninstall and reinstall did not resolve the error.

BUT I tried the psets fix: I had one pset saved from previous MLRE version. I deleted that preset and then tried launching MLRE again and it worked! So something about the pset was contributing to the error perhaps, but I don’t know why. Hopefully that’s useful @sonoCircuit and thank you for the tip @JosueArias !!

zfigz · 2024-04-22T14:06:36.062Z

yeah, it’s recommended to recreate psets as tedious as that may be.

sonoCircuit · 2024-04-22T17:28:15.453Z

Thanks for the feedback. that’s really weird because mlre v2 should not load the default pset when loaded. But yeah, v1 psets are not compatible with v2. Anyway, glad you got it running!