MU.LAB 2 Test B

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

MU.LAB 2 Test B has been released to a closed group of testers.

If you're an experienced music software user and want to help with testing MU.LAB 2, feel free to join the test group by sending me an email.

Feedback on MU.LAB 2 Test B can be posted in this topic.
Top

Post

Oh no!

I'm getting the same VST screen draw garbage in this version too.
iMac (21.5-inch, Late 2009), 3.06 GHz Intel Core 2 Duo, 8 GB RAM, OSX 10.12.6
Top

Post

Windows MuLab 2 Beta Test B - Small bug with Midi Output.

If you start a new MuSession when no Midi Output has been defined in the Edit>Midi Setup (e.g. none), the MuSession is forever relegated to no Midi Output. The Choose Target dialog will never provide a choice for Midi Output even though it is defined and appears in the Midi Setup dialog. Even saving the MuSession and Opening it again after a Midi Output has been defined will not allow you to choose Midi output for any part.

Test:
- Start a new session with No Midi Outputs in Midi Setup
- Edit>Midi Setup --> add a Midi Output
- Save the session and Quit
- Open the previously saved session (no Midi Output is available - ever)

Maybe this is a feature?
Image
Top

Post

Oh no!

I'm getting the same VST screen draw garbage in this version too.
It's not yet fixed in Test B as it's still being researched...

But there were enough important fixes besides this one to put the light on green for releasing Test B.
Top

Post

jpumphandle wrote:Windows MuLab 2 Beta Test B - Small bug with Midi Output.

If you start a new MuSession when no Midi Output has been defined in the Edit>Midi Setup (e.g. none), the MuSession is forever relegated to no Midi Output.
No, not true, because you can still create the needed midi outputs in the MPA (Modular Plug Area).

Thing is: When a new session is created MU.LAB automatically creates a MIDI Output plugin for each enabled MIDI Port in the MIDI Hardware dialog.

If no MIDI Ports are enabled at session creation time, then indeed no MIDI Output plugins are created, but you can add them manually lateron when needed.

Hope i explain it well.
Top

Post

mutools wrote:Thing is: When a new session is created MU.LAB automatically creates a MIDI Output plugin for each enabled MIDI Port in the MIDI Hardware dialog.
Got it. The plugin is created automatically in the MPA for each Midi Port that is present for a new session. Adding a Midi port later (in Setup), does not automatically add it to the MPA.
Image
Top

Post

Correct.
Top

Post

toxicoh wrote:I'm getting the same VST screen draw garbage in this version too.
Toxicoh, i guess i did not yet say but just fyi: i don't have the issue on the mac mini here. That's why it's more difficult to resolve it.

Is there anyone else on the mac who's experiencing graphical problems when using vst plugin editors?
Top

Post

Just started working with it this morning and noticed a couple things really quick before going to work.
  • 1-. When selecting a plug with the arrow at the upper right corner. I can not use the arrow to close it again and I think it would be a nice option.
    Another thing is that I save a p'roject with CTRL S and a window pops up. Why can't I use the keyboard to chose wether to overwrite the project or not? I think keyboard shortcuts are nice for quick automatic stuff like this.
    2-. I'm having problems with some synths like UGO's. I just can't find how to change presets in them
    3-. Vertigo crashes MuLab while scanning for VSTs. There is another one that does the same but have not found which one it is. I will do a clean set up later tonight and check for the other one that does it. After MuLab recovers from the crash it ignores it, but the crash seems odd
These were things I noticed right of the top of my head and are probably normal behavuiour since V1, but I just got started. I will try to do some audio recording this weekend and finish a tune to get more things going on. :wink:
Carpe diem quam minimum credula postero
Top

Post

Hey joe, great work :) You have no idea how happy i am to see that youve added a sampler to mulab!

I encountered my first crash. I first replaced the the WFT Oscillator with the sample player, and everything is fine. Then when i try to replace the multimode filter with the muverb, mulab crashes. This problem is repeatable. this only happens once i push play, or if i do it while playing.

imac g5 osx 4.10


Something else i noticed, that doesnt really bother me, and is obviously not a priority, is that when i try to clean up (auto arrange) the modules in the musynth, the embeded editors cover up the parts. I guess i expected the modules to wrap around the embeded editor. Again, this is not a big deal, but maybe keep it in mind for a much later release :)
Top

Post

mutools wrote:
toxicoh wrote:I'm getting the same VST screen draw garbage in this version too.
Toxicoh, i guess i did not yet say but just fyi: i don't have the issue on the mac mini here. That's why it's more difficult to resolve it.

Is there anyone else on the mac who's experiencing graphical problems when using vst plugin editors?
No problems here :?

OSX 10.4.11

VSTi tested: RMIV, Crystal, Crossfade Loopsynth, Ticky Clav, Cheeze Machine, Symptohm Melohman and a few others with no GUI (mda synths)

What exactly would I have to do to get the redraw trouble? Just nudging them around?


But I got this crash on quitting Muzys after the VSTI GUI test. Probably something about me trying "MULAB" in the Finder header first? More likely to be RAM trouble after having many biggie VSTI open at the same time.

http://www.fileden.com/files/2007/5/13/ ... _vstis.txt
Top

Post

Good Idea Of The Day:

"Snap to Grid" in the Modular Plug area.

(very low priority)
Top

Post

GermanFafian wrote:When selecting a plug with the arrow at the upper right corner. I can not use the arrow to close it again and I think it would be a nice option.
You mean closing the popup list? Just click outside it and it disappears without making a choice. Just like a normal popup menu.
Another thing is that I save a p'roject with CTRL S and a window pops up. Why can't I use the keyboard to chose wether to overwrite the project or not? I think keyboard shortcuts are nice for quick automatic stuff like this.
You can use the keyboard there. Press [Y] for Yes and [N] for No (on the question "Overwrite xxx")
I'm having problems with some synths like UGO's. I just can't find how to change presets in them
Right-click on the vst name (in the MU.LAB gui) and choose "Choose Program" from the context menu.
Vertigo crashes MuLab while scanning for VSTs. There is another one that does the same but have not found which one it is. I will do a clean set up later tonight and check for the other one that does it. After MuLab recovers from the crash it ignores it, but the crash seems odd
Will have a look at Vertigo.
Top

Post

ApBTranCer wrote:I encountered my first crash. I first replaced the the WFT Oscillator with the sample player, and everything is fine. Then when i try to replace the multimode filter with the muverb, mulab crashes. This problem is repeatable. this only happens once i push play, or if i do it while playing.
Indeed, a crash bug there.

Will add protection there.

Anyway, note it's not possible to use a MuVerb/Stereo Echo/Mux between the voice input and voice output!
when i try to clean up (auto arrange) the modules in the musynth, the embeded editors cover up the parts. I guess i expected the modules to wrap around the embeded editor. Again, this is not a big deal, but maybe keep it in mind for a much later release :)
Ok, i see what you mean; Taken note.
Top

Post

Bonteburg wrote:But I got this crash on quitting Muzys after the VSTI GUI test. Probably something about me trying "MULAB" in the Finder header first? More likely to be RAM trouble after having many biggie VSTI open at the same time.

http://www.fileden.com/files/2007/5/13/ ... _vstis.txt
Thanks for the crash log.

The crash log tells the crash occurred in Symptohm.
Top
Post Reply

Return to “MuTools”