MU.LAB beta A

[muzycian]

Oh I see!
That's normal behaviour then, never mind that.

I guess you were playing *very* low notes then, right?

A quick check: did the startup demo groove played ok?

But hey: Come to think of it wouldn't it be cool to turn it off? To have that quick and dirty sampler option.
But that's more of a feature request.

Sure a sampler module will be added lateron

I'll try and recreate the neverending note thing with a simple MuSynth patch and DX10 is that ok?

OK, thanks!

By the way: i'm doing some optimizations regarding the lists; Marco, please check if with beta B navigating thru your wave libraries goes faster. Beta B will be there 1 of the days, may be 2morrow.

[Bonteburg]

ok ...

[Bonteburg]

pm sent!

[Bonteburg]

Also, I couldn't see the sequences I had recorded. I could still hear them, though.

[> DiGiT <]

wow great improvement all around, and cool to see the modular musynth!

as soon as i chose an asio driver, it played until i canceled out of the vst scan, then everything got slow, almost like a lockup. i couldnt break it out of this but was able to close the program. when i restarted, the same thing happened but no vst scan... played for a few seconds and then froze.

cant wait to see this workin well!

[Trapaki]

This really looks cool!!!

Modular system is amazing. I think it would be
even great to switch from building patch view
to simple interface view - with everything in
the one window.

From my first experience:

1. OSX first startup - no sound.
2. Mu.LAB seems to be much more CPU heavy. It's probably because of new modular structure and my rather old laptop. Anyway with PowerBook 1.5 GHz and over 1.25 RAM I had problems even with listening to demo song.
3. While loading audio sample and changing view to LAB
I heard just some glitches and cuts.. but will need to try it again lateron... it was very late at night.

Best!
P.

[Trapaki]

To be more specific - this view switch - of course as an additional option - not instead building view.

[Caleb]

Oh - that's a nice update!

I wasn't fond of the last skin for some reason - but this one is somehow more "fun".
MuZynth looks like a monster - LOVE the assignable parameter buttons. There's lots.

I'll have to see if I can make some time to play.

Are you only interested in bug testing at this point or are you open to pushy feature requests?

In any case - very tasty!

Regards
Caleb

[aMUSEd]

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.

[aMUSEd]

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

[muzycian]

Also, I couldn't see the sequences I had recorded. I could still hear them, though.

Bonte, as pmed tonight, i'll dig into the files you sent. Hope to find some reason(s).

Can you please let me know your system details again. Thanks.

[muzycian]

wow great improvement all around, and cool to see the modular musynth!

as soon as i chose an asio driver, it played until i canceled out of the vst scan, then everything got slow, almost like a lockup. i couldnt break it out of this but was able to close the program. when i restarted, the same thing happened but no vst scan... played for a few seconds and then froze.

cant wait to see this workin well!

Does this mean that the music was playing well while the vst folder browser window was open?

And so it slowed down as soon as you closed that window?

You can easily repeat the first startup sequence by

1) quit mulab and got mulab/settings folder
2) open mulab.txt and set ApplicationRunCount=0
3) save file and restart mulab

[muzycian]

This really looks cool!!!

Modular system is amazing. I think it would be
even great to switch from building patch view
to simple interface view - with everything in
the one window.

That's the plan

From my first experience:

1. OSX first startup - no sound.

On 2nd run yes?

2. Mu.LAB seems to be much more CPU heavy. It's probably because of new modular structure and my rather old laptop. Anyway with PowerBook 1.5 GHz and over 1.25 RAM I had problems even with listening to demo song.

The little demo song does use some cpu, but i'll check this more profound.

3. While loading audio sample and changing view to LAB
I heard just some glitches and cuts.. but will need to try it again lateron... it was very late at night.

Maybe that's related to 2) ?

[muzycian]

Oh - that's a nice update!

I wasn't fond of the last skin for some reason - but this one is somehow more "fun".
MuZynth looks like a monster - LOVE the assignable parameter buttons. There's lots.

I'll have to see if I can make some time to play.

Are you only interested in bug testing at this point or are you open to pushy feature requests?

In any case - very tasty!

Regards
Caleb

I'm always open to suggestions.

Atoh, for the very moment i whish i had a dual core head so to speed up the beta stabilization

[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.

But it always can be that there is another problem that slips thru this safety net.

Anyway, if anything goes wrong during scan, you should see a "VstPluginScanLog.txt" in your mulab/settings folder.

Then the very last line should hint you about the problematic one.

Can you please let me know which one that is, so i'll scan it here too (if available version).