Charlie Austin
Forum Replies Created
-
Charlie Austin
November 11, 2014 at 3:43 pm in reply to: Why new final cut X is so RESTRICTIVE with connected clips? I DO NOT SEE ANY BENEFIT[Gary Huff] “7. The FCPX timeline may be frustrating, at times even painful, but no more painful that jamming a fork into an AC outlet (try it now)”
AC!? phi it’s only 110 volts, not painful at all! 🙂
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Charlie Austin
November 11, 2014 at 12:12 am in reply to: Why new final cut X is so RESTRICTIVE with connected clips? I DO NOT SEE ANY BENEFIT[Andy Neil] “Standard Click-bait.
10 REASONS WHY YOU SHOULD LOVE THE MAGNETIC TIMELINE. NUMBER 7 WILL SHOCK YOU!!!
“Crap! Why didn’t I think of that?!
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Charlie Austin
November 11, 2014 at 12:08 am in reply to: Why new final cut X is so RESTRICTIVE with connected clips? I DO NOT SEE ANY BENEFITHow timely… Some hack just had an article on this topic posted on the cow. 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
No help, but you’re not alone… https://forums.creativecow.net/readpost/3/960245
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Charlie Austin
November 9, 2014 at 8:54 am in reply to: Careful now: Premiere saves all your project info in the meta data of your exported published files[Herbert van der wegen] “Also, I discovered that Premiere amends the meta data of any file you import into Premiere. Not such a big deal”
It actually can be big deal becomes sometimes, when you’ve imported a file from a NAS share, modifying the original file on the disk can cause the file to become corrupted. This isn’t a Pr issue per se, I’ve seen it happen with other NLE’s, but they at least warn you that you’re about to modify an original file. Also, the fact that this behavior is enabled by default is maybe not the best choice. Just something to be aware of.
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Jeremy Garchow] “You’d have six mono outputs with the appropriate Roles (left, right, center, so forth), and then one stereo output that has all Roles selected.”
Exactly, just trying to figure out how to export stems of the surround mix s I can assign Roles to them. If I do a surround QT movie, or multichannel audi… oh duh, didn’t think to try resetting the channel assignments on the surround mix I output to mono so I could set the roles… I’ll try in the AM.. thanks!
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Paul Neumann] “Wasn’t sure if it was the multiple desktop thing or not, but it’s definitely a new feature of Yosemite. “
FWIW, I’m running a late ’12 iMac, NVIDIA GTX 680MX, 32GB, 3TB Fusion, 2 monitors, the built in and an LG 34UM95.
It’s definitely new with Yosemite. And Pr (or something Pr is interacting with) seems to be the only thing that causes it. (so far) I wish there was something that “set it off” and I could sample the process or something to track it down, but it just seems to randomly appear…
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Mike Most] “It doesn’t matter what bin(s) the AMA clips are in. What is important is that the bin(s) be open with all of the clips selected in order for the relink to work in the way I’ve described.”
Thanks Mike. 🙂
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Dan Pearce] “Exactly the same thing happening to me on my MBPr after upgrading to Yosemite. The machine usually crashes shortly after i start seeing it though. Hoping the next OSX update fixes it.”
… Or a Pr update. As I said, I’m running PrCC, FCP X, FCP 7, MC 8, and Resolve 11 on the same machine and so far, only Pr seems to set it off. They’re all affected by it, (as is the whole UI) once it appears. Something’s not happy. 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Thanks Mike… just to throw a wrinkle in here… Say I’ve imported the AAF to an empty bin with no AMA masters in another bin. But… all the source media is on the shared Drive.
Should I first drag all the AMA masters into another bin so MC sees them and then follow your steps? Sorry if this is relink 101, it’s been a while….
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~