MSL recording problem - did note-off behaviour change in 16.05??

[BennyG]

I've just installed 16.05 and I'm immediately having problems recording. Tapping on the record button on my MIDI controller (note #60) no longer instigates the record function. All settings are identical to my 16.04 installation, which works just fine.

I've spent about an hour fiddling with this, and I think the problem might be down to the way 16.05 interprets note-off commands? Couple of quick vids to demonstrate (I'm using Reaper's virtual MIDI keyboard here, to make the timing and duration of button presses obvious)...

Here's 16.04 working perfectly, quick tap and recording starts at the next checkpoint:



And here's 16.05. You can see it takes five attempts at pressing the button before MSL responds to the command and actually starts recording:



Looks like recording is getting cancelled each time I let go of the key, which didn't happen previously. The only way to get it to record successfully is hold the button down a bit longer until the metronome hits the first beat of the bar, and then recording engages.

This might seem like a small/innocuous change, but it's really bugging me. 'Long hold' on my MIDI controller is currently set up to output a completely different MIDI note, which triggers a different command via a multiparameter, so I really need tap-record to work.

[martin-meldaproduction]

Dear BennyG,

thank you for providing this information and for the time you spent testing it. I made significant changes to MSL to remove all loop and track limitations. While I was also testing MIDI events for start/stop recording, I did not anticipate that users would employ this feature with velocities and MIDI note-off events, and as a result, I reverted the behavior back to how it was in version 16.04 to make it more familiar to users. Therefore, in the next release or possibly still in version 16.05, the behavior will be the same as before.

[tonycore]

Hi Martin - apologies for hijacking the thread briefly, but when you write that you removed "all loop and track limitations" does that mean we are no longer tied to bar/beat lengths and multiples of the main loop, and can have completely independent/arbitrary loop lengths on each track?

[BennyG]

Hey Martin, thanks so much for the swift response and explanation. I was quite excited to try out the new version with the loop and track limitations taken away, but happy to stay on 16.04 for the time being (I'm gigging with this setup in a few days, so fingers crossed everything runs smoothly! )

I've noticed you're responding in a few of these threads recently - are you now the 'go-to' guy for MSL dev?

[martin-meldaproduction]

Hi tonycore,

I think I should have written "most of the limitations" instead of all. Of course, the very first loop (or better call it the main loop) defines the base loop length, and the other loops are integer multiples of this length. However, if you want to make MSL work with virtually any loop length, make the base loop very short, and then the other loops, even if they are multiples of the base, can have literally any length. But I do not recommend this, as it requires quite a lot of work to synchronize the looper on your side, which MSL normally makes for you.

In the new version, you can now:

Freely record the very first loop in any track/loop position.
Delete all loops in the first track, which was not easily possible before.
Delete the main loop, and MSL still remembers the base loop length (if the loop is not the last remaining one).
The first track does not need to automatically create redundant empty loops.
Delete all tracks and loops without pressing reset all button.

But remember, as soon as you delete the last loop, the information about the main loop length is lost, and you have to start from scratch again.

[martin-meldaproduction]

Hi BennyG,

Yes, as you provided the reproduction that was really well-documented, it was easy for me to revert it back to its previous behavior. So, this issue is fixed now. Please wait for the new release.

Also, I would like to confirm that MSL has been handed over to me, and I am responsible for it from now on. So, please direct all questions/request about this great plugin to me:-)

[tonycore]

Thanks for your quick reply, Martin. For my free-form, soundscape looping, completely independent loop lengths would be ideal! (I'm running MSL in Gig Performer, not a traditional DAW.)

[BennyG]

Hi BennyG,

Yes, as you provided the reproduction that was really well-documented, it was easy for me to revert it back to its previous behavior. So, this issue is fixed now. Please wait for the new release.

Also, I would like to confirm that MSL has been handed over to me, and I am responsible for it from now on. So, please direct all questions/request about this great plugin to me:-)

Thanks for confirming Martin, that's good to know. I'm currently making MSL the centre of my entire live-looping setup (as well as a compositional tool), and I agree it's a great plugin that already does a lot very well and could potentially get even better. I have a lot of ideas/suggestions, as well as a few little niggles here and there - would you prefer me to keep posting threads here or do you have a direct email for the more specific/detailed reports?

[martin-meldaproduction]

Hi BennyG,

if you have any new ideas/suggestions/improvements/potential bugs... on MSL, you can contact me directly here: martin@meldaproduction.com