3.98 gb MXF's giving me problems!

Hey All!

FCP 6.0.1 AND 6.0.3
HVX200A
16 and 32 gb P2 cards

I have been trying to convert MXF's to QT's and they keep giving me errors or creating QT's that will not open. The weird thing is, all the problematic clips are 3.98 gbs.

Anyone run into this one before?

Thanks!

greg

Well...try this...

#36 - One or More P2 files failed to import.

Shane's Stock Answer #36 - "One or more clips failed to import..."

Very often in the field with this camera the camera operator will delete clips from the P2 card that they just don't like. That is the beauty of this camera. But, the still for that video file (located in the CLIP folder in the CONTENTS folder)...the still that you see when you are in the P2 Import window...is not deleted. So you will see the image, and the name, but the video file would have been deleted.

What you can do it compare the file names in the VIDEO folder and CLIP folder and see if anything is missing. If something is, then you know what the problem is. You can then just import the rest a few at time, skipping that one.

ALSO...in the P2 Import window...in the P2 Browser, there is a little sprocket drop down menu. Click on that and choose PREFERENCES. Uncheck REMOVE PULLDOWN and then try importing again.

ALSO...make sure your file names aren't too long. Try shortening them and see if that works.

<img src=http://homepage.mac.com/comeback/.Pictures/P2ImportSprocket.png>


www.shanerosseditor.com

Listen to THE EDIT BAY Podcast on iTunes
[itunes.apple.com]

And check how the disk you're writing to is formatted. If it's not Mac OS Extended it won't write files larger than 4 GB, which sounds suspiciously like what you're getting.

Scott

Oooo....good catch. Didn't dawn upon me, but that makes PERFECT sense.


www.shanerosseditor.com

Listen to THE EDIT BAY Podcast on iTunes
[itunes.apple.com]

Isn't it 2GB? It does sound like a 4GB split is happening though.

Hey guys, thanks for responding....

Here is some additional info, plus the way that I dealt with it...

Additional info:

1) I am capturing to a networked RAID, and I too suspected something about the drives, given that the files were all the same size. However, it is the MXF's, not the QT's, that are all identical sizes (3.98), so if there was a file format issue it had to have been with the P2 cards.

2) That being said, when I had my assistant "capture" to a local drive in lieu of the RAID, things worked out fine.

3) I have transfered other MXF's tot he same RAID, using the same workflow, that are much bigger than 4gb. I'm looking at one now that is 11gb

Jude - What is "a 4gb split"??

Thanks everyone!

greg

Hmm.. It seems to point to a similar issue- the drive connection or the formatting. Being able to transfer large files to the RAID doesn't necessarily mean that it can handle a capture properly.

I had issues with a networked RAID a while ago- they were on a gigabit ethernet connection. Something was wrong with the set-up, as it can handle file transfers, but on capture, the folder could get corrupted, or it would split a file (an -av extension, linked to a bunch of files split into either 2 or 4 gigs uniformly). And it was just DV, so it's not a huge stream. I believe the drives were formatted to HFS and not FAT32, but tech support at that place just didn't seem to know how to handle macs properly.

> Jude - What is "a 4gb split"??

I think what she means is a 4gb split across a .mov file. Eg. The -av extension, with a bunch of files with a similar name after, all with a -1, -2 extension.

FAT32 formatted drives do present an issue when transferring files bigger than 4 gigs (or was it 2?). But basically the file won't copy and it will cite a 00 error.

Hope this helps.



www.strypesinpost.com

hhhmmm, it seems like I need to do a little more specific investigation to get to the bottom of this...hopefully the production schedule will allow!

Thanks everyone for the tips, if I get tot he bottom of it I'll let you all know..
greg

Quote
Jude asked:
Isn't it 2GB? It does sound like a 4GB split is happening though

I think a drive formatted NTSF (Windows NT secure format) tops out at 4GB, MS-DOS or Mac not Extended limit is 2GB. I think. Anyway, it doesn't sound like that was the issue here.

Scott

Ahh... NTSF... now i remember.. that blasted thing was NTSF, and geez, i'm no IT guy...

Here's a guide [discussions.apple.com]



www.strypesinpost.com

But it's weird....I mean why are the problematic clips all derived from MXF's that are the same size, and happen to be 3.98gbs?

Could the P2 cards have been formatted wrong?

>I mean why are the problematic clips all derived from MXF's that are the same size, and happen
>to be 3.98gbs?

If you didn't get problems capturing to the internal drive, it can't be a p2. Drives are touchy stuff. They might prompt an error on file transfer. Error 0 isn't an actual error, btw. They might not. But an automatic "trimming" of the file size could mean an improperly formatted drive.



www.strypesinpost.com