MU.LAB Beta B

[muzycian]

Do you have other asio hosts on your system.

What if you go to their audio setups several times, and/or switch asio driver a couple of times?

I ask this because i want to know wether it's an asio driver issue.

No other ASIO/sound drivers on my system. Just the Creative Audigy 2Zs.

No, i meant other hosts, for example Audacity.

If you go more than once to their audio setup and/or change asio device, do they crash too?

On to something else:
Start MU-LAB
The splash screen comes up, and a dialogue asking what I want to do
Click on "Open..."
The File browser will pop up, but it is partially obscured by the splash screen. Have to move the file browser to see what is there.

True. Will be resolved!

Thanks.

[muzycian]

(I realise this wasn't addressed by BB2 but I thought I'd summarise a bit.)

Still getting the same VST scanning the BB2 as BB. It scans through to Rapture Demo then ignores all subsequent plugins.
http://www.drealm.info/mu.lab/scancrash.jpg is the popup error.
CM Vocoder was in my scan but didn't cause a problem.

Will check the Rapture Demo.

[muzycian]

"File->Save Session As" doesn't seem to work. I created a new folder for my MU.LAB projects called "MU.LAB". I opened an old LUNA PR8.4 project, fixed it up for MU.LAB and then did "Save Session As", chose the new folder and clicked the "New" button to type in a filename. The session was saved as "MU.MuSession" in the same folder as my new folder (not in the new folder).

I'll try a folder without a dot in the name.

-edit- Yes, it seems that the dot in the folder name confused MU.LAB -/edit-

Indeed, mulab does not support dots in file names or file paths.

[muzycian]

(I realise this wasn't addressed by BB2 but I thought I'd summarise a bit.)

Still getting the same VST scanning the BB2 as BB. It scans through to Rapture Demo then ignores all subsequent plugins.
http://www.drealm.info/mu.lab/scancrash.jpg is the popup error.
CM Vocoder was in my scan but didn't cause a problem.

Will check the Rapture Demo.

On windows it runs fine here.

Did a single scan of it though, but i assume that makes no difference.

Anyone else confirming that rapture doesn't load in mulab on windows.

On OSX it doesn't load for some reason, will research further.

[jens]

I don't know if this really is a bug but I can say for sure that it really bugs me:

if the pencil tool is in use, switching from the compossr to the midi-editor or from the midi-editor to the composer, automatically switches to the selection tool.

Each editor memorizes its tool

nope, it doesn't - hence my post - so it's a bug then...

it indeed doesn't.

not that that is a big problem.

i just remembered it wrong.

what's the ideal behaviour here?

the ideal behaviour would be imo either


a) the editors memorize their tool

or

b) the default tool is the pencil instead of the arrow

[Fuzzbeard]

No, i meant other hosts, for example Audacity.

If you go more than once to their audio setup and/or change asio device, do they crash too?

I have is Luna PR8.4 and can go into the Audio Setup as often as I want, see all the inputs and outputs there and I can get into the ASIO control panel no probs.

As far as anything else goes: Notation Software -> Audio Setup no hassels, Kontakt Player 2 -> No probs there either.

Cheers...

Daz :0)

[pljones]

(I realise this wasn't addressed by BB2 but I thought I'd summarise a bit.)
Still getting the same VST scanning the BB2 as BB. It scans through to Rapture Demo then ignores all subsequent plugins.
http://www.drealm.info/mu.lab/scancrash.jpg is the popup error.
CM Vocoder was in my scan but didn't cause a problem.

Will check the Rapture Demo.

On windows it runs fine here.
Did a single scan of it though, but i assume that makes no difference.

I did a single scan and only got the error when closing MU.LAB. The log file has

VstPluginManagerClass.cpp[83]: Exception while creating aeffect for Rapture.dll

Oh..! I get that popup error when I try to run the demo standalone (well, in Seib's minihost).

Still, I'm more concerned that the scan doesn't continue properly.

[Newbie Brad]

I did a clean install of Mu.Lab beta B. I didn't test it very hard, but I got good audio. I noticed when using ASIO4All audio driver I couldn't get the control panel button in the audio setup window to function.

Maybe Asio4All doesn't have a control panel?

Any A4A experts here?

FreeAmp 2 loads but if a few notes are played it seems to crash Mu.Lab beta B's audio, just like it did in beta A. As with beta A, beta B couldn't read keFIR v.1, Loopitch, WaveThresh, Synchro, Eclipse, PanGloss, AlienArtifact, or ReValver 2.

Will check (some of) these plugs.

Not an A4All expert, but it has a control panel. Of the VSTs I noted, I think ReValver 2 might be the most popular, not sure.

[pljones]

Heh... When MU.LAB starts, the splash screen appears (still as lovely as as in LUNA) and then the popup "Open <last>, Open other or New?" (or whatever it says). I chose "Open other" to open an existing MuSession. Hmm. The open dialog appeared under the splash screen!
http://www.drealm.info/mu.lab/splash.jpg

[muzycian]

No, i meant other hosts, for example Audacity.

If you go more than once to their audio setup and/or change asio device, do they crash too?

I have is Luna PR8.4 and can go into the Audio Setup as often as I want, see all the inputs and outputs there and I can get into the ASIO control panel no probs.

So in LUNA it works ok

Also when you actually popup the asio driver list box and choose the same driver?

(effectively choosing the driver, even if it's the same toggles off and on the audio engine in luna)

[muzycian]

or

b) the default tool is the pencil instead of the arrow

Even if there are already parts/notes there?

[muzycian]

(I realise this wasn't addressed by BB2 but I thought I'd summarise a bit.)
Still getting the same VST scanning the BB2 as BB. It scans through to Rapture Demo then ignores all subsequent plugins.
http://www.drealm.info/mu.lab/scancrash.jpg is the popup error.
CM Vocoder was in my scan but didn't cause a problem.

Will check the Rapture Demo.

On windows it runs fine here.
Did a single scan of it though, but i assume that makes no difference.

I did a single scan and only got the error when closing MU.LAB. The log file has

VstPluginManagerClass.cpp[83]: Exception while creating aeffect for Rapture.dll

Ah, on exit you say, so maybe that's the same bug as reported/confirmed earlier (that was with dsk strings i think).

That bug will be resolved in beta C, which will come very soon (tomorrow?) as i want crash bugs to be fixed asap.

Oh..! I get that popup error when I try to run the demo standalone (well, in Seib's minihost).

Euh, not sure if i understand but so this means it's not a mulab issue, right?

Still, I'm more concerned that the scan doesn't continue properly.

Strange that it is not recognized on your system.

Here it loads fine. How about other windows systems?

[muzycian]

(I realise this wasn't addressed by BB2 but I thought I'd summarise a bit.)

Still getting the same VST scanning the BB2 as BB. It scans through to Rapture Demo then ignores all subsequent plugins.
http://www.drealm.info/mu.lab/scancrash.jpg is the popup error.
CM Vocoder was in my scan but didn't cause a problem.

Will check the Rapture Demo.

On windows it runs fine here.

Did a single scan of it though, but i assume that makes no difference.

Anyone else confirming that rapture doesn't load in mulab on windows.

On OSX it doesn't load for some reason, will research further.

On OSX the Rapture demo doesn't load in MU.LAB.

But neither it loads in Live 6.0.10 !

[jens]

or

b) the default tool is the pencil instead of the arrow

Even if there are already parts/notes there?

To be sure! - and why not?

[Fuzzbeard]

So in LUNA it works ok

Also when you actually popup the asio driver list box and choose the same driver?

(effectively choosing the driver, even if it's the same toggles off and on the audio engine in luna)

Hi Jo

Yup, it all works ok in LUNA.

The ASIO driver list offers 3 drivers (which are essentially the same, I think)
1) Creative ASIO
2) SB Audigy 2ZS ASIO [DF00]
3) SB Audigy 2 ZS ASIO 24/96 [DF00]

I can select any one of these, and each one will let me select the control panel and select input/output

Cheers...

Daz :0)