Sunday, June 26, 2011
Dvice has an article on Final Cut Pro X
Dvice has an article titled "Final Cut Pro X: Apple's biggest mistake in years?" which you can read here.
Randy Ubillos Emails about FCPX
There's a lengthy thread here with all manners of comments after Randy Ubillos apparently returned an emailed question about FCPX.
Josh Mellicker talks FCPX
Josh Mellicker has a quick write up of his thoughts and history of FCPX here.
Friday, June 24, 2011
How To Run Final Cut Pro X on Non Open CL Capable Cards
Hardmac has an article up describing how someone discovered that, while slow, FCPX and Motion 5 can run on a Mac without a video card that supports Open CL.
"Yesterday I was unable to install Final Cut Pro X on my Dual-Core Mac Pro Intel Xeon rev. 1.1 (from September 2006) because the graphics card is not compatible with OpenCL. I created a session with my name on a friend's recent MacBook Pro and bought it with my iTunes account to test it on his computer and buy it on mine after would have changed the graphics card.
Today I put the MacBook Pro in target mode to transfer some video files.
Then, from my Mac Pro, opened the Application folder of the MacBook Pro and I was able to launch the Application!
I then copied it in the application folder of my Mac Pro and tried to launch it again, it worked!
I went to the software update menu and the other softwares were installed!
"Yesterday I was unable to install Final Cut Pro X on my Dual-Core Mac Pro Intel Xeon rev. 1.1 (from September 2006) because the graphics card is not compatible with OpenCL. I created a session with my name on a friend's recent MacBook Pro and bought it with my iTunes account to test it on his computer and buy it on mine after would have changed the graphics card.
Today I put the MacBook Pro in target mode to transfer some video files.
Then, from my Mac Pro, opened the Application folder of the MacBook Pro and I was able to launch the Application!
I then copied it in the application folder of my Mac Pro and tried to launch it again, it worked!
I went to the software update menu and the other softwares were installed!
For Motion, a 10 seconds animation is read in 23 seconds in Motion 5 on the Mac Pro.
Graphics cards are important, but since I am not a professional, it is plenty enough for me. I understand that Apple didn't want that lower performances with older hardware would be officially possible.
On the MacBook pro 5.2 (Intel Core 2 Duo 2.66 GHz), the animation is read in real time, 10 seconds."
I'm unure of the complete legality of this but it's pretty interesting. It would likely be too slow to be of any real use though in real-world editing.
Apple has a support document here which lists cards that do support Open CL.
Graphics cards are important, but since I am not a professional, it is plenty enough for me. I understand that Apple didn't want that lower performances with older hardware would be officially possible.
On the MacBook pro 5.2 (Intel Core 2 Duo 2.66 GHz), the animation is read in real time, 10 seconds."
I'm unure of the complete legality of this but it's pretty interesting. It would likely be too slow to be of any real use though in real-world editing.
Apple has a support document here which lists cards that do support Open CL.
The Clip's Master Clip Is Not Present - Error
FCP has a long standing bug where when you have the playhead in the Timeline over a clip and hit SHIFT + F for Reveal Master Clip, you'll inexplicably see this:
Restarting FCP will not help.
Reconnecting the clip will not help.
Trashing prefs hasn't helped me in this case.
Bizarrely, the clip will be fully visible in your Browser and/or Bin yet FCP will simply not be able to find it. It may be able to find other clips in the Timeline that reside in the same Bin as the errant clip, though.
I have no solution but it's an irritating, frustrating bug.
See, with the Timeline in the foreground and placing the playhead over a clip and tapping The F Key will perform a Matchframe where the frame -and Master Clip- that the playhead is over will appear in the Viewer.
But, hitting SHIFT + F with the Timeline in the foreground and placing the playhead over a clip and tapping F will perform a Reveal Master Clip; only sometimes it will just stop working. I have no idea why.
A workaround this to find a Master Clip and have it load into the Viewer is, like I mentioned, just place the playhead over the clip, make sure the Timeline is in the foreground (active) and tap the F key. You won't see the clip in the Bin or Browser but you'll be able to scrub around to see what else the clip holds footage-wise.
It's an incomplete workaround however especially if you need to see the following and preceding clips around the clip you're interested in. You'll likely find yourself doing this a lot while cutting a documentary and know that the footage is listed chronologically; a Reveal Master Clip would show you where the clip rests in accordance to the order the clips were shot in.
Another quirk is that if you do hit OK to "add a master clip to the browser" it'll do just that; and it'll find it if you load that into the Timeline (or Viewer, Reveal Master Clip works if the Viewer is the active window as well) and perform a Reveal Master Clip. Frustrating.
So there is a solution if you're willing to add a master clip to the browser (at root level) for every clip that suffers from this bug. But there's no guarantee that it won't randomly happen again. In fact, if you do add a master clip to the browser, place some of it in the Timeline, then for fun delete the newly created master clip from the Browser, FCP will toss up the Master Clip Not Present error.
Reconnecting the clip will not help.
Trashing prefs hasn't helped me in this case.
Bizarrely, the clip will be fully visible in your Browser and/or Bin yet FCP will simply not be able to find it. It may be able to find other clips in the Timeline that reside in the same Bin as the errant clip, though.
I have no solution but it's an irritating, frustrating bug.
See, with the Timeline in the foreground and placing the playhead over a clip and tapping The F Key will perform a Matchframe where the frame -and Master Clip- that the playhead is over will appear in the Viewer.
But, hitting SHIFT + F with the Timeline in the foreground and placing the playhead over a clip and tapping F will perform a Reveal Master Clip; only sometimes it will just stop working. I have no idea why.
A workaround this to find a Master Clip and have it load into the Viewer is, like I mentioned, just place the playhead over the clip, make sure the Timeline is in the foreground (active) and tap the F key. You won't see the clip in the Bin or Browser but you'll be able to scrub around to see what else the clip holds footage-wise.
It's an incomplete workaround however especially if you need to see the following and preceding clips around the clip you're interested in. You'll likely find yourself doing this a lot while cutting a documentary and know that the footage is listed chronologically; a Reveal Master Clip would show you where the clip rests in accordance to the order the clips were shot in.
Another quirk is that if you do hit OK to "add a master clip to the browser" it'll do just that; and it'll find it if you load that into the Timeline (or Viewer, Reveal Master Clip works if the Viewer is the active window as well) and perform a Reveal Master Clip. Frustrating.
So there is a solution if you're willing to add a master clip to the browser (at root level) for every clip that suffers from this bug. But there's no guarantee that it won't randomly happen again. In fact, if you do add a master clip to the browser, place some of it in the Timeline, then for fun delete the newly created master clip from the Browser, FCP will toss up the Master Clip Not Present error.
Wednesday, June 22, 2011
RIP Final Cut Server & Final Cut Express
Apparently Apple has killed off Final Cut Server and Final Cut Express according to Appleinsider.
What Final Cut Pro X Can't Do
I'm keeping a list as I run across things. Don't expect this to be complete, always accurate or exhaustively detailed.
Here we go: (this is for the dot zero release, btw and keep in mind I haven't played with FCPX very much yet)
1. You cannot currently import FCP6/7 projects into FCPX (see #4)
2. There is no Multiclip/Multicam.
3. Many plug-ins currently do not work.
4. Currently there is no XML Import or Export.
5. Currently there is no native OMF Export or Export to Logic.
6. Doesn't currently work natively with R3D or XDCAM (they need to be re-wrapped first).
An update has already addressed this somewhat.
7. There are no longer distinct Canvas and Viewer windows.
8. You cannot set In and Out points for tape capture nor (AFAIK) is there a batch tape capture ability.
9. You cannot "Save As" to duplicate a project (at least not that easily).
10. Apparently you can't Print (output) to tape, anymore.
11. Currently there is no support for EDL Import or Export.
12. You can't easily open two projects at once and drag media, sequences or custom filters between them.
13. Apparently lacks support for HDMI Input and Output
14. Apparently lacks support for SDI Input and Output
15. Not compatible with many, if any 3rd party video (capture?) cards
16. Timeline seems to always start at 00:00:00
17. Can you keyframe effects? I can't find it.
Here we go: (this is for the dot zero release, btw and keep in mind I haven't played with FCPX very much yet)
1. You cannot currently import FCP6/7 projects into FCPX (see #4)
2. There is no Multiclip/Multicam.
3. Many plug-ins currently do not work.
4. Currently there is no XML Import or Export.
5. Currently there is no native OMF Export or Export to Logic.
6. Doesn't currently work natively with R3D or XDCAM (they need to be re-wrapped first).
An update has already addressed this somewhat.
7. There are no longer distinct Canvas and Viewer windows.
8. You cannot set In and Out points for tape capture nor (AFAIK) is there a batch tape capture ability.
9. You cannot "Save As" to duplicate a project (at least not that easily).
10. Apparently you can't Print (output) to tape, anymore.
11. Currently there is no support for EDL Import or Export.
12. You can't easily open two projects at once and drag media, sequences or custom filters between them.
13. Apparently lacks support for HDMI Input and Output
14. Apparently lacks support for SDI Input and Output
15. Not compatible with many, if any 3rd party video (capture?) cards
16. Timeline seems to always start at 00:00:00
17. Can you keyframe effects? I can't find it.
Apple vs. Final Cut Pro X User's Reviews
There's been so much backlash against the new version of FCP (FCPX) that Apple may have removed not just some but as of this post, all or nearly all reviews on the App Store (not to be confused with Amazon's Appstore, btw).
They're back up as of now.
9to5 has a post about it here.
Daring Fireball has more info about FCPX's reception in general here.
Arstechnica has some more reactions and comments from Apple on FCPX here.
Appleinsider has an article on reactions to FCPX here.
They're back up as of now.
9to5 has a post about it here.
Daring Fireball has more info about FCPX's reception in general here.
Arstechnica has some more reactions and comments from Apple on FCPX here.
Appleinsider has an article on reactions to FCPX here.
Subscribe to:
Posts (Atom)
Posts
