Hello!
I am a registered user of MuLab XT. Recently I upgraded my old MuLab installation with MuLab 4.5.1. Then I loaded a project and it shows a lot of CPU usage while being idle. I press no keys and there is no playback, but the CPU meter is well above halfway to the right. Task Manager shows alternating 28-33% CPU usage by MuLab.exe. I cannot even play anything, because the CPU meter overloads instantly and the sound disappears. I tried the 4.5.2 patch, but it was the same. Then I rolled back to MuLab 4.3.12, but now my projects won't open there! How can I fix that? My PC is Dual-Core AMD system at 2.4GHz.
MuLab 4.5.2 CPU overload issue
- KVRian
- 1451 posts since 4 Oct, 2012 from Utah
The reason why you can't downgrade your session is because you opened it in a new version. The new version updated the session with the new versions features. Those features did not exist in the old version. That's why you can't use your sessions in the older version
May I suggest you try beta? It's fairly stable and has some features that may help your situation. If it doesn't work you can ask Jo(Mutools) to help you.
You can find the latest beta here: http://www.mutools.com/mulab/everest/
Here is a tutorial on how to upgrade to a new version: http://www.mutools.com/info/docs/mulab/ ... ation.html
Please keep in mind that some things may be very different and may cause some (small) issues.
Hope this helps
Dakkra
May I suggest you try beta? It's fairly stable and has some features that may help your situation. If it doesn't work you can ask Jo(Mutools) to help you.
You can find the latest beta here: http://www.mutools.com/mulab/everest/
Here is a tutorial on how to upgrade to a new version: http://www.mutools.com/info/docs/mulab/ ... ation.html
Please keep in mind that some things may be very different and may cause some (small) issues.
Hope this helps
Dakkra
Software portfolio
M.N.I.E - soon to be my musical portfolio
Hey, I'm Eurydice(Izzy for short) - she/her
M.N.I.E - soon to be my musical portfolio
Hey, I'm Eurydice(Izzy for short) - she/her
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
If you only saved your session once with M4.5.x then go to the folder containing the session and save the .Backup file version of your session. Because each time MuLab saves a session it first renames the previous file version to .Backup so that you can recover it in case there would be something wrong with the save. (eg VST plugs)
So first of all try to recover your session. A good backup system is always recommended.
So first of all try to recover your session. A good backup system is always recommended.
-
- KVRer
- Topic Starter
- 17 posts since 30 Jun, 2012
dakkra, mutools
Thank you for the suggestions! I just remembered I may have a backup of that session on an external drive. But in case I find it, how do I determine which version it was saved from, and where can I download older versions of MuLab (between 4.3.12 and 4.5.1)?
Thank you for the suggestions! I just remembered I may have a backup of that session on an external drive. But in case I find it, how do I determine which version it was saved from, and where can I download older versions of MuLab (between 4.3.12 and 4.5.1)?
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Open it in a plain text editor, then at the start you'll see with which version it was saved.Bellmaker wrote:I just remembered I may have a backup of that session on an external drive. But in case I find it, how do I determine which version it was saved from
(Note: Do not change/save the session from the text editor as it will become unreadable for MuLab!)
I checked the change log but i don't see why M4.3/M4.4 would be different on that aspect than M4.5.and where can I download older versions of MuLab (between 4.3.12 and 4.5.1)?
Please do this: Open the session in M4.5 and start removing plugins until you see a serious drop in the cpu. Then the last removed one is the problematic one.
If there is no such single plugin, then i wonder whether your audio setup is the same. Maybe you used a larger audio buffer size in your M4.3 install than in the M4.5 install? The smaller the audio buffer size, the better the responsiveness but the more cpu is consumed.
