EXTREMELY strange exploding sound!!!

[Frank S]

OK here's my setup when experiencing "the problem":
1. 400Mhz Sawtooth G4, OS 8.6, 192 mRAM
2. Atto Express Dual channel ultrawide SCSI card to external Glyph/Cheetah (10,000) 9G HD - same one as qualified for the Protools 24/Mix systems. The Audio drive is partitioned in two.
3. Occurs on 24 bit, 44.1 sessions only, but my 'n' is much lower for 16 bit sessions.
4. Mono track counts usually 8-12, sometimes as low as 4-6
5. Buffer size 128 (usually, sometimes 256)
6. CPU meter never reads above 40-50%, system load meter much much lower
7. Ren Comp on 6-8 tracks
8. Ren EQ on 2-4 tracks
9. Single True Verb on an aux stereo channel, bus from 2-4 tracks.
10. L1 Ultramaximizer on the master fader, usually with dither/noise shaping off during initial mixing (obviously on for bounce to disk).
11. Pretty sure I have had it with space bar to initiate play, and using the numeric keys to transport as well. I can't honestly remember if it happened with the on-screen play transport controls. Definitely happens when in Loop record mode.
Hope this helps...
Frank

[AvidCS]

Thanks for the info folks. We're looking into it. More info as I get it.

Bob

[stone]

I've had this happen to me...G4 450mhz...no waves plug ins BUT DigiDesign 4band EQ...

too much volume will make it clip and go into a state of freeze...ALWAYS getting to an error message...

Huh?

It's like you put to much juice and BAM!!

[DARinGR]

I'm also experiencing the same kind of wierdness, i.e. "exploding, squealing" sounds in the middle of sessions. It seems to happen when my Waves Gold Bundle plug-ins are being used in 24 bit mode and tends to occur after I make several tweaks on the plug-ins then hit the space bar to play.

I have a G4/400 AGP • 192Mb ram • Maxtor 30 gig HD • MacOS 9.02

My system is strictly used for production and is stripped of all unnecessary extensions.

John Fritz
DigitalARTS Recording

[Jeff D.]

I've had this happen also, but only with Waves Ren Comp. On one session I had Ren Comp open when it happened, and I could see the gain reduction meter go almost completely to the top - not towards more gain reduction, but towards gain boost. The gain reduction meter was blue (it's not normally blue when in normal "gain reducing" operation).

Session: 48kHz 24bit 20 tracks
I don't remember how I initiated playback.
I almost always have the transport set to "loop play" mode.

System: G4 400 yikes 192MB ram 27GB Maxtor (unpartitioned, HFS+) for audio.
OS 8.6
Disk cache 768kb
DAE memory = 30MB
PT memory = 66.4MB
Adaptec 2930 and Yamaha 8424 CDR

[obseco]

I'm only working w/ 16 bit sessions. This exploding happens w/ 2 different setups:

Beige G3 300 MHz/ G4 AGP 400Mhz
Mac Os 8.6 / 9.0.4
Internal ATA / Adaptec 2930 or Ultra ATA 66


Always with... (same sessions)
2x digi EQ
2x digi Comp
1x TrueVerb
1x +L1

It's not a USB problem. G3 doesn't have it.

[yoz]

Hmm, I have that problem on G4-350 192MB on 16 bit session buffer 128, with RCL on master or other track...

[Dean Bohana]

I get the "spike" with no Waves' plug-ins, small track counts, moderate volume on a G4/350/256mb setup. Thought it was perhaps a power conditioning problem on my end but this is quite a bit of shared company. Waiting for improved midi and the spike remedy, DB

[DanXx]

I have had the problem with a session loaded with plugs, but all from digidesign (no Waves plugs or other). I ran it on a G4 400 MHz sawtooth using the standard internal ATA-drive.
When I transferred the session to an external drive and tried playing it on a 450 MHz B/W G3, the problem occurred again.

Later I have had the problem in a small session (not so many tracks/plugs). And then another problem occurred as well: clicking on play or stop (with the spacebar).

We have had a thread on this called "Clip problem: please help" (which appears to be dead now), so there's some additional info on this subject.

Greets, Dan.

[lwilliam]

OK, I'm starting to get a pattern here. I had it happen twice last night. (24-bit session)

Both times it happened right after a created a new audio track to convert midi tracks to audio, so I had the midi module plugged into inputs 3 and/or 4 on the new track. I had a ton of plugins (8-12) loaded, including Waves, Digirack, and McDSP. I wasn't getting "out of CPU" messages, tho.

It happened when clicking on the "play" button on the transport, so it doesn't appear to be related to the USB keyboard.

Was this coincidence or is this pointing somewhere?

------------------
LW


[This message has been edited by lwilliam (edited April 15, 2000).]