MuTools

imstre · Post by **imstre** » Sat Apr 15, 2017 4:11 pm

I use UR22mkII (Steinberg)
no problem at this time

MuTools · Post by **MuTools** » Sat Apr 15, 2017 9:32 pm

New M7.3.18 available in http://www.mutools.com/galaxa/mulab

What's new:

In some cases while live resizing windows, they were not immediately fully updated. Fixed.
Improved behavior in case a VST causes a problem during instanciation.
Added explicit crash protection against a unreal case in PolySynth processing that was/is assumed to never happen. (The log file will tell if it ever does happen)
Improved several aspects wrt logging.
And other micro improvements.

How to install:

First make sure you already have installed the complete M7.3 package.

Then:

Windows: Put the new .exe and .id files into the M7.3 installation folder.
MacOS: Put the new .app file into the M7.3 installation folder.

MuTools · Post by **MuTools** » Sat Apr 15, 2017 9:33 pm

@imstre:

1) Pls make sure you're using this newest version.
Then goto MuLab menu -> Help -> Command Line -> "catch audio exceptions"
You should get a confirmation alert saying "catch audio exceptions = ON".

2) Pls make sure you are only using rock solid VST plugins, avoid buggy VST plugins as those can cause crashes too, even in the host, when they corrupt the RAM.

BlackWinny · Post by **BlackWinny** » Sat Apr 15, 2017 11:43 pm

Hello Jo !

A little bug:

Now when I add a new VST synth to the list of VST synths, the width of the message informing of the success is... hem... reduced to only the small size of the button "Ok" that it contains.

MuTools · Post by **MuTools** » Sun Apr 16, 2017 12:13 am

Sorry about that, fixing it...

MuTools · Post by **MuTools** » Sun Apr 16, 2017 12:47 am

It's fixed in M7.3.19: http://www.mutools.com/galaxa/mulab

Thx for reporting this

BlackWinny · Post by **BlackWinny** » Sun Apr 16, 2017 12:52 am

Thank you Jo !

imstre · Post by **imstre** » Sun Apr 16, 2017 6:58 am

mutools wrote:@imstre:

1) Pls make sure you're using this newest version.
Then goto MuLab menu -> Help -> Command Line -> "catch audio exceptions"
You should get a confirmation alert saying "catch audio exceptions = ON".

2) Pls make sure you are only using rock solid VST plugins, avoid buggy VST plugins as those can cause crashes too, even in the host, when they corrupt the RAM.

Thank you for upgrade!

Ok I will do!
I have tried use only instruments Mux - analyzer using no Mux and I compare Mux vst with others to know what makes Mux.

Thank you for a great job!

MuTools · Post by **MuTools** » Sun Apr 16, 2017 9:30 am

Imstre did you set "catch audio exceptions" to ON?

imstre · Post by **imstre** » Sun Apr 16, 2017 10:08 am

mutools wrote:Imstre did you set "catch audio exceptions" to ON?

Yes, turn on; whan perform the function?

MuTools · Post by **MuTools** » Sun Apr 16, 2017 10:18 am

If it's ON then it's ok, then when you get new crashes the log file will be more detailed. I hope to narrow down the cause of the crashes you're encountering. (hopefully it's not about a buggy vst cause then i'm wasting loads of time)

imstre · Post by **imstre** » Sun Apr 16, 2017 10:21 am

Every time I turn on MuLab, this should be done?

MuTools · Post by **MuTools** » Sun Apr 16, 2017 10:55 am

No, once is enough, thx for asking.

BlackWinny · Post by **BlackWinny** » Sun Apr 16, 2017 2:18 pm

I guess that this option is to reset to off when there aren't any bug any more for a quite long time (counted in days), isn't it ?

Because I also guess that this log is cumulative, could you confirm, Jo ?

MuTools · Post by **MuTools** » Sun Apr 16, 2017 3:24 pm

If no errors occurred the log file is automatically deleted upon quit, so no unnecessary cumulation.

MuTools

KVR Audio

MuLab & MUX VST 7.4.6