Any takers? Figured I'd give a message bump, before we try to get in touch with an Adobe rep.
If nobody has a solution, has anyone else experienced the same issue? I'm curious as to if this is a widespread problem or just exclusive to us.
We are experiencing all of the above, but also an additional problem occurs after the .MFX file is copied to the Clip folder, and the resulting file when played back from the XDCAM disc fails to play back properly. The video playback "stutters". Not throughout the entire video, but often appears during scenes with movement. We've tested and are able to recreate this problem from various test projects in Premiere Pro CS 6 on a Mac OS 10.8.4.
We too would like to be able to export directly from Premiere Pro to XDCAM disc and of course have the video playback properly from the disc.
How did you attempt to export the file. Did you use one of the XDCAM presets under Format > MXF OP1a?
I used a preset from the MXF OP1a list. Specifically, I used the "XDCAMHD 50 NTSC 60i" preset. I'll also used the "XDCAMHD 50 NTSC 60i" preset to create a custom preset that would "turn off" the metadata or set the "Metadata Export" to "None", because someone suggested that might help, but it does not seem to make any difference with my video playback "stutter" issue.
Any other ideas to help resolve this issue?
Thanks for your help.
I meant to do an update sooner, forgot I had this thread opened until the recent posts appeared. I have a pretty detailed update for everyone.
I got on a call with Dennis Radeke from Adobe (who I believe manages broadcast solutions for the company) and we spoke about a few things about adobe (I was using CS6 and he was using CC, but it seemed to be irrelevant for this issue)
We spoke about the problem, and he came up with a potential reason why the issue exists, that now I find silly I didn think of this earlier.
The potental reason why a direct export from APP to XDCAM (even in the proper MXF OP1a format, and even with the XMP metadata disabled since the XDCAMS dont use those) is that APP is trying to render AND write directly to the destination at the same time. Since XDCAM disks are optical, it is limited by the write speed of that medium. What he thought is hapening (and what I agree with) is that the render and transfer speed is working FASTER than the drive's ability to bring it to the destination, causing APP to freak out and give up.
On FCP, this is circumvented because when you push to XDCAM directly from FCP, it uses XDCAM Transfer as an intermediary, where FCP will render the file out in a cache, and then transfer it after (which is why you see a new window pop-up).
Now the good news is Dennis responded to us and said that now Adobe is possibly going to try to address the issue in CC, and find a work-a-round for this. Aside from that I cant speak on behalf of Adobe aside from: some people are aware of it and may want to make it a working process.
I did find a "solution" thats a bit more autmated then transferring to desktop and then transfer to dsc, although it's essentially the same thing:
1.) make an "output" folder somewhere, where the sole purpose is to temporary hold the files.
2.) Push the MXF OP1a file (without .xmp metadata if possible - although even if it creates one it doesnt really matter) TO that output folder
3.) Make a script in Automator which automatically searches for .MXF files in that output folder, and moves it to the "Clip" folder on your XD drive.
For fun, I use automator combined with AppleScript to make a little "beep" when the transfer is complete.
It's not as streamlined as an in-line process in APP, but it is doing the same thing nonetheless. Obviously, you need to make sure all other boxes are checked, like having naming set to "free" on your utility if you want to have named files.
I would make a more detailed walkthrough but I dont have time at the moment, just wanted to give an update. Feel free to ask any questions