Forum Replies Created

Page 7 of 16
  • Francois Driessen

    January 28, 2013 at 4:09 pm in reply to: Media Encoder Unknown error… ?

    I’ve updated the cuda driver for my Quadra4000. And also unistalled & updated to BMDesign DesktopVideo driver 9.7
    Restarted and all is back to life. Seems like it’s either a CUDA issue. or a BMD codec / driver issue that thankfully got solved by the latest versions… Yiy!

    Thanks for your input guys. Enjoy safe pasture…

    Francois

    FireTrigger Inc.
    https://firetrigger.com

  • Francois Driessen

    January 28, 2013 at 3:29 pm in reply to: Media Encoder Unknown error… ?

    I was. But I’ve removed it from the timeline to test. No joy… 🙁

    Spoke to a friend who are having render issues from AE with AI projects embedded over the weekend. He was able to port his project to 5.5 and that rendered out fine… What’s going on with CS6 rendering, Adobe? Is it just me that’s experiencing this here?

    Francois

    FireTrigger Inc.
    https://firetrigger.com

  • Francois Driessen

    January 28, 2013 at 3:25 pm in reply to: Media Encoder Unknown error… ?

    Tried it. Unfortunately that did not help in this case at all.
    I’ve exported the project to AE and was able to render out from there just perfectly… So I don’t believe wonky media is the culprit here. THis is definitely a PP / ME disease…

    Francois

    FireTrigger Inc.
    https://firetrigger.com

  • Francois Driessen

    January 26, 2013 at 10:59 pm in reply to: Media Encoder Unknown error… ?

    No adjustment layers. Straight forward cuts with standard (non-variable) speed changes only.

    Francois

    FireTrigger Inc.
    https://firetrigger.com

  • Francois Driessen

    January 26, 2013 at 10:58 pm in reply to: Media Encoder Unknown error… ?

    Interesting. I’ll give it a try…

    Francois

    FireTrigger Inc.
    https://firetrigger.com

  • Francois Driessen

    September 25, 2012 at 11:58 pm in reply to: Quadro 4000 and ATI 5770 on a Mac Pro

    I’ve been running the 5770 and a Q4000 for premiere without hassles…

    MacPro 8core Wesmere. 24G ram.
    OS 10.7.4
    Latest Cuda driver 5.0.24 & Resolve9
    Black Mgic DecLink Studio SDI. Latest driver. 9.6.4

    Got the 5770 in Slot 1 running 2 displays
    Q4000 in slot 2. GPU only.
    Then DecLink in 3 and CalDigit eSATA for raid.

    What problems are you facing exactly? What codecs are you working with and what’s you sequence codec?

    Francois

    FireTrigger Inc.
    https://firetrigger.com

  • Francois Driessen

    September 25, 2012 at 11:46 pm in reply to: 23.976 to 29.97i Avid DNxHD

    Aah. Good old Media Encoder. I’ve obviously not graduated to using its strengths yet… (Still stuck on the FCP workflows.)
    Awesome.

    Concerning field order: I’ll cross check with them, but that’s what the spec sheet calls for.

    Thanks!

    Francois

    FireTrigger Inc.
    https://firetrigger.com

  • Francois Driessen

    August 31, 2012 at 7:20 pm in reply to: FCP7 I/O Error Mystery

    That DID work. 🙂
    Why, QT7 & FCP export is wonky I’m trying to figure out…

    Francois

    FireTrigger Inc.
    https://firetrigger.com

  • Francois Driessen

    August 31, 2012 at 6:50 pm in reply to: Can I load FCPX on the same partition as FCP6

    Hi, D

    WIth a clean Lion install, is there an actual tested reason for keeping FCPX and FCP7 separate on partitions? He’s mostly addressing OS upgrade install problems (that is an absolute given). And I guess separate installs are the safest way to go. – But is there actual conflicting elements / codecs that gets introduced by installing FCPX? It’s a totally separate app, like having After Effects or iMovie on the same system drive is it not? As far as I know there’s no shared application support between FCPX / FCP7 right? – Or am I missing something (quite possible 🙂

    Francois

    FireTrigger Inc.
    https://firetrigger.com

  • Francois Driessen

    August 31, 2012 at 6:38 pm in reply to: FCP7 I/O Error Mystery

    Its the QT7 issue. When checking the exported file attributes after encode: exporting was actually at 1888x as it said. As mentioned. I think its a media clip that’s causing it maybe…? An error or codec clash that existed in the source media that got passed down somehow when trying to export out of FCP via QT…?

    Francois

    FireTrigger Inc.
    https://firetrigger.com

Page 7 of 16

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