MU.LAB 2 Test B

[Bonteburg]

Successfully reproduced the dropped note syndrome:

http://www.fileden.com/files/2007/5/13/ ... .MuSession

http://www.fileden.com/files/2007/5/13/ ... ion.backup

MU.LAB synths are fine so far as I can tell. Only VSTi do it (all of them).

[Oxygenee]

Hi, Jo!

I just found that the bug preventing me from entering text into text fields on OSX has just come back.

There's another question for you:
Why does Mulab create new instances of a plugin when I put a plugin into a rack, select 'pull out of rack' and put again the plugin into the rack the same way I originally did (is there a way to 'grab' exactly those instances of a plugin back into a rack that have once been 'pulled out'?)?

As well, may I suggest to implement a 'reset to default' button into the colour chooser?!

See you!

[pljones]

As well, may I suggest to implement a 'reset to default' button into the colour chooser?!

Me too!

I will be doing some more MULAB2 testing. I've just finished something in Reaper that wouldn't have worked in MULAB1, so I'm going to give 2 a go.

[MuTools]

I see what you mean, and have done some tunings in Test C, for both Composer as Note Editor.

Anyway, what i don't understand is that if you don't like certain zoom ranges, then it's just a matter of not using them, right?

Oh, what is there now is "good enough". A little optimization would make it a bit more "fantastic"!

Yeah, i do agree that the bit of optimizing definitely makes it more friendly.

[MuTools]

Successfully reproduced the dropped note syndrome

Marco, reason is that in the beginning of that sequence, you have around 230 controller events just before that note, all on position 9.1.0000.

MU.LAB uses a 200 event buffer for sending events to a vst plugin.

If you delete the redundant controller events, the note does play.

About the 200 events per time slice:

For example: audio device using 256 samples at 44100 Hz, that is 200 events per 6 ms!

Limit could be increased this but i think it's not making much sense, because it's about redundant events.

I would rather invest in a way in which the user is warned about this situation.

Taken some note about this.

Thanks for reporting this, and the demonstrating musession!

[MuTools]

I just found that the bug preventing me from entering text into text fields on OSX has just come back.

The OSX windowing system has changed indeed, so to make MU.LAB compatible with OSX 10.5.

Will research text entering in VST's again.

There's another question for you:
Why does Mulab create new instances of a plugin when I put a plugin into a rack, select 'pull out of rack' and put again the plugin into the rack the same way I originally did (is there a way to 'grab' exactly those instances of a plugin back into a rack that have once been 'pulled out'?)?

MU.LAB doesn't create new instances in that case.

It's about 'moving' the same instance.

Why do you think it's creating new instances?

As well, may I suggest to implement a 'reset to default' button into the colour chooser?!

Ok, improved in Test C.

[MuTools]

As well, may I suggest to implement a 'reset to default' button into the colour chooser?!

Me too!

Done in Test C.

I will be doing some more MULAB2 testing. I've just finished something in Reaper that wouldn't have worked in MULAB1, so I'm going to give 2 a go.

Feel free to feedback what you're missing in MU.LAB

[Bonteburg]

Thanks for looking into the dropped notes Jo!
Bizarrely, now that I know the cause of it I don't think it's so bad anymore.
It's certainly not a showstopper, seeing as I've always been rather an "internal synth guy" anyway.

-
Observation about multisampla: New Sample Zones should default to "no loop" instead of "forward" in the loop mode settings. The way it is now, you end up manually disabling looping in 99 per cent of all cases.
Default settings should always represent the most basic settings IMO.

[pljones]

Okay...

The project: record some drums to a supplied audio file.
The method: load up Kontakt2 and ns_kit7, play my TrapKAT, record the MIDI output, freeze that, mix with supplied audio, return demo.

I didn't try the recording in MULAB, didn't get time. In Reaper... well, I started getting all sorts of clicks and crunches as I was playing. No idea why. However, it caught all the MIDI events okay. Next step was to freeze the track - i.e. Mixdown. Reaper did this in "faster than real time" - about 4.5x. The output sounded spot on to me.

Nightmare: I couldn't find MIDI export in Reaper! MIDI Yoke to the rescue: played back the track in Reaper, MIDI record in MULAB. I had a couple of problems here:

(*) When recording MIDI, if the play position passes bar 16 and goes off the screen, you can zoom out (so bar 32 shows). However, when the play position goes past bar 32, that's it. No more zoom out! (This is in an otherwise empty session.)

(*) To get the events to record, I think I had to have a synth plugged into the rack I was targetting. Not sure on that one. Something meant I had two recordings with no events and then it started working.

OK, now the MIDI is in MULAB!

Oops: the CC4 values had got inverted by MIDI-OX on the way. I had to export the track to a .MID, convert to text, run the file through a PERL script, convert back to .MID and re-import.

(*) Can we have an "Invert Value 2" tool in the Sequence Editor, please?

Mm, and when I imported the new .MID, it created a new Composition.

(*) Is there an easy way to move Parts between Compositions? (I bet I'm missing something obvious.)

(*) There's no "Edit->Cut/Copy/Paste" for people who end up using menus... nor is it always obvious where these sit on Right-Click. Sometimes Ctrl-X is the only way.

Now for the bad news.

(*) MULAB still fails to render. It got perfectly through about 39 bars. It looks like it's doing the whole thing. However, after that point, only a few notes get rendered.

I had played the sequence back in real-time. It might have been at bar 39 I stopped (I didn't play the whole thing). I tried both render to Sample and render to File. Exactly the same result.

The Sample is rather large and I'm still running the .MuSession file, plus the Reaper WAV and MULAB WAV, through 7-Zip. I'll link the file once it's on my website. (Hopefully it'll be under the 400Mb it's starting as...)

OK - here's a 150Mb self-extracting 7-Zip of the bits:
http://www.drealm.info/mu.lab/TheSumPLJDrums2.exe

[Bonteburg]

New crashbug:

http://www.fileden.com/files/2007/5/13/ ... ayback.txt

[MuTools]

New Sample Zones should default to "no loop" instead of "forward" in the loop mode settings. The way it is now, you end up manually disabling looping in 99 per cent of all cases.
Default settings should always represent the most basic settings IMO.

Yes, had already changed it this way in Test C

[MuTools]

When recording MIDI, if the play position passes bar 16 and goes off the screen, you can zoom out (so bar 32 shows). However, when the play position goes past bar 32, that's it. No more zoom out! (This is in an otherwise empty session.)

Why do you want to scroll in the empty composition while recording?

Not sure if this is relevant but pressing in the Composer and Sequence Editor toggles the auto scrolling on/off.

To get the events to record, I think I had to have a synth plugged into the rack I was targetting. Not sure on that one. Something meant I had two recordings with no events and then it started working.

Just tried recording events when there is no focussed target plugin.

Works fine here.

Can we have an "Invert Value 2" tool in the Sequence Editor, please?

What do you mean with "Invert Value 2"?

Is there an easy way to move Parts between Compositions?

Using Cut, Copy, Paste:

Via the Composition context menu (right-click the composition background, not a part!)

Or with Control + X, C, V

OK - here's a 150Mb self-extracting 7-Zip of the bits:
http://www.drealm.info/mu.lab/TheSumPLJDrums2.exe

Thanks, will investigate asap.

[MuTools]

New crashbug:
http://www.fileden.com/files/2007/5/13/ ... ayback.txt

Do you remember what you were doing at that moment?

[Oxygenee]

I just found that the bug preventing me from entering text into text fields on OSX has just come back.

The OSX windowing system has changed indeed, so to make MU.LAB compatible with OSX 10.5.

Will research text entering in VST's again.

There's another question for you:
Why does Mulab create new instances of a plugin when I put a plugin into a rack, select 'pull out of rack' and put again the plugin into the rack the same way I originally did (is there a way to 'grab' exactly those instances of a plugin back into a rack that have once been 'pulled out'?)?

MU.LAB doesn't create new instances in that case.

It's about 'moving' the same instance.

Why do you think it's creating new instances?

As well, may I suggest to implement a 'reset to default' button into the colour chooser?!

Ok, improved in Test C.

I am using OSX 10.4.11 .

What I mean about the instances is that when I put a plugin into a rack (say 'Synthia'), 'remove from rack' it then, add the same plugin just as if the rack had never been filled, then the plugin is inside the rack just as before, but it has a different number (such as 'Synthia(2)').

Have a nice day!

[Bonteburg]

Morning!

New crashbug:
http://www.fileden.com/files/2007/5/13/ ... ayback.txt

Do you remember what you were doing at that moment?

So far as I know, I was just browsing for another sample to add to my snare zone. I was testing velocity layering and I already had a pretty good kick zone with 12 stacked samples playing back on C3. Snares were going on E3, and I was pretty much done with the snare zone. Maybe doing it all during playback made MU.LAB crash.

Good to see you agree on the default Multissampla settings!

Two observations:

-We should have some kind of tool to merge parts (already mentioned this in the other thred this morning)

-The possibility to name a sequence when you create it, as in "new part -> sequence part -> name dialogue".