Plug In Window

[imprint]

I've been trying to test MuLab on a Mac mINI, Corei7 8gb RAM, Yosemite

I am having a pretty consistent issue when I close plug-in windows, the window where the plug was opened remains as white space and can't be closed without exiting the program altogether.

Below is what happened after closing FL Studio Host Mini Modular, previously also happened with Numerology, Diva, etc.

[Zexila]

Take a look here.

http://www.kvraudio.com/forum/viewtopic ... 9&t=444290

[imprint]

Thanks. So this is not news to any of us except new users.

Disappointing there is not some sort of workaround, or key combination to avoid it. I really like the workflow potential of MuLab. The developer seems intrepid, brilliant and resilient, and hope he can figure out a way around it.

[Zexila]

Hope dies last, unfortunately, only real workaround for time being is to stay on 10.9, as I said in the linked thread without repeating everything or getting into same personal preference argument, choose wisely.

[MuTools]

I've spent a lot of time researching that issue and it was indeed disappointing not finding a solution. For details indeed read the topic Zexila mentioned. That topic also includes some workaround iirc. About the reason: Maybe there is some OSX incompatibility somewhere between the Carbon and Cocoa frameworks and/or a JUCE issue. I'm quite sure it's something outside MuLab. Anyway, i'll be researching moving to Cocoa on relative short term, which is something to be done anyway, at least in order to realize MuLab 64 bit for Mac and MUX Modular for Mac. Stay tuned.

[imprint]

Yes, I did read through the thread and staying on 10.9 isn't an option of course if you have already upgraded. I suppose it's possible to perform a system restore back to 10.9 but that's a pretty tall order just to audition software.

That said, I really like it. I want to utilize it. Numerology in particular is a powerful in combination with it, as it has complementary modules that integrate spectacularly well with MuLab. I appreciate the programming challenges - it's got to be frustrating for you to find and solve a problem that's not inherent in MuLab. It took a brilliant mind to conceive MuLab so far from taking issue with the software, just hope you can, and believe you will, find a solution.

In the meantime, I'll experiment. The Rewire limitation of the demo closes down the most logical avenue but at the same time understand why that constraint is in place. You have to build limitations in a demo.

Is there a mailing list for MuLab to stay updated on progress?

[syntonica]

I'm pretty sure Apple mangled Carbon in 10.10 on purpose.

However, it's a very old framework going back to OS 9 days and earlier. I wish they'd wrapped it in Cocoa in the beginning and then they could have redone it on the back-end over the various OSes, the same as how they recoded routines in PPC while the old 68k code was interpreted.

[MuTools]

Is there a mailing list for MuLab to stay updated on progress?

Like MuTools on Facebook: http://www.facebook.com/mutools

Listen to MuTools on Twitter: http://www.twitter.com/mutools_com

[Zexila]

Yes, I did read through the thread and staying on 10.9 isn't an option of course if you have already upgraded. I suppose it's possible to perform a system restore back to 10.9 but that's a pretty tall order just to audition software.

There's possibility 10.9 is in your App Store account (Purchased tab), if you by any chance downloaded it using that account, so you can now re-download it, make bootable usb drive with Disk Utility and smaller additional partition and instal 10.9 on it, so before booting on blank screen you can choose which version to boot holding alt/option and selecting one of two options.

Sure, this might be just little over the top for using an app, but imagine you need to buy new machine which can run nothing less than 3 years old OS you don't like which is bare minimum for application update without a demo that you actually don't even like to start with (actual update). Yeah, Logic X.

[imprint]

Thanks. I have an older mac book pro (core duo) so might be an option...but then again not all my VST are on that system and none of my hardware is connected to it.

Again the developer is to be commended for trying to support multiple evolving platforms (unlike Logic or Numerology both of which are OSX only) so I'll probably rely on that genius rather than backing in to a band aid solution.

[Zexila]

Thanks. I have an older mac book pro (core duo) so might be an option...but then again not all my VST are on that system and none of my hardware is connected to it.

Next best option (after using 10.9 for audio only) is still dual booting Mavericks and than just symbolic linking the important&big stuff for audio and copying old user preference plist's.

10.10 have no improvements over 10.9 for audio and overall lower resource usage, so you aren't gaining much staying on it for audio anyways, maybe Safari is better, but that's trivial here, again, better to dual boot in cases like this, keep one trusty audio system and one for networking where you can use latest OS all the time not worrying about a thing.

It's not like audio developers (Apple doesn't count) are the ones forcing us to update to newest and last all the time, they can barely keep up with it, we have no reason to jump that easily either, but for some strange reason, we do

Just saw new Logic update is out, they killed 10.9 support on this one, go figure.