Activity › Forums › Apple Final Cut Pro › FCPX problem!!!
-
FCPX problem!!!
Posted by Theo Hall on March 16, 2012 at 2:27 pmso i just finished my edit in FCPX and i realize that after i export there is at least 3 mintues of black it just goes to after my edit is done, i checked to see if a gap was in there but there wasnt, i zoomed all the way out i saw nothing, and i try to zoom all the way at the end of the timeline but it wont let me, it just goes straight to the end of the edit, so what i did was i created another gap and extended that all the way to the end, thinking i could find it, that sure didnt help, i zoomed to the end and then deleted that one, now my timeline is even longer, its like it still keeps gaps but there invisible, what is going on?
AGAIN!, i tried to zoom in to the end but it will not let me, it will just zoom to the edit, i have 10.0.3 of FCPX is this part of the new update? i hope i made sense of this, anybody is having this problem?
Bill Davis replied 14 years, 2 months ago 8 Members · 18 Replies -
18 Replies
-
Adam Helwig
March 16, 2012 at 3:50 pmI’ve had this problem too and have not been able to find a solution. I don’t know what triggers it, but I’ve had it happen in two projects so far. Once back in 10.0.1 and once in 10.0.3. I’d be very interested to hear a solution (if there is one).
-
Andy Neil
March 16, 2012 at 4:27 pmTry copy/pasting the contenst of your project into a new project. Perhaps you have a corrupt project.
Andy
https://www.timesavertutorials.com
-
Theo Hall
March 16, 2012 at 5:40 pmtried that and no good, so then it could be a corrupted a project then, i dont know how thats possible cause i have been editing normally as i always do
-
Andy Neil
March 16, 2012 at 5:54 pmProjects go corrupt usually due to no fault of the user. It can happen if the program saves data incorrectly into the project file. It’s just one of those things that sometimes happens.
But if copy/paste didn’t solve it, then you probably don’t have a corrupt project. I suppose you’ve trashed your preferences?
Also, how did you copy/paste to a new project? If you hit CMD+A and then CMD+C you could have copied the problem over as well. Make sure that you did a manual selection by lassoing.
Another thing to try. Delete the final clip in your sequence. Try to export. If that fixes problem, re-edit the clip back into the project (don’t undo or paste back in there).
Andy
https://www.timesavertutorials.com
-
Mark Morache
March 16, 2012 at 6:58 pmI’m curious… try expanding all of your audio. Is it possible that there is some hidden audio that’s tucked into another clip that’s extending beyond the end of the video?
Another idea… try compounding the entire timeline. Where does it end? With the video or does it add the black that you see?
I’ll bet that if you trim the compound clip you can export just the portion that you want.
I’d be tempted to duplicate your project (without renders) before you compound the entire project. I’ve seen a few instances where compounding and breaking apart can leave clips in slightly different places than where you’ve placed them.
———
Don’t live your life in a secondary storyline.Mark Morache
FCPX/FCP7/Xpri/Avid
Evening Magazine,Seattle, WA
https://fcpx.wordpress.com -
Michael Sanders
March 16, 2012 at 8:08 pmHow about this.
if you do shift+Z, this zoom’s the timeline to fit. If the end of where you think the timeline should be isn’t near the right of the screen, then maybe there’s a black or a gap generator in it. click on delete and then press Shift+Z together.
If the end of the timeline is to the right hand side then you have a corrupt project.
Michael Sanders
London Based DP/Editor -
Lance Bachelder
March 16, 2012 at 10:23 pmExactly! Had the same issue – deleted a few stray clips that were way down the timeline and rendered but forgot that the blank area is not “blank” it’s slug and needs to be deleted.
Hopefully this will be fixed soon – we need to be able to set in/out and export that area.
Lance Bachelder
Writer, Editor, Director
Irvine, California -
Bill Davis
March 17, 2012 at 8:44 am[Lance Bachelder] “Hopefully this will be fixed soon – we need to be able to set in/out and export that area.”
Lance,
I understand the desire for “range export” but I don’t think it’s coming back. (Although I hope I’m wrong on this.)
I think it’s the NLE equivalent of “versioning” replacing “save as” in the whole OSX evolution.
At the level of a single user always trying to export a single “finished” document – “save as” was what we got accustomed to. But in theory – it’s a pretty weak concept compared to the VERSIONING process built not OS-X today.
In the increasing cloud-based world where we (and potentially others) can log onto the same file from different places and at different times, you don’t want someone else to “save as” a minute before you log on – and then suddenly changes are being made to TWO discrete copies of the same file.
You want the software to understand which VERSION is being revised and keep ALL the versions active until the decision is made how (or if) to integrate such changes.
Same with an X project. If they ever do make the Project library function as a “published finals” structure – you don’t want the sound folks, or the color folks to come into and “save changes” to YOUR file – making the original one disappear! You want their input saved as “VERSIONS” of the document – with the program keeping tack of YOUR version in the exact state YOU left it in – regardless of who made subsequent changes.
That’s why I suspect we lost the “export a section” capability in X – not because they simply didn’t have time to code it.
Said another way “export a segment” is a temporary construction that cuts the export off from all relationship to the original arrangement.
Duplicate, OTOH preserves all the data structures that exist at that point and lets you make changes to the new work independently of the connected state of the original construction.
Seen that way – the X design has a lot more potential than “export” and “save as” ever did.
But it sure is a lot more difficult to get used to – and real easy to simply see as a “loss” of something that worked easily and well.
The problems as I see it is that it worked well for the world we used to edit in (discrete individual assembly and single file export cut off from the past) and not so well for the “on-line” persistently connected world we’re moving toward.
Maybe?
My 2 cents anyway.
“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
-
Lance Bachelder
March 17, 2012 at 9:21 amYikes, I hope you wrong too. I’m not getting your hook up with versions and exporting a section? The two have nothing to do with each other. There’s always times working on a show when a section needs to be exported for review or whatever – every other NLE has this necessary feature and I’m sure it will be added back to FCPX. I don’t get how versioning replaces the need to export a specific area of the timeline.
Lance Bachelder
Writer, Editor, Director
Irvine, California -
Brandon Parigo
March 17, 2012 at 3:15 pmMaybe they thought it was redundant since you can push to compressor and then select the portion you want exported. Why have it in both programs. Just a thought.
That was also my suggestion to the original poster. Have you tried to push it to compressor and trim out the end?
Reply to this Discussion! Login or Sign Up