Copy link to clipboard
Copied
Update:
This question is no longer relivant because I based my initial test off of a prerendered clip.
I am using a 5 year old build that I recently upgraded to Win 11 and Adobe CC 2025.
Issue is timeline scrubbing/playback.
specs:
Threadripper 2950X (usage is 50% during playback)
64GB DDR4 3000
Samsung Pro NVMe 2TB (scratch)
WD NVMe C: (program install)
Old GPU: 1080Ti
New GPU: 5070Ti (usage is 40% during playback)
I started using MOGRT's for automated effects like light leaks, motion, blur etc... My old GPU would peg at 100% trying to review/scrub in the timeline and I was getting 1 frame per 5 seconds... unusable. So I bought a 5070Ti. When I installed it and the drivers, that day I found that my timeline scrubbing (same project) was SO SMOOTH I could scrub super fast. No lag at all! Zero. And I never ever do any prerendering like render and replace or anything. When I encoded this 5 minute sequence, what used to take 4.5 hours now took 5 minutes.
that was 2 weeks ago. Today I sat down to edit... same template that I opened up for a new sequence. Now I'm back to my old performance. It's unusable again. Cuda acceleration is "selected", but greyed out.
I've done:
uninstalled and reinstalled drivers.
restarted PC
checked all my settings including playback quality etc...
What am I missing? I just dropped $1k of my personal money on something that helped for 1 day, then, nothing!
I'd like to avoid having to build another PC, especially since the current one worked so well for one day on the new card.
TIA
Hey there,
Thanks for the post. The 5070 has an issue with hardware encoding. You can either switch it off or roll back a version. See if one of those things works. The team knows about the issue and is working on a fix.
Thanks,
Kevin
Well this is embarassing. I just realized that my day-one test that turned out so well had been a rendered video that was placed into the timeline. So I have no "why was it working so well at first?" argument. Thanks for the info on the 5070. I'll just sit here and weep Thanks!
Copy link to clipboard
Copied
Hey there,
Thanks for the post. The 5070 has an issue with hardware encoding. You can either switch it off or roll back a version. See if one of those things works. The team knows about the issue and is working on a fix.
Thanks,
Kevin
Copy link to clipboard
Copied
Thanks for the fast reply. Are you talking about rolling back a version of Adobe? Or the GPU driver? if you are talking about Premiere, I just installed adobe in May. how do I roll it back. Also, since this mogrt uses AE, does that have to be rolled back too?
Thanks
Copy link to clipboard
Copied
Copy link to clipboard
Copied
This must be very frustrating after investing all that money.
@Kevin-Monahan - you say the 5070 has a known issue. Its a bit weird that the 5070Ti worked OK initially ?
@texmant123 do you have the problem on all projects?.
The latest studio driver I see is 577.0 but NVidia have released a Gaming driver 4 days afterwards 580.88 on 31 July.
Did you try a complete re-install of Premiere and also a clean install of the NVidia Driver ?.
Having said that, this is what Mr Google just brought up :
'The NVIDIA GeForce RTX 5070 Ti, while a powerful card, has been reported to have issues with hardware encoding, particularly in real-time scenarios like streaming. Some users have reported problems with the card being unable to handle encoding at reasonable settings, even when compared to previous generation cards. This can manifest as performance bottlenecks, crashes, or even black screen issues'.
I would also raise a case with NVidia Support to see what they say.
Copy link to clipboard
Copied
May 2025 post on community, just spotted
Copy link to clipboard
Copied
Well this is embarassing. I just realized that my day-one test that turned out so well had been a rendered video that was placed into the timeline. So I have no "why was it working so well at first?" argument. Thanks for the info on the 5070. I'll just sit here and weep Thanks!
Copy link to clipboard
Copied
Hopefully as Adobe team are on the case it will be resolved relatively quickly .
Thanks for letting me know the mystery of why it worked first time!
Find more inspiration, events, and resources on the new Adobe Community
Explore Now