MU.LAB 1.0 bugs and observations

[Bonteburg]

That is normal: because of the medium/high resonance the filter needs some time to decay.

So what you need to do is make sure the patch has an amplifier + envelope for it and set the decay/release time high enough for the filter to fade out.(e.g. 20 ms)

Tip: If you have multiple envelopes in a patch, make sure to mark the most relevant envelope as the main envelope.

Otherwise the patche voices make take more time to end (and use cpu) than the time you're hearing them.

Cfr http://www.mutools.com/mulab/docs/musynth.html

This has not specifically to do with your filter question, but thought i just added this info here again

hm, sounds interesting!

I need to delve into 'modular' a lot more...

[funkychickendance]

Ah, here's an interesting bug. Mu does not seem to like LinPlug's SaxLab at all, and disables it. No issues with their other products. Wonder what this is about?

Edit: And, does the same to SampleTank 2.2 and Sonic Synth2. "Caused a problem during scan, will be disabled"

//fnx

I had a similar problem with dmiHammer, a chromatic-percusion synth, and LUNA pr 8.4; when running LUNA for the first time it suddenly quit while scanning the plugins. The second time I ran it, and try to add VST plugins, it prompted a message similar to that "Caused a problem during scan, will be disabled". I just deleted the .dll and then re-copied the .dll to my vst folder and the problem disappeared.

I'm surprised by the "delete-dll-then-copy-again" thing too

<edit>
Ah, ok, now i read that it was about "delete-dll-then-reinstall-again".
OK, that sounds much more natural/logical.
</edit>

Nice to know of a possible solution. Are you saying that the .dll for the program needs to be in the root of the VST directory, rather than in a subfolder, or am I missing something here? Or that deleting then reinstalling is the answer?//fnx

For MU.LAB it doesn't matter where the plugin is, because you just tell MU.LAB where the plugin is! (via the Plugin Manager)

Well, I told it, and it didn't get it.

Now, this may sound totally off-the-wall to you, but I'm damned if I'll uninstall and re-install humungous-sized programs like Sonic Synth and Sampletank just to circumvent a bug in someone else's software.

You'll have to ring me up as 'NO SALE'

//fnx

[> DiGiT <]

ok i didnt read anything in this thread yet, so this is just me making comments on the design of mu.lab.

i wish the vst windows were independant of any view, could be viewed in either modular plugin area or rack/arrangement window. as it is now, when you double click to open the plugin in the modular window, the view automatically switches to the arrangement window. i want to stay in the modular plugin area and still view my plugins.

otherwise i like! the new musynth is quite intriguing! nice sounds!

[muzycian]

Well, I told it, and it didn't get it.

Now, this may sound totally off-the-wall to you, but I'm damned if I'll uninstall and re-install humungous-sized programs like Sonic Synth and Sampletank just to circumvent a bug in someone else's software.

You'll have to ring me up as 'NO SALE'

//fnx

If you had to re-install the plugin before it could be used in MU.LAB, then it's almost certain that that was a plugin issue! (some missing file or so...)

Not a MU.LAB issue.

[muzycian]

ok i didnt read anything in this thread yet, so this is just me making comments on the design of mu.lab.

i wish the vst windows were independant of any view, could be viewed in either modular plugin area or rack/arrangement window. as it is now, when you double click to open the plugin in the modular window, the view automatically switches to the arrangement window. i want to stay in the modular plugin area and still view my plugins.

Huh

When i:

-> switch to modular view
-> doubleclick a vst plugin to open its editor

the view stays what it is: composer + mpa, with the vst editor on top of these.

Are you saying that when you doubleclick the vst plugin the MPA switches back to the Rack Desk???

Wich OS?

Anyone else encountering something like this?

[> DiGiT <]

im using XP.

so the composer pops up when you open a plugin from MPA? i dont want that to happen.

[funkychickendance]

Well, I told it, and it didn't get it.

Now, this may sound totally off-the-wall to you, but I'm damned if I'll uninstall and re-install humungous-sized programs like Sonic Synth and Sampletank just to circumvent a bug in someone else's software.

You'll have to ring me up as 'NO SALE'

//fnx

If you had to re-install the plugin before it could be used in MU.LAB, then it's almost certain that that was a plugin issue! (some missing file or so...)

Not a MU.LAB issue.

Actually, it's probably not a showstopper, since I don't care much about having every damn plug-in in every host -- though these two work fine in eXT, exT2, FL, ACID 6, Podium to name a few. SaxLab2 appears very soon. But I'm not sure if I'm up to buy 'the Moo' on Jan 6 with so many other issues still live here...

//fnx

[pljones]

Also limit the display/edit to the events in the clip both in the piano roll and the event list.

Does everyone agree with this?

No, I prefer the solution I outlined . As does JP .

i wish the vst windows were independant of any view, could be viewed in either modular plugin area or rack/arrangement window....

...When i:
-> switch to modular view
-> doubleclick a vst plugin to open its editor
the view stays what it is: composer + mpa, with the vst editor on top of these....

Start up Windows Explorer. Start up LU..er.. MULAB and load up a plugin in a rack. Alt-TAB to Explorer. Alt-TAB to the RACK. Now open up the plugin. Ooh! Up pops the Composer window from nowhere. Okay, Alt-TAB back to Explorer. Now, where's the plugin... Hmm... You can only Alt-TAB to the plugin window by going to the Composer window.

I think what's wanted is that each plugin should have its own taskbar entry and not pull up the Composer window.

[D-Fusion]

I just noticed that ZebraCM is disabled in the vst scanner by default and that is is recognized as an effect instead of a Synth.

[jpumphandle]

I just noticed that ZebraCM is disabled in the vst scanner by default and that is is recognized as an effect instead of a Synth.

My version of ZebraCM.dll shows up fine as a Synth and I have had no problems with it. I have used it both on WIN XP MU.LAB and OSX MU.LAB. The latter has a built in problem with Presets. Under the OSX VST version, the Presets folder must be precisely located since the location of this folder is hard coded into the module.

Maybe you have a Beta version or it needs to be removed and re-added to the list of synths?

[Caco]

ZebraCM is working fine as a synth here as well on Windows

[muzycian]

im using XP.

so the composer pops up when you open a plugin from MPA? i dont want that to happen.

Ok, i see what you mean now.

Will be improved in the next version.

[muzycian]

Also limit the display/edit to the events in the clip both in the piano roll and the event list.

Does everyone agree with this?

No, I prefer the solution I outlined . As does JP .

Euh, please point me to your outlined solution again.

(and who/what is JP?)

[Bonteburg]

J. Pumphandle, yes?

[D-Fusion]

I just noticed that ZebraCM is disabled in the vst scanner by default and that is is recognized as an effect instead of a Synth.

My version of ZebraCM.dll shows up fine as a Synth and I have had no problems with it. I have used it both on WIN XP MU.LAB and OSX MU.LAB. The latter has a built in problem with Presets. Under the OSX VST version, the Presets folder must be precisely located since the location of this folder is hard coded into the module.

Maybe you have a Beta version or it needs to be removed and re-added to the list of synths?

ZebraCM is working fine as a synth here as well on Windows

Hmm. weird
I have tried to reinstall ZebraCM and Mulab a few times now and i still get the same result, so i guess it must be another vst that is conflicting with ZebraCM so it is getting mixed up.