MuTools

pgregory · Post by **pgregory** » Sun Oct 02, 2016 6:12 pm

Whenever I run, MuLab 7.0.47 on a MacBook Pro Retina running macOS Sierra, I get the attached small window only and cannot do anything. In fact, it is completely non-responsive to the point I have to launch a command prompt and kill it with ps and kill.

Any ideas?

Screen Shot 2016-10-02 at 19.07.07.png

Calum · Post by **Calum** » Sun Oct 02, 2016 6:28 pm

I had the same problem until I put the Mulab folder in the Applications folder then Mulab launched normally.

Zexila · Post by **Zexila** » Sun Oct 02, 2016 7:07 pm

pgregory wrote:Any ideas?

Don't use cutting edge version of OS for starters, what are you gaining with it really for audio/DAW usage at this point in time?

syntonica · Post by **syntonica** » Sun Oct 02, 2016 7:19 pm

Sierra has some buggies, you really should wait for the .1 version. I ended up restoring Mavericks on my computer so I could get some work done!

The 32-bit version ran for me fine, but there were issues galore with VSTs, especially the ones that were compiled with JUCE. Empty white windows on pretty much everything.

The 64-bit version runs fine, except for the CPU issues that Jo is trying to iron out. The latest incarnation (.15) has been the best for me so far, being slightly more CPU efficient that the 32-bit version.

I'm not even sure what I'm looking at when I look at your screenshot.

Are you running a fresh install of Sierra, or did you perform an upgrade? Unfortunately, the usual things to try are more difficult to do, such as repairing permissions.

pgregory · Post by **pgregory** » Sun Oct 02, 2016 7:39 pm

Zexila wrote:
pgregory wrote:Any ideas?
Don't use cutting edge version of OS for starters, what are you gaining with it really for audio/DAW usage at this point in time?

Thanks, if DAW were the only thing I did with my MacBook, that might be sound advice, unfortunately, it's not. One of the things I do is software development, which requires me to be able to develop on the cutting edge version of the OS, so that when it is launched formally, my applications work.

pgregory · Post by **pgregory** » Sun Oct 02, 2016 7:42 pm

syntonica wrote:Sierra has some buggies, you really should wait for the .1 version. I ended up restoring Mavericks on my computer so I could get some work done!

The 32-bit version ran for me fine, but there were issues galore with VSTs, especially the ones that were compiled with JUCE. Empty white windows on pretty much everything.

The 64-bit version runs fine, except for the CPU issues that Jo is trying to iron out. The latest incarnation (.15) has been the best for me so far, being slightly more CPU efficient that the 32-bit version.

I'm not even sure what I'm looking at when I look at your screenshot. Are you running a fresh install of Sierra, or did you perform an upgrade? Unfortunately, the usual things to try are more difficult to do, such as repairing permissions.

Thanks for the extra information. Sounds like there's a lot of instability here, which is worrying. I'm looking for a solid, stable DAW for the Mac, trying out different options, including Reaper, FL, etc. To be honest, I'm a little concerned about the amount of issues with Mu having scanned the forums, especially for a commercial product. Perhaps I'll wait until it matures a little and come back to have another look, it looks nice on the surface, so I have high hopes for it.

Zexila · Post by **Zexila** » Sun Oct 02, 2016 7:52 pm

pgregory wrote:
Zexila wrote:
pgregory wrote:Any ideas?
Don't use cutting edge version of OS for starters, what are you gaining with it really for audio/DAW usage at this point in time?
Thanks, if DAW were the only thing I did with my MacBook, that might be sound advice, unfortunately, it's not. One of the things I do is software development, which requires me to be able to develop on the cutting edge version of the OS, so that when it is launched formally, my applications work.

You can partition your HD and use two or more versions of OS X too (Windows and Linux also), that plenty of audio guys and developers do, so your audio work doesn't need to suffer because of non audio one and vice versa.

MuTools · Post by **MuTools** » Sun Oct 02, 2016 9:50 pm

pgregory wrote:Thanks for the extra information. Sounds like there's a lot of instability here, which is worrying.

MuLab is a stable DAW. The MuLab for Mac version however needed a serious rewrite (it was still on 32 bit Carbon, now rewriting to 64 bit Cocoa) and that's what i'm working on these days. I'm aware of the issue you're encountering and will work on that. My advice: Be sure to check out the forthcoming MuLab 7.1 release, expected in a couple of weeks, it will be worth having a good play with it. And if you're not afraid of some testing and want to help getting the new MuLab 7.1 for Mac rock solid asap, pls join this topic: http://www.kvraudio.com/forum/viewtopic ... 9&t=470160

pgregory · Post by **pgregory** » Mon Oct 03, 2016 11:42 am

mutools wrote: MuLab is a stable DAW. The MuLab for Mac version however needed a serious rewrite (it was still on 32 bit Carbon, now rewriting to 64 bit Cocoa) and that's what i'm working on these days. I'm aware of the issue you're encountering and will work on that. My advice: Be sure to check out the forthcoming MuLab 7.1 release, expected in a couple of weeks, it will be worth having a good play with it. And if you're not afraid of some testing and want to help getting the new MuLab 7.1 for Mac rock solid asap, pls join this topic: http://www.kvraudio.com/forum/viewtopic ... 9&t=470160

Completely understand, as a software developer, I'm totally sympathetic to the sort of problems you're facing. I am not at all afraid or averse to testing new stuff, that's fine and I'm happy to help if I can do so. I have taken a look at the thread linked, and will monitor it. However, I tried the 7.1.15 version in the linked download folder and it did the same thing. If I could get past this basic problem I'd be happy to test deeper and provide constructive feedback.

MuTools · Post by **MuTools** » Mon Oct 03, 2016 11:55 am

Sorry, forget to tell that you first need to install the complete M7.1 zip package (+-32 MB, also in the galaxa webfolder) and then update the MuLab.app file to the latest M7.1.15
That's how it typically goes here with test versions: Basic test package + regular .app file updates. As you're a dev too, i'm sure you see what i mean.

That said please also note that i'm aware of the startup issue you're encountering. It only occurs on some systems in certain cases. Until recent i could not repeat that issue but coincidentally i could repeat it yesterday so that's good, can research it now and work on a solution. That issue has not yet been fixed in M7.1.15 but i'm working on it at this very moment. I hope to share an update later today that will fix this possible startup issue and the other remaining issues (eg the VST flickering + some UI lag).

Thanks for your interest, hope you'll look thru the details of this update process and will enjoy what MuLab really is.

pgregory · Post by **pgregory** » Mon Oct 03, 2016 12:01 pm

Thanks for the prompt response. I've got the zip package and got all setup to test. As soon as you need someone to test, just throw it my way, happy to kick the tires.

From what I've seen on the site via videos, it's very intriguing. I'm struggling to settle on a perfect DAW, so would dearly like to be able to test MuLab properly to see how it stacks up.

MuTools · Post by **MuTools** » Mon Oct 03, 2016 12:09 pm

Ok, thx, pls check back in a couple of hours. Or send me a PM / email, then i'll reply as soon as the new MuLab for Mac test version is ready.

MuTools

KVR Audio

Cannot get MuLab to work on Mac