MuVerb causing major audio distortion!

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

MU:LAB 3.2.14
MacOS 10.7.2
Quad Core i7 870 CPU

This has suddenly started to happen recently and I have no idea why. One or more instances of MuVerb causing the audio to become distorted or slow. When using the iMac's internal speakers, it slows down to a crawl as if the computer is struggling to process the audio - but the CPU is far from strained. When using my external sound card (Lexicon I.ONIX U82S) it maintains its speed, but cracks, pops, clips, distorts, snarls etc.

http://benanderson.homeip.net/video/mulab_verb.mp4 (video - right click > open in new tab to view)
Starts with verb off.

Delay, MuX, 3rd party VST/VSTi all work perfectly. The second I open one instance of MuVerb anywhere in MU:LAB, chaos and frustration ensues.

So, yeah, Help! :cry: :help:
Do you chip-tune?

Post

Memory problem. Not enough RAM I think.

Post

Can you reproduce it in 4.0.107? Or even the current 3.2.x? (It's unlikely to get fixed in an old version 3.2.x.)

Post

sorohanro wrote:Memory problem. Not enough RAM I think.
10GB of RAM. Don't think that would be the problem. :lol:
Do you chip-tune?

Post

pljones wrote:Can you reproduce it in 4.0.107? Or even the current 3.2.x? (It's unlikely to get fixed in an old version 3.2.x.)
Just opened the MU:LAB 3 project in MULAB 4. Same problems. Identical, in fact.
Do you chip-tune?

Post

Is the CPU meter suddenly rising when you activate the MuVerb?

Also: Click on the CPU meter until you see #O = n where n is an increasing number counting the audio processing underflows. Is that number going up all the time when the MuVerb is on?

Also: Based on what i read you have use MuVerb in the past too, without probs, right? So if there suddenly is a problem, then something on, your system must have changed. Any idea what?

Post

mutools wrote:Is the CPU meter suddenly rising when you activate the MuVerb?

Also: Click on the CPU meter until you see #O = n where n is an increasing number counting the audio processing underflows. Is that number going up all the time when the MuVerb is on?

Also: Based on what i read you have use MuVerb in the past too, without probs, right? So if there suddenly is a problem, then something on, your system must have changed. Any idea what?
The same 8-bar LinnDrum loop caused 52 overflows. it keeps steadily rising in the background with nothing playing. With the three instances of MuVerb switched off (2x MuVerb, 1x MuX Gated Verb) the average CPU usage drops from around 5/6% to 2/3%.

MU:LAB 4 is just the same - constant overflows. My old MULAB 2 install, however, works fine.
Do you chip-tune?

Post

bendragon wrote:
mutools wrote:Is the CPU meter suddenly rising when you activate the MuVerb?

Also: Click on the CPU meter until you see #O = n where n is an increasing number counting the audio processing underflows. Is that number going up all the time when the MuVerb is on?

Also: Based on what i read you have use MuVerb in the past too, without probs, right? So if there suddenly is a problem, then something on, your system must have changed. Any idea what?
The same 8-bar LinnDrum loop caused 52 overflows. it keeps steadily rising in the background with nothing playing. With the three instances of MuVerb switched off (2x MuVerb, 1x MuX Gated Verb) the average CPU usage drops from around 5/6% to 2/3%.

MU:LAB 4 is just the same - constant overflows. My old MULAB 2 install, however, works fine.
Okay: I restarted my iMac thinking never shutting it down for weeks at a time (I just out it to sleep) might be a problem. It works now, though I have a strange feeling its going to go wrong again when I wake it in the morning. pljones Mentioned I don;t have the latest version of MU:LAB 3, is there a download to the latest binary?
Do you chip-tune?

Post

Yes restarting everything is a very good idea.

You can find the legacy versions of MuLab, including MuLab 3.2.14, here:

http://www.mutools.com/mulab/legacy-versions/

Post

bendragon: I remember having a similar problem with a plug called autotalent in MULAB. It would behave normally and then start to consume progressively more cpu after(!) processing audio. Can you repeat the problem?


10 GB crikey! Have you started on that individual-bricks-3D-model of Manhattan yet?? :hihi:

Post

mutools wrote:Yes restarting everything is a very good idea.

You can find the legacy versions of MuLab, including MuLab 3.2.14, here:

http://www.mutools.com/mulab/legacy-versions/
That seems to have fixed everything. Including the missing splash screen. I think something must have gone funny with my old install. However there is one more problem with the new install.

Image

Any chance of getting a new key? You should have my name on record somewhere.
Do you chip-tune?

Post

Bonteburg wrote:bendragon: I remember having a similar problem with a plug called autotalent in MULAB. It would behave normally and then start to consume progressively more cpu after(!) processing audio. Can you repeat the problem?


10 GB crikey! Have you started on that individual-bricks-3D-model of Manhattan yet?? :hihi:
Screw brick by brick, this is atom by atom, baby!

But in all seriousness; Adobe software takes up a lot of RAM, especially when I'm scribbling away in Photoshop.
Do you chip-tune?

Post

bendragon wrote:Adobe software
RAM
Tell me about it!

Post

bendragon wrote:Any chance of getting a new key? You should have my name on record somewhere.
Can't find anything based on your kvr name.
Please email me about this with your purchase email account, or include details so i can retrieve your record. Thanks.

Post

Bonteburg wrote:
bendragon wrote:Adobe software
RAM
Tell me about it!
1.32GB of RAM with a 1 layer sketch right now :/
Do you chip-tune?

Post Reply

Return to “MuTools”