M3 Tests
- KVRian
- 1372 posts since 21 May, 2004 from Serbia
(This is not M3 specific since it's inherited from earlier MuLab versions)
In The VST Manager there's no way to remove a plugin from a group, just to move it to another group. Though this is possible by editing the VstPlugins.Xml file it might be good to have a "no group" option, or something similar.
In The VST Manager there's no way to remove a plugin from a group, just to move it to another group. Though this is possible by editing the VstPlugins.Xml file it might be good to have a "no group" option, or something similar.
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
MU.LAB 3.0.37 is available at
Full package: http://www.mutools.com/downloads.html
Application patch: http://www.mutools.com/mulab/patch
If you have already installed 3.0.32, you can simply apply the latest patch.
What's changed: http://www.mutools.com/mulab/changes.txt
Release planned on coming friday.
Full package: http://www.mutools.com/downloads.html
Application patch: http://www.mutools.com/mulab/patch
If you have already installed 3.0.32, you can simply apply the latest patch.
What's changed: http://www.mutools.com/mulab/changes.txt
Release planned on coming friday.
- KVRAF
- 1706 posts since 22 Apr, 2009 from Belgrade
a little bug report:
double click the composition window to create a new sequence. the new sequence automatically gets a default name. now, record some midi into this empty sequence. when finished recording, mulab will prompt for a sequence name. enter a desired sequence name and press enter. the sequence keeps its old default name.
double click the composition window to create a new sequence. the new sequence automatically gets a default name. now, record some midi into this empty sequence. when finished recording, mulab will prompt for a sequence name. enter a desired sequence name and press enter. the sequence keeps its old default name.
Bedroom Producers Blog << Free VST Plugins!
-
- KVRist
- 152 posts since 15 May, 2009 from Germany
2nd bug report:
having selected multiple notes in midi editor,
and changing the beginning of one of these notes, then only this one note is affected,
not all selected notes (as when changing end of notes).
having selected multiple notes in midi editor,
and changing the beginning of one of these notes, then only this one note is affected,
not all selected notes (as when changing end of notes).
Everything should be made as simple as possible, but not simpler!
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Will check and fix.bpblog wrote:a little bug report:
double click the composition window to create a new sequence. the new sequence automatically gets a default name. now, record some midi into this empty sequence. when finished recording, mulab will prompt for a sequence name. enter a desired sequence name and press enter. the sequence keeps its old default name.
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
It's not a bug. It's just not (yet) supported. Would be more consistent if it does, agreed. It's on the whishlist.Eggu wrote:2nd bug report:
having selected multiple notes in midi editor,
and changing the beginning of one of these notes, then only this one note is affected,
not all selected notes (as when changing end of notes).
