Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Forums Adobe Premiere Pro User can’t queue renders from PPro2017

  • User can’t queue renders from PPro2017

  • Jon Doughtie

    November 19, 2018 at 9:38 pm

    I have one user on a workstation that, when they queue one render (or a series), Media Encoder launches, but the render list never populates. They’re both CC2017.

    We tried launching PPro clean (Shift+Alt at launch) but this made no difference.

    The issue is isolated to this one user.

    Ideas, anyone?

    System:
    Dell Precision T7600 (x2)
    Win 7 64-bit
    32GB RAM
    Adobe CC 2017.1 (as of 8/2017)
    256GB SSD system drive
    4 internal media drives RAID 5
    Typically cutting short form from UHD MP4, HD MP4, and HD P2 MXF.

  • Todd Perchert

    November 20, 2018 at 7:54 pm

    Sorry, this will most likely be absolutely no help, but I have seen that a couple times in the past. I recall just resending, or quitting Adobe Apps and reopening, or restarting the computer. It’s been awhile since I ‘ve had it happen… I’m sure you’ve done all the above.

  • Jon Doughtie

    November 21, 2018 at 4:10 pm

    ‘Fraid so, Todd. But I still appreciate the read and the response!

    System:
    Dell Precision T7600 (x2)
    Win 7 64-bit
    32GB RAM
    Adobe CC 2017.1 (as of 8/2017)
    256GB SSD system drive
    4 internal media drives RAID 5
    Typically cutting short form from UHD MP4, HD MP4, and HD P2 MXF.

  • Daniel Corcoran

    November 24, 2018 at 10:27 am

    Hi Jon,

    I’ve had the same issue for a few weeks. Hope this helps you!

    I’m using…

    PP CC 2019: Version 13.0.1 (Build 13)
    AME CC 2019: Version 13.0.1 (Build 12)

    Windows 10 Home 64bit (10.0, Build 17134)
    Dell XPS8900 BIOS 2.4.0
    Processor Intel Core i7-6700 CPU 3.40GHz (8CPUs) 3.4GHz
    RAM 32768MB
    GPU GeForce GTX745 (Driver 416.81) (11.08.2018)

    Adobe recommended a few things:

    – upgrading GPU driver,
    – trashing preferences,
    – renaming ME’s folder to “old##.#
    These worked, but only momentarily.

    Last night, I thought I’d solved this by copying my entire 3 hour timeline into a fresh new project. And lots of sequences encoded (CUDA) no problem over night (apart from one sequence where I had the Error 1609629695 which I’ve never had before but seems to have been a mystery error in Adobe’s community for a number of years.)

    But this has only worked once. Having rebooted to try and solve this 1609629695 error, I’m back to square one and it won’t encode again!

    I’ve copied/pasted into a fresh project yet again, trashed the preferences, renamed ME’s “13.0” folder to “old130” etc and it still doesn’t work.

    It’s as if once PP knows you’ve got a remedy to it’s illness, it gets resistent to the treatment!

    Also, what is even more frustrating, PP is suddenly saying that my hardware doesn’t support CUDA anymore for “H.264 Highbitrate” and my only option is software encoding.

    Since I invested in “upgrading” from CS5 (which never let me down) only in the Summer, I’ve had nothing but problems!

    I hope this idea of copying and pasting into a new project works at least once for you but you’ve probably already tried it.

    All the best,
    Dan

Viewing 1 - 4 of 4 posts

Log in to reply.

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