Forum Replies Created

Page 22 of 333
  • Andrew Kimery

    February 27, 2018 at 9:27 pm in reply to: Codex – more color tools

    Looks interesting, but I wonder how big the market is for a $299 grading plugin when Color Finale ($149) seems to be the go-to grading plugin for X, and Apple just re-vamped the built-in tools. Also, $1500 seems pretty pricey for only working with the that one plugin.

  • Andrew Kimery

    February 20, 2018 at 3:30 am in reply to: Why one user Switched to FCPX

    [Tim Wilson] “Now, it’s not uncommon to skip multiple upgrade cycles, all of which are coming much farther apart. Can you imagine trying to run a cutting edge business with even a 5 year old box in 2002? Yet the number of 2011, and even 2008, computers that are out there doing the heaviest of heavy lifting is quite remarkable to me. “

    I’ve been noticing this for a while too, and I it boils down to a few things

    1. People/businesses continue to cross the ‘good enough’ threshold when it comes to computing power so the

    2. Making a CPU faster isn’t as straight forwards as just cranking up the hertz anymore.

    3. (and this one is obviously Mac-centric) Apple hasn’t released a widely compelling replacement for the cheese grater MP. If the 2013 MP was a cheese grater with modern CPUs, GPUs, I/O, etc., I doubt there’d be so many people running 5, 6, 7 year old Mac Pros (and figuring out how to put modern CPUs, GPUs, I/O, etc., in them).

    If Apple kept releasing cheese grater MPs with new CPUs, new GPUs, Thunderbolt, etc., I don’t anyone

  • Andrew Kimery

    February 18, 2018 at 12:43 am in reply to: iMac Pro thoughts

    [Gabriel Spaulding] “If you were looking for a job at another post facility that’s a different story, but in that case you’d no longer be a freelancer.”

    While it’s common to use ‘freelance’ as an umbrella term to cover both freelancers and independent contractors they aren’t the same thing. A freelance employee is still an employee of the company (W2) while an independent contractor is not.

    Some employers will classify freelancers as ICs in order to avoid things like payroll taxes but that’s a bit shady and illegal. And some employers will hire freelancers to fill staff positions, becauset by hiring a freelancer they don’t have to provide staff benefits (not illegal, but still shady). This, and/or a freelancer staying with the same company for years, is usually referred to as ‘perma-lance’.

    I went freelance/IC again about 6 or 7 years ago and I’d say 3/4 of my time I’m working as a freelance employee so I need to know the gear that companies typically use. In my neck of the woods it’s Avid and PPro for editing (an AE/PS for graphics).

  • Andrew Kimery

    February 10, 2018 at 9:25 pm in reply to: Crazy deal on base iMac Pro

    $1000 off? Did the find a pallet of iMac Pros laying by the side of the road? 😉

  • Andrew Kimery

    February 4, 2018 at 4:32 pm in reply to: fcpx is optimizied for apple hardware, they say

    [Richard Herd] “It’s just my cheap computer, but still, what settings have I missed so that it ain’t processing stuff to conform to what “optimized for apple hardware” means.”

    Are you talking about FCP creating Optimized Media (which just means it’s transcoding everything to ProRes 422)? I think that’s a tic box in the import settings or in preferences.

  • Andrew Kimery

    January 26, 2018 at 9:49 pm in reply to: iMac Pro thoughts

    [Jeremy Garchow] “Is it 6k and 8k red raw footage like Tom is using, though?”

    No, but the original talking point was that 5TB of media was the max PPro could handle w/o slowing down and my responses have been to that point. Factoring in codecs, HD vs 6K/8K, specific machine hardware, etc., are obviously different variables that can play into what Tom is seeing.

    I don’t work with 6K/8K red raw footage, so I can’t comment specifically to that workflow, but I do work with large amounts of media and don’t experience Tom’s problems so that can help eliminate variables with regards to trouble shooting and workflow development. To that point (and the most recent post from Tom), the problem sounds specific to the footage he is using, as opposed to using large amounts of media in general.

  • Andrew Kimery

    January 26, 2018 at 8:41 pm in reply to: iMac Pro thoughts

    [Jeremy Garchow] “Slowness is the in the eye of the beholder. Isn’t that how the saying goes?”

    It is, though when I’ve been opening, saving, ingesting, etc., into the projects I mentioned in the previous post they do so quickly and not “horribly slow” like Tom has experienced. Sure, it’s all relative, but I doubt my ‘quickly’ and Tom’s “horribly slow” are the same speed. ????

    On my current gig we generate about 80TB of media each week (11 video feeds running for 90min stretches, three times a day, four days a week). All of that footage ends up in PPro and the projects open and save in a few seconds. Importing media is a little slower than I’m used to, but it still happens in seconds, not minutes (and I’m used to importing files that are much shorter than 90min so my point of reference isn’t really comparable).

  • Andrew Kimery

    January 26, 2018 at 5:26 pm in reply to: In LA Tomorrow…(Wed 1/24) at LACPUG

    [Scott Witthaus] “And what does THAT mean?”

    People that don’t often have intensive CC needs? If they did they’d probably use another tool like Color Finesse or Resolve.

  • Andrew Kimery

    January 26, 2018 at 5:17 pm in reply to: iMac Pro thoughts

    [Oliver Peters] “I really haven’t run into that and over the past year we’ve had about 7 editors on various machines running some pretty large projects.”

    I’m working with a company that has two docs in PPro and each doc has about 20TBs of media in it and I haven’t heard them complain about slowness when opening or saving the project.

  • Andrew Kimery

    January 24, 2018 at 7:12 pm in reply to: In LA Tomorrow…(Wed 1/24) at LACPUG

    Can’t make it, but should be a show. Sorry I’ll miss you this time around, Bill.

Page 22 of 333

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy