#366

oof, tempo mapping did it, thanks. I missed that in the manual. guess I had my RTFM moment :sweat_smile:

#367

actually mlr is under-documented so all questions are fair :wink:

10 Likes
#368

The M in mlr stands for mystery :nerd_face:

4 Likes
#369

Mysterious, Like Really. :joy::joy::joy:

7 Likes
#370

an evening with MLRā€¦
more Late Night Noiz for Late Night Fiends:

3 Likes
#371

Something im struggling with it the looping. I am often looking to loop just one of the 16 ā€œstepsā€ on the original MLR i believe you did this buy holding the desired step and then the one before it and it would loop just that step. When you do it now it makes a loop of the 2 steps.

Is it possible to loop just the one?

1 Like
#372

hey I am certainly interested in keeping up with your mlr64 port! I have been working on getting non monome-grids to play nice with scripts, and yours I think is pretty seamless with my apc so far, but do you have any updated documentation on it? Everything is kind of all over the place. If you get some information in your github repo, thatā€™d be nice, and iā€™d be happy to bug test and PR and such.

One thing: in my debugger, I am getting that your script is sending grid:led messages to a x=0 column sometimes, is this just a bug, or is the 64 grid 0 based??

1 Like
#373

Iā€™m still having similar midi issue to this.
I can assign it just fine but MLR wonā€™t respond to some faders. It was looking like just the even numbered faders for a while now it seems like just the ones on the left half. So weird

#374

can you remind me whatā€™s going on? would like to fix this for you!

#375

Yes! Sorry I should have explained more about the issueā€¦
when using the 16n, I will go through and assign CCs to volume per channel and overdub using midi learn. Norns recognizes the incoming CC when in midi learn but then when back in the main MLR view not all of them will be active. most often it is the first fader (cc 32) that will be ignored but sometimes it is every other fader. so strange.
Iā€™ve cleared out all midi assignments to make sure that there isnā€™t an accidental double assignment and also made sure that 16n doesnā€™t appear twice on the midi device list but there is nothing that makes it more reliable. scratching my head.

#376

Great stuff. What kind of documentation are you looking for?

#377

can we bribe you with sandwiches or something? Iā€™m pretty baffled by aspects of mlr still, which is annoying given itā€™s almost the app. I even find the main ui diagram vague and confusing.

2 Likes
#378

I think this caught me out today. I kept accidentally hitting K2 (from memory) to load a clip when I didnā€™t mean to, which immediately stopped playback, even if I ā€˜cancelledā€™ out without selecting a file to load.

Perhaps better behaviour is to only stop playback if a file is actually selected.

1 Like
#379

beholdā€” a sortof blurry mumbly not-live capture from the brooklyn norns meetup: https://vimeo.com/373768732/3ca0ac4a39

37 Likes
#380

Thank you thank you thank you! I learn primarily by watching other people do stuff, and this answered several big questions for me. Good on you!

#381 
thankyouthankyo
hankyouthankyou
ankyouthankyout
nkyouthankyouth
kyouthankyoutha
youthankyouthan
outhankyouthank
uthankyouthanky

i owe someone a :sandwich:

1 Like
#382

I added this as git issue 18. Feel free to nuke it if thereā€™s background Iā€™m not aware of or if you just plain olā€™ disagree.

#383

thatā€™s an easy fix and makes total sense.

#385

this newly posted video explains a lot of mlr functionality:

right around the 9min mark a drum loop is loaded and snapped to the clock and quantize is activated.

2 Likes
#387

Thanks for this! Was very helpful with the sync demos.