Ive got Duel 2Gz G5 machine with the Delta 66 sound card. Im having problems playing back audio. It seems to play fine for a few seconds, then be it in logic or itunes, it stops and starts a few times, returns to normal, then does it all over again. Its almost like its a hard drive problem, but im not sure. Any sugestions?

I suppose It does this with only a few tracks so no obvious reasons?

- is the drive overfull (and tracks in multiple parts everywhere all over the place) ?
- On which drive are they?
- are the buffers correctly set up? (to increase even to dramatic size doesn't help)
- does the mac do something else beside this at the same time?


check this:
- no audio file on the system drive
- no filevault on them
- no journaling of the audio drive (but of the system drive sure YES!!!)

right the drive has barly anything on it, as the g5's only a few months old, buffers are all correct. im not sure what you mean by; no audio file on the system drive and no journaling of the audio drive.

im sure the whole hard drive is running a bit slow

shall i try turning the filevault off completely?


oh and it comes up with the error code (-10010) when it bottoms out in Logic 7

This post has been edited by Injured Rezz: Mon 14 Mar 2005, 13:14

Journaling should be disabled on your audio drive (at least for Logic use) and your audiofiles shouldn't be protected by FileVault.

Do you encounter problems when you play audio on your integrated soundcard as well or only when using Delta? If so, check out the settings for Delta (Wordclock source, buffer size, etc.)

This post has been edited by coldharbour: Mon 14 Mar 2005, 13:46

I can't tell for the error code, it seems not to be an OS X code so it must be a Logic one.

Note that Filevault eats some CPU you could use elsewhere. and if something in your user account is constantly needed, it'll be at work all the time. I don't see the reason why using Filevault if you're not working for the NSA Now, it may not be the moron…

i didnt have the dam filevault on anyway, stupid me

thanks for the surgestions guys. ive managed to solve the problem by going into the promt and running the sbin/fsck -f command. this seems to have cleared the problem up