Premiere Pro: GPU Render Error -1609629695 (5 Solutions)

[@videowithjens]

What was your solution to fix the error?

[@welcome3652]

I followed some solutions that worked after trouble, but I found the best positive solutions you have

[@helgabeuving7408]

changing the project settings. Thanks so much for this video!

[@Green1920Tanki]

Deleting the warp stabiliser effect from some clips

[@wout4052]

project settings

[@0tintifax0]

Copying to new sequence. You sir, are a genius!

[@AlexCarter-m6z]

Thanks so much for the video but... am I the only one who still has this problem despite trying all Jens' suggestions?

[@twistletowntreasures448]

No bro - same still here

[@simon.kostelnik]

Hello, my friend. I also solved this problem. The solution is as follows. The reason why this happened to you is that you probably stabilized a clip that has a different FPS than what you have set in the sequence. For example, your RAW clip has 50fps but your timeline has 24fps. When you stabilize, you do get a field count, but one frame disappears. You probably lost one frame somewhere in that clip and then a black spot was created. You need to cut out this ''empty'' frame. After cutting, the error message no longer appears. That's all. Good luck :)

[@rollyca]

This is the solution for me, Thank you from Mexico.

[@thenaturals]

also helped me thank you from chicago!

[@reginesharon]

Wow thank you!!! Noticed this on my clip but I thought I fixed it.. never thought it was a problem..

[@all0932]

o, hello! It's exactly my problem, and your solution is work! Thank you!!!

[@vigilantspb]

thanks!!! making cross dissolve transition couple frames larger solves the problem (stupid problem, adobe style problem)

[@MujoKujo]

I spent HOURS trying to fix this and the longer export method is the only thing that worked. Thank you so much for solving this, I now know who to go to for stuff like this.

[@SergSpace]

There we go. Premier Pro pushes us back to cave.

[@pragmaticcreator]

The"Software Encoding" option worked excellently for me and I exported it without glitches nor hitches. God bless, buddy.

[@heyguys9873]

Solution at 1:00 worked for me. I couldn't render the warp stabilizer effect for some reason throughout. But this fixed it.

[@gusjaramill0]

the long render it was for me, thanks a million, super hard when trying to meet a deadline and you encounter this issue. ive got 64 gb of ram i thought i could handle anything LOL 58 are designed to premiere pro . once again thank you

[@va_creativespace]

Really helpful brother. I was trying to figure it out for so long. Keep doing what you are doing and thanks for helping out. Cheers!

[@DArkLionLive]

Very nice! For me, replacing the clips (with the same clip) that were in conflict made the error go away. Adding this to my favs for sharing when needed!

[@IngenieroViajero]

I can't believe I had to view a youtube video to solve the issue by just rebooting the app. It should have been my first thing to try. Thanks a lot :)

[@videowithjens]

Hahah, glad I could remind you of it

[@irenemaundu843]

I can listen to you all day. The accent is Phenomenon. Thanks for the assistance.

[@videowithjens]

Hahah thanks, that's how I roll! Glad you found it helpful :)

[@TheBucksBiker-lh2nm]

Thanks mate for the video.... You helped me fix the annoying issue. Mine was checking the time code and found a clip that was causing the pain! Replaced it and all good.

[@jamesh3939]

Thanks Dude! You just saved me a lot of time and heartache. I'd already tried tip 1 (turn it off and on again), and tip 2 (deleting the clip and re-adding it) but changing the project settings and the export settings to render using software rather than hardware did the trick on this one!

[@videowithjens]

Glad it was helpful!

[@setmayv]

Thanks man, solution with project settings is the best!

[@iamgallivantin]

Solution 5 worked for me, thanks so much for the tip!

[@videowithjens]

Im glad to hear!

[@nickyfurmage]

Thanks for this, creating a new sequence works for me when everything else fails.

[@esegabbbo]

Had this problem, in my case, when I had a cut from one clip to another, I noticed there was a black frame in the cut that made it look really weird. My solution was to, given the timecode of the error, look up the footage in my project and reload it.

[@tummy_rupples]

THANK YOU. true life saved. Appreciate getting right to it without typical KZbinr mess. Will be returning for more help when needed 🤙

[@Drywest]

THANK YOU SO MUCH, YOUR A BIG HELP!

[@videowithjens]

Very nice! Glad I could help!

[@OneMadNugget]

Straight off the bat, the first solution helped lmao. Thought I'd be wasting time restarting and waiting for it to start back up again instead of trying something else 😂

[@videowithjens]

Hahah, restarting ftw!

[@AortaProd]

Yes sir you know what you are talking about. I changed the rendering settings and got through. Thank you

[@videowithjens]

Fantastic, glad to hear that

[@Extra-Salt]

frustratingly for me I had no issues rendering my file as a portrait for a YTS, but now i'm trying to export it again as your traditional 16:9 and the error persists.

[@sunk99]

Thanks. Changing to software only fixed my error, although I had to change out a light ray transition that required acceleration. Again - thanks.

[@Никита-ф5к5х]

Thank you very mush! This problem almost made me insane but your solutions help me

[@competitivegamer9193]

Very Helpful. Thank you

[@FishingwithFin]

Great video! Helped me render my project after the error code kept coming up. I changed my Renderer to ‘Mercury Playback Engine Software Only’ however this has changed the colours of quite a few clips on the timeline making it almost impossible to colour grade back to how the original colours look, is there a way to solve this issue? Thank you! 😊

[@Butter_interesno]

Thanks my friend ! Really helped

[@mr.harambae]

I marked the sequence with in and out and then headed to Sequence(top of your screen)>Render in to out it seemed to export fine after that

[@InsanityFN1]

thanks for this! all i had to do was quit premiere pro and re-open it and the problem was fixed. im relieved it was that easy

[@videowithjens]

Awesome! Love it when that works🙏

[@DreamerVisionary]

Hi Jens I’m new to Premiere Pro, how do I set up a brand new sequence and make sure the settings are the same as my export settings please, also how do I free up memory in the application so I don’t run out of space thank you

[@welcome3652]

Thank you for these great tips, good luck my friend

[@videowithjens]

Thanks! Happy to help

[@itslucasyap]

I am glad that I switched, I went back to use for today Pr and I realised...I hate it now.

[@INGLES.Gratis]

what are GPUs for? Gosh... adobe must fix those issues once for all!

[@criticactual]

yes..with previus versions works fine.

[@Dbabasbz111]

keep it going bro from egypt ♥

[@HorrorbleDriver]

Thanks, man. Much appreciated.

[@FocusMusicProduction254]

Very helpful. Thank you

[@videowithjens]

Glad I could help!

[@El.hero.]

i tried the first and second solution and it works thx to match

[@SergSpace]

This premier Pro becomes pain in the butt. I was able to Export my project with 1920x1080 30fps. There were lags in Playback, so I went to Sequence and changed to 59.94fps. My project was whipped with red lines over clips with warp stabilizer. I had to redo stabilization again. Ok No red lines now, but this Error keep popping up. Looked at the time marked on time code. There is nothing there! no transitions, I redid stabilization on that clip again. It didn't help. Rebooted computer. No help again. Now I turned off GPU acceleration in Project Settings so, I'm sitting and staring at rendering estimated time of 1 h 30 minutes of 37 minutes movie clips that I edited and wonder if this will even help. In 1 hour of Rendering progress bar window shows 44% done and 1 h 40 minutes left. OMG, this is not even a 4k. I can't tell how long it took, fell asleep, but I think about 3 hours in total. But it helped. The movie was produced without a Error hiccup.

[@criticactual]

This error did NOT occur before the premiere pro.

[@SlayerSpaz]

Why do I have none of these tabs? My software is up to date but I don’t get any of these fancy options as far as file, settings etc.

[@videowithjens]

Sounds weird, are you using Premiere "Pro" and not "Rush"?

[@romannh22]

thx i had an error when I change the speed of my project now it's working thanks

[@videowithjens]

Very nice! Glad it was helpful

[@dantemv1950]

So, does this error occur because of the gpu? Is there something wrong with it or is it maxed out?

[@nidhyanapuri6343]

thanks for this video.... your tips are very helpful...

[@videowithjens]

I'm glad to hear that!

[@hassantariq4086]

1:43 worked for me

[@dannyitssodeluxe]

Yo, this helped. Thanks mate.

[@SarojRanzit10Jr]

thank you so much i got my error fixed in just away 🥰😇

[@kfunnyshortfilms]

Is it effect foe the vid quality?

[@Sanju047D]

Thank you, I managed to solve my problem.

[@marlonssousa_]

Obrigado, ao excluir o video com problema e colocar ele de novo no projeto o video renderizou.

[@danyeldev]

Very Helpful Thanks

[@rohanshxtty]

I had applied a preset multiple times to all the clips. that was causing duplicate and was crashing my gpu. I removed all the duplicate and it worked

[@sig.editzz]

still same error

[@videowithjens]

Check out the article too

[@Pashopvn]

Thanks bro so much! I have solved this problem!

[@videowithjens]

Excellent!

[@seketestudio6488]

thanks dude it worked!

[@barbietheuntoldstory3908]

Thank you it worked ❤

[@wout4052]

you safed my life bro thank you so much :)

[@videowithjens]

I'm glad to hear that!

[@rico3567]

Tusen takk!

[@muratkaralux]

thank u very much. u made my day !

[@dilshanariyawansha2678]

You like a god bro thank you somuch😻❤

[@kfunnyshortfilms]

Thank you very much😍

[@videowithjens]

Happy to help!

[@anoopsajay4746]

second solution worked for me thanks

[@artji0829]

Thanks! IT FIXED!! Thank a lot:)

[@videowithjens]

Awesome! Happy to help

[@mohammadtorikh]

thank you so much m8, god bless you

[@Wewew-o7n]

Thank you very much

[@lensbaad6069]

you just saved my life!!!!

[@geschielogie]

I love you thank you so much

[@AryanVeysi]

thanks my love, you saved me :)

[@aemahe1]

dude thanks so much

[@1300gabriel]

Thanks Bro!

[@trx-hamodi2701]

thank you so much bro you saved me

[@EL17CT]

tanks You are the goat

[@UrsoValen]

These bugs make premiere pro so frustrating to use! Like I love the program but this stuff holds it down so much

[@kionix_071]

tnx for the video

[@EYZONME75]

THANK YOU!!!

[@grindnowshinenow]

Bro if we need the effects how tf is deleting the effect a solution? 🤦🏽‍♂️

[@videowithjens]

Hello, I recommend reading the article if you don't get it. But you'll figure out which effect causing the error

[@topenglishreels]

Thanks just shift gpu

[@robinceuleers]

The most annoying thing about Premiere pro

[@stress_cure]

Agreed 💯

[@unitmultimediappktkampuskk]

can solve my problem. tq

[@videowithjens]

I'm glad to hear :)

[@zulfilarrythelobster]

thanks you so much

[@zinu94]

thank you its work

[@ntbruno2210]

i only have to reset premiere XD

[@regromanillos8257]

Great thanks. This saved my ass!

[@Biring1]

Helt rå norsk aksent hehe

[@videowithjens]

Thanks. Ingenting er verre enn å måtte uttale "error" igjennom en hel video

[@EiCult]

obrigado

[@picturehuntpicturehut8911]

thanks bro thanks for everithing

[@TravelStatusLLC]

Adobe sucks. Nothing worked for me. What’s a better alternative?

[@itslucasyap]

Switch to Davinci Resolve...

[@Fitzaey]

I'm more than annoyed that the premiere is so unstable that people can make videos about it.... like there's 1000s of videos about it...

[@videowithjens]

thanks

[@PSPhotography-i3q]

thnaku bro

[@media_quokka]

HEY, I LOVE YOU.

[@shimronnetia]

you are the best

[@ahmedibrahim.]

thx lov

[@CinthyaVong1]

🙌🙌🙌

[@damosaprods]

Te quiero

[@Akshubha]

Please startup gaming channel for your career

[@videowithjens]

Haha maybe, I enjoy creating these tutorials

[@robsonfotofilme]

Thank you!