Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Creative Cloud Adobe CC affected my CS6 Mercury Playback!

  • Adobe CC affected my CS6 Mercury Playback!

    Posted by Denis Danatzko on August 17, 2013 at 4:44 pm

    I’ve had CS6 Prod Studio Premium on my machine for nearly a year.
    Two days ago, I subscribed to Adobe CC, leaving my CS6 install intact. Both CS6 and CC seemed to be working fine; I worked on projects in both without problems.

    Yesterday, while logged-in to CC, I also saw some update for CS6 was available. I foolishly clicked on that, and some sort of update was made to my CS6 install.
    Since that update, when I start CS6 to work on a project that was created BEFORE that update, I get a message telling me that the project was started with MPE hardware enabled, but that hardware rendering is no longer available, so rendering can only be done via software.

    My GPU is an Nvidia Geforce GTX 670, running under Windows 7 Pro.

    I’d be indebted to anyone offer a solution to bring back hardware rendering.

    Denis Danatzko replied 12 years, 8 months ago 2 Members · 2 Replies
  • 2 Replies
  • Todd Kopriva

    August 17, 2013 at 5:09 pm

    This question seems to be about Premiere Pro, so I recommend asking in the Premiere Pro forum.

    That said, I’ll point out that the GTX 670 is not one of the cards on the Premiere Pro whitelist for GPU acceleration, so you must have modified the text file to make that card work.

    Updates can overwrite that text file, so your changes may just need to be redone.

    Also, read this:
    https://blogs.adobe.com/premierepro/2013/06/adobe-premiere-pro-cc-and-gpu-support.html

    ———————————————————————————————————
    Todd Kopriva, Adobe Systems Incorporated
    After Effects quality engineering
    After Effects team blog
    ———————————————————————————————————

  • Denis Danatzko

    August 17, 2013 at 5:36 pm

    A big THANK YOU.
    That’s what I ended up doing, and it’s working now.
    It had been so long, I forgot about that update.

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