-
FCP X Summit: new features/news
-
[Andy Field] “it was a joke”
I don’t miss much
But you can back-paddle if you want to.
-
[Scott Witthaus] “Seriously though, it will be interesting to test.”
Unless Apple has fixed this issue in iMovie iOS, then this was the issue I ran into when working on my iPad Pro review:
“For editors, the built in option is iMovie. It is possible to edit external material, if you brought it in via the card reader, DropBox, iCloud Drive, or by syncing with your regular computer. (Apple’s suggested transfer path is via AirDrop.) Once you’ve edited your piece, you can move the project file from iOS iMovie to iMovie on your computer using iCloud Drive and then import that project into Final Cut Pro X. In my tests, the media was embedded into the project and none of the original timecode or file names were maintained. Frame rates were also changed from 29.97fps to 30.0fps. Clearly if you intend to use this path, it’s best for video originated on the iPad itself.”
It will be interesting to revisit this with FCPX 10.4, but I suspect we won’t see any change related to iMovie.
– Oliver
Oliver Peters – oliverpeters.com
-
Apple buying Tim Dashwoods plug-ins was a key thing that indicates their view of how important 360 and VR creation could be for content producers. He had figured out how to do something that even oculus refused to support on their own website and proved that Apple hardware was fast enough to be used for 360/VR. This is why having native support for VR is better than plugins – because it requires a complete understanding between hardware and software producers which hasn’t been there before now.
If fcpx is going to natively support the HTC Vive, this indicates a major shift because it means that htc will have to produce a Mac driver – even if this is only supported by the new iMac pro.
Apple are damned if they do and damned if the don’t with VR – it’s excellent they have added the native support and the non specific release date to me could indicate a timed release with the iMac pro and official drivers from htc/Apple.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
You hit the nail right on the head, Tom. And not only for the 360/VR part of the game.
The new VR tools in FCP X are way more than just the Dashwood plug-ins being integrated in the NLE interface. Alex Gollner, who has quite some experience with VR and is a good friend of Tim Dashwood, says that “the next version of Final Cut Pro X will be the first professional editing tool that inherently understands spherical video.” And he has explained this in more detail here: https://medium.com/@alex4d/apple-to-introduce-next-level-professional-vr-video-tools-in-final-cut-pro-x-and-motion-5-855226168aeb
The same goes for the Color update. It’s way more than just color wheels being added to the toolset. IMO the color wheels are actually the least important feature in this update (although they do look pretty neat). It’s about being able to add very powerful corrections without affecting realtime performance, even when working with high resolution media on standard hardware. That is something that cannot be achieved with the current third-party color plugins for FCP X, and it’s something that other grading and editing applications still struggle with. So it’s a very welcome update that goes far beyond “features”.
– Ronny
-
Oops, I notice that the link to Alex’s article has been scrambled. This is the correct link:
– Ronny
-
This is exactly the case. For the short film we did I couldn’t figure out when or why it behaved like that.
– Some clips had the entire source clip in a compound clip with source clip TC, with just the given section in the active timeline. These I could de-compose but they still cause head-aches.
– Some clips had the entire source clip in a compound in another compound with reset TC. These where a mess to deal with.
When you try to media manage a project like this Resolve simply takes EVERYTHING since, technically, every bit of media is used (given only in un-nessasy compound clips).
I’ve never seen this odd behaviour from any other editor but I’ve seen it from the last 3 FCPX shot shows cut by 3 different editors. Likely a FCPX / Resolve or FCPXML “feature” / “bug”. Edits do translate very well BUT this causes serious head-aches for a lot of workflows.
-
[Bill Davis] “Reference clips buried within reference clips is a sign to me that an editor doesn’t really understand X very well – and are maybe trying to re-capture “nesting” behaviors they relied on in other software approaches. “
I ran into this issue with a short edited by the Director/Writer.
Since it was a short, I had to try and break all the clips apart.
Resolve wasn’t having a hard time with the CC but I can’t stand working on messy edits.
I know if I edited I would make sure its all in the Primary and no anomalies.
Now I wish FCPX had the old legacy jooin/merge clips option.
I know this can be fixed in Resolve but would like to have it back in FCPX. -
[Bill Davis] “Reference clips buried within reference clips is a sign to me that an editor doesn’t really understand X very well – and are maybe trying to re-capture “nesting” behaviors they relied on in other software approaches.”
Exactly. That’s when you go and kick the editor in the shin and tell them to get their sh** together before coming to finish.
Scott Witthaus
Owner, 1708 Inc./Editorial
Managing Partner, Low Country Creative LLC
Professor, VCU Brandcenter -
We must do it the Apple way…..and no other!
Andy Field
FieldVision Productions
N. Bethesda, Maryland 20852 -
[Scott Witthaus] “That’s when you go and kick the editor in the shin and tell them to get their sh** together before coming to finish.”
To be fair to some editors they don’t realise compounding happens when any clip in X has an effect applied and is then sent to Resolve as an xml. I had a feature doc with heaps of compounds after the editor assured me he had gone through and decomposed all compounds but there is a translate issue with fcpxml to Resolve that compounds clips that aren’t. At least in Resolve it is possible to select multiple clips to decompose unless they have any speed changes. Apart from this annoying behaviour, X to Resolve via fcpxml is pretty robust.
Reply to this Discussion! Login or Sign Up