Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Final Cut Pro X

I guess that as Apple has told the world about FCP 10 then (basic) questions can be asked....

1) Do you still need to (officially) transcode into Quicktime? or will it handle say DVCPro HD natively?
2) Is there upgrade pricing or does everyone pay $299 regardless
3) A video I saw had the presenter refer to FCP 10... if I'm using the latest which is 7 where did 8 & 9 go?
Cheers

HVXser

Message was edited by: hvxuser

17" i7 MacBookPro 8GB, Mac OS X (10.6.4), 7200 Hard Disk

Posted on Apr 13, 2011 3:28 AM

Reply
1,741 replies

Sep 30, 2011 3:33 AM in response to mikael - foolcolor

Hello


For your information I wrote an applescript app to send FCP X project to Adobe After Effects with support for most of the magnetic timeline features :


main and secondaries storylines, anchored clips, time effects, audio levels, audio roles, scale, position, anchor point, rotation, opacity (all with with keyframes), cross fades and can also conform to RED raw files instead of .mov (it will upscale everything to full resolution)... more features are added frequently...


get all the details here : http://foolcolor.net/foolcut


I am also working on more tools, like :


FCP X to FCP 7 audio only XML (so you can then export an OMF with audio levels from FCP 7)

FCP 7 bins and clips to FCP X events

FCP 7 sequences to FCP X


FCP X beeing a trackless editor some of those conversions are very complex to keep everything as close as possible to the original so I cannot give any date yet for the other products but foolcut_AE works today (check out the screencast and try the demo version version from the website)


Have a good day


Mikael, I think this work ur doing is fantastic, and I will try the AE script asap. On the the other needed items, FCP 7 to FCPX transfers, will they be priced individually or as a package? Cheers!

Oct 6, 2011 1:26 AM in response to ProMaxed

Another recent article (posted -like ProMaxed link- also to the FCX forum):


Apple's Richard Townhill discusses the latest FCP X release

A quote from that article I'd like to focus on:

"But can you import XMLs of FCP 7 projects into FCP X? No. “The formats are actually different, so this is a laws of physics sort of problem. The XML from FCP 7 describes just the project; the XML in 10.1 describes the event and the project (two sets of XML). Making those two work together with perfect fidelity is impossible because the effects stack in FCP X is new and improved at 64-bit and the Magnetic Timeline works much better than the old one.”


Basically, going from the old to the new would result in missing information.

This is handled all the time with heuristics and clever software making good guesses. Even if not perfect - I get, for instance, that Apple has abandoned support for old plugins and they would not carry over - Apple could still have translated the projects. The most important thing is the edit and organization. It still seems to me that Apple was not interested in customers who have old FCP projects to translate.
As to the magnetic timeline being better, I say "Why?"
Why is the magnetic timeline better? Because it fixes a problem I didn't have? Just the same way that FCX "fixes" the problem of potentially relinking to the wrong media - by not allowing relinking?
The open timeline is like a blank sheet of paper - flexible - and allows the user the freedom to create and organize as best suits them. The magnetic timeline is more restrictive - once again, to protect the user from themselves, regardless of their abilities.
The magnetic timeline seems basically a user interface representation of an internal programming organization that maintains the clip data in a parent/child arrangement. Touting this as "revolutionary" strikes me as a bit of making virtue of necessity...

Oct 6, 2011 7:50 AM in response to Patrick Sheffield

I'll go further... While the plugins are not compatible, their function most likely is.


Most of the effects people use in FCP projects are Apple's built in ones. Flip, 3-Way Color Corrector, De-Interlace, etc. They all have counterparts in FCX. All Apple needed to do was translate the name and convert any values. The interface in FCX's Color Board is different, but the function is the same as the 3 Way, for instance.


Not only that, but Apple is best suited to this translation, as they know the internals of both programs!


This is not the kind of thing best left to 3rd party developers and during the years Apple spent developing FCX, they could have assigned an engineer to write this translation, so I have to think they made a conscious decision not to. They had to have decided that the number of people they would anger and alienate were not worth that engineer's time.


I believe they were wrong.

Oct 19, 2011 5:17 PM in response to coocooforcocoapuffs

http://www.squarebox.co.uk/fcpxml.html


"Using CatDV as a translation tool, you can now transfer clips and sequences from your old Final Cut Pro 7 projects over to FCP X"


It looks like they updated their webpage on October 6th to include detailed instructions explaining how to do this despite inherent limitations:


"Currently, because of differences in how FCP 7 and FCP X describe clips and handle timelines, there are some limitations as to what data you can transfer over to Final Cut Pro X:

  • A basic "cuts only" sequence is moved across. Titles, transitions and other special effects or filters, including detailed handling of certain multi-channel audio files, are not fully supported and may need to be reapplied. Timing is preserved however.
  • Most regular clips that come from a single .mov or .mp4 movie file, as well as subclips, simple stills and audio clips, are copied across. Complex clips such as multiclips, sequences within sequences, P2 mxf files, or image sequences are not fully supported in most cases.
  • Clip name, media path, timecode, log notes, and markers are copied across, but other metadata (such as reel number, description, label, angle, marker category, and CatDV user-defined fields) is not supported in the .fcpxml file format at this time."

Oct 30, 2011 1:59 PM in response to hvxuser

Folks, before the last update my Canon 5D Mark II always were conected to Final Cut Pro X automatically once I opened the program. After the update that doesn't happen anymore...Can someone tell what's the problem here? Thanks in advance.

Dec 7, 2012 3:15 AM in response to Tom Wolsky

Can you really call Final Cut X a professional application? "Wow" it can now export a still frame in the latest version? There are still too many features missing from FCPX. It seems as if they are working backwards. Why not recode FCP7 rather than make a whole new application? Dual viewers are back again? I wounder when round tripping to Motion will return? I like Final Cut X, but it looks like Apple have spent too much time on consumer apps that are free like iTunes 11, which is dissapointing. Once again stripped of great functionality in place of asthetics. However, this is a good community.

Dec 8, 2012 12:38 PM in response to Macden

Macden...if you don't like it, don't use it. Plenty of other options out there, like Adobe Premiere Pro, which is so close to how FCP works people are calling it FCP 8. It has some oddness that is different and will take getting used to, but people are transitioning to that app fine.


Or, like me, they are going to Avid. But Avid is really best for broadcast editing work when you have mutliple editors and shared storage, or need offline/online cutting. REALLY good media management. Not the easiest to composite or blend footage. And Premiere allows you to edit formats natively, without transcoding.


Ignore **** like Black Sun. They are trolls.


<Edited By Host>

Final Cut Pro X

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.