I know nothing about GameCube , but you're playing it on the PC via the 550, aren't you? (Forgive my ignorance)Originally Posted by hrlslcbr
If so I think the example still holds cos GameCube is processor intensive. Basically lots of stuff works on the engineers dedicated bench, but we home users want to multi-task.
I have an old conexant chip, so if I want the audio in sync on captures, it's ctrl-alt-delete and close all non-critical processes: then the audio stays with the image when I capture. Before starting to capture I close about 15 processes. I googled to figure out which ones.
Try this and if you still notice audio lag/desynch with GameCube, you've narrowed it down to ATi's non-optimized drivers. Unless your card's hardware is dodgy, but without better ATi drivers it's going to be impossible to tell.
Now you can see why on paper this card looked good to me cos when I capture, my machine is unavailable for anything else.
Too bad the 550 is only good on paper so far.
Satnav4, sorry, I wasn't clear:
What I meant was: the tuner does what it does, and for the 550, from what I've read, from a hardware point of view, the tuner can theoretically resolve all broadcast frequencies. But only if ATi drivers are up to it!Originally Posted by Satnav4
Therein lies the delay on ATi's part: to be nice to them, I would assume writing the drivers is not non-trivial. Maybe to get PAL all flavours to work causes NTSC conflicts. Maybe it's a lack of developer resources or some sort of technical impossibility that's come up by surprise. ATi isn't telling. We can only speculate in the dark.
What's for sure is this card should never have hit the market until the dev was off the critical path. Playing catch up when the card is released does nothing for a company's reputation. I've seen key developers crumble under such stress and just walk out.