Bug report

[pquenin]

Ok, I missed this too.
What is the Stereo width for ? If you set it to the minimum, the audio signal is mono ? if it is set to the maximum, the audio signal is not affected or does it make wider stereo than the original ?

[muzycian]

Ok, I missed this too.
What is the Stereo width for? If you set it to the minimum, the audio signal is mono ?

Yes.

if it is set to the maximum, the audio signal is not affected or does it make wider stereo than the original ?

Then the signal is not affected, pan-wise.

[pljones]

I still find this hard to grasp... Or it might be simpler than I imagine. Does this sound right:

If I set the stereo width to minimum, I get a sound that appears to come from a single position in the stereo field ("mono"). I can then pan this.

If I set the stereo width to maximum, then the sound comes from its "natural" position in the stereo field. I can't pan this, as there's "no room" left.

If I want to change the apparent stereo positioning of a sound, I have to narrow the stereo field and then pan the whole field, with the sound coming from the new relative position.

What I find hardest is the UI. I'd like to be able to adjust the width and position independently if the above is correct - i.e. one gesture to narrow the field and then drag the "whole field" left or right without further affecting the width. It's quite a small widget and needs a great degree of dexterity to feel like you have much control, currently...

[Bonteburg]

I was under the impression that, given the field is set to maximum, you have to move the right marker to the left to pan left, and vice versa. Didn't know that you could monofy a rack by moving both markers to the centre,
This is about the pan controls on racks, right?

[muzycian]

I still find this hard to grasp... Or it might be simpler than I imagine.

It's the latter, imho

Does this sound right:

If I set the stereo width to minimum, I get a sound that appears to come from a single position in the stereo field ("mono"). I can then pan this.

Correct.

If I set the stereo width to maximum, then the sound comes from its "natural" position in the stereo field. I can't pan this, as there's "no room" left.

Nope, you CAN pan this because MU.LAB will calculate the possible width from the pan position.

So if you're hard panned left, then there is no room for width, which is 100% logical.

In fact, the GUI displays this.

What I find hardest is the UI. I'd like to be able to adjust the width and position independently if the above is correct - i.e. one gesture to narrow the field and then drag the "whole field" left or right without further affecting the width. It's quite a small widget and needs a great degree of dexterity to feel like you have much control, currently...

Well, it's like you whish:

If you simply click & drag the value, it's about the panning.

If you hold Alt, the you're tweaking the width

[muzycian]

I was under the impression that, given the field is set to maximum, you have to move the right marker to the left to pan left, and vice versa. Didn't know that you could monofy a rack by moving both markers to the centre,

The panner strategy has changed since MU.LAB beta D.

Before then, it was like you described. But that had the disadvantage that you couldn't simply control a panning, as the left & right pan were independent.

The current system is very good, imho.

I'm surprised it causes confusion.

-edit-

atoh, stereo panning isn't always as simple as it first looks.
many people are used to just a pan, even for a stereo signal!
which is spoiling an important parameter: the stereo width!

-/edit-

This is about the pan controls on racks, right?

Yep

[pljones]

If you simply click & drag the value, it's about the panning.
If you hold Alt, the you're tweaking the width

Alt-Click sets the widget back to default. AH! Ctrl-Click set just the width..!

Right... it looks like it works pretty much as I expected now I've found Ctrl-Click I'm happy for MU.LAB to manage the width whilst I'm panning... it's fairly natural now I understand it.

[muzycian]

If you hold Alt, the you're tweaking the width

Alt-Click sets the widget back to default. AH! Ctrl-Click set just the width..!

Oops, right, 'Ctrl' indeed

[pquenin]

Hello,
I want to report another bug :
I create a sequence A.
Now I create a sequence B, and I move the line that separate the note editor and the "value 2" editor. I close the sequence B and open the sequence A.
The line that separate the note editor and the "value 2" editor has also been changed for the sequence A !

I have also noticed that when I go to the "value 2" editor of a sequence and choose a controller or parameter to edit, and then save the session, when I re-open the session, Mulab has lost the controller or parameter that was last edited, you have to choose it again.

Another thing I would love it's that when you right-click in the note editor or the parameter editor, the mouse tools appears in the contextuel menu, so you can quickly change the current tool (I know you can do this with the T key, but then you have to use your other hand or released the mouse...).

[MachFront]

pquenin,
You can also bring up the tools by clicking the mouse wheel.

[pquenin]

Oh yes MachFront, you're right, very nice !

[muzycian]

Hello,
I want to report another bug :
I create a sequence A.
Now I create a sequence B, and I move the line that separate the note editor and the "value 2" editor. I close the sequence B and open the sequence A.
The line that separate the note editor and the "value 2" editor has also been changed for the sequence A !

Not a bug, it's the way it works.

But i guess it can be regarded as a feature request.

I have also noticed that when I go to the "value 2" editor of a sequence and choose a controller or parameter to edit, and then save the session, when I re-open the session, Mulab has lost the controller or parameter that was last edited, you have to choose it again.

Idem.

Cheers

[pquenin]

Hello,
I want to report another bug :
I create a sequence A.
Now I create a sequence B, and I move the line that separate the note editor and the "value 2" editor. I close the sequence B and open the sequence A.
The line that separate the note editor and the "value 2" editor has also been changed for the sequence A !

Not a bug, it's the way it works.
But i guess it can be regarded as a feature request.

It looks like a bug for me, I must admit that it's not a serious one.

I have also noticed that when I go to the "value 2" editor of a sequence and choose a controller or parameter to edit, and then save the session, when I re-open the session, Mulab has lost the controller or parameter that was last edited, you have to choose it again.

Idem.

OK for this one.

[pquenin]

Hello,
can I report new bugs ????

A) Scroll and Zoom
------------------
I have seen that :
1) mouse wheel ............ : scroll vertically
2) alt + mouse whell ...... : scroll horizontally
3) ctrl + mouse wheel ..... : zoom vertically
4) ctrl + alt + mouse wheel : zoom horizontally

All is fine in the sequence editor.
In the composer view (3) don't work (but perhaps there is a reason to this).

B) Loading wav file
-------------------
I draw a part, and choose "Audio part", and then Mulab freezes and crashes.
I think it's because I have not audio device defined (well, I admit that it's strange to have no audio device, but it was just a test).

[muzycian]

A) Scroll and Zoom
------------------
I have seen that :
1) mouse wheel ............ : scroll vertically
2) alt + mouse whell ...... : scroll horizontally
3) ctrl + mouse wheel ..... : zoom vertically
4) ctrl + alt + mouse wheel : zoom horizontally

All is fine in the sequence editor.
In the composer view (3) don't work (but perhaps there is a reason to this).

Thanks for reporting; Fixed in the next version

B) Loading wav file
-------------------
I draw a part, and choose "Audio part", and then Mulab freezes and crashes.
I think it's because I have not audio device defined (well, I admit that it's strange to have no audio device, but it was just a test).

Strange, can't repeat that here...