-
artifacts artifacts, dying video card?
Here’s the scoop,
In the past couple weeks I’ve been having artifacts show up on my screens, in video playback and just in general use of the computer(finder, entourage, etc. all have the issue). The artifact is usually a couple lines of random coloured or black pixels. In video playback they bounce around the video stream often constantly and in regular app windows they will just be lines across the window that usually go away when I resize the window or just do something in the app. When I try to do a screen cap of any windows with the issue it doesn’t show up in the screen cap.
AS You can see by this example(pic on right is from camera phone)
https://img264.imageshack.us/img264/571/artifactcomparejt3.jpgSo I figure I have a bad video card right?
Well not quite, today I rendered out a big clip(hdv timeline nested in sd prores hq timeline, exported to prores hq, then compressed quickly 1 pass for dvd). I noticed that in the rendered video I am seeing similar artifacts at one point in the video. It appears in my prores file and obviously my m4v dvd file as it was encoded from the prores. As far as my knowledge goes, FCP and compressor don’t use the video card at all for rendering, especially for an output file, that should be done by the cpu only. So maybe I don’t have a bad video card, but maybe i do and this rendered artifact is just a seperate issue. I’m not too sure, maybe one of you will have some insight into it.Here is an image of that artifact:
https://img167.imageshack.us/img167/6462/renderedartifactsg2.jpg -
2 Replies
-
by the way I’m on a quad core 2.66 mac pro with 5gb ram 500gb system drive, 2 750gb drives in software raid 0(editing off of this) and 1 320gb storage drive, x1900xt 512mb video card(running dell 24″ and 19″ 720p lcd tv).
Running the latest final cut studio 2 w/ updates, osx 10.4.11, and Quicktime 7.3.1. -
I honestly can’t tell.
But in the olden days, back when SCSI ruled the earth, all such glitches were directly attributable to the SCSI connectors, cables, or, if the easy stuff didn’t fix it, the SCSI card or, end of the trail, a dying drive.What was happening is that a few elements of the file were being corrupted on the read, the transfer, the rendering, or the write to disk. the debugging was binary and linear: eliminate one thing, move on to the next possibility.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
Reply to this Discussion! Login or Sign Up