Posts Tagged ‘P2’

 

Timecode Mismatch – 20. June, 2009

I’ve run into a post-production issue and I need to call upon the hive mind for help.

My film was shot on the HVX200 @ 1080/24pA (23.98) and the audio was recorded into a Sound Devices 702T as Wave Files (WAV). We jam synced both devices and also used a timecode (TC) slate. We then fed the audio out of the 702T and back into the HVX200 via the camera’s XLR inputs.

As the footage was transferred from the P2 cards and ingested into Final Cut Pro (FCP), we ended up with clips that had one video track and four audio tracks (a doubling of our stereo audio feed from the 702T, I believe).

clip-timeline

Now, I was always told that I’d need to take my FCP ingested clips, rip out the four tracks of audio, import the original stereo 702T WAV files, sync audio to picture, lock the new clip and repeat until done. Why do this? So I can use the “better” audio.

For anyone that has ever had to sync hours of footage, you know this sucks big time. But that’s why we jam sync the TC; it’s supposed to make this whole procedure less painful. Plus Sam from the Confidence Bay showed me an awesome way to use QuicKeys to cut tens (if not hundreds) of hours out of this process.

Perfect. I’m ready. I’m excited. I’m dying to sync all this footage so I can hand it over to my new kick ass editor.

Just one problem: the audio and image use two different TC counts.

The WAVs use a 24 (23.98) TC count (check out the TC in the top right window).

audio-fr23-hl

audio-fr24-hl

The HVX200 footage, well, that’s a complicated story. If I recall properly, 1080 24pA DVCproHD footage is recorded to the P2 cards as 29.97. Then, in FCP, you ingest using the advanced pulldown setting and TADA, you have 23.98 clips. Unfortunately, what I found is that the 23.98 footage still uses a 29.97 count. I kid you not. A 23.98 clip counts up to frame 29. The TC doesn’t convert to a 24 count.

image-fr29-hl

image-fr30-hl

And here’s the proof that 1) the clip is 23.98 and 2) that the sequence is set to cut 23.98 footage.

image-item-properties-hl

sequence-settings-2398-hl

Do you see my problem? I have one chunk of media that counts from 0-23 and another that counts from 0-29 and I’m supposed to use their respective TC to sync them together. “00:00:00:27″ in the footage is “00:00:01:03″ in the audio. Without resolving this discrepancy in counting, I can’t see a way to have FCP automatically sync the audio and image via TC.

How do I easily resolve this so I don’t spend the next month syncing my footage? Is there a way to resolve this discrepancy without 1) a massive re-ingesting of all the footage or 2) paying for some expensive hardware transcoding? Should I even bother with this now? Is the the audio routed from the 702T to the HVX200 via XLR that much worse than the original WAV files? Would it be simpler to just clone a drive for my editor now and deal with this problem after I’ve locked the cut? This violates the “5 minutes now saves you 5 hours (or days) later” rule I learned from my buddy Ken but maybe this is one where I just have to suck it up and sync the WAVs to the edited picture (that might take a month as well).

Thoughts? Questions? Solutions?

Importing HVX Footage into Final Cut Pro – 28. January, 2009

As I’ve had a few requests, I’ve decided to post instructions for importing footage shot w/ the Panasonic HVX200 into Final Cut Pro.  I created this document for my DIT.

For reference:

Lastly, you should know that I culled this from Creative Cow and Shane Ross, an editor I once worked with.

Best of luck.

P2 Field Report – 1. September, 2007

First, a warning to save often. I had written a massive post on this subject but wasn’t saving regularly. When I finally did, my wi-fi was down and I got the “try again” message. I hit “reload” and everything was gone. :(

Frustrated and angry, I’ve decided to blog using short bullet points.

Recently I was hired to AC (1st & 2nd) a shoot using the HVX200 and P2 cards. Here’s what I learned:

  • Panasonic recently released a 16 GB P2 card. That gets you 16 minutes at 1080i (this project’s format).
  • You need a driver for your Mac and Final Cut Pro to see the new 16 GB P2 card. Otherwise they won’t show up.
  • The P2 records MXF (Material Exchange Format) files but ingesting the data into FCP will place them in a Quicktime wrapper. Note: you must bring in all the metadata, not just the “video” or “audio” content in the MXF, for FCP to see your footage.
  • “Incomplete” clips aren’t really incomplete. They’re clips that span over two P2 cards. Ingest the data from both cards at the same time and FCP will make them into a contiguous/”spanned” clip.
  • You may find “spanned” clip on a single P2 card. Don’t worry. Because the cards are formatted FAT32, no single file can be over 4 GB. Therefore, continuous shots over 4 minutes long in 1080i are stored as two files. When you ingest this footage into FCP, the clip will appear as one contiguous shot.
  • We were shooting 1080-24pA (that’s 1080 vertical lines of hi-definition resolution at 24 frames per second shooting progressive with an advanced pull-down of 3:2:2:3) but we’re actually recording 1080-60i (60 interlaced fields per second), as if we were laying down to tape. The HVX200 can record 24p-N (24 frames per second shooting progressive in the native frame rate – no duplicated frames and no pull-down required) but only when shooting 720p.
  • The filmmakers rented a P2 Store and it stayed in the box the whole weekend. Why? First, we had a G4 Powerbook (with PCMCIA slot for the P2 cards) and two 320 GB G-Raid drives to store and back up the data. Second, because of a hardware glitch, although the P2 Store is USB 2.0 capable with Macs it can only transfer at USB 1.1 rates. That means a 3:1 ratio and 48 minutes to copy 16 minutes of footage is just plain stupid.
  • The filmmakers should have rented a Firestore FS-100. It’s a 100 GB portable hard drive that connects directly to the camera via firewire. I’ve only heard two complaints about this device. First, when it heats up the fan can be obnoxiously loud. Second, all reports indicate that you can’t record in the “native” format (although the manufacturer says they’ve repaired this with a firmware update). Still, this point would have been moot on our set as we were shooting 1080i and the “native” frame rate is only an option when recording 720p.
  • Although some people suggested we use HD Log or P2 Genie to transfer the data from P2 card to our hard drives, I transfered material using the old fashioned method of “drag and drop”. It worked fine.

In the end, I found this workflow to be incredibly addicting. There’s nothing more satisfying than watching dailies 30 minutes after they were shot. What’s more, someone could have edited the first day’s footage by the middle of the second day. Amazing. After this experience, I’m 93% positive I want to use this camera to shoot my thesis; that remaining 7% of uncertainty is in regards to the camera having a 1/3″ chip instead of a 2/3″ and my desire to use prime lenses.