FCP 5.1.2 Import issues...Query for you all

Shane Ross

Shane Ross

Veteran
For those of you, like me, who are having issues importing footage from the HVX-200 camera into Final Cut Pro 5.1.2, I have a question.

What is the firmware version of your camera?

And to those who can import successfully, what is the firmware version of your cameras?

Here's how to find out:

In P2/MCR mode
Hit menu
Scroll to Property
Scroll to System info
hit set button, will give you the Firmware version number.

Just trying to narrow this down...
 
HI Shane,

I've been following this problem as described in all the threads here and elsewhere, Happy to help track this down. I've yet to have a problem in more than 160 card transfers and imports. Cards xferred to 2 Lacie Firewire drives via a Powerbook g4 using p2genie (os 10.4.7) Media imported from those drives to internal media drive on a MacPro 3.0ghz intel with an AJA Kona LH, running FCP 5.1.2, OS 10.4.8

Camera firmware reported as 2.02-00-0.00

Let me know if there's other info that'd be helpful
Thanks, tim
 
Thanks Tim.

We have been using five 4GB cards and a P2 store, then P2 Genie to transfer them (using a MacBook Pro) to a LaCie bus powered firewire 800 drive.

I too have a Kona LH, but sport a Dual 2Ghz G5, that is running FCP 5.1.2, OS 10.4.7. And the firmware version of the camera is 3.03-00-0.00.

Hmmmm....maybe the newer firmware is the key...
 
Shane

My firmware version is 2.02-00-0.00 and i definitely have import problems.

Since you have been running the 3.03 firmware have you experienced any FCP import probems?

Ned Soltz
 
The import problem is intermittent and elusive. After upgrading to FCP 5.1.3, footage which would not import in 5.1.2 did indeed import. However, I hear that others continue to have problems even with 5.1.3

Debating now whether to update my HVX firmware or just leave well enough alone.

Ned
 
5.1.3 does in deed fix the P2 import bug in FCP. The upgrade in fact installs a whole new DVCPRO-HD component in the QuickTime library that was never there before! After shooring Mardi Gras parades all day, a couple of full P2 cards, and a full FS-100 worth of P2 data, no problem at all importing into FCP.

The problem has been totally solved with 5.1.3.
 
Sorry Ben...it does not. Maybe for you...which is cool. But not for me and a whole lot of other folks. I have FCP 5.1.3 on my laptop and i STILL cannot import footage using the P2 Import option. Same clips will not import.

So no, it hasn't been "totally solved." But I am glad that things have been fixed for you.
 
Does that footage you have (that won't import) play back properly on the camera? Can you copy it back out to a card and play it?
 
Well, seems that we are back to where we were with the FCP or OS question.

I had noted in a prior post that the 5.1.3 installed a new DVCPRO Hd component and after I installed the update, I could import footage that would not previously import.

I'll be shooting some additional test footage both on the FS100 and P2 cards to see if this holds. But as of the moment, there is something really elusive here.

Ned
 
Very interesting. I have folders of stuff on a drive that would not import, they're all importing fine now. Hmmm....

I know the 5.1.3 upgrade installed a whole new DVCPRO-HD component in QuickTime Pro that was never there before.

Hmmm.... interesting...
 
I can import it just fine with FCP 5.1.1. And it plays back in the camera...and not only that, it plays FINE in the FCP 5.1.3 playback window. Just won't import. ERROR: NO DATA. Which there obviously is.

So..bug. Working on it.

EDIT: Dang it...working for Ned too. WTF?! Darn it you guys...
 
Shane Ross said:
I can import it just fine with FCP 5.1.1. And it plays back in the camera...and not only that, it plays FINE in the FCP 5.1.3 playback window. Just won't import. ERROR: NO DATA. Which there obviously is.

So..bug. Working on it.

EDIT: Dang it...working for Ned too. WTF?! Darn it you guys...
Click to expand...
Are you pointing to a CONTENTS folder on a hard drive, or a P2 card?
In the FCP P2 window, if any P2 is recognized right away, highlight it and hit delete. Then hit that little folder icon and manually connect to it. Just thinking off the top of my head.

It's Lundi Gras today here in N'Awlins, y'all! The darkness is already taking over me. I'll stick around as long as I can, but soon, very soon...
 
Last edited:
I am pointing to the CONTENTS folder...and another try I pointed to the folder containing the CONTENTS folder. Both ways, no go. And nothing appears in the P2 Import window until I point to a folder.
 
Just for curiosity, Shane, are you renaming any of the clips you are importing or just retaining those wonderfully-descriptive 005FEW#Iu or whatever naming convention P2 uses? I found that if the name was too long, FCP would return the no data message.

Ned
 
Nope...straight import. I never change the names, or mark IN OUT...I want to have the ability to relink if a drive fails.

Good idea though...
 
Shane Ross said:
Nope...straight import. I never change the names, or mark IN OUT...I want to have the ability to relink if a drive fails.

Good idea though...
Click to expand...


Shane:

My experience is that the mxf files are not renamed just because you rename them on import

What is named is the conversion to QT.
 
David S. said:
Shane:

My experience is that the mxf files are not renamed just because you rename them on import

What is named is the conversion to QT.
Click to expand...

Correct. And if you begin editing with that clip with the new name...say MAN WALKS ACROSS STREET. Then "oh no, my drive died!" So you go to reimport your P2 footage only...say you have 200 shots (very low estimate)...which you have to remember how you named them...EXACTLY...or FCP will not reconnect.

And if you marked in and out...that only makes it worse. Most likely you won't be able to relink your cut, but have to recut.
 
Shane,

Just a thought, but are there spaces or odd characters in the name of the folders containing the contents folder? a long shot, but I remember someone haveing trouble with that in the very early days of the HVX.

-tim
 
You must log in or register to reply here.
Back
Top