-
Can’t export .dv file out of FCPX
So I have this .dv file which I imported into FCPX and it seemed to transcode fine and plays correctly within FCPX. Every time I go to export it, whether via master file or out to compressor it fails to export. For the life of me, I can’t get this thing to export. I don’t have issues with other projects, granted this is the only .dv file I have so it’s definitely the culprit. Does anyone have any idea of what can be causing this?
Oh one last thing, the original .dv file can’t be copied to anything outside of my computer. Anytime I try to copy the file I get an “Error code 36”. I’m sure that has something to do with it as well. I’m perplexed because it plays just fine but I can’t seem to do anything else with it.
Thank you in advance!
~Erick
-
18 Replies
-
Hi Eric
Sounds like a dodgy source file. Have you tried Edit Ready.
What I have also done with strange or old formats like this that don’t work properly or transcode I import in After Effects and then export to ProRes. Sometime I have to export around the damaged area. The fact that you can’t copy it off your HD seems like it is a corrupt file.
-
I have not tried “Edit Ready”. Don’t know if I should spend $50 just to see if it’ll work. The trail only encodes the first minute of a clip. This is easily a 6-7 minute clip and the problem area might not appear in the first minute. The AE idea is interesting. I’ll give that go and see how it works. I’m now wondering if Motion can do something similar to AE in terms of the way it exports to ProRes. Thank you for the suggestions. I’ll try later tonight and get back with results.
-
Try to optimize the file in FCPX, then import the optimized file and has that. Delete the dv file completely out of the library.
You can also try Compressor (or Motion) to make a new version.
-
@jeremy Thanks, I’ll give that a go as well.
-
For safety’s sake, you should first make a solid backup of the original file with some form of checksum duplication before you start working with, or delete anything. If you don’t have something like Carbon Copy Cloner or Shotput or Hedge – then at least make a finder copy to external media via drag and drop.
It’s alway better to have a solid copy of the original file (if you can) to “re-process” should some transcode not work.
Just a suggestion.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery. -
@Bill Unfortunately that seems to be one of the original problems. I can’t seem to copy the file to any external storage or server. Every time I do I get that Error 36 and I have no idea why. I can play the video via Quicktime and when I import it into FCPX, it transcodes just fine and I can play it in the timeline. The issue is when I go to export it either within FCPX or bounce it out to Compressor, it fails to export every time.
-
For what it’s worth, and this might be a little vague because it’s been a couple of years since I had to deal with it, error code 36 was related to the ._ invisible file associated with the file or directory in the Finder and most often occurs with files and directories created on a Windows machine, then copied to the Mac.
At the time, I found a utility that cleaned out the relevant ._ files and the error went away. Unhelpfully, I can’t remember what it was called though.
—-
Jeff Kirkland | Video Producer & Cinematographer
Hobart, Tasmania | Twitter: @jeffkirkland -
So I tried to optimize the media in FCPX, which seemed to go fine but when I went to export it out either natively or through compressor, it failed. Placing it inside an AE project and exporting failed as well. The damn thing plays in FCPX fine but can’t get it out. There has got to be a way. How is it that FCPX can play it, yet not export it out.
-
[Erick Puentes] “How is it that FCPX can play it, yet not export it out.”
Some sort of corruption.
Can you duplicate the clip on the Finder level? That may shake loose permission errors.
If that doesn’t work, you should try and “Get Info” on the file and turn off all permissions.
-
[Jeff Kirkland] “error code 36 was related to the ._ invisible file associated with the file or directory in the Finder and most often occurs with files and directories created on a Windows machine, then copied to the Mac. “
This, I think, is the correct diagnosis. There’s a UNIX command line tool (built into MacOS) called ‘dot_clean’ that can be run from Terminal.app.
How comfortable are you with the command line, Erick?
Doug Metz
Anode
Reply to this Discussion! Login or Sign Up