MU.LAB Beta B

[muzycian]

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?

Why not?

Because if there already parts/notes there, then why would it be obvious the first next action you want to do is something with the pencil?

Besides this filosofical question, i think to go for the 'memorize tool' option, sounds the most logical to me.

[muzycian]

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

And you are sure that you are working with beta B2 now?

With beta B2, in audio setup, the asio ins/outs must show up!

Can others please confirm that the audio setup -> no ins/outs problem of beta B has been resolved in beta B2.

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

Why not?

Because if there already parts/notes there, then why would it be obvious the first next action you want to do is something with the pencil?

first of all the pencil tool has all the functions the selection tool has (so what's the selection too for anyway? - or am I missing something?) and then a sequence is never final - e.g. with beat-programming I often start with a basic pattern and then later on add breaks and stuff...

...and last but not least in the composer you need the pencil to add seuquences.

[muzycian]

Ok, i checked some vst plugins in MU.LAB beta B2 that were reported to cause problems:

-------------------------------------------------

LoopPitch:

Can't find it, it appears that the website has gone..?

keFIR:

Scans and loads ok here.

I note that if i plug it in, it first gives a nasty sound until i load a wave in it.

Nice plug btw.

PanGloss:

Scans and loads ok here.

Revalver II:

Scans and loads ok here.

Sounds good.

Cinematic Reverb:

Scans and loads ok here.

Funny sound

-------------------------------------------------

So the problems seem to be system dependent.

If a plug is not working in your MU.LAB, please also try it out in another host.

Also, you can always check wether there are any missing files on your system that the plugin needs by using this free tool: Dependency Walker.

Of course this tip is valid for plug problems in any host, not only MU.LAB.

[muzycian]

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?

Why not?

Because if there already parts/notes there, then why would it be obvious the first next action you want to do is something with the pencil?

first of all the pencil tool has all the functions the selection tool has (so what's the selection tool for anyway? - or am I missing something?)

it can simply lasso parts/notes

ok, the pencil tool can make selections too by holding shift, but then you need the shift (and you need to know it).

and then a sequence is never final - e.g. with beat-programming I often start with a basic pattern and then later on add breaks and stuff...

...and last but not least in the composer you need the pencil to add seuquences.

ok, in beta C, the editors memorize their tool. so that's absolutely the best option as everyone can use his favorite tool.

i must admit that the arrow and pencil tools are almost equal, they've grown to eachother.

if the selection issue could be resolved in an easy and user friendly way, both tools could be merged, and only the flexible pencil tool would survive. but i don't see a friendly way (=without using modifiers)

[jens]

but i don't see a friendly way (=without using modifiers)

what about left click + right click?

[muzycian]

but i don't see a friendly way (=without using modifiers)

what about left click + right click?

right click is reserved for the context menu thruout the application.

[jens]

but i don't see a friendly way (=without using modifiers)

what about left click + right click?

right click is reserved for the context menu thruout the application.

I know of course - but what I meant was left-click first and, while keeping the left button pressed, also click the right one...

[Fuzzbeard]

And you are sure that you are working with beta B2 now?

With beta B2, in audio setup, the asio ins/outs must show up!

Can others please confirm that the audio setup -> no ins/outs problem of beta B has been resolved in beta B2.

Hi Jo

I Deleted the version that I was working with. You're right, it was B1 (the file dates were different from B2). Sorry about that.

So, now I can see the inputs/outputs
But...
Still cannot access the ASIO control Panel
MU-LAB still crashes if I go into the Audio Setup again after the initial run. It crashes after I click the OK button.

Cheers...

Daz :0)

[Stephan326]

Everything is working great here!!!!!

[muzycian]

but i don't see a friendly way (=without using modifiers)

what about left click + right click?

right click is reserved for the context menu thruout the application.

I know of course - but what I meant was left-click first and, while keeping the left button pressed, also click the right one...

nice suggestion jens, thanks, but i regard that as equally difficult as using shift.

both methods are difficult to know without knowledge about the application.

and that's a VERY important criterium.

i want mu.lab to be so easy that it can be used by kids, without reading any docs.

that's the goal.

(not there yet, i know)

now having said that, i'm sure you can give me a list where this criterium fails

well, if you do, i will be happy to finetune each and every item on that list!

[muzycian]

And you are sure that you are working with beta B2 now?

With beta B2, in audio setup, the asio ins/outs must show up!

Can others please confirm that the audio setup -> no ins/outs problem of beta B has been resolved in beta B2.

Hi Jo

I Deleted the version that I was working with. You're right, it was B1 (the file dates were different from B2). Sorry about that.

No prob, i'm glad to hear, as this explains and resolves part of the problem.

So, now I can see the inputs/outputs
But...
Still cannot access the ASIO control Panel

True, that one is fixed in beta C, coming one of the days.

MU-LAB still crashes if I go into the Audio Setup again after the initial run. It crashes after I click the OK button.

Well, this one i don't understand yet...

Will think it over.

It's so strange because you say it works in luna and not in mulab... can't see a reason yet.

[muzycian]

Everything is working great here!!!!!

Thanks for the feedback

[fycfung]

Hi Jo,
Those recording problems are perhaps even a bit worse than I first said in my message above. I haven't quite pinned down exactly how to reproduce it yet but probably close to 1/3 of the time when I try to record a MIDI track, it doesn't get persisted as a track (though it's there and if I hit the play button, it will play, and then get stuck on the last note). Has anyone else had a problem like this?

[muzycian]

Hi Jo,
Those recording problems are perhaps even a bit worse than I first said in my message above. I haven't quite pinned down exactly how to reproduce it yet but probably close to 1/3 of the time when I try to record a MIDI track, it doesn't get persisted as a track (though it's there and if I hit the play button, it will play, and then get stuck on the last note). Has anyone else had a problem like this?

Hey fycfung, i didn't forget about your message.

But i don't have my keyboard here at the moment. Will only have it back wednesday. Then i will concentrate again on these midi input / recording issues.

By the way, what system are you on? which midi device? which keyboard?