MU.LAB test 3.0.27 is available in http://www.mutools.com/mulab/azalea
What's changed: http://www.mutools.com/mulab/azalea/mul ... hanges.txt
If you have already installed 3.0.24, you can simply apply the latest patch.
This is one of the last test versions.
Please report any left bugs!
Thanks!
M3 Tests
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRist
- 357 posts since 5 Aug, 2006 from St. Louis
M3.0.27 Crash
When I have Loopazoid in a rack, Then Edit>Audio Setup and click OK, I get a crash.
Loopazoid uses multiple outputs 1/2, 3/4, 5/6, 7/8. My Audio setup only has 1/2, 3/4.
Loopazoid is compiled for both PC and MAC, my crash is on the PC.
When I have Loopazoid in a rack, Then Edit>Audio Setup and click OK, I get a crash.
Loopazoid uses multiple outputs 1/2, 3/4, 5/6, 7/8. My Audio setup only has 1/2, 3/4.
Loopazoid is compiled for both PC and MAC, my crash is on the PC.
-
- KVRist
- 152 posts since 15 May, 2009 from Germany
Ah, just checked the event graph editor,
had a little bit to try until I see that snap is also working in this editor.
With snap on, unusual behavior, but at the end seems to be logical,
might be useful for something
(e.g. drawing a short line near a grid bar leads to nothing,
because start and end of the line are snapping to the bar resulting
in a line of length zero, logic, but confusing the first time)
had a little bit to try until I see that snap is also working in this editor.
With snap on, unusual behavior, but at the end seems to be logical,
might be useful for something
(e.g. drawing a short line near a grid bar leads to nothing,
because start and end of the line are snapping to the bar resulting
in a line of length zero, logic, but confusing the first time)
Everything should be made as simple as possible, but not simpler!
-
- KVRist
- 152 posts since 15 May, 2009 from Germany
Does mulab support multi screen ?
Would be nice to extend e.g. composer window across two screens,
but I suppose this does not work.
Would be nice to extend e.g. composer window across two screens,
but I suppose this does not work.
Everything should be made as simple as possible, but not simpler!
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
And this wasn't the case with 3.0.26?jpumphandle wrote:M3.0.27 Crash
When I have Loopazoid in a rack, Then Edit>Audio Setup and click OK, I get a crash.
Loopazoid uses multiple outputs 1/2, 3/4, 5/6, 7/8. My Audio setup only has 1/2, 3/4.
Loopazoid is compiled for both PC and MAC, my crash is on the PC.
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
I understand.Eggu wrote:Ah, just checked the event graph editor,
had a little bit to try until I see that snap is also working in this editor.
With snap on, unusual behavior, but at the end seems to be logical,
might be useful for something
(e.g. drawing a short line near a grid bar leads to nothing,
because start and end of the line are snapping to the bar resulting
in a line of length zero, logic, but confusing the first time)
What do you suggest?
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Yes.Eggu wrote:Does mulab support multi screen?
Should work fine i think.Would be nice to extend e.g. composer window across two screens,
but I suppose this does not work.
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
Maybe I didn't think this one deep long enough but,
why is that if I change the length of a group of selected notes (the "end" of the notes) all of them are effected but if I try to modify the start position (the beginning of the notes), only the dragged "note" (just that one) is effected?
In other words:
Editing the end position of multiple selected notes effects All of them
While
Editing the Start position of multiple selected notes effects only the one being edited out of the group.
why is that if I change the length of a group of selected notes (the "end" of the notes) all of them are effected but if I try to modify the start position (the beginning of the notes), only the dragged "note" (just that one) is effected?
In other words:
Editing the end position of multiple selected notes effects All of them
While
Editing the Start position of multiple selected notes effects only the one being edited out of the group.
ABEFLGMOPPRRST 
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
What is the most frequent Part used by MuLab users?
I was thinking that the context menu could show the Sequencer before the Audio.
It is just a little detail but if it is the one mostly used by us it should be the first. Trying to smooth out corners....
Any opinions on this one?
I was thinking that the context menu could show the Sequencer before the Audio.
It is just a little detail but if it is the one mostly used by us it should be the first. Trying to smooth out corners....
Any opinions on this one?
ABEFLGMOPPRRST
-
- KVRist
- 131 posts since 10 Jan, 2010 from York, UK
Options, for new Part type, after just deleting a Sequence part.
Not sure if this has been covered previously (or is possibly intended behaviour).
Using test version M 3.0.27 (Windows):
1. Record a short midi sequence on Track A (targeted, for example, to Rack A).
2. Add a plugin to slot 1 of Rack A, and check that playback is ok.
3. Delete the Sequence part, from Track A.
4. Double click in Track A, to create a new Part. The options no longer include 'Audio File' (ie 'Sequence' is the only available option ).
Other (blank) tracks are not affected.
5. Then delete the plugin from Rack A.
Double-click in Track A, to add a new Part, and the options are back to normal.
Les J.
Not sure if this has been covered previously (or is possibly intended behaviour).
Using test version M 3.0.27 (Windows):
1. Record a short midi sequence on Track A (targeted, for example, to Rack A).
2. Add a plugin to slot 1 of Rack A, and check that playback is ok.
3. Delete the Sequence part, from Track A.
4. Double click in Track A, to create a new Part. The options no longer include 'Audio File' (ie 'Sequence' is the only available option ).
Other (blank) tracks are not affected.
5. Then delete the plugin from Rack A.
Double-click in Track A, to add a new Part, and the options are back to normal.
Les J.
-
- KVRian
- 1372 posts since 21 May, 2004 from Serbia
I doesn't seem to work. I can't stretch MuLab's window outside of the screen where it resides, and when I position MuLab to partially fill both screens and then try to stretch it, the other end of the window automatically resizes to the end of screen from where it is stretched. It is possible to use the mixer and the modular area in another screen, though.mutools wrote:Should work fine i think.Eggu wrote:Would be nice to extend e.g. composer window across two screens,
but I suppose this does not work.
-
- KVRist
- 152 posts since 15 May, 2009 from Germany
Yes,Branis wrote:I doesn't seem to work. I can't stretch MuLab's window outside of the screen where it resides, and when I position MuLab to partially fill both screens and then try to stretch it, the other end of the window automatically resizes to the end of screen from where it is stretched. It is possible to use the mixer and the modular area in another screen, though.mutools wrote:Should work fine i think.Eggu wrote:Would be nice to extend e.g. composer window across two screens,
but I suppose this does not work.
I have the same behaviour (windows 7),
single sub-windows can be placed on 2nd screen,
but streching of main window over both screens does not work.
Everything should be made as simple as possible, but not simpler!
-
- KVRist
- 152 posts since 15 May, 2009 from Germany
Hmm,mutools wrote:I understand.Eggu wrote:Ah, just checked the event graph editor,
had a little bit to try until I see that snap is also working in this editor.
With snap on, unusual behavior, but at the end seems to be logical,
might be useful for something
(e.g. drawing a short line near a grid bar leads to nothing,
because start and end of the line are snapping to the bar resulting
in a line of length zero, logic, but confusing the first time)
What do you suggest?
leave it as it is (because it is logcal, though strange),
but display snap status permanently (might be together with current grid setting)
Everything should be made as simple as possible, but not simpler!
-
- KVRist
- 357 posts since 5 Aug, 2006 from St. Louis
Yes, this crash occurs on all versions of Mulab (including 2.7).mutools wrote:And this wasn't the case with 3.0.26?jpumphandle wrote:M3.0.27 Crash
When I have Loopazoid in a rack, Then Edit>Audio Setup and click OK, I get a crash.
Loopazoid uses multiple outputs 1/2, 3/4, 5/6, 7/8. My Audio setup only has 1/2, 3/4.
Loopazoid is compiled for both PC and MAC, my crash is on the PC.
This may be an error in the Loopazoid plugin, but when you close the Audio engine and try to open it you get a crash in Mulab.
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
I've got an idea how to improve it. Added to the whishlist.Eggu wrote:Ah, just checked the event graph editor,
had a little bit to try until I see that snap is also working in this editor.
With snap on, unusual behavior, but at the end seems to be logical,
might be useful for something
(e.g. drawing a short line near a grid bar leads to nothing,
because start and end of the line are snapping to the bar resulting
in a line of length zero, logic, but confusing the first time)