Is 768 CUDA cores enough to Encode with?

[Duke Sweden]

Greg, that quote you included referred to Brent’s assertion that he has never seen a post from me in which everything worked flawlessly.

Anyway, I agree with Chris, but, again, what is the point of plugins if they don’t work. Strictly a rhetorical question. Thanks for responding.

Dell XPS 8920
Intel i7 core 7700 build
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0

[Tero Ahlfors]

Real world example time:

Plugins can fail for a number of reasons. Hardware changes, software changes, file corruption, bugs. If a plugin fails on me when I’m doing a job do you think a client will happily wait until the plugin developer fixes it? Probably not. That’s the time where one will either troubleshoot and if that doesn’t work use other tools to finish whatever one needs to do until the problem gets fixed.

What’s the point of whining on the internet?

[Duke Sweden]

I’m not whining. I’m just wondering why this PC, whose specs you can see in my sig, has difficulty handling what my previous PC handled with no problems (other than being super slow). I’m looking for answers. NOT whining.

It’s like owning a 2010 Mustang that I could do 90 mph in easily, then I get a Ferrari, but I can only do 70 because anything above it causes it to overheat.

Dell XPS 8920
Intel i7 core 7700 build
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0

[Ann Bens]

On a side note: the gpu is only used for scaling down, blend modes and two other tasks ( I forget what they are).
(Adobe took down the page about cuda and the MPE).

You need to fix the Lumetri effect between 00:01:09:23 – 00:01:10:08.
Remove and add again.

———————————————–
Adobe Certified Expert Premiere Pro CS6/CC
Adobe Community Professional

[Duke Sweden]

But, as I said, when I encoded it again it ran smooth, no problems. Is that normal in cases like this? If a Lumetri setting is causing a fail, shouldn’t it fail every time? Again, I’m just looking for answers. If anybody thinks I’m “whining” just ignore me.

Dell XPS 8920
Intel i7 core 7700 build
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0

[Todd Perchert]

You had major problems with your new machine after attempting to install the Adobe Developer’s Toolkit. You said after one week you couldn’t get everything back to normal after that. One question. Have you just wiped your drive and reinstalled everything – WITHOUT attempting the Toolkit? Tell me you’ve tried that. Because I’m still guessing you haven’t and there is something with the toolkit install giving you issues. If you’ve already done what was suggested, then we’ll move on. Win10, the GPU, the computer – I doubt those are the issues, unless somewhere in your build you got components that don’t work well together – such as incorrect RAM.
TC

[Jeff Pulera]

Hi Duke,

I don’t know the cause of your errors, but I did notice that the file export path went to the C: drive. Never, ever export to C: drive (or keep video sources there either). That’s what the other, faster, dedicated drives are for. Best practice = no C: drive media.

Thanks

Jeff Pulera
Safe Harbor Computers

[Walter Soyka]

[Duke Sweden] “they cause crashes which, btw, after cleaning my media cache, (which I do every day)”

Cleaning your media cache probably isn’t doing what you think it’s doing. While it’s a good troubleshooting step, it’s not necessary to do every day. See here for more details:
https://forums.adobe.com/thread/2152942

If you’re having problems with a plugin, you might want to clear the plugin cache. Hold Shift while launching Premiere Pro. It will launch slowly once; it’s slow because it’s reloading and caching all the plugins. Thereafter, launches should be regular speed.

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

[Duke Sweden]

Hey Jeff. I always encode to my H drive, that’s what it’s for. I save final encodes to my F drive. I was testing Media Encoder so I just sent that file to my Desktop so I could find it easy enough to delete when I was done, but, yeah, normally I don’t render to my C drive.

Anyway it’s running really smoothly lately so I thank you again for pointing me to the Dell XPS PC’s. Other than these weird problems which are slowly sorting themselves out, this thing rips.

Dell XPS 8920
Intel i7 core 7700 build
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0

[Duke Sweden]

Thanks, Walter. I know it’s not necessary to clear my media cache every day, I’m just being anal until I get this thing running smoothly, which it is now.

Dell XPS 8920
Intel i7 core 7700 build
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0