Charlie Austin
Forum Replies Created
-
[David Powell] “I’m not sure which fixed the problem, but after running Onyx for a full cleaning, I also went inside the library and trashed all the render files manually. Seems to be working now.”
Was actually gonna suggest it was a corrupt source or generated file. Glad it seems fixed. I’d look into X-Wiper for doing this kind of stuff. Arctic whiteness Library Manager also works, But for me, it comes to a complete standstill when indexing Libraries, of which I have well over 100. X-Wiper is drag and drop, works great. 🙂
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Walter Soyka] “New Search Bins allow editors to build new bins automatically, based on metadata searches within a project, with results showing as aliases of the original project items.
An advanced Timeline Search makes it simple to find and select clips within a sequence based on specific criteria such as Clip Name or Marker comment.””
And everyone here wonders why Apple doesn’t announce features that are coming to FCP X. :-/
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Mitch Ives] “Jeez Charlie, how about the things that have already been discussed in this thread?
“As far as I can see, the only timeline related thing discussed is that the clip opacity bar is harder to get to than other NLE’s. The audio fade thing could maybe be reworked, but is really is a non-issue, it’s just the way audio components work. And any comparison to other NLE’s in really Apples to Oranges as none of them have embedded audio components. You can detach your audio and add fade effects to the connected audio clips just like any other NLE. If you keep the components embedded you work with them in, uh, the way they work. If you cut in MC you need to step into effects – which people who don’t like MC might consider a flaw – but it’s just the way it works right?
[Mitch Ives] “BTW, Charlie… who gets to decide when something crosses the threshold from Annoying to a Problem? It sounds like you might have given yourself that duty… :-)”
lol. Yes, I am the decider! Look, Like most everything here, I’m expressing my opinion. Just for laughs, I’m cutting spots for the same job in Pr and X the last week or so. Same source footage, music, SFX library, everything. Both have annoying aspects. Although… having Pr open in the background doesn’t do anything for me when I’m in X. But having X open in the background make cutting in Pr easier. It’s exponentially easier to locate shots in multiple feature reels and audition SFX etc in X, then, knowing where they are, pop to Pr and use them. Also, tracks are a PITA. According to me. The decider! 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Hans Douma] “Especially since the latest OS X update where it keeps verifying its origin, because it is not acquired via the App store. Apple don’t even recognize their own software anymore. When it eventually does start, it doesn’t play the clips in the timeline and/or any clip is misformed.”
If you didn’t get FCP X from the App store, your problems are not due to FCP X.
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Mitch Ives] “Apple forces you into the tedious 1990’s approach of using the Inspector to adjust things that we should be able to do on the timeline. If you had all the things Steve discussed then you could close the Inspector..”
huh? There are timeline operations that should be more efficient sure, what do you feel you can’t do? I use the inspector for things like text adjustments, effects controls, color controls etc. Things I’d need to open a panel/tab for in other NLE’s. The issue (IMO) with the inspector is that it’s always updating in real time which, depending on your project, sometimes bogs down. I’d imagine Apple is aware of this, and in practice it’s more of an annoyance than a “problem”. There are plenty of annoying things in Pr and MC as well. FCP 7 is, of course, perfect. 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Helmut Kobler] “I’ll try with it closed but that’s a horrible “solution” since I use the inspector all the time.”
I agree, If you do notice a difference, please send feedback to Apple. Honestly, CMD-4 is my most used keystroke 🙂
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Dennis Radeke] “Well, this is certainly a very interesting list.”
How so?
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Helmut Kobler] “but in general, the interface is not spry.”
This is annoying, but were you cutting with the inspector open? I find that keeping it closed makes X run like butter. Open, not so much. Hope they sort this out…
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[tony west] “He’s a much better X-man than me but I would never use the route he used to accomplish that.”
Me either. He’s basically saying you can’t put a crossfade effect on embedded audio, which there’s really no reason to do. Actually, there’s an Alex 4d audio only fade transition out there somewhere for anyone who wants it. https://blog.alex4d.com/2011/07/11/fcpx-transition-sound-only/ He reworked the fade effect so it doesn’t do anything to the video…
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[John Davidson] “I would like a preference check box to automatically apply broadcast safe limits on all exports”
It’d be nice if Compressor had a Broadcast Safe filter available. Does it?
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~