View Full Version : FCP cannot re-import an XDCAM export..
Harley Flanagan June 7th, 2007, 11:28 AM Sorry guys...I have a feeling this might have been posted already, but I personally couldn't find any old posts.
We effortlessly import at least 10 XDCAM field discs (with multiple clips) a week without any issues. We use XDCAM Transfer along with FCP 5 & 6.
We hit a brick wall whenever we try to re-import a "mastered" XDCAM disc (we master back three 1/2 hr shows to a disc with different audio and gfx configs....a master, a split and a foreign version). For some reason, whenever I go to import one of the three files off this disc, it only imports approx 3 minutes (give or take a few seconds).
Why does material straight out of our cameras import fine, but the discs we create here have a problem?
Here are some kickers to the issue:
-Everything plays back fine in AVC mode.
-We HAVE imported clips well over 30 minutes long from field recordings.
-We tried disabling audio tracks in the Transfer tool
-We tried importing footage straight from the transfer software to a drive...FCP wasn't even launched.
We tried all of the above as a means of troubleshooting, but to no avail....
For what it's worth, the file compression is HDV 1080 25cbr, although I doubt that has anything to do with this.
Any clues here? Is there any other info I might provide you guys?
Greg Boston June 7th, 2007, 02:00 PM That's a strange one. Do you get any error messages? Is it FCP5 or 6 causing this? I'm trying to obtain an answer from someone else. Will let you know if and when I get a response.
-gb-
Mike Watson June 7th, 2007, 02:12 PM There was a discussion on this over at LAFCPUG last year, and I believe there is a soft limit to how long clips can be that are written back to the disk.
I also have had this problem, and I just import via AV/C. I don't have this problem with clips that are shot with the camera. I don't know why.
Search LAFCPUG.org, or Andy Mees will know. Andy knows everything.
Mike Watson June 7th, 2007, 02:13 PM Also... and this is purely an administrative comment... you'll do better with your thread if you name it something like "XDCam re-import troubles, 25Mbit CBR - freezing up", and put the cursory note to the mods at the end of the message... not the other way around.
Harley Flanagan June 7th, 2007, 02:26 PM That's a strange one. Do you get any error messages? Is it FCP5 or 6 causing this? I'm trying to obtain an answer from someone else. Will let you know if and when I get a response.
-gb-
Greg..
No error message. XDCAM Transfer just stops like it normally does when it is complete. It's only ingesting 3 minutes of a 1/2 hr show. This problem occured initially on FCP 5.1. I tried to troubleshoot on FCP 6 but had the same exact issue.
Harley Flanagan June 7th, 2007, 02:27 PM There was a discussion on this over at LAFCPUG last year, and I believe there is a soft limit to how long clips can be that are written back to the disk.
I also have had this problem, and I just import via AV/C. I don't have this problem with clips that are shot with the camera. I don't know why.
Search LAFCPUG.org, or Andy Mees will know. Andy knows everything.
See..yeah...you are experiencing the same thing. Clips from the camera can be long no problem, but re-ingesting an export is not happening!
AVC is an option of course, but this just does not seem right. Thanks for the input Mike...good to know it's not just a fluke.
Mike Watson June 7th, 2007, 04:26 PM I also get errors while exporting to disk, and blowing out the render files and re-rendering seems to fix that. Unfortunately, it can be an hours-long fix. No rhyme or reason to it, Sony tech support was stumped. Let's say I've been less than thrilled with the transfer software thus far.
-MW
Andy Mees June 7th, 2007, 08:34 PM Sorry Harley (and Mike!)
The best I can do is confirm that I have had this same problem reported to me too in the past. However when I tried to duplicate the issue I was unsuccessful. Here's my findings at the time:
22.2.07
Hi XXXXX
I’ve been trying to replicate your issue over the last couple of days but have not been successful :/
For a test I imported a 33 minute clip from disc (XDCAM HD at 25 Mbps) using XDCAM Transfer, then edited it down to 30 minutes in FCP and exported it back disc, then I re-imported that file back into FCP .... everything worked.
I also tried it numerous times with smaller files (between 3-5 minute edits cut in the DV codec) and again, no issues with multiple generations of export and re-import.
The 33 minute clip’s file size was a little over 6GB, so I would doubt that your issue is directly file size related ....
...that said, my hard disc space was running a little low on my laptop, so I made sure to free up plenty of space first, to ensure there was room for temporary cache files etc, how much free disc space are you working with?
Is there anything else about your media or setup that you can think of that I should need to know? Perhaps I can try testing with the exact same clip format you are working with... what is your source format?
Cheers
Andy
so it's clearly not any kind of set limit.
... and Mike, I've had plenty of those Export Failed messages too. Same fix as you. Blow out the renders and re-export or check the "Recompress all frames" checkbox in the export dialog.
We are all eagerly awaiting the long long overdue update to this otherwise promising software. The trouble is that Sony have adopted a "we provide it for free so we're not obliged to anyone" approach. Frankly, I'd rather pay for it and then be owed some support.
Andy
Klaas van Urk June 8th, 2007, 08:15 AM Looking from the sideline. Is the name of the clip following the 'name convention' for MXF files? (like C0001.MXF or such).
Harley Flanagan June 8th, 2007, 08:33 AM Looking from the sideline. Is the name of the clip following the 'name convention' for MXF files? (like C0001.MXF or such).
affimative.
Harley Flanagan June 8th, 2007, 08:37 AM Sorry Harley (and Mike!)
The best I can do is confirm that I have had this same problem reported to me too in the past. However when I tried to duplicate the issue I was unsuccessful. Here's my findings at the time:
so it's clearly not any kind of set limit.
... and Mike, I've had plenty of those Export Failed messages too. Same fix as you. Blow out the renders and re-export or check the "Recompress all frames" checkbox in the export dialog.
We are all eagerly awaiting the long long overdue update to this otherwise promising software. The trouble is that Sony have adopted a "we provide it for free so we're not obliged to anyone" approach. Frankly, I'd rather pay for it and then be owed some support.
Andy
Andy..thanks for your reply.
This is really odd. I'm now leaning towards the possibility of us doing something wrong on export. I'm really out of answers.
Mike Watson June 8th, 2007, 09:52 AM Andy... you ever get over here, stateside?
Harley Flanagan June 8th, 2007, 09:59 AM Ok..
A few more updates...
I saw that someone suggested that XDCAM Transfer has issues sometimes with SAN MP (which we use). I quit SAN MP and wrote to a local drive instead. SAME ISSUE.
I had been using discs @ 25, so I tried a disc @ 35. SAME ISSUE.
Andy-
Our 25 Mbps shows were shot @ XDCAM 10801 60 25 and imported onto an HDV 1080i 60 timeline. We currently shoot on XDCAM 10801 60 35 and import it into a sequence with the same settings we shot at.
The exports of both will not re-import.
Alister Chapman June 8th, 2007, 10:28 AM There is certainly an issue with SAN drivers. This has cropped up a few times now and can cause all kinds of import and export issues.
Greg Boston June 8th, 2007, 12:15 PM Our 25 Mbps shows were shot @ XDCAM 10801 60 25 and imported onto an HDV 1080i 60 timeline. We currently shoot on XDCAM 10801 60 35 and import it into a sequence with the same settings we shot at.
The exports of both will not re-import.
Harley,
This is the response I got from my technical contact at Sony America HQ.
I think if they upgrade the decks they are using to ingest the files to
version 1.60, the problem will go away.
The was a bug in Version 1.56 when a 60i MXF file which was created
using GOP splicing techniques was written to the disc. The file is
valid and is accepted by the deck (and it plays perfectly in the deck).
However, when you try to read the file (ie re-ingest the file into the
NLE), the deck would read up to the splice point and then stop (on
Windows the operating system would say that there was an I/O error).
Version 1.60 for the PDW-F70 fixes this reading problem.
So I would make sure that your decks (and camera/s) are all at firmware revision 1.6 to eliminate that as a cause.
regards,
-gb-
Harley Flanagan June 8th, 2007, 01:00 PM Harley,
This is the response I got from my technical contact at Sony America HQ.
So I would make sure that your decks (and camera/s) are all at firmware revision 1.6 to eliminate that as a cause.
regards,
-gb-
Duuuuuude.
That's great. Let me check right now.
It's makes total sense about the error when it hits a "splice point". One thing I forgot to mention was that the transfer stops at THE SAME POINT every time..which totally falls in line with the info you provided.
I will post my results. Thanks Greg, top notch stuff.
Mike Watson June 8th, 2007, 01:13 PM The export function I was complaining about on the first page has the same behavior, where it exports to a given point, and stops there, every time. The re-render that Andy and I discussed solves this problem.
I wonder if the software didn't put something on the disk in the writing process that freaks it out, and now can't read it. I wonder if you had the same project written to disk twice, if you could import the second one, when the first froze at the same spot every time. (This would be the equivalent of the re-render Andy and I spoke of in the writing process.)
Sorry to threadcrap with my complaints about a different process, but I suspect the answers are similar.
Harley Flanagan June 8th, 2007, 03:06 PM Duuuuuude.
That's great. Let me check right now.
It's makes total sense about the error when it hits a "splice point". One thing I forgot to mention was that the transfer stops at THE SAME POINT every time..which totally falls in line with the info you provided.
I will post my results. Thanks Greg, top notch stuff.
Ugghh..
No luck. In all fairness though, all I found was Firmware Version 1.59, not 1.6.
Did you mean 1.59?
Also, I wonder if the disk would need to be formatted under this firmware revision to work?
Greg Boston June 8th, 2007, 03:38 PM Ugghh..
No luck. In all fairness though, all I found was Firmware Version 1.59, not 1.6.
Did you mean 1.59?
Also, I wonder if the disk would need to be formatted under this firmware revision to work?
No, I meant 1.6 which is what I have on my camera. I don't have the deck. 1.6 specifically fixes this issue. My Sony America source also spoke to Japan about this and they seem confident that 1.6 will resolve the issue.
Go to https://servicesplus.us.sony.biz/sony-software.aspx
Do a search in model number field for PDW-F70 (if that's the deck you're using). There search will return 5 items. The second from the bottom is the 1.6 update and is just over 8 mb in size.
-gb-
Harley Flanagan June 8th, 2007, 04:23 PM No, I meant 1.6 which is what I have on my camera. I don't have the deck. 1.6 specifically fixes this issue. My Sony America source also spoke to Japan about this and they seem confident that 1.6 will resolve the issue.
Go to https://servicesplus.us.sony.biz/sony-software.aspx
Do a search in model number field for PDW-F70 (if that's the deck you're using). There search will return 5 items. The second from the bottom is the 1.6 update and is just over 8 mb in size.
-gb-
It's working so far!
Never got beyond 3%...now I'm up to 75%
Greg Boston June 8th, 2007, 05:36 PM Never got beyond 3%...now I'm up to 75%
I'd call that progress! (grin)
Hope this puts the issue to bed. BTW, this affected not only FCP, but Avid as well.
-gb-
Andy Mees June 9th, 2007, 12:18 AM good info Greg, explains a lot. thanks for passing it along. so this is (or seems likely to be) a firmware issue affecting both camera and deck (and is specific to 60i? i'm thinking probably not)
thanks.
hey Mike... no, sadly I don't get over to the US often. which is lucky for you guys, or you'd have me forever cadging beers and sofa space ;)
Greg Boston June 9th, 2007, 12:41 AM good info Greg, explains a lot. thanks for passing it along.
Yeah but Harley didn't come back and post a 100%. The suspense is killing me. (hehe)
-gb-
Alister Chapman June 9th, 2007, 01:51 AM 1.6 fixes quite a few small bugs. It fixed the issue I had with auto iris on my canon lens.
Well done Greg!
Greg Boston June 9th, 2007, 01:53 AM Well done Greg!
Thanks! BTW, a major tornado outbreak may happen in the midwest next week according to one local forecaster.
-gb-
Harley Flanagan June 11th, 2007, 08:51 AM Thanks! BTW, a major tornado outbreak may happen in the midwest next week according to one local forecaster.
-gb-
Greg..
You deserved the final word on this. Thanks for helping me out.
As of 7 o'clock on Friday, I imported 2 30 min shows to completion.
I'm going around the facility right now with my trusty memory stick upgrading all the decks.
Thanks again!
TTT
Greg Boston June 11th, 2007, 12:13 PM As of 7 o'clock on Friday, I imported 2 30 min shows to completion.
Awesome! And don't leave me hanging at 75% next time. (grin)
-gb-
|
|