Let's solve this glitch once and for all

I just came back from a vacation in Japan and shot the vacation footage with the HVX at 1080p30. I transferred the P2 cards to a P2 Store slung over my shoulder as we were walking around.

At the end of the day, the footage was copied onto a mirrored RAID with a MacBook Pro from the P2 Store.

No glitches. No lost footage. And the P2 Store worked flawlessly despite doing the transfer while moving around like a bunch of tourists... well, we WERE a bunch of tourists!
 
Hey Dean,
Post some shots, I'd like to see what ya been up to.

For my film we've shot over 500 gigs so far of 720 24pn. No problems tranferring any footage through my G4 laptop. Still going & going....
 
esperman said:
Hey Dean,
Post some shots, I'd like to see what ya been up to.
Can do. I gotta get through a few other things first.

This is the first time I've seen cherry blossoms (sakura). No wonder they go nuts over this stuff.

Psts... yes, the P2 Store does pause when it gets jostled, especially in the vertical axis. I was half expecting glitches and other difficulties but it all ended up quite clean.
 
Barry...Guys,

I'm doing a shoot in Australia for the next couple of weeks. I'm editing on Avid Xpress Pro 5.7 , on a PC laptop, from SD footage shot on the HVX 200. Another editor is cutting on FCP 5 from another HVX 200. So two different setups, two different cameras.

We BOTH are getting the glitch. I have a few HD shots I have noticed it on, none of the SD footage. The FCP editor has noticed it on SD footage only.

This suggests that it is not only an Apple phenomenon.

Is there a workaround or a fix yet?

Regards,

Cre8tive
 
cre8tive said:
Barry...Guys,

I'm doing a shoot in Australia for the next couple of weeks. I'm editing on Avid Xpress Pro 5.7 , on a PC laptop, from SD footage shot on the HVX 200. Another editor is cutting on FCP 5 from another HVX 200. So two different setups, two different cameras.

We BOTH are getting the glitch. I have a few HD shots I have noticed it on, none of the SD footage. The FCP editor has noticed it on SD footage only.

This suggests that it is not only an Apple phenomenon.

Is there a workaround or a fix yet?

Regards,

Cre8tive


What was your workflow on the PC platform ? How much does it GLITCH ?
 
The workaround is to always, religiously, zealously, always always always write-protect your cards before they ever get seen by a Mac.

There is some indication, as yet untested, that once the Mac writes its invisible files to the card then it may actually glitch on both platforms. If your cards never see a Mac, you'll never have the problem. If your cards are always write-protected, you may never have the problem. If you put your cards in a Mac without write-protecting them, you're opening yourself up to causing the problem.

At least, that's the working theory.
 
My cards, my camera and my edit system have never even seen a Mac. All PC all the time. Avid Xpress Pro 5.7

Please tell me how to post an attachment and I will uplooad an image of the glitch I get.

**Note: This has happened on a shot or two over the course of hundreds of card recordings. Not an everyday occurence. It IS worrisome, however, since we are not E/E where you see what has been recorded. So you think you've got it only to find that you have an unusable shot!**
 
cre8tive, are both FCP and Avid exhibiting the exact same symptoms at the exact same time with the same material?
 
Wouldn't know. I've always been PC only. Tell me how to post an attachment and I'll show you what my glitch looks like. (The posting rules at the bottom of my page says "You may not post attachments."
 
I'm wondering if this also might be related. On one mac I running 10.4.8 and one 10.4.9
On the 10.4.9 when i try to copy the P2 card (straight from the HVX mounted thru firewire to a hard drive by drag and drop I get the following error window.

"The finder cannot complete the operation because some data in 00010M00.MXF could not be read or written (Error code -36)"

When I try to burn the mounted P2 (from the HVX as above) to a DVD with toast I get the following two messages:

"The file 00010M000.MXF could not be accessed. (Data fork. -36)"
and
"Couldn't complete the last command because there was an i/o error (your disc may be copy protected) Result code= -36"

The funny thing is, on 10.4.8 there is none of these issues whatsoever (with the same camera and P2 card
 
The drive you are writing to may have some bad sectors. You might want to scan the drive and also make a backup of it if you haven't already done so.
 
The dropouts that I had on my P2 cards ended up being the card its self. The dropouts would happen a quater of the way through the card. The Panasonic service center that I took both the cards and the camera to gave everything a clean bill of health the first and the second time I got the cards and camera back.

I've never had any problems importing files from my HVX or my P2 store into FCP. All the problems I've had took place inside the camera before it had come in contact with any computer.
 
I wonder if this new Mac P2 card driver (kext) will have any fixes for these issues:
New P2 Mac Drivers
This is version 1.3, the old one was v1.0.1.

edit: actually 1.0.1 was a very old (2005) PowerPC only driver, what was the latest Universal kext before that?
 
Last edited:
cre8tive said:
Wouldn't know. I've always been PC only. Tell me how to post an attachment and I'll show you what my glitch looks like. (The posting rules at the bottom of my page says "You may not post attachments."
Bump. I'd like to know how to post a still of my "glitch" on PC to get feedback from you guys to see if this is like your glitch.

Regards,
Cre8tive
 
Click 'Go Advanced' at the bottom of the page and use the 'Member Upload Centre' button (red eject type button) to upload your picture and copy the link into your post.
 
Thanks, Mark.

For those interested, here is the "glitch" I got on a recording to my P2 card at 1080/60 and edited on Avid Xpress Pro 5.7 on an HP xw8000 workstation. Card, camera and project never touched a Mac.

1177360080.jpg


Is this the same "glitch" you guys are seeing? I experienced it throughout the take, and never again on this project. It has popped up a couple more times, however. Don't know if it was the same card or not (I have one 4GB and one 8GB).

Regards,

Cre8tive
 
Back
Top