unexpected level spikes-- OUCH!

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
jersmi
Posts: 22
Joined: Wed Feb 02, 2005 8:44 am
Location: Oakland, CA

unexpected level spikes-- OUCH!

Post by jersmi » Tue Dec 25, 2007 2:18 pm

Problem: out of nowhere I am currently experiencing tracks with levels suddenly spiking to infinity, overloading sound systems, making sound techs very upset in performance venues, etc. And to complete Murphy's Law, this will happen ten minutes before a performance, causing me to disable as much as i can for a "safe" performance.

This problem started showing up several weeks ago in rehearsal, and it has been difficult to trace/resolve. This behavior appears to involve Live's 3-band EQ and/or Reverb. For a while it appeared to happen on only one audio track (#2) using Live's 3-band EQ, but lately it has started jumping around to other tracks. Also, it appears to involve often the Reverb, which is on a Return track with several tracks fed to it. Usually when it happens it is one track and the Reverb return track spiking equally, simultaneously, buried in the red to infinity. These tracks are not using any third-party plugins. For this project I have only used native Live effects and one third-party plugin, Plogue Bidule, but no track using Bidule has ever displayed this behavior.

I hope I am doing something wrong and someone can tell me. And if not, I hope someone understands how to help me fix this-- it has created much anxiety in recent performances. This is music for a contemporary dance performance-- it is supposed to be very quiet, spacious and subtle!

jersmi
Posts: 22
Joined: Wed Feb 02, 2005 8:44 am
Location: Oakland, CA

Post by jersmi » Tue Dec 25, 2007 9:55 pm

P.S. Live 6.0.10, MacBook Pro, OS 10.4.11.

So I found this post describing the same problem with multiple instances of EQ Three:
http://www.ableton.com/forum/viewtopic. ... t=overload

Also, discovered that this problem was addressed for beta 7.

Question: should I assume this will never be fixed for any versions of 6.x.x?

Locked