MU.LAB Beta C

[libero]

I don't know if someone already mentioned this possible bug:

Inside the Value editor (the one for velocity etc. etc.), If I change tool using the shortcut "T" to open the tool palette, the tool doesn't change. If I change it clicking the tool chooser on the corner, it works.
The shortcut works properly on the Sequence editor.

libero

[libero]

-> now you can automate that MUX meta parameter => stereo panning

The problem is that if I draw very fast changes it start to make glitches and noises, as if there is a lack of interpolation between the values created in the Value editor.
EDIT:
It seems more a CPU problem: if I bypass all the other racks, the problem is less and less audible (except for the very fast (ie. vertical) value changes).


-> Suggestion:
When a rack is maximized and a plugin is bypassed, the plugin name becomes grey.
However, if the rack is minimized, there is not any sign that shows the plugin status. Maybe, the white circle should be grey, in those cases.


thanks

libero

[muzycian]

I don't know if someone already mentioned this possible bug:

Inside the Value editor (the one for velocity etc. etc.), If I change tool using the shortcut "T" to open the tool palette, the tool doesn't change. If I change it clicking the tool chooser on the corner, it works.
The shortcut works properly on the Sequence editor.

Right, indeed a little bug there. Will be fixed in beta D. Thanks!

[muzycian]

I don't know if someone already mentioned this possible bug:

Inside the Value editor (the one for velocity etc. etc.), If I change tool using the shortcut "T" to open the tool palette, the tool doesn't change. If I change it clicking the tool chooser on the corner, it works.
The shortcut works properly on the Sequence editor.

Right, indeed a little bug there. Will be fixed in beta D. Thanks!

Note that keyboard input always goes to the focussed gui component.

Initially the note editor has the keyboard focus.

In mu.lab (as in most software), you can change the keyboard focus by clicking a gui component.

Now from mu.lab beta D on, you can also change the keyboard focus by simply hanging over a gui component!

This is an new way, which works very smoothly

So, if you press T in the sequence editor (which contains both the note editor and curve editor), then the tool box of the focussed component pops up. So eventually hover the note editor or curve editor for a moment to make sure it has the keyboard focus.

All this is from beta D on.

[muzycian]

-> now you can automate that MUX meta parameter => stereo panning

The problem is that if I draw very fast changes it start to make glitches and noises, as if there is a lack of interpolation between the values created in the Value editor.
EDIT:
It seems more a CPU problem: if I bypass all the other racks, the problem is less and less audible (except for the very fast (ie. vertical) value changes).

Yes i came to the same conclusion.

The problem is in the curve editor: when you draw very steep curves over small time distance, then mu.lab creates too many duplicate events and that is taking a lot of cpu power when being processed in realtime.

You can see the duplicate events (events on the same time) in the list editor.

This issue is fixed in beta D!

-> Suggestion:
When a rack is maximized and a plugin is bypassed, the plugin name becomes grey.
However, if the rack is minimized, there is not any sign that shows the plugin status. Maybe, the white circle should be grey, in those cases.

Nice suggestion, added on the whishlist.

[libero]

You can see the duplicate events (events on the same time) in the list editor.

This issue is fixed in beta D!

I checked the list editor, now it's clear.

...waiting for beta D

libero

[D-Fusion]

I Mentioned that Firebird+ V1.8 does'nt work in Mulab Beta C.
So i took the time to test it in Cmusic 1.5 and it works fine there

When will Beta D be out?
Beta C has expired.

[muzycian]

-> Suggestion:
When a rack is maximized and a plugin is bypassed, the plugin name becomes grey.
However, if the rack is minimized, there is not any sign that shows the plugin status. Maybe, the white circle should be grey, in those cases.

Nice suggestion, added on the whishlist.

It's graphically not directly evident.

In fact there are 5 slot states:

-> nothing plugged in
-> something plugged in
-> something plugged in & bypassed
-> something plugged in & focussed
-> something plugged in & focussed & bypassed

It would be graphically not obvious to differentiate all these in a clear matter.

I've made a little improvement though: in beta D, the tool tip text now also shows whether a plug is bypassed or not.

So hovering a plug slot with e.g. a bypassed MuVerb tooltips "MuVerb [bypassed]"

[muzycian]

Hi!

feature request:
I find quite difficult to draw the automation for the pan, because left and right pan are separated. if I draw one automation line for one channel, it would be nice to see in transparency (or with another colour) the line for the other channel. Otherwise is quite tedious to jump back and forth from one channel to the other.
Or is there already a better way to control panning?

In beta D, the stereo panning system for racks has changed: instead of separate left & right panning parameters, you now have Stereo Panning and Stereo Width parameters.

[muzycian]

Beta C has expired.

Indeed.

When will Beta D be out?

At latest next saturday.

Sorry for the gap.

[pljones]

blank
-> nothing plugged in

name bold on default background
-> something plugged in (not bypassed, not focussed)

name dimmed on default background
-> something plugged in & bypassed

name bold on highlight background
-> something plugged in & focussed

name dimmed on highlight background
-> something plugged in & focussed & bypassed

Or something?

[muzycian]

blank
-> nothing plugged in

name bold on default background
-> something plugged in (not bypassed, not focussed)

name dimmed on default background
-> something plugged in & bypassed

name bold on highlight background
-> something plugged in & focussed

name dimmed on highlight background
-> something plugged in & focussed & bypassed

Or something?

Yes, that's how it is now for the expanded rack.

But the question was more about a collapsed rack, where there are no names displayed in the plug slots, so we only have the background to play with.

[pljones]

Yes, that's how it is now for the expanded rack.
But the question was more about a collapsed rack, where there are no names displayed in the plug slots, so we only have the background to play with.

Ah, I'd lost track of that... Just use an "X" instead of the name in the circle and follow the same scheme?

[muzycian]

Yes, that's how it is now for the expanded rack.
But the question was more about a collapsed rack, where there are no names displayed in the plug slots, so we only have the background to play with.

Ah, I'd lost track of that... Just use an "X" instead of the name in the circle and follow the same scheme?

Yep, had the same thought

-- edit --

unfortunately it doesn't *look* too good...
so will try to find another solution

-- /edit --

[Jace-BeOS]

i'm assuming the next release will also mean a new release for CMusic?