Crazy Pixels

Looks like something went wrong in the transfer. Do you still have the original fil as it was transferred off ot the card. Is it still an MXF file. If so re-import the clip.

Hope that helps,

Jan
 
cgravat said:
My thoughts are maybe a probelm with the camera's CCDs but I don't know?
I'll guarantee you there's nothing wrong with your camera's CCDs.

Possibly something went wrong when dumping from the P2 card?
Yep. This is "the glitch" that very rarely happens. I'll also bet heavily that you're using a Mac, right? And the final question: did you write-protect the cards before you put them in the Mac?

If you still have the footage on your cards, play it in-camera and you'll see that the footage on the cards is perfect. It's only the transfer to the hard disk that has this corruption.

The current advice is to always write-protect your cards before putting them in a Mac, or connecting them in any way to a mac.
 
A Mac was never used in the workflow. The workflow is as follows:

1. P2 footage ingested on laptop PC via cardbus slot.
2. Contents Folder(s) arrived safely on laptop Hard Drive. (Although I did not ingest the Lastclip.txt, maybe this could be the culprit?)
3. Transfered footage on laptop Hard Drive to external Hard drive.
4. Footage stays on external Hard Drive as backup and was dumped onto Desktop PC Hard Drive for use with Avid Workstation.
5. Ingested into Avid XP via the media tool. (MXF's were put into Avid MediaFiles/MXF/1 folder)

Again there was no mac involved in this process at all. It really boggles my mind. I did however re-try the above steps 3-5 and the clips still had the crazy pixels, but at different points in the timecode. Maybe something wrong with the external Hard Drive?

Thanks for your insight.

- Chris Gravat
 
Last edited:
cgravat said:
2. Contents Folder(s) arrived safely on laptop Hard Drive. (Although I did not ingest the Lastclip.txt, maybe this could be the culprit?)
- Chris Gravat
Re do the transfer with the Lastclip.txt, i guess you are supposed to always transfer that as well.
 
Get your P2 card or cards replaced that are doing this. I had the exact same problem with one of my cards. I even had Panasonic check out the card and they couldn't find a problem with it using their software. Most of the time if its a problem with the card it will happen around the same area in the card. Meaning when the card is full to a certain level the drop outs will happen.
 
Just viewed the footage on my laptop (the hard drive that the P2 cards were directly dumped on). The pixel thing isn't happening from what I can tell.

It seems somewhere between here and getting to the editing machine theres a major foul up! This makes no sense to me though because its just the transfer of a file, but sure enough every time I go from this hard drive to the next the problem arises.

I do not own this camera, I was the operator on a commercial last week where we checked the camera out from school, so I am very limited in my tests with workflow. However I have saved up just about enough cash to buy the thing, now this happens. I basically refuse to buy a P2 store because they are so over priced, So this workflow that I have going on now is really my only economic option. I really am at loss for words right now.
 
It's not a P2 card problem, I can almost guarantee that. Especially since you've verified that you can go back to the footage and the glitches aren't happening in the same place.

Your original footage on the laptop is solid, so somewhere along the way you're copying your footage to another drive and it's getting corrupted along the way. And you're right it should not be happening. But it's not the camera, it's not the cards, and it's not in your footage. It's an issue with your computers somewhere. I'd suspect your firewire cables.
 
Barry, thanks for the solid input.

I just recently purchased this 500 GB Western Digital External Hard Drive. It's USB 2.0 and ESATA. I'm pretty sure you're right, it's either the cable or this hard drive itself. I will be returning it to best buy today to get the 320GB with Firewire and USB2.0. We'll see what happens after that. I'll keep you up to date on my findings.

- Chris
 
Back
Top