Mulab Task Manager?

[TorresBob88]

Does MuLab have a task manager?
Like a Chrome browser does?
I think Firefox may have one too.

I thought I saw somebody mention that it was a hidden function?
Like the screen recorder? But maybe I imagined that.

I'm trying to narrow down what VST or process setting keeps shutting down my MuLab.
But the error logs are not in plain anglish.

I dont know what this means "0x00001094 07:42:00:106 Error SqPl[506]"

The only way I can figure to try and suss this out,
is removing every efx and every instrument one at a time,
try to play it again, and see if it stops crashing.
Which doesn't seem like the most streamlined way to do it.

If I could take a look at an internal Task Manager,
for what isn't playing well with MuLab's resources,
I can just take that out of my library, and look for alternatives.

It seems to me that resource management IS, an issue with MuLab.
Probably because of the modular nature.
So it seems like that would be a useful utility, for the MuLab user,
if there isn't one.

Also this seems to be whats crashing me, in this example:
https://physicalmodeling.net/plugins/qu ... m-autoharp
http://flowstoners.com/wp-content/uploa ... v1.001.zip

Is it badly coded? Just too awesome?
I'm not aware of anything else that does something similar.
It will be a shame to have to throw it out.

[MuTools]

Does MuLab have a task manager?

There is the audio engine monitor: Right-click MuLab's CPU meter.

I dont know what this means "0x00001094 07:42:00:106 Error SqPl[506]"

Which MuLab version are you using?
On which platform: Mac or Windows?

The only way I can figure to try and suss this out,
is removing every efx and every instrument one at a time,
try to play it again, and see if it stops crashing.

Not sure what you mean by "crashing".
Does MuLab suddenly quit? = Crash.
Or does MuLab become totally unresponsive? = Hang.
Or does MuLab become slow with MuLab's CPU meter going into red? = Overload.

[TorresBob88]

The audio cuts off.
Its actually still scrolling the playback and I can still manipulate the GUI.
But I have to shut it down to reactivate the audio engine.

...sometimes.
Or sometimes I can just turn off and then turn back on the MuxRack.

The strange thing is, that it seemed to be killing my MuDrum before anything else.
And sometimes other Instruments would still be playing.
Which made me tear down and rebuild my MuDrum preset a few times.

The MuDrum would stop playing audio,
but the Autoharp, which I THINK is the problem, would still be playing.

It sounds like its the "process weight limit" stalling. Which I have turned off.
But its not entirely freezing, its just turning off some sounds.
And it seems like the MuDrum before anything else.

Maybe because of Polyphony of the drum sounds?
If I'm using 2-3 layers for each pad, and no choke groups.

"Show audio engine stats" does give me some kind of clue to work with. Thanks.
Turning some Vst's on and off jumps the "Project CPU Maximum" to 752%.

You have seen the Chrome Task Manager right?
It will show the Mem and CPU usage of every tab and extension that you've got open or installed.
I dont know if something like that would be possible for MuLab?

If it would be bloated inside of the MuLab Exe, Chrome is kind of bloaty,
maybe it could be a separate downloadable trouble shooting Plugin.
Modular style.

[MuTools]

Which MuLab version are you using?
On which platform: Mac or Windows?

[TorresBob88]

Windows, 9.6.7

I am on a beta,
and its certainly possible that its already fixed.

[MuTools]

Please update to the latest MuLab 10.