-
One for the rumor mill :-)
Just came across this and thought I’d share fwiw:
https://www.macrumors.com/2010/09/30/final-cut-studio-update-scaled-back-and-delayed/
-
19 Replies
-
Cannot imagine how clunky a single interface for everything would be. How long would it take that application to load?
Personally I would have been shocked if Apple actually released an update to FCP in 2010. I was figuring early to mid 2011 all along as this really will be their make or break version. A lame version of FCP that doesn’t keep pace with all the tapeless integration that Adobe and Avid now do on board with no third party plug-ins using MXF is impossible to ignore.
The good news is that if Final Cut Studio 4 (or whatever it’s called) is not “awesome” it’s easy enough to replace the applications and convert entire facilities over to one of the other A’s pretty easily. Right now Apple is king of the hill in terms of user installed base. I have said that this next version will show us how serious Apple is to staying in the professional video industry.
Walter Biscardi, Jr.
Editor, Colorist, Director, Writer, Consultant, Author, Chef.
HD Post and Production
Biscardi Creative Media -
I’d invite an all in one. I was staring at and day dreaming about Smoke on the Mac today.
-
So let’s talk about some of the features that need to be in Final Cut Studio X to meet our expectations…
• Fix ALL gamma problems in QuickTime and FCS once and for all.
• ProRes 4:2:2:4
• Ability to use almost any codec with RT Extreme
• Real Time compositing and effects with 4:x:x:4 material
• RGB workflow @ >8bits, including 10 and 12 bit linear and log with RT Extreme
• More extreme RT Extreme
• Real Media Manager including a SAN integration piece. FCServer… not feeling it.
• Native support for MXF, as in no rewrapping to QT. If you can’t do it, license mxf4mac.
• Return the favor with RT support of DNxHD. It’s got 4:2:2:4
• Make all effects at least 10-bit capable and label those that are not.
• Fix the scaling artifacts
• True mixing of codecs and resolutions in the same timeline and keep it real time with high quality.
• Active frame rate conversion
• Since there will be bugs, it’s inevitable, how about a quicker turnaround for bug fixes and more tech notes for known issues. The head in the sand routine is getting old.
• Tiny chocolates for my pillow -
Incidentally, one of the hold ups, I have to imagine, is that QuickTime X is feature incomplete since all those resources have gone into iCrap. Perhaps that’s why we don’t have USB 3 or an eSATA port or two like the rest of the world.
-
[walter biscardi] “Cannot imagine how clunky a single interface for everything would be.”
Hi
But think about it the other way round – a single ‘application code’ for everything, with appropriately different interfaces for working on differing aspects of the timelined media.That is what Adobe have been aiming for – no ’round-tripping’ of anything ever, its all the same code, working on the same media, in the same place, but just the interface tools change as you switch work-mode…
Buried in the discussion for the MR article is Phil Hodgetts excellent summing up:
https://www.philiphodgetts.com/2010/09/what-should-apple-do-with-final-cut-pro/This is on Apples Web site – a Pro Apps senior interface designer post:
https://jobs.apple.com/index.ajs?BID=1&method=mExternal.showJob&RID=61607 -
[Paul Dickin] “Buried in the discussion for the MR article is Phil Hodgetts excellent summing up:
https://www.philiphodgetts.com/2010/09/what-should-apple-do-with-final-cut-p...”
Great article.
Everybody around should read it.
Very interesting what he say about the new Premier Pro:“Adobe seems to have worked around the problem by spinning off a 32 bit thread for QuickTime support so you lose that Mercury Engine goodness”.
Rafael
-
Unified interface doesn’t have to be clunky at all. Common timeline, common media pool (bins), open tabs or rooms as needed – Color-Motion-Soundtrack-DVD(Bluray)- I imagine a iOS APP Builder application may be in there too. Don’t care one bit about USB 3.
Tony Manolikakis
Rev13 Films -
[Jeff Bernstein] “• More extreme RT Extreme”
Heh heh. Nice one.
-
Jeff –
Along with those nice chocolates and the increased media support you are looking for, how about fixing some of the ridiculous bugs and limitations in FCP that still make me yearn for NLE’s I was using 10 years ago.
How about the ability to mute the top video track without destroying all your renders.
How about the ability to easily and quickly capture and automatically separate clips over time code breaks.
How about the ability to change the amplification of waveforms in the timeline so you can actually use them in soft audio passages.
How about a decent integrated character generator.
How about the ability to use multiple clips in one stream of a multi-clip sequence.
How about the basic ability to map every action to a keyboard command – as opposed to finding that some actions are mouse-click only.
How about intelligent rendering that recognizes when a change to the timeline requires a re-render or when it doesn’t. This alone would save me 30 minutes a day of unproductive time. But then again it allow me ample time to check out the cow so I guess it’s really a FCP “feature.”
Herb Sevush
Zebra Productions -
From the HardMac article the link in OP references:
“The idea of having a unified interface has been abandoned for the time being because of difficulties in reaching a satisfactory compromise among not only the various applications but above all between different development teams, those working on Shake and those working on Motion.”If the Motion team is arguing w/the empty desks formerly occupied by the Shake team (Shake was EOL’d in ’06) I think Apple has bigger problems than we thought. 😉
-Andrew
3.2GHz 8-core, FCP 6.0.4, 10.5.5
Blackmagic Multibridge Eclipse (6.8.1)
Reply to this Discussion! Login or Sign Up