No BTD probs? Please list your system!!!

[Joshua Lopatin]

I also, have had no problems bouncing anything. I regularly run 32 track sessions with 15-20 aux tracks, and numerous midi tracks with no problem. I normally run 44.1/24 sessions, but last night i converted some sessions to different sample rates/bit depths, and i had no problems at all. I should add that these sessions use many plugins and have heavy automation.

I've also tried as many plugins combos as possible. even with an almost maxed CPU, i do okay.

I've run into no problems at all.

So, my conclusion is that I must be as lucky as Rail. :P

-josh

[gtrguy4]

*runs to store to buy Joshua's setup*

but really, I'm curious about laptop success also ...is there any? lol

[Roy Howell]

I've run into no problems at all.
So, my conclusion is that I must be as lucky as Rail. :P
-josh

I think you guys may have stumbled onto the solution to this sinister BTD problem.....all it takes is...LUCK!
Now all we have to do is get Rail to create a LUCKbtdHELPER.exe app.
Whew!...glad that's settled.

[citi]

I have been doing a lot of research on this one last night with big sessions and I have narrowed it down to one variable. Waves. I can run as many pt plugs as I want but If I start to use more than like 5 or 6 waves plugs I get BTD errors. It's not a power issue because I have enough. It is more random. I can sometimes run like 10 and btd fine, but the next time error and then I have to remove 2 waves plugs. It's very strange but I believe it is waves. I don't believe it's a hardware issue.

I am running xp2500 barton asus deluxe (you know which one) with radeon ve dual, 3 hd 40, 60, 80 8mb cache wd for audio with NO optimization at all except for visual best performance.

[in10shun]

I've haven't had any BTD probelms since upgrading to 6.1. Also, I did absolutly nothing to my machine like re-installing Windows, changing IRQs, etc. I guess I just got lucky, seeing as there have been so many problems. Here's what I've got:

Digi001
P4 2.53GHz
ASUS P4B533-E mobo, RAID disabled
1024MB PC2700 DDR RAM
Seagate 80GB 7200RPM HD internal
Western Digital 200GB 7200RPM firewire external
Soundblaster Live card
GeForce4 MX 128MB video card
Adaptec FireConnect 4300 firewire controller card

I built this machine in Jan '03 and, like I said, I haven't done any tweaking of Windows or the BIOS. Everything just worked.

In regards to what Citi said, Waves plug-ins really hurt my system's performance. The only error I ever get is the 9093, and that's only when too many Waves plugs are going at once. Depending on which ones they are, it can be as few as 5 or 6, or as many as 20.

Hope this info is helpful.

-James

[Rail Jon Rogut]

CiTi

You may have a point.. I never tried a Waves stress test.. so following your post I did:

I took my original stress session which works perfectly with DigiRack plug-ins and removed all plug-ins, then:

Buffer size 1024 samples
CPU Usage 85%

32 x REQ 6 band
8 x RComp
2 x RVox
1 x REQ 2 band
1 x RBass
1 x L2
3 x RVerb (mono/stereo)
1 x MetaFlanger
1 x MondoMod

adding one more REQ 2 band wouldn't allow playback.

To get a succesful BTD I had to remove:

2 x RVerb (mono/stereo)
1 x MetaFlanger
1 x MondoMod

adding one more REQ 2 band wouldn't allow BTD.

Of course, using this many plug-ins isn't recommended and isn't a real test of what you would use while mixing (or you need to seriously improve your recording skills).. but it does demonstrate that with Waves plug-ins.. they have different CPU usage when bouncing to disk. I have contacted Waves about this issue.

Rail

[tele_player]

hmmm, very interesting. I've seen the BTD error a couple times, and I was doing a moderate number of tracks, with a sensible number of plugins. But one of those plugins was probably Renaissance Reverb, and probably a small number of Ren Comp.

[SKI]

Have any of the people having the BTD problems looked into their disk controllers?
This can have a big effect on your system performance.
Also seems strange that those of us not having the BTD problems are running systems with very little tweaking.
PT 5.3 was very stable for me and 6.1/6.1.1 has been the same.
This is on a:
P4 2.4g
D845PESV
512m ram
WinXP home
Digi001
32 + 12 if I remember correctly

Typical sessions are at least 28 tracks with lots of aux tracks and plugs from DigiRack, BF, and Waves Gold.
Can't do 96k since it's an 001

Is there anyone having BTD problems who isn't using PT's MIDI?
The MIDI is still a little strange and I notice differences between my HUI's performance if I go back and forth between 5.3 and 6.1.1 on the same machine with the same settings.

[fredsparky]

Hi. Is this right?? I'm having no problems.

Resource Device Status
IRQ 22 Microsoft ACPI-Compliant System OK
IRQ 22 3Com EtherLink XL 10/100 PCI For Complete PC Management NIC (3C905C-TX) OK
IRQ 16 NVIDIA RIVA TNT2 Model 64/Model 64 Pro (Microsoft Corporation) OK
IRQ 21 Digidesign Digi 001 OK
IRQ 23 HSP56 Micromodem OK
IRQ 23 Intel(r) 82801BA/BAM USB Universal Host Controller - 2444 OK
IRQ 0 System timer OK
IRQ 8 System CMOS/real time clock OK
IRQ 13 Numeric data processor OK
IRQ 6 Standard floppy disk controller OK
IRQ 4 Communications Port (COM1) OK
IRQ 3 Communications Port (COM2) OK
IRQ 1 Standard 101/102-Key or Microsoft Natural PS/2 Keyboard OK
IRQ 12 PS/2 Compatible Mouse OK
IRQ 14 Primary IDE Channel OK
IRQ 15 Secondary IDE Channel OK
IRQ 19 Intel(r) 82801BA/BAM USB Universal Host Controller - 2442 OK
IRQ 17 Intel(r) 82801BA/BAM AC'97 Audio Controller OK

[nikki-k]

Hi!
Any problems I reported initially were with sessions with Waves plugs, and really pushing the limits of my system (LE). Last post on BTD issues from me was using sessions with only Digi plugs, which may account for my not having problems.

For those having problems with a lower number of tracks, and only moderate number of plugs, there must be something else contributing. Maybe a new thread for those having BTD problems with sessions that are only moderate, or lower? I have never had any problems with "average" sessions of say 2-24 tracks, and plug-ins hitting about 30-75% peak CPU-wise (via System Usage window).