Forum Replies Created

Page 136 of 139
  • Dude, it’s all hype and hot air. She was pimping Avid as a “pro editing application” because she probably hasn’t spent a lot of time in FCP. Our Avid editors who switched took the good part of 3 months to really understand the new way you approach media and management (lots of cursing in those days). Getting out of the Avid mindset takes time – especially if you’ve been cutting with it for 10 years. Just chuckle at people when they pimp how “superior” Avid is; like they’re missing out on the new media revolution.

  • Aaron Neitz

    June 3, 2005 at 6:49 pm in reply to: Using Kona SD with Decklink Drivers

    Use it heavily every day with OS 10.3.8 and driver 4.8. No problems in the slightest.

  • Xpress Pro is a great little app… I known it’s been used to cut a couple studio features films not too long ago. As an offline cut station there’s no reason to waste big $$ on the high-end Avids. But it suffers from 1) if you’ve never cut on Avid, the interface and editing workflow seems VERY antiquated and mechanical, and 2) we’ve found it to be VERY picky about the exact setup and software versions of your computer.

    Don’t let Avid’s PR buzz about “industry standard” sway you. Their reign of terror is fading away. We had 6 full blown Media Composers in house, now we have 1 and 5 FCPs. If I were you, I wouldn’t even think twice about staying FCP.

  • Aaron Neitz

    June 3, 2005 at 1:09 am in reply to: Kona SD working setups? 10.4, Qt7?

    Steve, Blackmagic (blackmagic-design.com) is still providing drivers for the KonaSD. Just download the latest Decklink drivers and they should automatically treat your SD as if it were a Decklink standard def. I don’t know about the new Tiger and FCP 5 driver (5.0b2), and don’t plan to try installing it until next week on my KonaSD system, but I have a feeling it will work. Their 4.8 drivers are solid.

  • Aaron Neitz

    June 1, 2005 at 9:22 pm in reply to: rendering time

    I know Zaxwerks can be slow as a pig depending on the complexity of the 3D/Lights/Materials… I was getting 8sec/frame on a simple 3D scene with 4 objects, 3 lights, and texture maps (on the fastest dual proc. Mac with tons of RAM, etc…) and I know Trapcode Shine can be *exceptionally* slow (so Particular is probably in the same ballpark). Not sure about Knoll.

    Try turning down some settings. I don’t think there’s anything else you can do short of getting an even beefier PC. good luck!

  • Aaron Neitz

    June 1, 2005 at 8:48 pm in reply to: rendering time

    What are you doing? Heavy effects? Greenscreen? What kind of video are you using? Are you using Motion Blur and Frame Blending? Any 3rd party plugins?

    Your box is plenty fast, chances are elements in the comp are causing the massive slow renders.

  • Without a 64 bit operating system, AE can’t use more than 2 gigs of RAM. I’d imagine the memory error is specfic to your OpenGL drivers/Zaxwerks/and your card coming to odds. Maybe an upgrade to Invigorator 4.0? I’m on Mac and the OpenGL renderer gives me bizzare shading problems – the built in rendered looks pretty good on Anti-Alias 4×4 and above.

  • Aaron Neitz

    May 31, 2005 at 5:39 pm in reply to: HUGE bug in FCP5, any solutions?

    We’ve always had problems with graphics in DV. Even in FCP 4.5. Same solution – set fields to ‘None.’ But then, of course, any speed ramps in your timeline look horrible. I was hoping FCP5 solved this – but I guess not.

    Double check that FCP didn’t automatically set your graphics to 98.76% size. I’ve had it do that many times before (no apparent reason) which was causing some soft looking video.

  • Aaron Neitz

    May 31, 2005 at 5:38 pm in reply to: HUGE bug in FCP5, any solutions?

    We’ve always had problems with graphics in DV. Even in FCP 4.5. Same solution – set fields to ‘None.’ But then, of course, any speed ramps in your timeline look horrible. I was hoping FCP5 solved this – but I guess not.

  • with ya on that one.

Page 136 of 139

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