skippy
New member
This is a very vexing problem. I've searched this site, the various Cubase and PC_DAW sites, and the sites for all my hardware vendors, and haven't been able to solve it. I've followed every PC setup/optimization suggestion I've seen, and I still haven't been able to solve it. Most recently, I sacrificed a live potted plant to the Gawds, and yet still no joy.
Symptom: when recording, Cubase will drop out of record at random times. This happens about 10% of the time while tracking. It occurs at a different point each time, and is completely nonreproducible. It also occurs regardless of how many tracks I'm recording: it is equally likely to occur whether I'm recording one track as an overdub, or flying 16 tracks in at once via ADAT litepipe. CPU load (according to the perfomance meter) has nothing to do with it either: I can be running 1 track and only monitoring the click, or I can be playing around with lots of tracks and plugins, and have the meter up in the 70% range: no difference. 10% of the time, the thing just stops recording mid-take, freezes the screen while it updates the waveform display, and continues playing back as if nothing has happened, leaving me pissed as hell.
And yes, I'm sure that I've got the right marker out past the end of the song... (;-)
System: P3 800MHz, 512Mb, ASUS CUSL2-C, 20Mb SCSI system disk, 60MB SCSI audio disk (both 7200RPM), Initio In1-9XXX UW SCSI adapter, Yamaha CRW8824S SCSI CD-R, W98SE stripped down as far as humanly possible. Running Cubase VST32 5.0 R3 PB2. Sound card is an RME Hammerfall, clocked in slave mode via word clock from my Fostex D1624. The system also has an Audiophile 2496 installed, but I use it only for its MIDI interface at this time, receiving MTC from the Fostex. Also have Midiman Midisport 2x2 installed for instrument MIDI, with the latest drivers from Midiman for both. Networking is via a 3com Etherlink 100baseT Ethernet interface, connected to my network via a switch (not a hub), so there is essentially no inbound traffic congestion. Graphics are Matrox Millenium G450, and there's nothing else on the system: Cubase, Wavelab, and Sound Diver are the only apps. It's totally dedicated to the DAW task, and to allowing my sound data to be backed up over the network.
I've stripped, tuned, tweeked, optimized the buffer sizes, and finally run out of patience. Followed all of the setup advice from Slackmaster2k and others here that the search function could come up with, all the advice on the Cubase support sites, all the tuning tips from the RME site. Audio sync is solid as a rock: word clock is properly terminated, and the Hammerfall is the only load on it.
And yet I still can't get through a session without it randomly dropping out of record at least once or twice. I've seen lots of references to this problem on the Usenet archives and other sites- but none of the fixes suggested there either work, or apply (most of them I'd already done by following the tuning suggestions, for example disabling power management and systray junk, bumping up the buffer sizes, and the other more or less obvious stuff).
Any suggestions would be highly appreciated: It really does annoy me. No, actually, it drives me apeshit wildman bugfuck _nuts_. The good news is that I always track to the 1624 simultaneously, so I don't lose the take- but then I have to fly the data down, and I'd like to avoid that overhead. It oughta just work, dadgummit! Until I can get this to go away, I'll never trust the silly box.
Whaddaya think, computer recording guru persons?
Symptom: when recording, Cubase will drop out of record at random times. This happens about 10% of the time while tracking. It occurs at a different point each time, and is completely nonreproducible. It also occurs regardless of how many tracks I'm recording: it is equally likely to occur whether I'm recording one track as an overdub, or flying 16 tracks in at once via ADAT litepipe. CPU load (according to the perfomance meter) has nothing to do with it either: I can be running 1 track and only monitoring the click, or I can be playing around with lots of tracks and plugins, and have the meter up in the 70% range: no difference. 10% of the time, the thing just stops recording mid-take, freezes the screen while it updates the waveform display, and continues playing back as if nothing has happened, leaving me pissed as hell.
And yes, I'm sure that I've got the right marker out past the end of the song... (;-)
System: P3 800MHz, 512Mb, ASUS CUSL2-C, 20Mb SCSI system disk, 60MB SCSI audio disk (both 7200RPM), Initio In1-9XXX UW SCSI adapter, Yamaha CRW8824S SCSI CD-R, W98SE stripped down as far as humanly possible. Running Cubase VST32 5.0 R3 PB2. Sound card is an RME Hammerfall, clocked in slave mode via word clock from my Fostex D1624. The system also has an Audiophile 2496 installed, but I use it only for its MIDI interface at this time, receiving MTC from the Fostex. Also have Midiman Midisport 2x2 installed for instrument MIDI, with the latest drivers from Midiman for both. Networking is via a 3com Etherlink 100baseT Ethernet interface, connected to my network via a switch (not a hub), so there is essentially no inbound traffic congestion. Graphics are Matrox Millenium G450, and there's nothing else on the system: Cubase, Wavelab, and Sound Diver are the only apps. It's totally dedicated to the DAW task, and to allowing my sound data to be backed up over the network.
I've stripped, tuned, tweeked, optimized the buffer sizes, and finally run out of patience. Followed all of the setup advice from Slackmaster2k and others here that the search function could come up with, all the advice on the Cubase support sites, all the tuning tips from the RME site. Audio sync is solid as a rock: word clock is properly terminated, and the Hammerfall is the only load on it.
And yet I still can't get through a session without it randomly dropping out of record at least once or twice. I've seen lots of references to this problem on the Usenet archives and other sites- but none of the fixes suggested there either work, or apply (most of them I'd already done by following the tuning suggestions, for example disabling power management and systray junk, bumping up the buffer sizes, and the other more or less obvious stuff).
Any suggestions would be highly appreciated: It really does annoy me. No, actually, it drives me apeshit wildman bugfuck _nuts_. The good news is that I always track to the 1624 simultaneously, so I don't lose the take- but then I have to fly the data down, and I'd like to avoid that overhead. It oughta just work, dadgummit! Until I can get this to go away, I'll never trust the silly box.
Whaddaya think, computer recording guru persons?