This has been driving me crazy for a few weeks:
I can't ⌘+E to export my Timeline / Project? Why? You can in Motion !!! But of course, you can in FCPX as well. Go to Share / Add Destination.
Right-click onto the Destination you want to export with (I choose Export File... )
Select Make Default from the drop down menu. Bang! Now I can ⌘+E all I want!
I found out about the shortcut in the Commands / Customize, searching for "export".
I was ready to make my own, but I saw ⌘+E already listed there as a shortcut for Export Using Default Share Destination, but... a Default Destination wasn't assigned.
Now it is!
⌘+E Bam!
Thursday, March 27, 2014
FCPX frame rate conform
Frame rate conforming cannot be easier in FCPX:
- Bring your clip into the Timeline. (29.97fps clip into 25fps Timeline for ex.)
- Select the clip, then go to the Inspector (+4)
- Under Video > Rate Conform, select Frame Sampling = Frame Blending or better yet Optical Flow. The later takes longer as FCPX needs to analyse the clip first.
Done. And it looks pretty good!
- Bring your clip into the Timeline. (29.97fps clip into 25fps Timeline for ex.)
- Select the clip, then go to the Inspector (+4)
- Under Video > Rate Conform, select Frame Sampling = Frame Blending or better yet Optical Flow. The later takes longer as FCPX needs to analyse the clip first.
Done. And it looks pretty good!
Tuesday, March 25, 2014
Apple Motion adjust Timeline duration
To adjust Timeline duration in Motion:
- Click on the arrow located right to the counter display.
- From the drop down menu select: Show Project Duration.
- Adjust time by click+dragging into the HH:MM:SS:FF display.
- Then click on the arrow again and select back to Show Current Time to display cursor position.
- Click on the arrow located right to the counter display.
- From the drop down menu select: Show Project Duration.
- Adjust time by click+dragging into the HH:MM:SS:FF display.
- Then click on the arrow again and select back to Show Current Time to display cursor position.
Apple Motion and FCPX
I cannot import Motion files into FPX the way I did with FCP7. But on Apple's website it says:
"Shared Render Engine
Final Cut Pro shares a render engine with Motion and Compressor for consistent speed and quality. The shared engine allows Motion templates to play back in Final Cut Pro without rendering. The engine renders in linear-light color space for exceptionally realistic results.
Well Motion templates, not really useful at this point. But then it also says:
"Shared Render Engine
Motion shares a render engine with Final Cut Pro and Compressor for consistent speed and quality across applications. The engine allows Motion projects to play back in Final Cut Pro without rendering, so you can get to work immediately."
Motion projects, OK great! But HOW??? Templates? I don't see this working.
"Shared Render Engine
Final Cut Pro shares a render engine with Motion and Compressor for consistent speed and quality. The shared engine allows Motion templates to play back in Final Cut Pro without rendering. The engine renders in linear-light color space for exceptionally realistic results.
Well Motion templates, not really useful at this point. But then it also says:
"Shared Render Engine
Motion shares a render engine with Final Cut Pro and Compressor for consistent speed and quality across applications. The engine allows Motion projects to play back in Final Cut Pro without rendering, so you can get to work immediately."
Motion projects, OK great! But HOW??? Templates? I don't see this working.
Thursday, March 20, 2014
Apple FCPX OpenGL error 506 workaround
From time to time, FCPX 10.1.1 gets stuck rendering.
The background task hourglass is stuck in a 0% - 100% loop and nothing happens.
Up to now I had to restart each time this happens (several times a day) to get out of the dreaded loop.
For info, when force-quit Apple report says:
"Final Cut Pro[1385]: *** OpenGL error 0x0506 (invalid framebuffer operation) in function "GL_CHECK_CURRENT_ERROR"
This morning after getting stuck again, I clicked: Modify/ Render selection. That got FCPX out of stuck mode and to render normally again! No need to force-quit/restart!
So this might be a workaround until the problem gets fixed in future version. Make sure that something is selected in the timeline/project. Shortcut: Control + R
--- Update (March 20):
It does not always work unfortunately, if I react took late, I cannot get out of the loop.
The weird thing is that sometimes several hours pass before I get the dreaded loop. And then it happens a lot. After a while, it does not appear again. I can't figure a reason yet.
--- Update (April 23):
I've now worked several days and the dreaded loop has not showed up. ;) Same project(s).
What's different?
- I moved all the media outside of the FCP bundle.
- I also purged a bunch of old rendered files.
- I moved all the media and the FCP bundle to a larger Raid drive. It was a similar Raid before, but smaller, with only a few 100'sGB of free space left. Now I have several TBs of free space.
--- Update (May 9):
Alas... It's creeping back. Again I've been crippled by this error. Not sure why or when this happens. There is nothing in particular that I can pinpoint as the culprit.
If only I could use my Control + R in time, but I'm usually too late. Cringe, cringe.
--- Update (much later)
Someone is asking if I figured this out... I don't remember!...
Since then I swapped my MacPro 3,1 for a MacPro 5,1 and all is fine. I also upgraded to newer OsX (from Mavericks to Yosemite) and newer FCPX versions.
I believe upgrading FCPX to 10.1.2 and subsequent versions, and upgrading the OsX got me out of trouble on the MacPro 3,1: Yosemite=good, Mavericks = bad.
Another thing for sure is that I turned background rendering OFF in FCPX and that is now my default setting. This probably helped as well, or at least it sorts of became a non issue.
Let us know how it goes for you, and list your specs in the comments.
Thanks!
The background task hourglass is stuck in a 0% - 100% loop and nothing happens.
Up to now I had to restart each time this happens (several times a day) to get out of the dreaded loop.
For info, when force-quit Apple report says:
"Final Cut Pro[1385]: *** OpenGL error 0x0506 (invalid framebuffer operation) in function "GL_CHECK_CURRENT_ERROR"
This morning after getting stuck again, I clicked: Modify/ Render selection. That got FCPX out of stuck mode and to render normally again! No need to force-quit/restart!
So this might be a workaround until the problem gets fixed in future version. Make sure that something is selected in the timeline/project. Shortcut: Control + R
--- Update (March 20):
It does not always work unfortunately, if I react took late, I cannot get out of the loop.
The weird thing is that sometimes several hours pass before I get the dreaded loop. And then it happens a lot. After a while, it does not appear again. I can't figure a reason yet.
--- Update (April 23):
I've now worked several days and the dreaded loop has not showed up. ;) Same project(s).
What's different?
- I moved all the media outside of the FCP bundle.
- I also purged a bunch of old rendered files.
- I moved all the media and the FCP bundle to a larger Raid drive. It was a similar Raid before, but smaller, with only a few 100'sGB of free space left. Now I have several TBs of free space.
--- Update (May 9):
Alas... It's creeping back. Again I've been crippled by this error. Not sure why or when this happens. There is nothing in particular that I can pinpoint as the culprit.
If only I could use my Control + R in time, but I'm usually too late. Cringe, cringe.
--- Update (much later)
Someone is asking if I figured this out... I don't remember!...
Since then I swapped my MacPro 3,1 for a MacPro 5,1 and all is fine. I also upgraded to newer OsX (from Mavericks to Yosemite) and newer FCPX versions.
I believe upgrading FCPX to 10.1.2 and subsequent versions, and upgrading the OsX got me out of trouble on the MacPro 3,1: Yosemite=good, Mavericks = bad.
Another thing for sure is that I turned background rendering OFF in FCPX and that is now my default setting. This probably helped as well, or at least it sorts of became a non issue.
Let us know how it goes for you, and list your specs in the comments.
Thanks!
Subscribe to:
Posts (Atom)