Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

CUDA "crash"

Christoffer Glans

Well-known member
Joined
Jun 11, 2007
Messages
4,993
Reaction score
36
Points
48
Age
42
Location
Stockholm, Sweden
So I'm editing offline files with some H.264 material mixed in with different framerates and so on, but nothing really "fancy" other than a usual 1080p project. Now, in order for me to speed up the workflow I use CUDA on my Macbook Pro late 2013 which has an Nvidia card present. I'm using El Capitan and the latest version of Premiere CC. Still, the video "drops dead" after a while of work. I usually can work for like 15min and then the screen goes to white or black and there's no response other than if I change to software playback, but it doesn't go back to normal when changing back to CUDA. Only restarting the software works. It's not "breaking" the workflow since I take coffee every 15min :smilewinkgrin: but it's very annoying to work like this. What is making the CUDA playback crash so much? And why do I need to restart? Is there a processing cache that I could restart instead for the CUDA playback?
 
https://forums.adobe.com/message/8415786?tstart=0#8415786

It's been 2 years now, with glitches, freeze, etc. Adobe says it's Nvidia's fault, Nvidia and Apple don't care. No solution so far. The only solution is to switch from CUDA to openCL.

Which creates graphical glitches all over the place, openCL is worse than CUDA at the moment. But as for all the brawls, I guess that these companies still keep acting like children instead of realizing that being the one coming up with a solution makes customers love them. I don't understand some companies, making sure their products and service is better than others is the most important part to maintain dominance in the industry, but instead they just keep to their end and makes a good product and then don't care how it works in the real world when released. I guess money is all they see... capitalism is working fine until it becomes the downfall. Temporary progress is better than long term, that's the zeitgeist of our age I'm afraid.
 
I don't have any problem with openCL, but CUDA is crashing my computer after a few minutes. Did you update CUDA's firmware?
 
I don't have any problem with openCL, but CUDA is crashing my computer after a few minutes. Did you update CUDA's firmware?

Well, as said, it's not crashing my computer, just stops showing video inside Premiere after a while. OpenCL glitches both video and interface inside and outside Premiere. CUDA works best for now, but annoying.
 
You can try to update it in the preferences system panel then if you didn't do it already.
 
I'm guessing it's a failing graphics card (which is soldered to the logic board). I've had the logic board replaced three times under Applecare on my 2012 rMBP for similar issues. They seem to be aware that it's an issue with the GT 650M at least, though you may have a different card in the 2013 rMBP.
 
I'm guessing it's a failing graphics card (which is soldered to the logic board). I've had the logic board replaced three times under Applecare on my 2012 rMBP for similar issues. They seem to be aware that it's an issue with the GT 650M at least, though you may have a different card in the 2013 rMBP.

I've seen a lot of people having these glitches using Premiere. As I've tried a few games on the computer I know the graphics card can handle much worse stress than Premiere gives it and that's easy to hear when the fans kick in.

I seem to have found that most of the time, the disappearing or glitching video is related to the trim mode. It seems that theres a lot of weird shit going on whenever I've used trim mode.
 
Is there any way you can try it with CUDA on Yosemite? Just wondering if its el capitan. I have seen a number of odd ball issues with capitan. Hardware that worked perfectly fine on the previous builds starts acting strange.
 
I believe H.264 is bad news in general for editing. Transcode it to an easier format like ProRes and see if that lightens the processing load.
 
I believe H.264 is bad news in general for editing. Transcode it to an easier format like ProRes and see if that lightens the processing load.

Yeah, did that and it's better. Although I get some errors from time to time anyway. Maybe it's because of the different frame rates and such.

Another thing is that this project should be 60fps for the majority of the material, while it was shot in 25fps. Now, I just edit in 25fps and then change it into 60fps right? I tried it and the edits seems to stick and it looks good, but first off I get a few more glitches now and then, and second the sound gets all distorted and "crappy". Why does it do that? Isn't this just a change in frame rate for the sequence (video)?
 
Back
Top