Let's solve this glitch once and for all

Thats worse than the very first pix posted ! And on a PC!

cre8rive - did you use a Firestore? If not, how did you get the p2 card data from camera to computer? DId you write-protect the p2 cards at any time ? Had those p2 cards EVER touch a mac before hand ?

.
 
dusterdoo said:
Thats worse than the very first pix posted ! And on a PC!

cre8rive - did you use a Firestore? If not, how did you get the p2 card data from camera to computer? DId you write-protect the p2 cards at any time ? Had those p2 cards EVER touch a mac before hand ?

.

Oh, great. :(

No Firestore for this shoot. I have one, but this shoot was P2 all the way.

I've never write-protected the cards, and the cards have necer touched a Mac. My camera has used cards that have been on Macs, and these cards have been in a camera that belongs to an FCP editor, but the cards were formatted by my camera before and during the shoot.

What does the collective thinking out there think this means??

Cre8tive
 
..but did you go Camera->PC workstation via cable ? Firewire ? USB? or PCMCIA card slot ? MWave ? One scene only via transfer ? try to narrow it down to this clip and the transfer process...Can you reproduce it ? Do you still have the bad scene ? It certainly isnt the software..

Sounds like we must ask the gods !

ouija01.jpg
 
Last edited:
It was P2 into an HP laptop via PCMCIA and directly to external FW hardrive. Transferred the entire card, only one scene showed up this way. I still have the bad scene (on hard drive only) and the entire take has hits like this.
 
Did you use P2Genie by chance ?

In reviewing all of these posts it does seem the PCMCIA slot is a common denominator ...

HHmmm.....I think we need Doctor Green for this mystery...
 
Last edited:
I was wondering if anyone has ever had the glitch when they use a PC PCMCIA to download onto an external drive. Then hooked that external drive to a mac and imported the footage into FCP?
 
The only glitches I've ever seen have been render and digitize issues related to what we thought was SATA Raid issues and the G5.

I'm running a MacPro with Kona LHe and a Caldigit raid. Usually digitize to a powerbook through to an external bus powered drive using p2Genie and have never had an issue/glitch/problem.

Tom
 
I just got back from an big budget studio shoot. The second set-up of 6-7 takes of a dolly shot has glitches in them. I made sure to check most of the takes after seeing when played back from the camera. I transfer to a P2 store and then to a Mac. This is a camera problem not a mac problem. I'm losing my confidence in the P2 system that I love so much.
 
Mike Savino said:
I transfer to a P2 store and then to a Mac. This is a camera problem not a mac problem. I'm losing my confidence in the P2 system that I love so much.

How do you reach the conclusion that the issue is a "camera problem?"

The reason I ask is because it seems to be directly experienced only in Mac OS, not on Windows machines.
 
It's only a camera problem if you see the glitch in the footage in-camera. And if that's what you're experiencing, then that means you've got some bad hardware somewhere in the chain -- either a bad card, or a bad HVX.

Or, maybe instead of the "glitch" we're talking about, you're talking about the OIS-jumping issue? In which case you should have the OIS off when you're using a dolly, and that should make the problem go away.
 
I never use OIS and quit frankly I don't think that it does a heck of a lot.

While in the studio I reviewed the clips in-camera and on studio monitors and the glitch appeared. It only happens on a bunch of clips within the card and not the whole card. I don't recall this happening before. I had situations with small hits or weird audio spikes on channel 3 audio but the glitches I experienced are the serious ones as posted by other users here where the glitch goes across the screen and is in multiple locations that flash for 1 or 2 frames. I originally thought that it was a codec decompression problem that was random but it is not. While masking and roto may fix the problem, I will now feel that I have to check every take . Especially when you're in a location that costs big bucks and goes away after the shoot. I do hope that there is a fix in the future for this problem. Tape hits are much easier to fix.

I don't think that this is related but my headphone jack is suddenly intermitten and the switch for audio 1 needs to be in just the right place to use audio input 1 and forget the component jack... The worst design ever.

I wonder if all this is related?

My camera was purchased in December 2006. I 've done 30 or so shoots with it and this is really the first hardward problem I have experience. But I don't want to experience any errors that I didn't cause. Especially when ten of thousands of doolars are on the line. I should probably get some "negative" P2 insurance for all my shoots. Off to the repair center.
 
Last edited:
First question I would ask is did the problem only occur after the footage had been transferred (I think you said into a P2 store right?), and did you have the write-protection tab in place before transferring information?

The entire process in detail is the only way to try to track this down. Perhaps it is the camera, but only meticulously checking peoples work flow will tell us anything.
 
The glitch happened during playback in the camera on the set and then after P2 store transfer on the mac.

I never use the write protection as everything goes to the P2 store.

My workflow:

Shoot
Transfer to P2 store via 8 gig cards
Import to the Mac

This is the first time this has happened. As I stated before I've had audio hits on ch. 3/4 and the occasional audio hit at the beginning of the shot.

I have a compositor who uses a PC download the footage to his PC laptop from the P2 card after I imported to the P2 store and he has the same bad clips.

I have about 7 clips that have the problem. The rest of the footage looks fine.

It makes you crazy because I can't reproduce the glitch. I'll be checking the clips more often now.
 
David S. said:
How do you reach the conclusion that the issue is a "camera problem?"

The reason I ask is because it seems to be directly experienced only in Mac OS, not on Windows machines.

OK, David, you've seen my postings showing the glitch I have experienced and the fact that the cards, camera and edit system were PC only, right?

If you are saying the problem is predominately Mac, then I understand, but "only in Mac OS?"

Cre8tive
 
Niot sure if it's a card problem. I just shot another 4 cards full using two 8 GIG cards and offloaded to P2 store and imported to the Mac....no problems. You'd think that it would be consistant if it was a card problem.... Strrange...

I'm sending my camera in for repair. Where is the best place to send it to?
 
Mike, just to be clear - did you see it on playback in the camera before it ever left the camera and went into any other device?

Also, why can you not use write protection with the P2 store? I'm not familiar wirth it myself.
 
Back
Top