Footage Glitch

BVK_FILMS_INC

BVK_FILMS_INC

Member
I have noticed this in some of my footage.

http://www.youtube.com/watch?v=5KgW7wLuh-c&feature=youtu.be

Has anyone else had this issue?

Cutting in adobe premiere pro cs6
canon ef 16-35mm 2.8
Sandisk extreme sdhc class 10 32gb
red rock canon live lens adapter
audio technica 897 shotgun mic
Sennheiser wireless lav

Thanks guys,

I will be contacting Panasonic tomorrow when the call center is open.
 

Attachments

  • af2 copy.jpg
    af2 copy.jpg
    110.1 KB · Views: 0
  • af1 copy.jpg
    af1 copy.jpg
    106.5 KB · Views: 0
I'm going to try and view the raw file...I could also playback the clip in camera. It's really weird. I don't have FCP anymore just cs6
 
I will almost guarantee you that it won't happen when you play the footage back in-camera. We see this type of thing occasionally in all sorts of digital media that's been copied on a Mac. Sometimes it just glitches. That's one major reason why I recommend using data verification whenever you copy footage on a Mac. We don't have consistent data on what or when it happens, but I've seen more reports of it on MBP's than on other macs, and especially when copying to an external drive.

But if you have the footage still on the SDHC card, and you play it back in camera, I would be floored if you found any glitch.
 
You're right. When I played back in camera there was no glitch. What software do you recommend for data verification on mac?

Thanks.
 
Hi Barry,

I use a MBP. If I have the data go from the P2 card reader to TWO drives, would this glitch happen on both of them? I own Shotput but now avoid using it, so I would hope dragging and dropping to 2 (1 800FW, 1 USB) drives would be insurance?

Thanks,
 
It would certainly be more secure than going to just one drive. But frankly, nobody's ever really gotten to the bottom of WHY the glitch happens, so we can't say for certain that a particular course of action will prevent it. When I talked with Apple about it, they said (off the record, obviously) that their FAT32 support wasn't great (and I'm kindly paraphrasing here) so I would suggest copying to MacOS drives if possible. And external firewire seemed more problematical than external USB, but even then, it's all speculation because there's no proven consistent cause of the glitch. We're talking about a couple of bytes being trashed in a copy of maybe fifteen or thirty gigabytes, so it's incredibly rare -- but a byte of compressed data that's inaccurate can cause a glitch in the footage like you're seeing.

The reason a data verified copy is recommended is because, well, it's verified -- presumably that guarantees that it was done flawlessly.

An alternate piece of advice that was given at one point was to not drag & drop at all, but to rather make a "disk image" of the SD card. I'm not a Mac user so I can't verify this, but I seem to recall them saying that there was some manner of data integrity check done when making a disk image? Maybe?
 
You must log in or register to reply here.
Back
Top