Charlie Austin
Forum Replies Created
-
[Herb Sevush] “I figure if the two most significant guys in the FCPX project (that’s Randy and Steve, not Tim and Bill) were discussing how botched up the release was, then at least that small part of the never ending argument can be put to rest.”
I think, privately, more people up there than just those 2 feel the same way.
[Herb Sevush] ” I’m waiting on client notes – what’s your excuse?”
lol… the same actually.
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~I still need to play Track Tetris sometimes. An old game that you can never win~
~\”The function you just attempted is not yet implemented\”~ -
[Michael Hancock] “For Adobe. They just released their a big update to CC2015”
Updated this AM and, as I don’t use proxies in (Pr or X), it’s… exactly the same. Like an old shoe. Comfortable.
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~I still need to play Track Tetris sometimes. An old game that you can never win~
~\”The function you just attempted is not yet implemented\”~ -
[Herb Sevush] “So apparently the inventor of FCPX and the big Apple himself both thought the release was badly handled — but then what would they know about it.”
Our fearless moderator here has a different opinion… too lazy to find the thread. Also… who cares. 😉
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~I still need to play Track Tetris sometimes. An old game that you can never win~
~\”The function you just attempted is not yet implemented\”~ -
[Rick Lang] “Charlie, do you know if that “Aperture formerly known as a Pro App” is supported in Sierra? “
No idea… I just reposted that pic. 🙂 There has been some discussion though, that while the QTKit Headers are removed, meaning you can’t compile new apps, the frameworks are still there, so older apps should still run. If that pic is real, seems like that’s the case.
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~I still need to play Track Tetris sometimes. An old game that you can never win~
~\”The function you just attempted is not yet implemented\”~ -
[Oliver Peters] “It’s been too long, but I remembered being able to save more than 2 layouts. Of course, maybe I just did these manually.
“Nope, you’re right… There were only 2 “default” layouts you could set and use a 2 key keystroke, but you could (wait, I mean you still can! Lol) make and save as many others as you want. Totally forgot about that.
Point is, they would open in the original state you had saved them, and the saved state would be the same even if you moved things around when in a particular layout…
Pr has it half right, and X should get on board and do it all the way right. FCP 7, still the gold standard! Lol 😉
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~I still need to play Track Tetris sometimes. An old game that you can never win~
~\”The function you just attempted is not yet implemented\”~ -
[Oliver Peters] ” I have a number of saved custom workspace layout when I work in Premiere.
“I do like that, but it has the same annoying issue as X in that if you’re in a workspace, and resize a window/panel, then that becomes the workspace layout. There’s no way to just snap to your original. You can (and I do) have a bunch of different workspaces, but to save every possible layout that I might want is, to me, unnecessarily complicated. Let me save a layout, and let me get back to that even if I change the layout while I’m in the layout. Like FCP 7. Sure, there were only 2, but the original saved state was always available, and only changed if you re-saved it.
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~I still need to play Track Tetris sometimes. An old game that you can never win~
~\”The function you just attempted is not yet implemented\”~ -
[Oliver Peters] “Well, you can sort of do this now.
“True, in a way it’s like Pr workspaces a la carte 🙂 I just wish that I could resize the windows… Tiny timeline, giant viewer, small effects browser, whatever, then hit a key combo and have it snap back to the original saved layout like FCP 7. (This is true in both X and Pr btw) The built in default layout isn’t what I want.
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~I still need to play Track Tetris sometimes. An old game that you can never win~
~\”The function you just attempted is not yet implemented\”~ -
[Craig Alan] “to toggle between specific layouts was ergonomically vital. FCP X needs to add this feature. custom layouts which you can toggle between. For audio for color correction for cropping for rough cuts etc etc.”
Totally agree. I resize/rearrange the relative size of the windows depending on what I’m doing. Be nice to save and recall the layouts. Pr works well-ish here with workspaces. But… you run into the same issue as in X if you rearrange windows/panels while in a layout. You still need to un-arrange stuff to get back to your “base” workspace state. As you noted, FCP 7 would save a recallable “base” state. We need that back 🙂
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~I still need to play Track Tetris sometimes. An old game that you can never win~
~\”The function you just attempted is not yet implemented\”~ -
[Craig Alan] “If you do all the heavy lifting in the browser and then just transfer the sequence to the timeline wholesale then its just a giant organized spreadsheet of media.”
FWIW, and contrary to some opinions here, not everybody does all the heavy lifting in the browser. Personally I do just enough to let the browser do the heavy lifting for me. (Smart collections/Roles etc) To me, that is the major benefit of FCP X. And not just in the Browser, but everywhere in the app. Some tend to obsess about the metadata, but to me, that’s only a part of it. How I interact with the app, what it can do for me, or make doing much easier for me, is the big deal.
Other NLE’s can copy all the features they want, but unless they copy how X works -which they can’t because mean old Apple has it patented – X will always stand out. In a good way for me, YMMV 😉
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~I still need to play Track Tetris sometimes. An old game that you can never win~
~\”The function you just attempted is not yet implemented\”~ -
[Andrew Kimery] “Maybe when the new, nMP come out Apple will offer the new GPUs will be backwards compatible with the 2013 nMP and Apple will offer them as stand alone purchase for those that want to upgrade, but that just seems very unlike Apple these days.
It all depends on the performance hit of course, but I’d bet most people would go with an external solution where they could pick their card vs paying a premium for Apple’s custom designed, AMD-based GPUs that only work in a nMP.”
This may offer a clue…. https://www.macvidcards.com/blog/macos-sierra-had-native-egpu-support
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~I still need to play Track Tetris sometimes. An old game that you can never win~
~\”The function you just attempted is not yet implemented\”~
