MU.LAB Beta B

[muzycian]

Hey,

Just using this same topic thread to announce that MU.LAB beta B2 is available at the usual location.

Notification emails have been sent also.

WHAT'S NEW
----------

* Fixed: Windows: Choosing the ASIO outputs didn't work, and resulted in no sound
* Fixed: Nasty crash bug when doing audio setup while music was playing

* Tuned: Finetuned logging system
* Tuned: On "New Session", sequencer stops

[muzycian]

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?

No, sorry, it's a bug which will be resolved in beta C.

[> DiGiT <]

all my problems so far have been fixed. very exciting to see this come together!

id love to see some arrangement tools built in, like the play room or the possibility to tie a sequence to a set of keys, and another routine to capture the 'performance' so to speak, for further editing.

but you knew that, right?

[muzycian]

-I still get the hanging note syndrome

-Being able to replace a VST for another one in the racks without having to delete it before would speed up things greatly

Would you liek to have the single-click back?

What do others think here?

To be honest, although Luna is now a pale shadow of what Mulab has become, there are still elemnts of Luna PR7b's functionality that I miss. It is hard to put my finger on what just felt right about using Luna PR7b, and it just may be that this was the version where everything fell into place for me and I gained a better understanding of how to operate Luna. But there is something about introducing double-clicking to replace the edit button that just seems to slow the whole process down (one more option to think about).

I fully agree.

In fact i was thinking about this last night.

I quickly removed the round controls at the right of the rack slots because they were "unused" for non-sends, and so they were confusing at that point.

But to be honnest i don't have a clue why the "edit" button slipped outside play. Can't remember a reason.

It seems definitely right to bring it back.

Doubleclicking the slot stays active too.

Still not sure what's the best action on single-clicking a filled rack plug slot.

I also miss the fact that recorded automation of a rack's volume and pan no longer flags up the name of the corresponding rack in the Property Panel (Just the words "mixer strip").

Ah, didn't notice this yet. Will improve this.

Perhaps something like pljones's suggestion may be the answer:

Would you liek to have the single-click back?
What do others think here?

Click on an empty rack-slot should prompt to add, as it does. Click on a filled in rack-slot should at least focus, if not open, the plugin (it doesn't focus it at the moment - just doesn't popup the plugin list). Right-click could offer "insert plugin", maybe, if the rack-slot is empty and "replace plugin" if it's filled.

Yes, i didn't read that post good enough.

In fact that's a very neat idea

And you know what: if the slot is empty then we could put a little dropdown control at the right to select a plug:



Together with:

A rightclick on an empty slot allows insert plugin.
A doubleclick on an empty slot allows insert plugin.
A singleclick does nothing (or also insert plugin?)

A rightclick on a filled slot allows replace plugin.
A doubleclick on a filled slot edits the plugin.
A singleclick focusses the plugin (?)

I know that some compromises were necessary to make the Modular Plugin Area work in conjunction with the Racks.

It's not about compromises. I just did some serious reorganisations in the code, and i guess what we experience now is that there are still "rough edges" on this new technology, so lets abrade these.

I would never want to see Mulab take a step backwards, but every now and then it may be worth revisiting the earlier incarnations of Mulab to make sure that nothing important has been lost.

100% agreed!

In fact (believe it or not) i've added a note on the todo list about re-checking the interface so that everything works nice and easy.

I'm confident you understand that i have been focussing on the technology side "a bit"

So lets also focus on the ergonomy now.

Easy workflow.

I realise i'm not providing any sort of solution here, just observations. Perhaps I just want the edit button back cause it looked pretty on my skin!

[muzycian]

all my problems so far have been fixed. very exciting to see this come together!

id love to see some arrangement tools built in, like the play room or the possibility to tie a sequence to a set of keys, and another routine to capture the 'performance' so to speak, for further editing.

but you knew that, right?

Yes i know

And i'm sure you're not alone!

But please try to keep real new feature requests for a bit later, just until this beta is rock solid!

It's so important that we finetune this version first!

And believe me, this is no time waste.

The better we get this structured and finetuned, the faster new developments will go.

It's about keeping everything neat.

[Fuzzbeard]

Hi Joe

MU-LAB will always crash on me if I try end edit the Audio settings.

On the first run I will get asked all the usual questions, (and I notice that the samplerate is set correctly in the audio setup) If I try and select Audio Inputs and Outputs, I still get no options, nor do I get a control Panel for ASIO (Creative ASIO does have a control Panel).
After answering everything, I will come to the Sequencer window. I can play the demo session, and get sound.

Now the following happens regardless of whether or not I have played the sample session or not.
Go to Edit->Audio setup
Click OK
Crash.

I then find the same thing as Beta-B. MU-LAB is still present in the Process List and I cannot get rid of it unless I reboot (there are currently 4 instances of MU-LAB in the process list - reboot after finishing this pos).

As far as the Samplerate issue was concerned, this behaviour (could not set the samplerate to 44000Hz) did also occur in Beta A, but only once. After it had automatically set the samplerate to 48000Hz, the error never came up again. It also occurred in LUNA as well as a couple of other apps, so I usually take no notice of it at all. One thing that was interesting with Beta A, on the first Run, I could not actually modify the setting for the sample rate directly via Audio Setup. But, as I say, MU-LAB seemed to fix this by itself, so I took no notice.

Cheers...

Daz :0)

[muzycian]

Hi Joe

MU-LAB will always crash on me if I try end edit the Audio settings.

Which version is that?

Beta A, B or B2?

-edit- ok, from reading the rest of your message, i assume B2 -/edit-

On the first run I will get asked all the usual questions, (and I notice that the samplerate is set correctly in the audio setup) If I try and select Audio Inputs and Outputs, I still get no options, nor do I get a control Panel for ASIO (Creative ASIO does have a control Panel).

With beta B2 the audio inputs and outputs should popup right. Can others please confirm?

The asio control panel issue indeed is a bug, will be resolved in beta C.

After answering everything, I will come to the Sequencer window. I can play the demo session, and get sound.

Now the following happens regardless of whether or not I have played the sample session or not.
Go to Edit->Audio setup
Click OK
Crash.

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.

Does anyone else has a similar problem with beta B2?

I then find the same thing as Beta-B. MU-LAB is still present in the Process List and I cannot get rid of it unless I reboot (there are currently 4 instances of MU-LAB in the process list - reboot after finishing this pos).

I'm sure that that is a driver issue.

As far as the Samplerate issue was concerned, this behaviour (could not set the samplerate to 44000Hz) did also occur in Beta A, but only once. After it had automatically set the samplerate to 48000Hz, the error never came up again. It also occurred in LUNA as well as a couple of other apps, so I usually take no notice of it at all. One thing that was interesting with Beta A, on the first Run, I could not actually modify the setting for the sample rate directly via Audio Setup. But, as I say, MU-LAB seemed to fix this by itself, so I took no notice.

I think it's ok that if the user gets the samplerate warning, he simply has to go once to the audio setup to choose a proper samplerate, agreed?

It's only once, and so then he has consciously chosen a samplerate.

Thanks.

[thearne76]

crash on exit using dsk strings....everything went to the autosave and was fine but it will crash when saving or exiting.

Also when going through the presets can you add the little presets box underneath the vst window. easier to go go through it that way when just scanning through looking for sounds ( this would only apply to those that use that preset setup.)

[Fuzzbeard]

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.

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.

Cheers...

Daz :0)

[Fuzzbeard]

As far as the Samplerate issue was concerned, this behaviour (could not set the samplerate to 44000Hz) did also occur in Beta A, but only once. After it had automatically set the samplerate to 48000Hz, the error never came up again. It also occurred in LUNA as well as a couple of other apps, so I usually take no notice of it at all. One thing that was interesting with Beta A, on the first Run, I could not actually modify the setting for the sample rate directly via Audio Setup. But, as I say, MU-LAB seemed to fix this by itself, so I took no notice.

I think it's ok that if the user gets the samplerate warning, he simply has to go once to the audio setup to choose a proper samplerate, agreed?

It's only once, and so then he has consciously chosen a samplerate.

Thanks.[/quote]

Yes, I agree.
As IU said, I usually Ignore it because after the initial warning on the first setup, Luna/MU-LAB sorts it out properly. I only included the symptom because I thought that it might be relevant to the crashing on Audio Setup.

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.

[pljones]

"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-

[muzycian]

crash on exit using dsk strings....everything went to the autosave and was fine but it will crash when saving or exiting.

Will check dsk strings.

[D-Fusion]

I was testing the assign midi controll function in MuLab and i wonder if you could add midi learn on the source midi (Controller).

It would also be cool if we could be be able to save midi controller templates

[muzycian]

crash on exit using dsk strings....everything went to the autosave and was fine but it will crash when saving or exiting.

Will check dsk strings.

Confirmed, a bug in mulab.

Mulab could crash on exit or new session, or revert session.

The bug not only applied to dsk strings, was more general, though will have occurred rather rare, i think.

Anyway, resolved in beta C.

Thanks