![]() And I'm running the same driver I would be running even with a newer card, the same driver many other people posting here are likely also running.įurther, when I go to the nVidia web site, they list the same driver for the 1080, the 980 and even my lowly 560 Ti. My hardware is definitely is need of an upgrade.īut your post was in response to someone running a 980, the top tier card available at a reasonable price when 2015.3 dropped. Is it so outlandish to suggest that you might need to upgrade your hardware periodically, say, every five years? Is there anywhere to go from here, or is the best course simply to wait for an update?įace facts, my friend. Not trying to point the finger, I'm truly not sure what the issue is, but I'm still mystified why one of our rigs is sailing smoothly with a Titan X and the other is struggling this hard to export anything above HD, the two systems are nearly identical to one another, save for the GPU discrepancy. What's the meaning of "certified" if we can't even export a measly 2 second test clip, never mind a full feature or commercial. I know, I know, we should never update in the midst of a project, but truly, if a card is certified for use, I don't think users like us should ever have to contend with system-killer software updates like this. Going back to 2015.2 isn't going to work for us over here. Kevin-Monahan what information do you need from us to elevate this issue? Or better yet, maybe we can come up with a workaround that doesn't involve circumventing CUDA support? At the very least, maybe point us in the direction of a stable driver to run alongside 2015.3. Was certain that this would work, given that the K2200 is certified/recommended for use with Premiere Pro CC, but apparently not? Swapped out our two (now defunct?) gtx 980's and tried installing a single brand new Quadro K2200 running certified driver 354.56 on our windows 10 64bit fresh install and still no luck with exporting anything above HD with max quality enabled. Well, add this to the pile of frustration. If I were under the gun, and on a deadline, I'd run down to your local computer hardware and get a 4GB or more VRAM GPU.Drawback: this is more a process you need to consider in the beginning of a project, not now.You might try mastering to DNxHD, Cineform, or ProRes instead.Currently, you are not taking much advantage of that by encoding directly to H.264.Take advantage of the smart rendering process as much as possible, especially if you have a somewhat underpowered GPU.The drawback of "Software Only" that the export is much, much longer than it would with a sturdier GPU.Change the renderer to "Software Only" (if you use Media Encoder, change it there too).My guess is that it is underpowered or not functioning correctly. You are scaling at the very least, so your GPU is engaged during the encoding process. ![]() Normally, encoding does not engage the GPU unless you are doing things like scaling, using GPU accelerated effects (including Lumetri color effects), etc. This taxes your particular GPU too much, so it could not finish the encoding process. From the info you gave, you are scaling footage as you are encoding it. Then, hopefully, you can export it without issues.Reading these errors, it sounds like your GPU is running out of VRAM for the task(s) that you are trying to perform.Lastly, once the project is exported, import it again, and apply the effect you removed. I also recommend using smart rendering, as shown above, and setting the format to something like QuickTime > DNxHR to preserve quality (as double compression is not optimal). That could be lumetri, effects, graphical design, etc. Then, try to remove something quite demanding to encode. To do this, start by creating a duplicate sequence as we did here in case this doesn’t work. ![]() Therefore, dividing the encoding process into two operations instead of one can help lift some weight off your GPU. Since exporting a sequence filled with clips, effects, color grading, etc., can be pretty demanding, a lack of computational power may cause the Accelerated Renderer Error. This solution is quite genius and definitely worth testing. ![]() Go to Edit > Preferences > Media, uncheck Hardware accelerated decoding, and restart Premiere Pro. ![]() If it didn’t solve the error, it sometimes works to disable GPU decoding. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |