#564

From the docs:

QUANTIZE:

touch to toggle quantization. ALT-Q to change tempo and division.

in REC/SPEED mode use ALT-FOCUS to toggle tempo-mapping.

a tempo-mapped clip will follow the tempo.

1 Like
#565

Thanks! I thought I had tried that but I’d been using two fingers on the FOCUS buttons out of habit (because of the pair of lights), which had been toggling the tempo-mapping on then off faster than I could see.

1 Like
#566

Hi all, I know this has been asked – is there a tutorial for MLR? Specifically, I am worried about BPM and tempo keeping. Do I need to record my input with an external metronome to ensure everything keeps time (knowing there’s no input quantization) or use loops that are guaranteed the same BPM? I feel like I’m about to be very lost, but also am very excited. Just received my grid and this is my first foray into using it so just want to make sure I’m having fun.

1 Like
#567

This would qualify as one of the more in-depth run through a of the script.

Honestly, in a way, scripts developed in house by monome have a history of being a little less documented than those by others.

After this script, I suggest you give Cheat Codes, Cranes and Otis a shot for audio mangling stuff as well. Although with that script you might actually get an embarrassment of riches when it comes to complexity and documentation!!!

Welcome to the monome family tho! The grid is great and we’re happy you’re here!!!

15 Likes
#569

Trying to record for the first time in MLR and I feel like I’m missing something obvious. I followed the recording quickstart in the docs exactly, but the notes I play into the L input channel on the norns (fates) don’t play back as the loops loop. I definitely hear it in the monitor and see the level bouncing on the leftmost menu page… what else can i check?

e.g. Otis works for recording so i know the system itself seems functional

#570

Thank you!! This is awesome. The only thing this didn’t really answer was quantization. What does “quant div” do? And if I’m trying to play a melodic piece I’ll effectively have to just use an external metronome then as quantizing changes the pitch (ie is more useful for rhythmic). Am I missing something there?

#571

Honestly, these are questions I don’t have much of an answer for. I apologize, but hopefully someone here might have a bit more knowledge on the inner workings of mlr in that regard.

#572

Sorry to double tap on the above, figured it’d be easier to ask in bulleted Qs

  • Is it better to use external clocked items for melodic pieces like Ableton or an OP1?
  • Are recorded patterns automatically tempo locked/quantized to the tempo without me having to tempo lock that track? I don’t want to tempo lock clips right now because it makes my entire track out of key.
  • What does “quant div” do? I am assuming it has something to do with note divisions, but how is it quantizing note divisions if it’s just slowing or speeding up the pitch of a clip? Is quant div for pattern record (meaning patterns are quantized to nearest 1/4 if the quant div is set to 4)?

Thank you all and sorry for bombarding with Qs :slight_smile: Hopefully this helps someone else too though.

#573

disregard this i suppose - did a reboot of the device and followed the same steps which actually did lead to output.

#574

Alright ladies and gents think I got it figured out (still curious about quantization methods but MLR doesn’t really seem truly built for things that need to be quantized / pitched like Ableton)

Here’s something I came up with using MLR and OTIS - my second day learning so be easy

https://youtu.be/uj9PJ4WGhh0

5 Likes
#575

I’m looking into the MLR.lua to try and make some small changes. I would like to make some adjustments to how playback speed changes work. Can someone point me at the chunk of code I can change to alter the play speed ratios? Like 3/4 instead of octave shifts?

Is it this chunk starting at line 481? Do I change “local n = math.pow(2…” and substitute another value for the 2?

update_rate = function(i)
local n = math.pow(2,track[i].speed + params:get(i…“speed_mod”))
if track[i].rev == 1 then n = -n end
if track[i].tempo_map == 1 then
local bpmmod = params:get(“clock_tempo”) / clip[track[i].clip].bpm
–print("bpmmod: "…bpmmod)
n = n * bpmmod
end
softcut.rate(i,n)
end

EDIT: yep! that did it. Thanks @tehn for keeping the script clean and making user end changes like this possible!

2 Likes
#576

It quantizes the loop to the tempo. You can edit its resolution in the tempo meny (ALT + Q).

#577

Just got shields, so excited, getting lost endlessly over and over again. Had MLR question after experimenting, reading doc, and watching the vimeo tutorial (super helpful):

  1. Are there still glitches in this in terms of connecting with grid?
    a.I frequently get a row that doesn’t respnod like normal all of a sudden;
    b.and I occasionally get a row that had a preloaded audio file that stops playing until I re-load it.

  2. What exactly does the overdub parameter do when recording?

  3. Does record record to the clip slot selected for a track in clip view, overriding whatever selection you had for the clip slot selected for that track already?

  4. What does resize do?

2 Likes
#579

Hello there!
I’ve got issues with MLR today: can’t record anything. (All other scripts can sample as usual). Levels menu shows the In-level correctly but no sound can be recorded.
Factory Norns, 2020 Grid, last update.
Am I missing something?
Thank you

EDIT: Same problem with Larc

#580

Maybe related to input parameters for softcut and the recent update? Did you check softcut levels under params?

1 Like
#581

Oh ok, that’s correct: it was “- infinite”.
Thank you

#582

Did you also check the softcut page under Parameters - edit - softcut?

1 Like
#583

sorry about this param menu bug that was introduced in the last update. luckily easy fix (and also solved in the next update)

3 Likes
#584

Thank you Brian, It’s super easy to solve but it will be even better as you say.
Super appreciated✌🏽

#585

@tehn a feature i’d personally find super valuable would be the ability to optionally reset a record-armed track’s playback position to the start once an input threshold is met, similar to how the OP-1 records samples. handy for cleanly recording stuff like percussion. perhaps via alt+rec?

i’ll take a look at the github, this is the sort of thing i’d love to be able to add one day :slight_smile:

might also be neat to have the option of pressing and holding a pattern slot to record activity for the duration of the hold, allowing for very precise pattern recording (rather than requiring another press to stop recording activity)

if there’s already a way to cleanly do either of these things, i’d love to know! right now i just try to manually restart the rec-armed track while simultaneously starting my sample.

1 Like