MU.LAB Beta C

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

Post

MU.LAB beta C is ready :)

This new beta fixes a handful of nasty bugs, but definitely also features a lot of fine tunings!

WHAT'S NEW
----------

* New: Each Rack can be collapsed/expanded individually via a little switch at the top-left of the rack. You can also right-click that switch for extra functions.
* New: When using equal names (e.g. Audio Files, Sequences, ...) then an automatic index is added to the name

* Tuned: Even faster startup
* Tuned: Finetuned first run procedure
* Tuned: Before doing the very first vst scan, other settings are saved, so if the scan crashes, you don't have to redo all initial settings

* Tuned: Shift + doubleclick Pencil = select none! Now the pencil tool can do almost everything! Cfr the included docs.
* Tuned: Editors memorize their mouse tool
* Tuned: No undo/redo alerts anymore, except to alert if no undo/redo available

* Tuned: Finetuned some aspects when recording MIDI
* Tuned: Audio File Pool and Sequence Pool are alfabetically sorted
* Tuned: Free version: No more limits on the number of racks and synths, but on the number of tracks: Free version can use up to 8 tracks.

* Tuned: When plugging in a *synth* in a Rack, the Rack gets focus
* Tuned: Rack Desk always shows some extra space at the right so you can always add a rack
* Tuned: Racks in the Rack Desk now have an indication wether it is focussed or not. This is independent from being collapsed/expanded.
* Tuned: A double-click on a rack output also opens the editor for that output, if any of course.
* Tuned: The edit button is back in play near the rack slots :)
* Tuned: A single click on a filled rack slot focusses that plugin
* Tuned: When recording a rack volume slider, a proper target name is used now (not when loading pre beta C sessions, the just toggle rack name to update)

* Tuned: MuSynth & MUX editors: when editing the parameter map, parameters without a custom name automatically get a default name
* Tuned: MuSynth & MUX editors: finetuned layout when the editor is wide
* Tuned: Browsing for MuSynth patches doesn't generate audio gaps anymore, so all music smoothly continues
* Tuned: Improved memorization of browse folders
* Tuned: Also keys up and down do preview a sound in the patch browsers
* Tuned: Slightly faster loading of MuSynth patches

* Tuned: VST Program Chooser: list size was not set perfectly
* Tuned: OSX: On first run, audio setup defaults to a device *with audio outputs* (before, sometimes built-in input was choosen as default)
* Tuned: Windows: Faster doubleclick sensing: as soon as you move the mouse a bit after the first click, doubleclick waiter aborts
* Tuned: Windows: The VST plugin browser will only show .dll files

* Fixed: Possible crash bug on new session, revert session or quit
* Fixed: Possible crash bug when clicking rack plug slots
* Fixed: WFT OScillator: Create Via Harmonics: Result was not yet normalized
* Fixed: When loading a MuSynth or MUX patch from within its editor, a single plug box appeared in the top-left corner.
* Fixed: Automating a rack slider while the rack had a send in it could result in the fact that the destinatin rack slider also moved
* Fixed: On renaming/deleting a plug, the Part Property Panel now neatly updates its display
* Fixed: When choosing a Target for a part, ghosty rack entries could appear in the list
* Fixed: Splash screen could be in the way of open session browser
* Fixed: When working with modal windows, in some cases you could activate an inactive window, which could hide the modal window
* Fixed: OSX: On first run -> audio setup: when not effectively choosing an audio device, then no device was selected, even if one was displayed in the device listbox
* Fixed: Windows: Asio Control Panel didn't open
* Fixed: Windows: When recording while a vst editor was open, then on stop recording, the "new name" dialog could be hidden by the vst editor, then it mu.lab seemed to be blocked

* And some other improvements

* Slightly extended the docs

Post

Hi Jo

Just downloaded Beta C and I'm still getting the crash when I re-enter the Audio Setup. Also, as with Beta B, when MU-LAB gets closed by windows after the crash, it is still listed in the processes list and can only be gotten rid of by rebooting the computer.
This seems to have started with MULAB beta B. I can go into and out of the audio setup in beta A with no problems.

On the plus side, Beta C now brings up the Creative ASIO control panel :)
Cheers...

Daz :0)

Post

Hey Fuzzbeard,

Indeed, nothing has changed in this version regarding the audio setup.

Have concentrated on killing general bugs, i.e. bugs which affected everyone.
Also focussed on boosting the overal user friendliness and workflow.

I'm confident this beta will be much more stable and so then i can concentrate on more system specific issues, like the issue you are experiencing.

Strange that it works ok in beta a, but in fact that's definitely an interesting piece of the puzzle.

I'll focus on this asap.

Post

MuSynth patch "BoogieMoogie":

http://www.mutools.com/mulab/beta/BoogieMoogie.mp3

No effects, only a bit of synth power.

The MuSynth patch itself is here: http://www.mutools.com/mulab/beta/BoogieMoogie.MuSynth

Cheers!

Post

Jo, I still get the issue with the Rapture Demo, too -- once it's decided it's not happy, it ignores all the other plug-ins from that point onwards in the scan. (And the "memory cannot be read" popup shows.)

Post

Hm! Seems flawless, except for the persistent Crossfade Looper bug.

I've given up on the hanging notes, I have a sneaking suspicion that it is my keyboard (USB, 2002 build.) . It seems to be a chord (ie data load ) problem.
However: I'll try and get my hands on a MIDI cable to test it with 'proper' MIDI.


Oh gosh - haven't tried the sample brwosing yet (20 secs for the directory to appear)
Will do on the morrow.

I can't wait for a simple sample 'oscillator' to appear :hyper:


Marco :D

Post

On the PC side, I've been having trouble loading some tunes created in Beta b2 into Beta 3. There's a message: "MU.LAB Free cannot load so many tracks".

Has this changed between versions? This tune has 7 tracks (2 of them muted) and 6 racks.

[Edit: The Mac side is fine. Are files between platforms compatible, apart from usual VST stuff?]
Last edited by toxicoh on Sat Oct 13, 2007 6:28 am, edited 2 times in total.
iMac (21.5-inch, Late 2009), 3.06 GHz Intel Core 2 Duo, 8 GB RAM, OSX 10.12.6

Post

Hey Jo, Not sure if your aware... I am having massive vst plug in issues. Crash on creation of Elastik, no gui on rapture, no sound of virsyn synths Tera + miniTera, no predator, crash on Rm4, I havnt checked my fx yet, I will post again when I do. I also have tons of sonic birth stuff to check 4 you, will post again when I do. will do some more testing tomorow... :)
I used to think the internet was going to unite mankind. Now I realize the internet is perhaps mankinds greatest wasteland of bickering, greed, and narrow minds. " And we all shine on, " Imagine that.

Post

toxicoh wrote:On the PC side, I've been having trouble loading some tunes created in Beta b2 into Beta 3. There's a message: "MU.LAB Free cannot load so many tracks".

Has this changed between versions? This tune has 7 tracks (2 of them muted) and 6 racks.

[Edit: The Mac side is fine. Are files between platforms compatible, apart from usual VST stuff?]
OK, I saw the new version has 8 tracks. It's great the restriction has been lifted on VST numbers! Does that include multi-timbral plugs? (I'm thinking DS404, even though that is now quite "old".)

Then I saw the "Delete Unused Tracks" option. That fixed my files. Everything now works as expected.

This is looking really good now. Next I have to learn more about automation of effects.
iMac (21.5-inch, Late 2009), 3.06 GHz Intel Core 2 Duo, 8 GB RAM, OSX 10.12.6

Post

Jo, I hate to tell you, but we are having serious crash and burn vst plug in issues over here... cam space, nomad fac, pluggo, mike norris... all these things just aint working, and causing crashes..
I used to think the internet was going to unite mankind. Now I realize the internet is perhaps mankinds greatest wasteland of bickering, greed, and narrow minds. " And we all shine on, " Imagine that.

Post

johnny2johnny wrote:Jo, I hate to tell you, but we are having serious crash and burn vst plug in issues over here... cam space, nomad fac, pluggo, mike norris... all these things just aint working, and causing crashes..
Hi are you on PC or MAC?

I am having problems with Firebird+ V1.8
After i have tweaked some knobs on it it freezes and crash afterwards.
In Beta A and B2 it worked Fine.

My system is:
Windows XP Homeedition with Sp2 and all the latest updates.

Post

intel mbp 2.2 c2d, 2gigs ram, and 7200 disk...
I used to think the internet was going to unite mankind. Now I realize the internet is perhaps mankinds greatest wasteland of bickering, greed, and narrow minds. " And we all shine on, " Imagine that.

Post

Fuzzbeard wrote:Hi Jo

Just downloaded Beta C and I'm still getting the crash when I re-enter the Audio Setup.
I've sent email to you about this.
Also, as with Beta B, when MU-LAB gets closed by windows after the crash, it is still listed in the processes list and can only be gotten rid of by rebooting the computer.
This is a consequence of the crash.

It's outside mulab's control.

I think it's an asio driver issue, i.e. if the driver crashes, it leaves soms system locks.

Post

pljones wrote:Jo, I still get the issue with the Rapture Demo, too -- once it's decided it's not happy, it ignores all the other plug-ins from that point onwards in the scan. (And the "memory cannot be read" popup shows.)
pljones, i've just emailed you about this, requesting special log info.

Post

Bonteburg wrote:Hm! Seems flawless, except for the persistent Crossfade Looper bug.
Which version of Crossfade Looper is that?
I've given up on the hanging notes, I have a sneaking suspicion that it is my keyboard (USB, 2002 build.) . It seems to be a chord (ie data load ) problem.
I'm afraid it indeed is a keyboard/driver/slow system issue.

If you could try another keyboard on this system,
or try the same keyboard on another system,
all with mulab,
please let me know how it goes in all these different situations.
by varying one thing at a time, maybe we can puzzle out what the problem is.
However: I'll try and get my hands on a MIDI cable to test it with 'proper' MIDI.
Normally USB is much faster than MIDI!

But anyway, it's definitely a good idea to try it.

Please let me know how it goes.
Oh gosh - haven't tried the sample brwosing yet (20 secs for the directory to appear)
Will do on the morrow.
OK, curious wether it's faster now.
I can't wait for a simple sample 'oscillator' to appear :hyper:
:)

Post Reply

Return to “MuTools”