#248

To clarify - “Ableton” will not “show up” in slot number one. Your midi interface will be listed there.

What is your midi interface named and what do you see listed for SYSTEM>DEVICES>MIDI? Is your midi interface device name listed in the first slot?

If not, you need to click button3 and then select the correct midi interface. (the interface needs to be connected via USB when you select it - norns will remember it in this position even if you disconnect it later.) If that interface is listed in another slot, then click button3 to set that slot to none

If at this point it’s still not working, then there may some problem with MLR itself.

FWIW - Just trying this now and I can’t make it send clock either.
EDIT - just tried again with a fresh install of MLR and I get clock to my computer OK.

EDIT #2 - if you’re still having trouble - try re-downloading the current version of MLR and start over from scratch. Also, you might want to do SYSTEM>RESET just in case.

#249

@okyeron That worked! Just needed to re download mlr. Thanks a bunch!!!

2 Likes
#250

ok unfortunately debugging this revealed some other issues I am tracking down, will continue tomorrow

9 Likes
#251

Was able to give it a go yesterday and seem to be starting to get the hang of it. Thanks for the breakdown, seeing it explained a different way helped me understand a bit better.

1 Like
#252

can anyone explain what the level slew param does? can’t quite identify it by ear

ed. should have searched first :disappointed:

#253

fixed! please download 2.1.1 to fix the pesky off-by-one bug, which also affects loop lengths.

12 Likes
#254

Fixed it for me! Many thanks as always.

1 Like
#255

Can anyone help me with the tempo. when i cage it im not seeing the light on the cut page move any faster or slower or anything seaming like its changing.

#256

Curious about that as well, so far for me the tempo parameter is virtually useless even for loops preset to the right tempo.

#257

@robotboot @LLK hold alt and press focus to enable tempo mapping of selected track

1 Like
#258

It was indeed in “quantize” section of the manual sorry for asking (somehow “tempo mapped” didn’t ring a bell in my mind for this kind of behavior ? weird). Thanks anyway ! Not that I’m using tempo much with MLR but that’s great to know for future use !

Edit : it’s pretty intimidating to answer that to someone who’s nickname is rdfm by the way.

1 Like
#259

I think this did the trick for me.
any reason "audio.level_cut (0.5) isn’t a sort of defat?

#260

i haven’t checked recently for overall levels consistency. do you fine 0.5 gives you good results? (ie, monitored input (at 1.0) is the same level once recorded?

#261

Yes with all the levels turned up to 100 in the level mixer everything that is coming in are matching the output…It is seamless. Also looking at a basic vu meter for visualization.

#262

I think this makes sense but To verify my understanding, I’m curious to know the whole details of what you are routing in and out of norns:

  • using stereo input?
  • comparing softcut playback level with monitor level?
  • what monitor mode?
#263

I’m getting the level mismatch after a recent update too (recorded MLR volume is louder than input monitoring).

Using Stereo input, in this case an OP-1 and monitoring via the stereo outs (not headphone).

Changed audio.level_cut in script to 0.5 and it is much improved now!

1 Like
#264

It works with imputing stereo and mono.
yes comparing soft cut with motor levels. i have everything tuned up in the level menu.
i am monitoring out of the headphone out into a machine big knob.

same change also worked for cranes.

#265

I’m not sure if this is an MLR question but this felt like the best spot to ask. I have some files recorded from my zoom h5 that were saved as xxxx.WAV aa opposed to xxxx.wav. These won’t load in MLR but load in Timber for example and behave as expected of .wav files elsewhere. Could one of you great minds enlighten me? Is there a difference I’m unaware of. I was hoping to avoid the tediousness of renaming them all and although I will do that if needed, I am expecting to use the zoom to create more MLR fodder and would like to avoid the extra naming step

#266

My guess is it’s because MLR does this check before loading a sound file on line 790…

if path:find(".aif") or path:find(".wav") then

You could try changing this to

if path:find(".aif") or path:find(".wav") or path:find(".WAV") then

but there’s probably a better way to do this. I feel like this kind of check for a valid audio file should be a global helper or library in norns if it isn’t already.

2 Likes
#267

thanks for pointing this out. i should do some case-insensitivity on this stuff (would accept a PR if someone wants to submit it!)

2 Likes