“- Real 10bit support. I have doubts that FCP renders all effects in 10-bits and some of them are just plain buggy in 10bit.”
They could do like Premiere 2 and support that via support for 16 bits AE compatible plugins (although I have not tested). So like Combustion which supports 10,12 and 16 and bump all to 16 bit for the effect. And before they put their head in the sand (never taking anything for granted here) – support for AE plugins on MacIntel. I stopped dreaming about improved support in that area and the Motion AE support is not of much help sometimes. There should be just two effects model supported, AE for CPU and FXPlugs for real-time effects and support made complete and any other ways to make effects deprecated so as to not dilute efforts.
—-
“-Better keyframes: Ability to select, move and copy multiple keyframes. Better keyframe window (why not a large animation graph as a new tab in the timeline or browser window?)”
—-
Add ability to animate menus and checkbox booleans and possibility for an effect to run through a sequence (analyze) and write values as key-frames.
—-
“Going to Cinematool is a huge loss of time and a very bad workflow.”
Maybe to embed that would allow then one to maintain different FPS (and hopefully even resolutions) gracefully in a timeline.
—-
Intelligent (not hidden) image sequences support.
—-
Would probably be cool as the age where everyone has quad processors and huge amounts of memory, it will allow things like background processing of a section of a timeline on a part of the sequence while continuing editing. Of course that would work only with CPU effects.