#123

Any possibility of one shot behavior on tracks in the future? And or gate

2 Likes
#124

I had this issue big time in the initial 2.0 release. One thing I noticed was that the meters on the audio page are not very reliable. You gotta play around with the levels for your input as well as the softcut level to get them to match up. At least this was for me how I got it pretty close.

#125

Making the above change sorted out the levels issue for me - were you able to try this?

2 Likes
#126

Can confirm I just experienced the same thing — all of my tracks fade to silence after ~90 seconds and record isn’t armed on any of them. I’m recording at full volume / full recording level (1.0).

#127

@Olivier @BKCP @kburwash @tehn

i can’t reproduce this issue. if i set recording off for a track (using the grid) then the audio on that track remains unchanged for as long as i care to loop it (tried with short loops for like >1hr, recorded, compared waveforms.)

same result if i enable recording, but set rec level = 0.0 and overdub = 1.0 in the REC page, which i would expect to have the same result since it sets equivalent values in softcut.

finally, same result if i set Nrec and Npre parameter values from the parameters menu page, again to 0.0 and 1.0 respectively, again as expected.

so, i would look for some other step that is necessary to reproduce. one thing i haven’t tried is loading / saving parameter sets; i can imagine this being an issue with either A) order of operations, if rec/pre levels are set before the record toggle state is set, or B) dropped OSC messages when many parameters are updated “at once.”

in either case, i would expect that “goosing” the record toggle for a track, after loading parameters, would put things back in a correct state. debugging indicates that this function is being called appropriately and is doing it’s job of “blocking” changes to rec/pre levels when recording state is off.

(hm, i guess it’s also possible that an OSC message is getting dropped at some random time during operation, since the phase polls make a lot of traffic. providing an alternate IPC channel to crone/softcut is at the top of my work priority list.)

@tehn i did find what appears to be a bug where if i load a clip while a track is using and looping, the loop points and phase quantization go totally haywire and can’t be recovered without relaunching the script.

2 Likes
#128

i will fix the script to stop playback if a clip is about to be loaded in.

i’ll try to reproduce this fadeout and volume issue as well…

3 Likes
#129

I had an issue where MLR was wiping out other tracks that I wasn’t recording on. I reran the 2.0.1 update script in via command line in the terminal, did ‘sudo shutdown now’ and rebooted Norns. Things seem normal now, although I need to do more testing.

#130

a few mlr questions:

does mlr expect 48k sample rate?
i had a sample at 44k and it didn’t seem to loop cleanly until i re-encoded it at 48k.

can the pattern recorder playback be quantized? i thought having quantization turned on would be enough, but it seems like over time the recorded patterns tend to drift out of phase with other loops. perhaps there is a “best practice” guide to nailing sync’d pattern looping?

2 Likes
#131

yes. sorry…
we could add resampling code here:
[ https://github.com/monome/norns/blob/master/crone/src/SoftCutClient.cpp#L222 ]
(and, ech, refactor mono/stereo while we’re at it, theoretically)

said code would involve pulling in something like SRC as well as libsndfile. here’s an example of how that’s done:
[ https://github.com/chirlu/soxr/blob/master/lsr-tests/sndfile-resample.c ]

#132

Thanks for confirming my suspicions. Not a problem for me, I mostly use it as a live looper right now. In this case I was making a metronome click track so I could loop in time with the mlr clock.

2 Likes
#133

a small modification should be made to allow this. right now events are quantized, but the recorder start/stop isn’t quantized itself, so multiple patterns will never precisely sync.

i’ve added a note to add this: https://github.com/tehn/mlr/issues/15

9 Likes
#134

hello!

I’m an old monome user, and I’m not very up to date with the softwares. I have a beginner question. I’m looking to use a 128 grid with the old MLRV but in a standalone format. I just want to use synchronized MLRV with some elektron machines. Could you confirm if with a NORNS and the MLR I can load some samples (I do not look to record in real time) and be able to run MLRV synchronized in time with the elektron machines?

I would greatly appreciate your help.

regards!

#135

norns mlr is more geared towards live sampling at the moment.

as it evolves there should be more extensive features for sample loading… for example, right now you can’t save presets of sample collections, but this is coming.

external sync via midi is implemented already.

4 Likes
#136

For the life of me I can’t figure out how to sync with my op-z. Anyone with an op-z have any insight/ success? All of my midi in/out settings should be correct. Op-z is recognized as a midi device. Midi sync is set to on. quantize set to on, etc.

3 Likes
#137

i think mlr is currently limited to midi clock out

that said, i’ve tried to sync the op-z to it and it doesn’t work for me either.

i was able to get the op-1 to sync to mlr… but when i looked at the tempo it was jittering a lot.

not sure what was causing the jitter & haven’t tried syncing with any other gear.

2 Likes
#138

Thanks, I tried to sync in either direction with no dice (after surmising that mlr couldn’t sync to a clock in), glad to know i’m not alone at least :slight_smile:

#139

This echo’s my experience aswell

#140

Last night I dreamed of an mlr where you could use a button to start recording your “master loop” and then hit it again to go into overdub/etc, but then each subsequent loop could either be synced or unsynced (like it is now) to that first loop’s master timing. But the first loop spits out a perfect bpm reading in the param’s page and starts midi clock one you punch out recording on your first iteration. Hope that makes sense. Like I said, it was a dream, so it’s all a little cloudy…

7 Likes
#141

Sounds like the behavior of pickup machines on the octatrack. And yes that is a good dream

3 Likes
#142

Until crow’s arrival, it would be neat to have mlr spit out a midi note on some subdivision for syncing with the modular. (I want to get into the studies and be able to do something like this, but music keeps getting in the damn way.)

1 Like