-
Problems exporting from FCPX
Hi.
I’m editing material from a DLSR camera (h.264, 720p) and have enormous problems with exporting the video. Here is the problems I have:
(1) When sending to compressor and exporting, I get Quicktime error -50 when trying to export a 20min movie, but if I divide the movie into 2 parts, I do not get the error (trying both h.264 and ProRes exporting). “Export media” does not give an error,
(2) When exporting (both compressor and directly) I get lines appearing in intervals (coming and going) with what seems to be lines from other part of the screen or maybe just a line with an offset (see link below). If I export by sending to compressor, I get vertical lines and if I choose “Export media” in FCPX I get horizontal lines. Example: https://s9.postimage.org/3vayyj333/Screen_Shot_2011_12_19_at_16_30_18.png
Please help!
Thanks.
-
10 Replies
-
I have had the same issue. Try making a new project (timeline) and copy everything in your video into the new timeline. Then export before you make any changes to your project. Worked for me hope it works for you.
Luke Hale
Producer/Editor BYU-I and Department of Energy
opticalsmarts.com (Just for fun) -
Did you optimize your media?
All the best,
Tom
Class on Demand DVDs “Complete Training for FCP7,” “Basic Training for FCS” and “Final Cut Express Made Easy”
Coming in 2012 “Complete Training for FCPX” from Class on Demand
“Final Cut Pro X for iMovie and Final Cut Express Users” from Focal Press -
[Tom Wolsky] “Did you optimize your media?”
Is that the FCX term for “transcoding to ProRes?” I thought that FCX dealt with more formats natively…including H.264.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Shane Ross] “I thought that FCX dealt with more formats natively…including H.264.”
I think it depends on how you define “dealt.”
If that means allowing them all to reside in a single timeline and doing the transcoding in the background so that you can manipulate video streams that originally were encoded differently – then yes, X “deals” with a wide bunch of formats “natively” (defining natively as without requiring external transcoding first.)
If you mean that it actually “edits” a host of differently encoded streams in their native format I don’t think X can do that – nor do I think that any other software can.
Unless I mis-understand things, you can’t actually co-mingle different types of data streams in a single interface unless you transcode them into common denominator types first. Good systems do this “on the fly” but at some point when you’re, say, dissolving between two clips, those two clips have to be represented by data that mathematically aligns in order to be combined thru calculation.
I could be wrong, but this is how I think all NLE’s operate.
I do know that the FCP-X process is to “sequester” any originally imported clips in their original format – and from that point, everything done to them is via layered meta-data manipulation. So applying effects, corrections, cuts, etc is never “destructive” simply because the program always “references” original clips but never actually changes them. (FCP-Legacy, did this as well, just differently.)
This also may be at the heart of the issues people have with the program not easily “dumping” the unwanted parts of captures. That ability to “kill all instances” of footage from ones storage is cool when one persons is the sole “owner” of them. But what happens when workgroups, or maybe even remote individual workers “log into” pools of assets on-line? The same ability to “dump” files, could conceivably lead to one clueless editor “erasing” fundamental assets – which would be a very bad thing indeed.
This is speculation. But speculation born of seeing more and more hints of the structure under X.
FWIW.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
[Bill Davis] “If that means allowing them all to reside in a single timeline and doing the transcoding in the background so that you can manipulate video streams that originally were encoded differently – then yes, X “deals” with a wide bunch of formats “natively” (defining natively as without requiring external transcoding first.)”
No. Dealing with formats “natively” means working with them as is. As they exist currently. NO transcoding, not even in the background. Transcoding in the background is still transcoding. So that means not working with the files natively.
[Bill Davis] “If you mean that it actually “edits” a host of differently encoded streams in their native format I don’t think X can do that – nor do I think that any other software can. “
Premiere Pro can. WIth just about any format. No transcoding. Working with files natively, as the are.
[Bill Davis] “Unless I mis-understand things, you can’t actually co-mingle different types of data streams in a single interface unless you transcode them into common denominator types first. Good systems do this “on the fly” but at some point when you’re, say, dissolving between two clips, those two clips have to be represented by data that mathematically aligns in order to be combined thru calculation.
I could be wrong, but this is how I think all NLE’s operate. “
You are wrong. This is how PPro 5.5 currently works. You can mix formats in a single timeline without needing to render (given a powerful machine with fast processors, RAM and a CUDA card), but when you render, the render files match the sequence settings.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
Thank you for the tip!
Do you mean that it fix the “Quicktime -50” error or the vertical/horizontal lines in the video?
-
No, I didn’t optimize my media. I’m editing on a Macbook Air with limited hard drive so when I tried it said that there was not enough space. But I guess it *should* not matter if I optimize or not?
-
I tried copying to a new timeline. If I used “Export media” using current settings it looks like this:
https://s11.postimage.org/ervnyq0ir/Screen_Shot_2011_12_21_at_13_46_27.png
And if I sent to compressor I got the “Quicktime -50” error again 🙁
Anyone know what might cause this?! Its terrible, I can’t export my project.
-
[Shane Ross] “Is that the FCX term for “transcoding to ProRes?” I thought that FCX dealt with more formats natively…including H.264.”
It handles h264 natively very well if you have a fast Mac, I never transcode h264.
“My Name is Steve and I’m an FCPX user”
-
[Gunnar Blom] “No, I didn’t optimize my media. I’m editing on a Macbook Air with limited hard drive so when I tried it said that there was not enough space. But I guess it *should* not matter if I optimize or not?
“It shouldn’t matter at all, have you tried trashing FCPX preferences?
“My Name is Steve and I’m an FCPX user”
Reply to this Discussion! Login or Sign Up