MU.LAB 2.0 Release
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 2938 posts since 18 Jul, 2005
Tougher to see when they're in chords or tight-ish clusters..mutools wrote:Aren't the velocity bars below the notes doing the job?
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Sorry for the delayed reply.Bonteburg wrote:What I personally still don't get is the following idiosyncracy of MU.LAB:
I record a sequence (filter automation in this case) starting from bar 1 to 49. I want the part from 33-49 to repeat over as a loop, so I split the sequence at 33 and duplicate the resulting bit. I open it and the start and end locators inside the sequence are between 65 and 81 rather than 33 and 49 as you (or I) would expect it?
No big deal -once you get it and work around the fact that inside your sequence, what's really bar 33 is now bar 65.
Is this a GUI bug or a function of the pattern logic?
I got your point. Researching...
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Got a question:
When using a Track Target, then that's the target for all parts on that track.
And so using "Choose MIDI Channel" in the sequence part's context menu won't have any effect because it's the track's target which rules.
No i wonder what would be best in such case:
-> Disable "Choose MIDI Channel" in the sequence part context menu
-> Remove "Choose MIDI Channel" from the sequence part context menu
The latter has the advantage that the context menu becomes simpler / easier.
So i would go for the last option. But not sure if this is breaking any stndard GUI rules.
When using a Track Target, then that's the target for all parts on that track.
And so using "Choose MIDI Channel" in the sequence part's context menu won't have any effect because it's the track's target which rules.
No i wonder what would be best in such case:
-> Disable "Choose MIDI Channel" in the sequence part context menu
-> Remove "Choose MIDI Channel" from the sequence part context menu
The latter has the advantage that the context menu becomes simpler / easier.
So i would go for the last option. But not sure if this is breaking any stndard GUI rules.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Generally, I'd go for disabling. It prompts the user to thing "Now, when would I be able to do this?" and they explore further. If they're not aware of an option at all, they won't explore and develop.
-
- KVRist
- 124 posts since 24 Oct, 2005
+1pljones wrote:Generally, I'd go for disabling. It prompts the user to thing "Now, when would I be able to do this?" and they explore further. If they're not aware of an option at all, they won't explore and develop.
-
- KVRAF
- 2938 posts since 18 Jul, 2005
I agree.. grey it out.pljones wrote:Generally, I'd go for disabling. It prompts the user to thing "Now, when would I be able to do this?" and they explore further. If they're not aware of an option at all, they won't explore and develop.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Damn, a typo quoted not once but twice. 
-
- KVRAF
- 2938 posts since 18 Jul, 2005
pljones wrote:Generally, I'd go for disabling. It prompts the user to thing "Now, when would I be able to do this?" and they explore further. If they're not aware of an option at all, they won't explore and develop.
-
- KVRer
- 23 posts since 7 Jul, 2008
Hello,
what about my suggestion to make users able to rename sequences automatically?
Here it is:
http://www.kvraudio.com/forum/viewtopic ... 30#3284330
And there is another user who wants the same:
http://www.kvraudio.com/forum/viewtopic ... 97#3289497
what about my suggestion to make users able to rename sequences automatically?
Here it is:
http://www.kvraudio.com/forum/viewtopic ... 30#3284330
And there is another user who wants the same:
http://www.kvraudio.com/forum/viewtopic ... 97#3289497
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
Bug: Dragging sequences from the arranger window onto my desktop crashes MU.LAB.
Is two-way drag and drop even supposed to be a feature? I was just giving it a go out of interest, when *bam*.
It mostly happens by accident during arranging. The mouse pointer dragging the sequence moves beyond the application window - crash.
Also- quick fix for the locator/start point issue after splitting/duplicating a sequence: Just don't split it!
Duplicating by dragging does the same trick nicely without having to split it up first.
OSX 10.4.11, MU.LAB 2.02
Marco
Is two-way drag and drop even supposed to be a feature? I was just giving it a go out of interest, when *bam*.
It mostly happens by accident during arranging. The mouse pointer dragging the sequence moves beyond the application window - crash.
Also- quick fix for the locator/start point issue after splitting/duplicating a sequence: Just don't split it!
Duplicating by dragging does the same trick nicely without having to split it up first.
OSX 10.4.11, MU.LAB 2.02
Marco
-
- KVRian
- 620 posts since 27 Jul, 2001 from france
I don't understand what you are speaking about, but I have this strange behaviour : I split a part, select one of the 2 pieces and want to move it elsewhere : the 2 pieces are moving ! I have to first select another part and then reselect the piece to have a correct behaviour.Bonteburg wrote:Also- quick fix for the locator/start point issue after splitting/duplicating a sequence: Just don't split it!
Duplicating by dragging does the same trick nicely without having to split it up first.
Marco
PQ
free software at : http://pquenin.free.fr/pqnaudio
free music at : http://www.soundclick.com/thepqueninproject
free software at : http://pquenin.free.fr/pqnaudio
free music at : http://www.soundclick.com/thepqueninproject
-
- Hun #3
- 4265 posts since 25 Mar, 2002 from A quaint little village just south of Hamburg, Germany
Can't repeat that - are you on OSX too?
[Dumb Question]Are you really sure that only one of them is selected? [/Dumb Question]
Because MU.LAB is a little tricky at that. When you split a selected part, both resulting parts remain selected by default. Even when you click ("select") one of them, they both remain selected. When you move the one, you're moving the other. Splitting an unselected part gives you two unselected parts.
That could easily explain your "I have to select another part first" syndrome.
I'm not sure if it's the best possible default behaviour but it's pretty easy to get used to. It's rather a small inconsistency than a "legitimate" feature I reckon.
What could be a better behaviour?
Possibly, MU.LAB could unselect all previously selected parts whenever you perform a split, giving you a clean slate.
Marco
[Dumb Question]Are you really sure that only one of them is selected? [/Dumb Question]
Because MU.LAB is a little tricky at that. When you split a selected part, both resulting parts remain selected by default. Even when you click ("select") one of them, they both remain selected. When you move the one, you're moving the other. Splitting an unselected part gives you two unselected parts.
That could easily explain your "I have to select another part first" syndrome.
I'm not sure if it's the best possible default behaviour but it's pretty easy to get used to. It's rather a small inconsistency than a "legitimate" feature I reckon.
What could be a better behaviour?
Possibly, MU.LAB could unselect all previously selected parts whenever you perform a split, giving you a clean slate.
Marco
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
It's on the whishlist.admc wrote: what about my suggestion to make users able to rename sequences automatically?
Here it is:
http://www.kvraudio.com/forum/viewtopic ... 30#3284330
And there is another user who wants the same:
http://www.kvraudio.com/forum/viewtopic ... 97#3289497
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
No.Bonteburg wrote:Bug: Dragging sequences from the arranger window onto my desktop crashes MU.LAB.
Is two-way drag and drop even supposed to be a feature?
It's not supported, but it should not crash.I was just giving it a go out of interest, when *bam*.
Will be fixed.
Thanks for reporting!