MU.LAB beta A

[aMUSEd]

Will do - off to work now though

Ok, thanks in advance.

OK I've been going through adding VST's folder by folder and checking the log. I'm afraid it looks like at least one of the culprits is Zebra 2 - it made it crash and try to bring up Dr Watson (which is possibly also why it took so long to close properly as Zone Alarm had blocked it from doing that)

Good to hear at least part of the problem, the difficult shutdown, is resolved.

About zebra2: Strange, it loads fine here.

Oh is that on windows or osx?

(sorry if i asked before, don't keep a record of that, maybe i should, at least temporary)

How does it load on other systems? Can others please check this out too.

Earlier was reported that CM Vocoder crashed, and that's the case here too, so i'll research that!

For the record I'm on a Dell XPS laptop - 2x2ghz Dualcore, 2 GG Ram, 100GIG 7,200 HD running XP SP2 and with NI KORE as my audio/midi interface.

It's working now - I had to delete my VST.xml file and start again as it kept ignoring Zebra due to the initial crash but now it loads. Maybe the problem was the playing demo.

[Richard Lichten]

Hi Jo,

regarding my earlier reported crash: i didn't manage to replicate it yet so i tried hard, but it didn't show any error message - it really crashed cold, no survivors, so to speak...

[Richard Lichten]

Just an addition: Got the same error several times
while clicking on the white dots at the mixer strip anf then choosing effects in the pop-up window with a left mouseclick. In both cases, the prog went out cold, when the sequencer runs it also produced a repeated sound.

[toxicoh]

Two things:
1) I also would prefer MuLab starts up without playing immediately. A dialog asking about opening Latest Project/Other Project/New Project would be nicer. [Edit: Ooops, it does. There needs to be more than just the Demo Project present.]

2) Not all of my VSTs are being detected.I use a small set of 7 synths and 6 effects. Many people here would use the CM VST packages from the DVD. Ohmygod101_vst2carbon isn't being detected, even after renaming it adding .vst extension. It's in the same folder as the others that are all detected. Trying to add it manually from the VST Manager didn't work either.I just checked, Luna is the same.

[D-Fusion]

Hi Jo
Thanks for your invite to test MU Lab.
So far i must say that i am really liking the new look

I have also tested the Vst automation and it is really great and i also love how easy it is to find your automation

I also noticed 1 weird thing and that is if you add a synth and then a effect under it in the rack the effect gets the midi focus from your keyboard instead of the vsti.

So to get back the focus on the instrument i had to right click on the name and reselect focus.

All my 74 plugins scanned fine so no problems there

Will MULab also have Step recording in the feature?

[D-Fusion]

Oh i also discovered that quantisize does'nt work yet (Ooops found the lenght Q so it works)

Btw. Does MULab have Multi processing support?

[pljones]

I also noticed 1 weird thing and that is if you add a synth and then a effect under it in the rack the effect gets the midi focus from your keyboard instead of the vsti.

Standard behaviour. The easiest way is to have a part pointing at the rack/synth so you can just click that, and it'll focus automatically. In the early LUNA days there was a lot of discussion on how this should behave...

[Caleb]

So you mean that whatever you add last to the rack gets the midi focus? I can see why that would cause some discussion.

At least now I know what the "Focus" option is. I couldn't work out what it was doing.

Regards
Caleb

[Caleb]

OK - non-MuSynth for a change.
Am I right that there is no ability to create or load FXP/FXB files for VST plug-ins and it's also not possible to change VST presets?

I'm assuming if this isn't there yet it will be prior to 1.0? Is that the case though?

You can do that:

Right-click on the plug (in the mulab gui, not in the custom vst editor), and there you got

-> Choose Program
-> Rename Program
-> Open Program/Bank
-> Save Program
-> Save Bank



Can you find this?

Ah OK - I get it.
Good thing is you can do it from the rack and from the upper panel.
Although I'd prefer it in the pop-up, this should do fine for me.

Thanks.

Regards
Caleb

[muzycian]

Quick message from the lab: i'm starting to get a clue what the problem is with racks within the musynth, even if they're neatly placed after the voice out, as they should.

There is definitely some bug there.

Going to take some sleep now so to get fresh to resolve it.

I'll reply soon to the messages.

Cheers

[Caleb]

Every bug found and squashed during a BETA testing session is cause for celebration.



Regards
Caleb

[hivkorn]

hey I want to beta test it too !!! my email jonalynkrauth@wanadoo.fr

[D-Fusion]

So you mean that whatever you add last to the rack gets the midi focus? I can see why that would cause some discussion.

At least now I know what the "Focus" option is. I couldn't work out what it was doing.

Regards
Caleb

Yes the last added vst in the rack gets the midi focus.
I was really surprised when my keyboard stopped playing the synth until i found out why it happened.

[muzycian]

Jo, sent you a PM with a link to my buggy .MuSynth file

Thanks, it certainly helped in narrowing down the racks-in-musynth bug.

[muzycian]

To edit a plugin in a rack, just doubleclick on it.

Does this help?

Maybe you have been clicking the round 'thing' at the right of the rack plug slot, but that is only active for a send: it shows the send level there.

I find that a bit confusing, so i'll communicate with the skin developer about that.

Hah - I had in actual fact never tried a double click.
Every time I clicked on there, I got a choice to use Plugin. Right clicking brought up the options and I figured out the button on the side when saw it in operation on the demo. Just never tried a double click

What about this idea:

When a single (or double) click on a rack slot:
Then when that slot is empty -> choose plugin
When that slot is not empty -> edit the plugin

And do you think it would be better if there is a "Edit" also in the context menu of the plugins?
Maybe it should be there, logically, but don't want to overload the menus if not necessary.