Forum Replies Created

  • Bryan Root

    January 1, 2020 at 2:33 am in reply to: Twixtor Problem

    Similar Problem: I had a layer with Twixtor FX that wasn’t rendering at all. The other layers rendered OK, but that Twixtor layer wasn’t there.

    I tried all these fixes and finally figured out that the “USE CPU” switch (3rd item down in the Twixtor menu) needed to be turned “OFF.” Renders well now.

    I have a mac pro 2012 with a new GPU–Radeon RX 580 8192 MB

  • Bryan Root

    January 1, 2020 at 2:33 am in reply to: Twixtor Problem

    Similar Problem: I had a layer with Twixtor FX that wasn’t rendering at all. The other layers rendered OK, but that Twixtor layer wasn’t there.

    I tried all these fixes and finally figured out that the “USE CPU” switch (3rd item down in the Twixtor menu) needed to be turned “OFF.” Renders well now.

    I have a mac pro 2012 with a new GPU–Radeon RX 580 8192 MB

  • Bryan Root

    September 17, 2017 at 5:06 pm in reply to: Export Module failure

    I struggled for hours with AE cc2017 trying to render a sequence at 3840 X 2160. I have a mid-2012 MacPro with 48GB ram and my GPU is an NVIDEA Quadro. I could render the sequence out at 1920X1080 just fine. I could render other sequences out at 3840 X 2160. It was just this one sequence that had a lot of large still images in it and nested sequences for which I’d created 1/2 res proxies.

    I thought, silly me, that if I just selected “use all proxies” or “use current settings” in the render settings tab of the AE render cue that I would be taking the strain off my machine for rendering all those complex effects in the nested sequences. I created lots of half rez proxies (which I could live with) and I made sure they were all enabled in the project window, but there just was no getting the sequence to render to 3840.

    What finally solved my problem was finding the proxy files I’d created (right click on the proxied comp in the project window and select “reveal in finder”) and import the proxies and replace the nested comps with these proxies physically in the final comp. A sort of “ignoramus’ prerender” workaround, but it worked and I was finally able to render out at my desired resolution.

    I suppose PRERENDERING that which you were using PROXIES for is the answer. Proxies seemed to muck up my render cue. Once I did that I was also able to render using Adobe Media Encoder which is much prefered.

  • Bryan Root

    January 15, 2014 at 10:07 pm in reply to: Audio mixing in PPr CS6 Causing Crashes

    I am having a similar problem. Getting this error:

    [/Volumes/BuildDisk/builds/MightySilt/shared/adobe/MediaCore/AudioRenderer/Make/Mac/../../Src/AudioRender/AudioRenderContextConstructor.cpp-110]

    I tried all the solutions on this thread and none of them seems to be fixing the problem. I opened up a different project, and that worked fine, so I think it’s something with the project file itself.

    Does anyone have any more suggestions?

    MacPro Mid 2012
    NVIDIA Quadro 4000
    48GB RAM

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