MU.LAB beta A

[muzycian]

Ps I love the new look but is there a way to maximise the view?

You can resize the windows as usual.

[aMUSEd]

Will do - off to work now though

[muzycian]

Will do - off to work now though

Ok, thanks in advance.

[aMUSEd]

Ps I love the new look but is there a way to maximise the view?

You can resize the windows as usual.

But no maximise icon?

[muzycian]

Ps I love the new look but is there a way to maximise the view?

You can resize the windows as usual.

But no maximise icon?

Should be there on the window, just like a standard window.

Oh, wait, which window do you mean?

Plugin editor windows cannot be maximized.

[jens]

Should be there on the window, just like a standard window.

Oh, wait, which window do you mean?

Plugin editor windows cannot be maximized.

No, it's the same as it was with Luna - neither the main window nor the rack can be maximized - they can only be resized.

[aMUSEd]

Yep it's not like a standard window for the 2 main windows that come up - only a minimise and close button.

[jens]

Seems to lock up every time I do a full scan of my VST folder - not found the culprit yet. Is there a log file somewhere I can use to see where it's stalling or a way to exclude some plugins from the scan?

Bit of a problem that it doesn't close that gracefully - took many attempts to kill the thread using Task manager to get it to close.

Normally, a crashing vst plugin should be smoothly intercepted, with a message about it.

This works here - however tbh I find it a bit annoying the the audio- and midi-interface dialogues pop up again after each scan-related crash.

Also during the whole configuration process there's no way to stop playback - and I'm not sure about this, but my assumption is that the scan-process is more prone to crashes during playback - hence I'm not sure about how reasonable this automatic playback of the demo-track really is - or perhaps it should start after the plugin-scan is finished.


edit:

oh, and another thing:

MU.LAB asks again for the vst-folder after each crash.

[pljones]

Just to throw a wide ball in... It still doesn't play nicely under Linux/WINE. The VST scan gets slower and slower as it progresses and audio playback just can't keep up. (C/f Reaper which runs so well you'd swear it was Linux-native.) The point being there's plenty of room for optimisation generally, I'd say.

[ApBTranCer]

wow im very impressed with what you have done so far

heres a couple of bugs ive found:
1: osx sound doesnt play on the first opening..... or the second or third.... 4th time worked like a charm
2: adding a MuVerb to my MuSynth somehow blocks the sound from the output
3: after having trouble with #2, i tryed adding the Muverb to the rack that the Musynth was on, and the same thing happened. Although, reseting the track target to the musynth somehow fixed this problem, but not #2s problem. I also tryed adding a VST effect instead of the muverb to the rack, and it had the same problem, so it might not be a problem with Muverb itself.

now a couple hours later, i tried using the stereo splitter and combiner, same problem, cuts off the audio output.

I cant wait for a stable release!! Im finally starting to see why i would use this host over other hosts

[pljones]

Okay, docs need some working on... What's "AIPS" on a WFT Osc?

If I add a MUX to a MuSynth between Voice In and Voice Out, I lose the audio (whereas putting a MMFilter in the same place is okay). Mono Echo (Short or Long) and AllPass Filter break the audio path. After Voice Out, they all seem to be okay.

I guess that, unless you have a separate MPA for editing the Voice, it's tricky to identify on the menu which components can go where. Would having a "Voice" component, with its own MPA (and built in Voice In and Voice Out plugins) be a bad idea?

[muzycian]

Should be there on the window, just like a standard window.

Oh, wait, which window do you mean?

Plugin editor windows cannot be maximized.

No, it's the same as it was with Luna - neither the main window nor the rack can be maximized - they can only be resized.

Right -> on OSX.

Will fix this.

But does it make sense to maximize it? As then you won't see the rackdesk window anymore?

Do you know about the F1, F2, F3 function keys. They memorize the window positions for 3 states:

-> Composer Only
-> Composer + Rackdesk
-> Composer + MPA

See also the main Edit menu.

[ApBTranCer]

wow im very impressed with what you have done so far

heres a couple of bugs ive found:
1: osx sound doesnt play on the first opening..... or the second or third.... 4th time worked like a charm
2: adding a MuVerb to my MuSynth somehow blocks the sound from the output
3: after having trouble with #2, i tryed adding the Muverb to the rack that the Musynth was on, and the same thing happened. Although, reseting the track target to the musynth somehow fixed this problem, but not #2s problem. I also tryed adding a VST effect instead of the muverb to the rack, and it had the same problem, so it might not be a problem with Muverb itself.

now a couple hours later, i tried using the stereo splitter and combiner, same problem, cuts off the audio output.

I cant wait for a stable release!! Im finally starting to see why i would use this host over other hosts

ok, i might have just fixed my problem... I was adding the muverb before the Voice Out..... now i added it after and it works fine... still doesnt explain the rack effects problem

[pljones]

The MuSynth MPA can't be resized on Windows, as far as I can tell.

The F3 MPA can (and has a Maximise button).

The F3 MPA has it's own Windows Task Bar button, whereas the MuSynth MPA doesn't (it appears when the MU.LAB task bar button is selected).

[muzycian]

Seems to lock up every time I do a full scan of my VST folder - not found the culprit yet. Is there a log file somewhere I can use to see where it's stalling or a way to exclude some plugins from the scan?

Bit of a problem that it doesn't close that gracefully - took many attempts to kill the thread using Task manager to get it to close.

Normally, a crashing vst plugin should be smoothly intercepted, with a message about it.

This works here - however tbh I find it a bit annoying the the audio- and midi-interface dialogues pop up again after each scan-related crash.

You're right.

Also during the whole configuration process there's no way to stop playback - and I'm not sure about this, but my assumption is that the scan-process is more prone to crashes during playback - hence I'm not sure about how reasonable this automatic playback of the demo-track really is - or perhaps it should start after the plugin-scan is finished.

Right again.

edit:

oh, and another thing:

MU.LAB asks again for the vst-folder after each crash.

Right.

Will finetune these things!

Regarding the last note: will make sure that at least the chosen folder is memorized.
I don't think it's bad that the folder browser opens again (with the last chosen path then!) because it offers the choice to change the path, or even cancel the new plug scan! Otherwise if the plug scan would be redone 100% automatic after a crashed plugin, this could be bad too. We need a minimum of control there.
But the proper folder will be memorized.