Athlon64+Acid4+Delta66

[sucram]

at the risk of double posting a problem, i apologize in advance, but i know there's not too much activity in the sonic foundry group...

anyone here having issues running Acid 4 Pro on Win XP with an Athlon64 DAW? I swear I'm about to jump ship with all sonic foundry/sony stuff. they're known for stability, but i've been having problems with a new DAW that really shouldn't have difficulty doing what I'm expecting. and now the problem is replicable.

are there users who have had stability issues (instant closing of the app) with this combination of hardware and software? i'm also using an M Audio Delta 66 (ASIO) and a Midiman Midisport 2x2.

i'd be grateful for any user experience with a similar setup. thanks in advance.

-marcus

p.s: there are more details in the sonic foundry forum if you're so inclined to look.

 

[Rstiltskin]

those who speak don't know? I guess I will prove it...

at the risk of double posting a problem, i apologize in advance, but i know there's not too much activity in the sonic foundry group...

anyone here having issues running Acid 4 Pro on Win XP with an Athlon64 DAW? I swear I'm about to jump ship with all sonic foundry/sony stuff. they're known for stability, but i've been having problems with a new DAW that really shouldn't have difficulty doing what I'm expecting. and now the problem is replicable.

are there users who have had stability issues (instant closing of the app) with this combination of hardware and software? i'm also using an M Audio Delta 66 (ASIO) and a Midiman Midisport 2x2.

i'd be grateful for any user experience with a similar setup. thanks in advance.

-marcus

p.s: there are more details in the sonic foundry forum if you're so inclined to look.

do you know what chipset your motherboard uses?

do you know what brand you mb is?

do you have the VERY LATEST bios flashed in it?

do you have the the VERY LATEST patches and service pack for win xp?

do you have the VERY LATEST drivers and patches for the video, the delta, the usb interface, in short, everything in or attached to your system?

basic problem resolution:
find out and do all the above (if you don't it will let all the support people off the hook with 'oh, you need the lastest driver, goodbye, WAIT>>click)

remove all the interfaces and drivers, (god, i hate to say this, but you might want to start with a clean install of winxp (i am making that assumption about your os))

see if you have the problem then, if not, add everything one at a time, testing for a period of time and reboots before you move on. (does it hurt when you do that? yes. then don't do that!)

try all the above and drink two beers and post me in the morning.......


ps......where is all the posts from all the AMD 64 UBER ALLES!! guys? the problem is probably in the drivers, the chipset, or the bios. there is no way for sony to test all the possible configs on a windows machine. that is why I always say to start with your software application and work backwords into the hardware. www.videoguys.com might have something that would help on their winxp tweeks post.

 

[hueseph]

Wait! Slow down. Before you go and start dismantling your system(and after you've updated your drivers of course), go into Start menu/program files/accessories/system tools/system info/hardware resources folder on the left hand navigator/conflicts and sharing. See if there are any conflicts. If your Video and audio share the same IRQ this is a bad thing. Restart and go into your bios. See if you can set the IRQ for each PCI slot. If you can change the IRQ of your soundcard without affecting the IRQ of your video card, you're in buisness. If not, you may have to move your card to a different slot, which means unstalling and reinstalling drivers. This MAY aleviate the problem. This would be the most basic problem. If this doesn't work, then go ahead and start following Rstiltskin's advice as above.

 

[sucram]

Thanks for the suggestions you two.

Rstiltskin: the MB is an MSI Neo FIS2R (socket 754), using the K8T8000 chipset (hope i got that right since i'm not at my DAW). The bios is the stock, which may be 1.7??? I don't recall, but the board was purchased last May, so there have been revisions that I haven't flashed. Flashing makes me nervous since I'm no computer guru, and I don't want to have to backtrack if i can avoid it. Actually, I'm of the type to not fix what's not broken (though things may be broken now!), so i don't update things until i feel the need to in order to avoid the possibility of inducing conflicts. I'll look into the video card drivers which also were never updated. The Midiman USB port seems to have had drivers revised in 2003 which i guess i'll try, and the Delta version is the .27, which I've read are the most stable, though maybe that's changed. Do you always update your drivers as they come out? Don't you think that's taking a risk?

hueseph: I'm fairly sure that I installed the PCI card for the Delta on its own IRQ, though I'll have to verify this using your method. If I recall, the card is in the second PCI slot beneath the video card.

I'll be away for a few days, but I'll explore these suggestions when i get back. I was actually hoping that it would be something more obvious. The behavior is strange. I discovered that when i start playback from a particular point in the song (bar 32 i think??), it crashes. when i start playback before that point, it plays fine, even past bar 32. Oddly enough, I went back to an earlier version of the project before I noticed any playback problems, and the crashes happened just as in the recent version. It didn't exist in a much earlier version, so I'll have to look at what I added between the good and problematic versions. I use lots of freeware and shareware, so I wonder if it's related to various plug ins.

Thanks again for your thoughts. If there are any other Athlon64/Acid4/Delta66 users out there with thoughts, keep em coming!

-marcus

p.s: Rstiltskin, "those who speak do not know" is a concept of taoism. it's not to be taken literally! please, by all means, speak!

 

[Rstiltskin]

xp has something called device driver rollback......might want to look into it.

also, does acid have a archiving kind of save where it compresses your work? I am just thinking of something to move the file around. you could copy it to another filename and rename the old one xyz.bad temporarily and try to play back the copy, that should eliminate the one in a zillion of having your data covering an unmapped bad spot.

I will look into the via chipset thing and try to have some info for you.

good luck.

oh, the section that causes the crash, can you copy it into a new empty project by itself (i don't know jack shit about acid so this may sound really stupid) and try to play it, with as few plugins as possible, and as little before and after data?

 

[sucram]

problem isolated

well, it looks like the issue involves the Sonic Foundry / Sony resonant filter. i've never had issues with it before, but when i delete the track that has this effect (which is utilizing extensive automation) inserted, everything plays as it should. in fact, when i bypass the effect in the effect chain, everything is fine. so i'm not going to bother updating drivers or flashing bios just yet.

interestingly, when i upgraded to Sony Sound Forge 8 from Sonic Foundry's Sound Forge 5, i noticed that all my multiband compressor thresholds in all my projects were reset to a "detect threshold" setting (a quick way to find where your peaks are in each frequency band i suppose). this was the only bug i've noticed since the transition to v8. it may be of interest to know that i'm still running Sonic Foundry's Acid 4. i didn't upgrade to 5, which was after it became Sony. i wonder if it's a growing pain bug where things aren't exactly compatible across the versions from S.F. and Sony.

anyway, thanks for the replies guys. i appreciate it. i guess i'll have to figure out a workaround somehow. at least i've narrowed it down, and i imagine i could always just render the resonant filter effect to audio through the troublesome spot and hopefully things will work okay after it.

take it easy,
marcus