-
Remaining enhancements
-
That’s a good list.
I would add:
Read embedded “Reel” in QT files. It’s in the General Info view for pete’s sake!
The ability to export metadata in the xml via whatever is included in the General Info View or new XML View.
A preference that will direct Render files somewhere other than the Project folder.
John
-
- ganging
- colour wheels
- copy paste effects that isnt useless
- avcintra MXF export and metadata exports for UK tapeless delivery
- template driven tapeless delivery e.g. clocks through templates
- outputs for M&E that work and more control over audio mixing
- Midi controllers
- hue curves
- on screen feedback for keyboard based trimming like mentioned above
- noise removal
- metadata driven auto colour correction and audio mixing/cleanup
- decent auto colour correction that can be modified
- storyboard editing like imovie (its got something that has a lot of promise that should be available e.g. metadata driven editing)
- subtitling workflow from STL files and improvements
- all fields searchable in the smart collections e.g. log notes
- metadata mapping from tapeless formats
- event metadata templates/stat points
- RED camera support
- decent tracker or support for mochapro
- default audio tracks as stereo not surround
- default keep in/out in event browser, not the dumb loose my in outs
- some more of the useful community filters e.g. FCP.co ones incorporated as core
not a lot to ask
-
I doubt we will see OMF directly in FCPX ever again. In the article previously posted by the 7 Editors take a look at FCPX…OMF licensing is owned by AVID. This would drive up the price of the software. I honestly think the entire exercise of FCPX was to purge all the 3rd party licensing built into years of Final Cut Studio iterations so that Apple can own and manage the base software. However, I am sure, someone out there will develop an OMF solution through the App Store that will deal with the licensing separately (in addition to many of our transcoding/exporting quirks we deal with in this medium.
-
[Brad Davis] “I doubt we will see OMF directly in FCPX ever again. In the article previously posted by the 7 Editors take a look at FCPX…OMF licensing is owned by AVID.”
You may well be right – but if the makers of the forthcoming XtoPro can afford the licence how is it that Apple cannot?
Possibly a bit cash-strapped, would be my guess …
Simon Ubsdell
Director/Editor/Writer
http://www.tokyo-uk.com -
My guess…They want to keep the price of the App at $300 and if you want that level of functionality you can buy it from someone else and they pay the licensing fees. Hence why the Pro Tools app is $99
-
[Brad Davis] “if you want that level of functionality you can buy it from someone else”
And if you don’t want to have that level of functionality you’re just the kind of editor that Apple has been aiming for all along.
Frankly I am astonished at how few of the posters on this forum (virtually none, apart from Michael Gissing that I know of) seem to have the slightest interest in getting their audio out of their NLE and into ProTools (or other pro-DAW of your choice) to be able to mix their final audio with the right tools, in the right room with the right monitoring.
Everything I do needs this kind of mixing and I don’t have the option of not doing it this way. Think yourself lucky if for you this is just an unnecessary luxury that you can happily do without.
Unless and until Apple provide this functionality as a built-in feature that works with rock-solid reliability, FCPX will remain just an amusing toy for that apparently diminishing sector of the market that has to deliver high-end audio with their pictures.
Simon Ubsdell
Director/Editor/Writer
http://www.tokyo-uk.com -
To be fair Simon, Jeremy Garchow and quite a few others have said OMF export needs to be a priority and is holding back them being able to use FCPX on much of their paid work.
-
What is also likely is that DAW manufacturers will eventually respond to FCPs XML and work out how to directly import from XML. Fairlight has had XML import from FCP7 for a while.
Of course in audio and picture post we need a system that can create a properly Media Managed version with just the shots plus handles and a stable robust XML. I think it may take some time for any sort of robust standard with FCPX XML, as it is also alpha development in beta software. How’s FCPX Media Management?
-
Fair enough, Michael – I definitely overstated, apologies.
I agree that Jeremy and one or two others have expressed a small but not especially vocal reservation about this.
But I don’t think the list is as long as all that.
And quite a few seem to be happy with the notion of some potentially unreliable third party solution, which may be here today and gone tomorrow, and may not even work reliably today.
For me FCPX doesn’t even begin to become an option until this is emphatically and unequivocally resolved – and I don’t see any sign of that happening yet.
XtoPro may change that, but then again anything is possible and everything is uncertain …
Simon Ubsdell
Director/Editor/Writer
http://www.tokyo-uk.com -
[Michael Gissing] “I think it may take some time for any sort of robust standard with FCPX XML, as it is also alpha development in beta software.”
I think this is at the root of the problem right now. I think there are going to be many teething problems to be got through with FCPXML before it all settles down enough to get us reliable audio export of the kind we have come to expect.
Simon Ubsdell
Director/Editor/Writer
http://www.tokyo-uk.com
Reply to this Discussion! Login or Sign Up