Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe After Effects i9 or threadripper on after effects CS6? Is downgrading a solution to multithreading?

  • i9 or threadripper on after effects CS6? Is downgrading a solution to multithreading?

    Posted by Cesar Siena on April 13, 2018 at 3:24 am

    Have someone tryed i9 or threadripper on the old CS6 multithreading capabilities? Do they work? It is known that they do not perform well on CC 2017-2018 (specially threadripper), but what about CS6? This answer would guide to choose new equipment. Thanks in advance.

    Cesar Siena replied 8 years, 3 months ago 3 Members · 12 Replies
  • 12 Replies
  • Walter Soyka

    April 13, 2018 at 9:35 am

    If you’re looking to get “Render multiple frames simultaneously” functionality back into the mix, you might also look at Render Garden from Mekajiki:
    https://www.mekajiki.com/rendergarden/

    Walter Soyka
    Designer & Mad Scientist at Keen Live [link]
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    @keenlive   |   RenderBreak [blog]   |   Profile [LinkedIn]

  • Cesar Siena

    April 14, 2018 at 12:12 pm

    Thanks, Walter. I was looking for saving money when working with older projects in new renderings, with new equipment. CS6 would be a non monthly paid alternative, non third party workaround. I didn’t find tests with it using newer chips. Thank you!

  • Cesar Siena

    April 14, 2018 at 12:15 pm

    Thanks, Dave. I was looking for a non monthly paid alternative to work with legacy projects, with new equipment. I didn’t find tests with CS6 using newer chips. Thank you!

  • Wallace Adrian d’alessio

    April 15, 2018 at 7:38 pm

    Are you saying you went to the CC archive and that CS6 and other older versions are no longer there for download by CC members who need them? Is that what you are saying?

    Adrian D\’Alessio aka; Fluxstringer

    fluxstringer@gmail.com
    https://www.facebook.com/FluxStringer
    https://www.linkedin.com/in/fluxstreamcommunications

    https://twitter.com/FluxStringer
    https://mog.com/FluxMuse

  • Cesar Siena

    April 17, 2018 at 4:39 am

    No. I work on non-profitable educational Ae projects with CS6 in one environment/work place, in which there’s no budget for montly subscribing, but the machines will be updated. We don’t know if updating them with threadripper will work well with CS6. Although there are 3D programs there that will certain respond well, most of the work is done with Ae, so the hardware update will have to consider that. i7 8700 seems no future proof regarding new multi-core tendencies.

  • Wallace Adrian d’alessio

    April 17, 2018 at 7:00 am

    I am low budget myself.

    I will speak , for what it is worth. I mean no disrespect to your situation.

    Personally I would rather have new software that was a legitimate copy and no ” issues” on an old CPU than an i7 8700 with old software which will always create issues.

    A better balanced yet underpowered system always seems less trouble than trying to tame an imbalanced system which will never really be tamed. I tried that for years with Premiere Pro trying to run in VM on Windows 7. It was crappy as hell.

    Adrian D\’Alessio aka; Fluxstringer

    fluxstringer@gmail.com
    https://www.facebook.com/FluxStringer
    https://www.linkedin.com/in/fluxstreamcommunications

    https://twitter.com/FluxStringer
    https://mog.com/FluxMuse

  • Walter Soyka

    April 17, 2018 at 5:55 pm

    To more specifically answer your question, first take a look a this comparison on Ae CC 2018:
    https://www.pugetsystems.com/labs/articles/After-Effects-CC-2018-CPU-Comparison-Intel-8th-Gen-vs-X-series-vs-Ryzen-vs-Threadripper-1123/

    I doubt you’ll find tests for the older software with the newer CPUs, but I’d expect the kinds of performance you see in the test above for “standard projects” to scale with CS6 – CC 2014 (with multiprocessing). The old performance advice still applies: max out your RAM (each render process launches a separate instance of the Ae renderer which requires its own RAM space), and get a good SSD for your disk cache (to allow Ae to avoid re-rendering frames it has rendered before).

    Walter Soyka
    Designer & Mad Scientist at Keen Live [link]
    Motion Graphics, Widescreen Events, Presentation Design, and Consulting
    @keenlive   |   RenderBreak [blog]   |   Profile [LinkedIn]

  • Cesar Siena

    April 17, 2018 at 6:22 pm

    Interesting advice! Thanks!

  • Cesar Siena

    April 17, 2018 at 6:26 pm

    This is wise, Dave; I learned with you, experienced Ae people, doing that in the last years. The real delay is RAM previewing several times during the work, which can’t be postponed.

  • Cesar Siena

    April 17, 2018 at 6:34 pm

    Thanks, Walter. The small educational oriented studio already works with plenty of RAM and SSD. Nowadays, even a NVMe disks RAID is affordable. The issue continues to be performance along the project (RAM preview). I remember an Adobe video on performance recommending 2x ou more Xeon. The video presented a machine with 32 cores (or threads?) and the host (presenter) worked flawlessly in real time. How do you manage that?

Page 1 of 2

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