-
Anybody HAPPY?
-
[Simon Ubsdell] “I’ve actually found the dancing dot to be a nice feature – apart from the dancing part. “
Me too. I jsut want more! 😉 Like option up or down arrow, changes the layer to which the ball dances.
[Simon Ubsdell] “It’s odd that the whole flatter UI aesthetic hasn’t yet permeated through to getting rid of this type of silly animation chrome.”
BUt at least the corners of the thumbnails are all squared off?
-
[Jeremy Garchow] “[Simon Ubsdell] “I’ve actually found the dancing dot to be a nice feature – apart from the dancing part. ”
Me too. I jsut want more! 😉 Like option up or down arrow, changes the layer to which the ball dances.”
Yes, I can see that being a really useful thing – feedback time.
[Jeremy Garchow] “[Simon Ubsdell] “It’s odd that the whole flatter UI aesthetic hasn’t yet permeated through to getting rid of this type of silly animation chrome.”
BUt at least the corners of the thumbnails are all squared off?”
Mostly squared off but they just couldn’t resist some residual roundness 😉 I can just imagine the battles over that one …
Simon Ubsdell
http://www.tokyo-uk.com -
[Jeremy Garchow] “[Simon Ubsdell] “It’s odd that the whole flatter UI aesthetic hasn’t yet permeated through to getting rid of this type of silly animation chrome.”
BUt at least the corners of the thumbnails are all squared off?”
Yay! OK, here’s my guess. A lot of the stuff editors need, was impossible to do with the old P/E split. So they spent all this time figuring out how to correct that “problem”. I also think that they needed stuff that’s in Mavericks to make it happen. Or maybe they’re just lazy and work really slowly. Whatever.
But, it’s done. Now the fun can begin! i hope…..
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Simon Ubsdell] “the battles over that one ..”
[Enter a clever Monty Python skit here.]
-
Other than the missing “Send To Motion” option and color board I am rather well pleased. Glad to see a library has been added. Best part, and a surprise, was the update was free! Perhaps the next few updates will bring the village people the tools they need.
-
Yeah I don’t see any improvements in actual editing – other than performance – Apple still wants us to edit their “newer, better” way.
I still believe it’s all a mistake – all we needed was a 64bit update to 7 with some of the sexy charcoalness and I’d be happy. Obviously that’s never gonna happen.
I do think FCPX will continue to be a winner with younger editors who “don’t know any better” and the old farts like myself will keep using NLE’s that make sense to us until we retire or move on.
Lance Bachelder
Writer, Editor, Director
Downtown Long Beach, California
https://www.imdb.com/name/nm1680680/?ref_=fn_al_nm_1 -
[Lance Bachelder] “Yeah I don’t see any improvements in actual editing – other than performance “
Well, one big editing improvement for me was fixing multicam so you could detach audio and/or cut just video or audio onto a sequence. That’s huge if you use multicam. Of course, like with the library revamp, it’s hard to get really enthused when they just fix something that was poorly designed to begin with.
Now I hope they turn attention to rethinking the browser. I need multiple windows, or saved states, or at a bare minimum a back button. I spend way too much time browsing, and flipping views around.
-
Like Oliver said, this release is +1 for engineers over editors. Being an engineer I agree. The first step to getting FCPX into a facility is winning over the engineers who have to integrate the damn thing into existing workflows. I think Apple thought FCPX would meander itself into facilities like FCP7 did in Avid environments. The tables are turned now however with a less flexible system (FCPX) trying to gain a foothold over a very flexible system (FCP7).
Apple made big foundational changes. Events have essentially been scrapped and relegated to simple folder like organization. San locations are gone too, so no more locked up media. The multiple “plates in the air” model has been scrapped and unified into a single library. The edges are starting so round meaning less pounding into that round hole.
It was mentioned how Apple could not foresee the dead end their initial course was leading to. Remember, this is the same company that presumably had meetings discussing the plan to not have FCPX open FCP7 projects and at the same time to kill FCP7. How a group of intelligent people could all agree to this is beyond comprehension.
In meetings with Apple I expressed that I saw no way of integrating FCPX in our shared environment and that I had no suggestions on how to tweak the existing Event based system. Apparently neither did Apple, and to their credit scrapped the foundation and built one that has a future. For that reason alone I am happy about the release and hopefully the people at Apple who knew better all along are now laughing at the emperor cowering naked in a corner.
John
-
[Tim Wilson] “Far be it from me to start a thread that might lead to some positive energy LOL but I’m curious. Is anybody looking at this and saying, “Wow, what a great update,” or “This has exactly the features I was waiting for,” or, “This update makes me feel better about myself” — anything like that?”
Libraries are a big improvement for us. We have several RAID systems with lots of projects on them. All elements related to a project (which can include consolidated footage used by Resolve, reel renders out of Resolve, numerous versions of audio mixes, final master ProRes files, DPX sequences, DCPs, etc.) are stored in a folder for that project. Previously, however, we couldn’t store FCP X events/projects in those folders. Libraries let us do that handily — just create one library per project. We might even start actually letting FCP X import the media files (instead of linking to external files) now that this is the case, which will help with file system clutter.
Custom frame sizes are also great. We’re working on feature content, which means we often need ‘cinema’ resolutions — primarily 2048×858 and 1998×1080 (DCI scope and flat). It’s a little odd that these aren’t just standard choices (since DCI ‘full’ — 2048×1080 is, but you essentially never actually use that for anything), but now I can just dial them in.
Workflow wise, the three things I’d still really like to see are built-in LUT support, support for image sequence formats (DPX, TIFF, Cinema DNG, maybe Arri Raw while they’re at it), and batch exporting. At that point FCP X would be a fairly serious online editing tool.
—
Digital Workflow/Colorist, Nice Dissolve.You should follow me on Twitter here. Or read our blog.
-
[Chris Kenny] “At that point FCP X would be a fairly serious online editing tool.”
shhh
Reply to this Discussion! Login or Sign Up