MuTools

fluffy_little_something · Fri Apr 05, 2013 3:30 pm

In the logs it always says things like:

07:50:24:540 Started the MIDI engine
07:50:24:542 couldn't find gui-rsrc rfmt
07:50:24:543 couldn't find gui-rsrc rfmt
07:50:24:543 couldn't find gui-rsrc rfmt
07:50:24:543 couldn't find gui-rsrc rfmt
07:50:24:544 couldn't find gui-rsrc rfmt
07:50:24:545 couldn't find gui-rsrc rfmt
07:50:24:545 couldn't find gui-rsrc rfmt
07:50:24:554 App[305]
07:50:25:975 couldn't find gui-rsrc xmld
07:50:26:044 couldn't find gui-rsrc rfmt
07:50:26:083 couldn't find gui-rsrc rfmt
07:50:26:084 couldn't find gui-rsrc rfmt
07:50:26:201 couldn't find gui-rsrc rfmt
07:50:26:210 couldn't find gui-rsrc rfmt
07:50:26:211 couldn't find gui-rsrc rfmt
07:50:28:238 BWindow[619]
07:50:42:084 couldn't find gui-rsrc rfmt
07:50:42:084 couldn't find gui-rsrc rfmt
07:50:42:084 couldn't find gui-rsrc rfmt

What does that mean? Doesn't sound positive

Mulab seems to work anyway...

MuTools · Post by **MuTools** » Fri Apr 05, 2013 3:48 pm

Just ignore that. Logging should only be enabled for diagnostic reasons.

fluffy_little_something · Fri Apr 05, 2013 3:55 pm

OK, if you say so

Ignored... ^^

fluffy_little_something · Sun May 26, 2013 9:05 pm

I am not sure, I guess I have asked about this problem before, a long time ago, without a solution. But I can't find that post or thread...

Am I the only one whose Mulab occasionally stops the audio engine from running? Then I have to restart it manually. Usually that works, on rare occasions it doesn't and the sound never returns. In this case I have to close Mulab,which gives me an error message saying:

Internal thread loop time-out error @ AAE[232] => OK

If you wish I can send you a log of today's session, where it happened several times.

I just had a new session, without opening any plugins and it happened again. So it is not some vst's fault...
It never happens with my other daw, so it seems to be something about Mulab...

MuTools · Post by **MuTools** » Mon May 27, 2013 8:33 am

fluffy_little_something wrote:Am I the only one whose Mulab occasionally stops the audio engine from running?

Personally i never get that. Anyone else?

Could it be that you're switching to some other audio apps in between, maybe an MP3 player or maybe playing audio via your browser? It could be that your audio driver is getting confused by it.

In this case I have to close Mulab,which gives me an error message saying:
Internal thread loop time-out error @ AAE[232] => OK

Are you on OSX or Windows? Which MuLab version?

If you wish I can send you a log of today's session, where it happened several times.

Yes email me such log if you got it.

I just had a new session, without opening any plugins and it happened again. So it is not some vst's fault...
It never happens with my other daw, so it seems to be something about Mulab...

I also don't suspect VSTs. I rather think there is some system-level interference with the audio driver.

If that's the case of course it should also happen in other audio apps that are using the same driver (ASIO i assume?) when the same type of system situation occurs.

fluffy_little_something · Mon May 27, 2013 11:58 am

No. For the past couple of months I have used mainly Mixcraft, my behavior in terms of any other applications running simultaneously is always the same, still Mixcraft never showed that problem, even if I had it running half the day. It only happens in Mulab.

I am using W7 64-bit, but the 32-bit version of Mulab (because of legacy plugins). Latest Mulab version, but the problem has been there for a long time, with previous versions also, which was one of the reasons why I have seldom used it recently. It is really a pity as I now have the Rhodes plugin separately, so I am no longer bound to Mixcraft, but I can't really standardize on Mulab as long as that problem is not solved. I won't even upgrade to Mulab 6...

Yes, ASIO.

Log files are on their way

Interestingly at the beginning of one log it says Mulab free instead of UL. Odd...

MuTools · Post by **MuTools** » Mon May 27, 2013 1:19 pm

Thanks for the logs. Ok lets talk further via email.

fluffy_little_something · Fri Sep 27, 2013 11:01 pm

Have you changed something about the audio engine? Seems my old audio driver problem is gone now

I noticed as I was investigating another issue: When I loaded racks or at least previewed them in the browser, they seemed to stay loaded even when I unloaded them, deleting racks from the session entirely. I only noticed by accident as one rack is very heavy on the CPU and the CPU meter did not return to 1 bar after unloading or deleting that rack.

In order not to jump to conclusions about Mulab, I restarted the audio engine from within Mulab and the CPU bar returned to 1 bar (from about 10 before). I tried the same thing with the Asus driver instead of the ASIO4ALL driver and noticed that it seems to be an ASIO4ALL issue because with the ASUS driver the CPU meter returns to 1 bar without restarting the audio engine.

Anyway, that is when I noticed that the old problem with my ASUS driver somehow killing the audio engine seems to be gone

Have to do more testing tomorrow, though, maybe I am simply having a lucky streak

The volume of the sound is also clearly lower when using the ASIO4ALL driver. The native ASUS driver sounds more powerful. Actually, I would have to readjust the volume in all my presets because the volume difference is considerable.

MuTools

KVR Audio

Logging question