-
Is 768 CUDA cores enough to Encode with?
I was researching why my PC occasionally, frequently, actually, needs to be rebooted because I can’t encode using Media Encoder without it “failing”. I read where you need at least 1,000 CUDA cores for smooth operation, (the GTX 1050ti has 768) but I keep thinking, my old baby PC had nothing compared to this one and, although extremely slow, never failed or froze on me. I also get an error sometimes opening a project that says the project was created using CUDA, which “isn’t available on this system” or words to that effect, when it obviously is, and needs to open in software only mode. Closing Premiere Pro and re-opening solves that totally unnecessary problem.
In short, the PC just acts weird and needs to be rebooted to fix these things at least twice a day if not more. I’ve put all my relevant info in my signature, finally. Can one of you old pals respond? I never hear from you guys anymore.
Dell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0 -
21 Replies
-
My old GTX 650 Ti only had 768 CUDA doors and worked great. My GTX 1060 has 1280 CUDA cores and works even better. I think something is wrong with your computer.
-
Duke either these computers you are buying are pieces of crap or Windows 10 is even more useless than these computers.
I have yet to see a post from you where anything on your system ever works.
I am primarily a Mac Guy but I have a Hex Core i7 PC that I built myself with Windows 7 64 Bit and a 4gb GTX-680 and Adobe CC runs great on it. I primarily use it to offload tons of H.264 encodes with Media Encoder while I keep working on my other stuff on my Mac.It runs AME so well that when I found a killer deal on a GTX-980Ti on eBay I bought it and can’t wait for it to be delivered and install it.
\”MY MEDIA/PROJECT MOTO: If you think three copies of your media or project are enough.
Take a moment to place a value on them and then maybe add two more.
Hard Drives are now stupidly cheap. A RE-SHOOT AND YOUR TIME AREN\’T.\” -
check your premiere crash report with windows’s event viewer- Windows Logs > Application.
Photoshop Elements Editor Help | How to Find Crash Log
https://helpx.adobe.com/photoshop-elements-editor/using/find-crashlogs.htmls on Windows (yes, i know it says photoshop, same concept)Premiere Pro self crash log: FAQ: How to find Premiere Pro crash logs on Windows?
Unhide hidden folders by following these instructions: https://support.microsoft.com/en-in/help/14201/windows-show-hidden-files
Navigate to the following folder to collect the crash log
OS:\Users\\AppData\Roaming\Adobe\Premiere Pro\11.0\logs
[NOTE: is your Windows user name]what are your power options set to? hd set to sleep? anything overheating? run PASSmark95 on components for hardware failures and overheating. do you see your ram being used up from a memory leak? what media, plugins, anything else running in the background?
update bios, drivers, and your premiere is not even updated! can you render successfully with render to software only? -
Brent, with all due respect I haven’t heard from you before I got this new PC, which, btw, is a Dell XPS 8920, which Jeff Pulera recommended to me over a year ago when I first started looking for a more workstation worthy box. My previous PC was an HP which, contrary to public opinion, NEVER gave me problems, through 4 different boxes. Also, I have never seen anyone post on this board complaining that their computer was working flawlessly, so I guess I’m in good company. Now….
Chris, it’s not Premiere Pro that fails. The only thing it screws up with is, every once in a while, I get that error message saying that the project I’m trying to open used CUDA, which “is not available on this system”. I created the project “on this system”, of course CUDA is present, but it only opens in software mode. Closing Premiere Pro and reopening it does the trick.
The major problem is Media Encoder. Sometimes it works fine, I can encode while going back to Premiere Pro, or checking my email, or opening Chrome. But other times as soon as I leave the AME window, it fails. Rebooting the computer will fix that problem, but I’m guessing maybe you might be on to something with the overheating since I have my power options set to never sleep and never turn off the monitors. I will try a more sensible setting and see if that does the trick.
As for your other questions, I didn’t like the new essential graphics and essential sound of the latest PPro so I rolled back. I did have the latest version and had the same problem with AME, so that’s not a solution.
No RAM leaks, latest drivers ( I did roll back on the Nvidia driver, then updated to the latest one that came out a couple days ago.
Anyway, I have a feeling changing my power options might do the trick so I’ll give it a shot. If AME fails again I’ll check the error log and report back. Oh, and btw, Photoshop, Audition, After Effects, all work flawlessly.
EDIT: Well, so far, so good.
Dell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0 -
I still have a gtx 480 and recently did the Creator update.
Other then a bit slow on the export no issues with Premiere.———————————————–
Adobe Certified Expert Premiere Pro CS6/CC
Adobe Community Professional -
Again, it’s not so much Premiere as it is Media Encoder, which hasn’t given me any problems today with the switch to a more reasonable power option.
Just for the record I checked crash reports and, even though Premiere Pro hasn’t crashed, there’s a report a mile long in the log directory. I won’t post the whole thing but this is the first 15 lines or so. Let me know if you see anything unusual:
Process: PProHeadless.exe [12848]
Path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2017\PProHeadless.exe
Product Version: 11.0.0.154
File Version: 11.0.0.154
Code Type: x64
Parent Process: dynamiclinkmanager.exe [11572]Date/Time: 2017-08-05 09:26:54 Eastern Daylight Time
OS Version: 10.0.15063.296
Report ID: 771f7228-0aa6-4b6e-b64a-2a85ca193f6aTime Awake Since Boot: 6917 seconds
Crashed thread: 29 [5024] THREAD_PRIORITY_NORMAL
Exception Code: 0xe06d7363 (C++ EH Exception)
Exception Parameters: 0x19930520 0x58b21cb0 0x2f945d30 0x2f100000
Exception Message:Application Specific Information:
C:\WINDOWS\System32\KERNELBASE.dllDell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0
-
I was literally sitting here running a test encode as I have since yesterday, to make sure things were all working normally after changing my power option, and I thought, well, I should update that thread to let everyone know that everything is working fine, and literally 2 seconds later, the encode FAILED!!! This time I took note of the reason, which I’m pasting below, and which makes no sense to me. Maybe one of you can figure it out. btw, the video merely had Lumetri tweaks, and one instance of FilmConvert Pro just to make it a bit heavier, nothing that my old PC couldn’t handle without failing.
08/06/2017 11:15:06 AM : Encoding Failed
————————————————————
Export Error
Error compiling movie.GPU Render Error
Unable to process frame.
Writing with exporter: H.264
Writing to file: \\?\C:\Users\john_\Desktop\P1000066.mp4
Writing file type: H264
Around timecode: 00:01:09:23 – 00:01:10:08
Rendering effect: AE.ADBE Lumetri
Rendering at offset: 69.958 seconds
Component: EffectFilter of type GPUVideoFilter
Selector: 9
Error code: -1609629695————————————————————
Dell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0 -
if you change nothing but remove film convert pro and it renders ok, then its..film convert pro that’s the culprit. alot of times its the extra plugins that do it, not premiere, (even though its buggy) I mean, if everyone used dnxhd for smart rendering and no 3rd parts plugins, there would probably be a large reductions in crashes.
-
[Duke Sweden] ” I have never seen anyone post on this board complaining that their computer was working flawlessly, so I guess I’m in good company.”
It’s certainly true that there’s always a few issues to deal with on any edit system. For comparison though, I’m also working on a Windows 10 PC and using the latest CC. The one difference being that it’s custom built. My system includes an i7-5820k processor and Nvidia GeForce GTX 970 GPU. I’ve never encountered any issues with Media Encoder or any hiccups with Premiere recognizing CUDA.
I also think Chris is on the right track in relation to tracing the source of your problems. Plugins tend to be the culprits when there’s no clear reason for these errors to pop up.
I Hate Television. I Hate It As Much As Peanuts. But I Can’t Stop Eating Peanuts.
– Orson Welles -
Thanks Chris, but then what is the point of FilmConvert Pro and any other plugin if they cause crashes which, btw, after cleaning my media cache, (which I do every day) the same file rendered with no problem. So strange that with all the storage space I have now, all the processing power, all the GPU, this can’t handle stuff that the other PC handled, albeit veerrrrrrrry slowly, with no problem.
Dell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0
Reply to this Discussion! Login or Sign Up