-
Multicolored Rogue Pixels
This has me stumped. When an AVI file is in the timeline and running, there is an occasional frame that shows rogue-colored-pixels. Probably 5-10 a minute. When rendered, and put on a DVD thru Architect, the rogue pixels show up on the DVD. My computer has the AMD Phenom Quad. The originating files are AVI.
Input:
720x480x24 29.970fps interlaced DV
Project:
720x480x32 29.970i
Preview:
360x240x32 29.97pThe editing software is Vegas Pro 10.
What in the world is going on here and what do I need to do to correct it?
Thanks in advance for your help.
-
8 Replies
-
Do you see these when you play the files back using Windows media Player?
It looks like it might be dirty camera heads or a worn tape.
Did you use a new tape in the camera?
When was the last time you cleaned the camera heads?
How old is the camera? (I wonder if the CCD sensor is going bad?)
~jr
http://www.johnrofrano.com
http://www.vasst.com -
If it is a tape capture, you might be able to recapture and hopefully see the artifacts in different spots and possibly splice the good spots back in.
If your AVI file is coming directly off a HDD camera or memory stick, it would mean that the artifacts are hard coded in the file, and there is little you can do. If it only happened in that recording environment, and has not occurred since, it would suggest to me that the camera may have been exposed to some form of unshielded or improperly shielded electrical equipment that was operating at the time, possibly a power tool or something with an electric motor in it.
There might be some 3rd party plug-ins that could be used to minimise the effects, much like the VHS noise remover plug-ins of old some NLE’s used to have.
Perhaps John Rofrano may know of a Vegas equivalent.
Intel i7 920, 12GB RAM, ASUS P6T, Vegas Pro 10 (x32/x64), Windows 7 x64 Ultimate, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
Those are data drops – not to be confused with Dropped Frames. You don’t say what camera or how you are getting the data, but you do need to go “upstream” to determine where the problem is being introduced.
If it is a tape in a DV camera, then…
Does it show up when playing in the viewfinder? If yes, then it was recorded that way – your data is toast.
If it’s clean in the viewfinder, then your data is good as recorded.So if you’ve determined that the data on the tape is good, then try recapturing. If the problem persists, then as another poster said, if the errors are in different places, you can mask/blend them into a good track.
A bad Firewire cable can introduce this kind of noise.
Dirty heads can also cause this, but if that were the case you would see it on the camera’s viewfinder.
Hope this helps.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I recognize those devils from my old Ulead Media Studio Pro days. They would randomly appear from a render. I, thankfully, have never seen them produced in Vegas.
If you are unable to re-capture or re-render the source AVI, you can “patch” non-movement bad spots by snapshoting the good frame before (or after)the bad one. Layer it underneath a snapshot of the bad frame in photoshop, then erase the bad areas. Merge the layers together, then overlay the repaired frame over the bad frame in Vegas.
Tedious, but doable for non-movement areas.
Re-creation of the source video and blending is a far better option, as (at least with Ulead)the bad spots would appear on different random frames—so you could splice the bad frames out, relatively quickly.
-
Sorry about not getting back to the forum in a timely manner. A VHS tape was passed thru a Canopus ADVC 300 then into Vegas Pro 10; Thus, no DV tape was involved. John, the digitalized video (AVI file) showed rogue pixels in Windows Media Player. Upon realizing that, it was played in another computer with Windows Media Player……………..with no rogue pixels!!
So the problem is not with Vegas nor any hardware or cables going to the computer it is withing the PC itself. Knowing my limitations, the PC is now in the hands of 3 trusted computer people. When they come up with what is causing the problem and also the solution, I will post it on this forum just in case some other soul happens upon the same problem as me.
I want to thank all of you who have not only responded to my question but for helping many other people, too. Your help and suggestions are truly appreciated beyond what you can imagine.
Today is Friday, and I am going under the surgical knife this afternoon. I won’t be able to give a response until probably the middle of next week. -
Well, there is finally an answer to the “Rogue Pixels”. The cause was a bad eSATA card. Mr Stephen Mann was extremely close to the answer when he stated it may be a bad firewire cable. My apologies for not getting back to the forum sooner, but the guys in the shop just discovered the answer to the problem. Again, many thanks for being here in this forum and helping all the people. It’s greatly appreciated.
-
Michael, thanks very much for posting the solution.
I saw your original post and was stumped so it’s good to know the solution. -
[Michael Lester] ” The cause was a bad eSATA card.”
Wow, I would have never guessed that one. Thanks for letting us know.
~jr
http://www.johnrofrano.com
http://www.vasst.com
Reply to this Discussion! Login or Sign Up