ERROR Compiling movie - 9 (possible) fixes - Renderer error Premiere Pro

Поделиться
HTML-код
  • Опубликовано: 10 окт 2024
  • КиноКино

Комментарии • 808

  • @Storysium
    @Storysium  3 года назад +50

    Another possible workaround: Try to export increments and then take those parts and piece them back together and export as a whole.

    • @luthandokhuzwayo4489
      @luthandokhuzwayo4489 3 года назад +1

      If you export footage more than once, don't you loose quality?

    • @Storysium
      @Storysium  3 года назад +3

      ​@@luthandokhuzwayo4489 If you import the exported video and then export again you might loose some quality (mainly depending on the codec you use). but if you use the same codec, bitrate, resolution etc. the difference is very very small.

  • @iheartotown
    @iheartotown 3 года назад +58

    I just needed to restart Premiere. Thank you for telling me the obvious in a calm voice. I so instantly frustrated when I kept getting the error after spending hours on a project, I really need that.

    • @Storysium
      @Storysium  3 года назад +4

      Glad I could help! Thanks for sharing!

    • @carnaget3936
      @carnaget3936 2 года назад

      Same here restart did the trick

    • @carnaget3936
      @carnaget3936 2 года назад

      @@Storysium thankyou

  • @ShanePehrson
    @ShanePehrson 2 года назад +23

    Omg, after literal hours of trouble shooting, this finally helped! Apparently creating a new sequence and copy/pasting was the cure! It's ridiculous to think that such a simple solution could halted my progress so much. Thank you so much for the video!

  • @Atomic67G
    @Atomic67G 3 года назад +50

    I have to give you huge credit for what you have done and are doing now. Being forced to change your entire, established brand and recreate your library is a monumental undertaking.
    You Sir are a true dedicated, talented, professional. 😊

    • @Storysium
      @Storysium  3 года назад +4

      Thank you very much ❤

    • @SouthpawAutoworks
      @SouthpawAutoworks Год назад

      Being forced to change?
      I always wondered why the name of this channel changed.
      Do you happen to know what caused this?

    • @SouthpawAutoworks
      @SouthpawAutoworks Год назад

      @@Storysium Were you forced to change the name of your YT channel (Orange83)? If so, would you mind sharing what happened?
      Just a fellow content creator (in a completely different lane), looking to minimize potential heartache/headache.
      PS - I just watched your video about you stepping away from the channel. Just wanted to say thank you for your contribution to this platform. I've learned a great deal from you.
      Hope you're able to reignite a fire for video, filming your own projects. You will do well, whatever you decide to do. Wishing you all the best.

  • @ChevaughnBeckford
    @ChevaughnBeckford 2 года назад +18

    Hey guys, if you're trying to render your timeline for preview and getting this error, a fix I've discovered on my Windows device with an NVIDIA GPU is to go into sequence settings and change your 'Preview File Format' to 'QuickTime'. I hope this helps as well.

    • @zyz-6490
      @zyz-6490 2 года назад +1

      thank you Love you so much :D :D :D :D: :D :D :D Love Love Love

    • @MylesMoncalieri
      @MylesMoncalieri Год назад +1

      worked for me!

    • @vhadianv
      @vhadianv Год назад +2

      It worked thank you, but why? 🤔

    • @ChevaughnBeckford
      @ChevaughnBeckford Год назад +2

      @@vhadianv It has something to do with your GPU and Drivers. QuickTime is a light and popular codec so it plays with almost everything flawlessly.

  • @THECHANTHANNAHSHOW
    @THECHANTHANNAHSHOW 3 года назад +1

    Storysium, you are a freaking genius. I have a Mac and nothing in the threads on Adobe's solutions areas for issues worked except for one of your suggestions here (finally LOL). It was the suggestion you had to 'mark in and mark out' an area of a project. 99% of my vids are all audio related so all i needed was the MP4 format to publish the video on YT. Your suggestion worked! So my advice to folks who are in the same position as I am: When you know you are doing a project to be published to YT, do a 'mark in and mark out' of your project and export into MP4. I had no solution and this worked great for me. Thanks Storysium! Now I can keep doing my interviews 😊

    • @Storysium
      @Storysium  3 года назад +1

      Awesome!! thanks for coming back and sharing your solution.

  • @1301Studios
    @1301Studios 3 года назад +4

    Finding Timestamp helped me, I had repeated effects on clips back to back and that was the issue. when I placed it on an adjustment layer it helped the situation and allowed me to export. THANK YOU!!!

  • @mabushemedia9326
    @mabushemedia9326 3 года назад +16

    The other possible resolution I often use is deleting the preview (.PRV) files where the Premiere project file is located. Premiere Pro creates cached/accelerator files to speed up your workflow but sometimes these files become corrupt or orphaned files.
    1. Close your project.
    2. Go to your Premiere Pro file location.
    3. Search for .PRV
    4. (When the Search is done) Select all and delete all the .prv files.
    5. Re-open your project and then try exporting again.

  • @HotshotArafath
    @HotshotArafath 3 года назад +5

    I have found one method to Render the heavy sequences ..it is by after completing your project select all except with the adjustment layers/ text that uses blending modes and nest them all..this will speed the rendering and export also.. 💯

  • @gathonikagwa6000
    @gathonikagwa6000 Год назад +1

    Thank you big time! After a million export attempts, export with NVEC worked, can’t thank you enough for this!!!

  • @miravespania
    @miravespania Год назад +2

    man i was sweatin cos nothing worked then the sequence did and god. my whole night's work is finally able to be exported, you da goat.

  • @katkatcyclists
    @katkatcyclists 2 года назад +1

    Thank you for your help. Disabling the GPU worked. Had I not bumped into this video, I would have started from scratch and frustratingly get the same error again. Subscribing!

    • @Storysium
      @Storysium  2 года назад

      Glad it helped. Thanks for sharing.

  • @moovintruespace994
    @moovintruespace994 2 года назад +1

    Restarting my system worked for me. It was getting glitchy with a lower third, and needed updating. Once updated, it kept doing it, so i closed everything and restarted. Thank you so much. Oh and it was doing this on Render in and out, not on Render/Export. You Rock!!!

  • @DjFunHub
    @DjFunHub Год назад +13

    Worked on a project for a week now unable to export even after using every single tactic present on youtube 😢

  • @dannivapour
    @dannivapour 2 года назад +1

    ahhh blessings to you, I just needed to free up space was my fix had so many past raw videos (gbs in size) just sitting around still

  • @brettjosh
    @brettjosh 3 года назад +5

    I've tried each of these steps and while they usually work, they unfortunately have not this time🙃
    Each and every time I get the export error message at a different random point in the video, have been trying to export this for 3 days straight now😑
    I do have to say thought this is the best video on the topic by far and is a 99% solution

    • @theashahmad
      @theashahmad 3 года назад

      Is it sorted now?

    • @EmbraceMaking
      @EmbraceMaking 3 года назад

      I'm having the exact same issue. Did you ever get it resolved??

    • @brettjosh
      @brettjosh 3 года назад +1

      Unfortunately still having the same problems😢

  • @ThapanDubayehudi
    @ThapanDubayehudi 3 года назад +9

    I solved this problem rather unconventionally, after trying all your solutions on my 1 hour 36 minutes long video, I came up with a cunning plan. I exported it as 15 minutes long individual videos (by looking at the exact point in time). So I basically had 6 parts of perfectly exported videos.
    I opened a new project, put them all together perfectly, and exported again, it worked like a breeze! ❤️

    • @Storysium
      @Storysium  3 года назад +2

      Good solution, thanks for sharing.

    • @AgungBayu025
      @AgungBayu025 28 дней назад +1

      works for me ty

  • @dariomacchio7673
    @dariomacchio7673 8 месяцев назад +1

    Just a quick tip that I am going to spam/comment in some video-tuttorials with this subject : I was stuck and frustrated with the ccp-814 error for many days. Then I started exporting my project in smaller sections (part1 part 2 part 3) hoping to connect it on a different edit session. And then BAM! One of the fragments/parts got the same error mesage. Then it became easy to detect the problem. It seems that adobe premiere has some kind of "sensitivity" for audio that is left even on a muted track. This was bringing the whole project to collapse. When I resolved this, everything went smooth like before! Try it.

  • @shakeywithlife
    @shakeywithlife 2 года назад +1

    your a legend mate, nothing was working... Exporting through the media encoder saved me... Working on a big paid project and I would be ruined if I couldn't get his footage out. Thankyou

    • @Storysium
      @Storysium  2 года назад

      Awesome, thanks for sharing :)

  • @RavindraJoisa_Official
    @RavindraJoisa_Official 3 года назад +2

    In my case the timestamp that was displayed in the error, I adjusted the transition between 2 clips. Thanks for saving my time, I wasted 3 hours in trying to fix, clearning the temp, restarting etc.

    • @Storysium
      @Storysium  3 года назад

      Glad it helped! thanks for sharing

  • @MelwynDmello
    @MelwynDmello 2 года назад +1

    worked for me..I just needed to restart Premiere & also clear some space on my hard drive . Thank you for telling these solutions..never thought a simple solution will solve it, Cheers to you

  • @Jurong_Jeon_Art
    @Jurong_Jeon_Art 3 года назад +2

    finally worked after pasting everything to a new project and found and adjusted the clip according to the error timecode...thank you!

  • @Amakaa042
    @Amakaa042 11 месяцев назад +1

    I actually came down here to appreciate the user recommendation that you added as the last option IT WORKED FOR ME AND IT'S SIMPLE! it should actually be the first.

  • @finaltouchautodetailingllc
    @finaltouchautodetailingllc 3 года назад

    Also, its awesome that you didnt give up and quit, but instead, got busy remaking your videos and still making new ones! You are awesome!

  • @bananacy
    @bananacy 3 года назад +6

    GPU running out memory during export. happens with effects and resizing 4k footage. Use 'render and replace' on affected clips. Set memory management to 'memory' instead of performance. in my case also turning off hardware decode/encode helps sometimes.

    • @Storysium
      @Storysium  3 года назад

      Thanks for sharing!!

  • @ryanenbom5246
    @ryanenbom5246 Год назад +2

    Had this issue several times because of the warp stabilizer not being rendered inside of a nested transition. It would render on the clip, but not on the nested transition portion - I just had to remove the warp from the 15 frames of transition and adjust the scaling to match the stabilized clip before it.

  • @doladocerto
    @doladocerto 2 года назад +1

    #8 did the trick... Copy and paste everything solved ALL the issues that were happening before... THANKS!

  • @saraths4377
    @saraths4377 3 года назад +4

    In my case, I had applied an Adjustment layer with lumetri color effect. Little did I know that the track benethe had a dip to black effect and lumetricolor wasn’t able to render that small portion hence the error came. Hence removed the dip to black from the clip below to the adjustment layer and solved the issue (I had CUDA on the whole time)

  • @alana9313
    @alana9313 2 года назад +2

    this was honestly the most frustrating issue and nothing was working, eventually i got to step 6 where you select software encoder rather than hardware encoder and it worked (but took much longer)!!!!!!!!!!! thank you SO much for your help :)

    • @Storysium
      @Storysium  2 года назад

      Thanks for sharing!

    • @Taterfried
      @Taterfried 2 года назад

      This solved my problem too. Even deleting the suspect file didn't work for me.

  • @michalina_malisz
    @michalina_malisz 2 года назад +1

    The solution with the sequence change worked, thank you! :)

  • @878SurvivorFM
    @878SurvivorFM 11 месяцев назад +1

    Fixed my issue by extending the intro ticker I designed to the start of the video. Thank you

  • @MichaelRippas
    @MichaelRippas 3 года назад +1

    Dear "Orange" ( :-D ) thank you so much!!! Maybe for years now I was suffering getting the only way I knew (direct export) and having so much pain. 9 from 10 tryouts failed. Now, with your suggestion to get it in the "render queue" of the Media encoder finally it works 100%! Really , I cannot believe. You are the best! Thank you again for your incredible work!

    • @Storysium
      @Storysium  3 года назад

      Awesome!! Thanks for sharing. 🟠

  • @fhehle
    @fhehle 2 года назад +1

    For me what worked was to copy sequence, then paste into a new sequence. Thanks !!

  • @3kgpoison177
    @3kgpoison177 3 года назад +6

    Thanks very much for the help

  • @krissweets6999
    @krissweets6999 2 года назад +1

    Nearly had a heart attack this morning! How infuriating!! I run an old Mac Pro with an RX 580 8Gb GPU. Disabling CUDA solved my issue. Seem to remember it solving this issue a few years ago, too. Very helpful guide. A big Thank you from Kris' Sweets! =)

    • @Storysium
      @Storysium  2 года назад +1

      Excellent, thanks for sharing.

  • @FancyTracks
    @FancyTracks 3 года назад +2

    First tip immediately worked for me. Thanks homie! You got that like.

    • @Storysium
      @Storysium  3 года назад

      Glad to hear it, thanks for coming back to let us know.

  • @OrgGardener
    @OrgGardener Год назад +1

    2nd solution worked for me. Thanks a lot for helping

  • @harshabhat1240
    @harshabhat1240 3 года назад +1

    I saw this video only after I got error in compiling H264 movie. Exporting through Adobe media encoder trick worked for me. Thank you.

    • @Storysium
      @Storysium  3 года назад

      Thanks for sharing! That really helps us all.

  • @someguy4096
    @someguy4096 2 года назад +2

    Saving and restarting my computer actually made it work no problems. Kind of silly how I always seem to forget turning it off and on again works so well.

  • @Harzhid
    @Harzhid 3 года назад +11

    I really appreciate ya man ,I see u are working so hard to re-create content... if there's any chance I'll support 😄 really appreciate your hard work 👏

  • @RivuSouravBanerjeeVideoEditor
    @RivuSouravBanerjeeVideoEditor 3 года назад +4

    Thanks for sharing the solutions, today only i got the error message while exporting my video. didn’t knew why it was showing. i was trying to export a preview copy only, but it was not working. then u unticked the “ use previews” option on the export window and used match source option and then it worked .

  • @afhamghuman2893
    @afhamghuman2893 2 года назад +1

    I was going to stop the tutorial bcz noothing was working then finally something worked for me at the end, THANKS IT WORKED

  • @-aflageakotet2217
    @-aflageakotet2217 Год назад +1

    Creating new project and importing the older is solution for me. Thank you so much

  • @rebeccacarter662
    @rebeccacarter662 3 года назад +2

    Disabling CUDA worked for me! Thank you so much you have saved my day!

    • @Storysium
      @Storysium  3 года назад +1

      Glad it helped! thanks for sharing.

  • @detroitjj
    @detroitjj 3 года назад +5

    A) I love you video's, amazing stuff. B) I made a cool vid using your "paper stack transition" (so cool by the way), and every time PrePro got to the first "paper stack" it failed because of the effects. So after 2 hours I tried all 9 of your suggestions here, and NONE of them worked. So then I did this...C) I nested the whole project and created a dynamic link to After Effects, then there I simply added to the AE render que and rendered it from there, then Re-Rendered it in PrePro, and that finally worked. Just a thought. Thanks again.

    • @Storysium
      @Storysium  3 года назад

      Awesome, thanks for the compliments and thanks for sharing your solution!

  • @Choofy
    @Choofy 3 года назад +9

    Thanks for making this video, this error has been killing by ability to get client work completed on time

    • @Storysium
      @Storysium  3 года назад +5

      Hopefully it's solved now for you

  • @heathers7269
    @heathers7269 2 года назад +1

    The media encoder option worked for me, thanks much!!! Saved me a ton of time.

    • @Storysium
      @Storysium  2 года назад

      Great to hear! Thanks for sharing your solution

  • @Reapervaloratch
    @Reapervaloratch Год назад +2

    it maybe sound weird , but it worked for me when i didnt change the video name !!

  • @Camerasnaps
    @Camerasnaps 2 года назад +1

    Saved and closed. Then re-opened. it worked. Thank you

  • @mabedin5577
    @mabedin5577 Год назад +1

    I was so helpful. my problem was solved by creating a new sequence and copying files to it. Thank you so much.

  • @vueport99
    @vueport99 2 года назад +1

    Best video of all the ones that cover this error. I switched to Media Encoder before watching this and it worked for me. But ME is slower even with hardware acceleration compared to PPro

  • @serhyibaranskyi2765
    @serhyibaranskyi2765 3 года назад +5

    As always clear english and concentrated content. And shift to Storysium channel name is very successful I suppose. Good luck. Thanks a lot.

    • @Storysium
      @Storysium  3 года назад +2

      Thank you very much!!👍❤

  • @shtoksy
    @shtoksy Год назад

    BIG THANK YOU! Copying everything from the project in new one make the difference and repair the problem , I exported right after I made the new project! THANK YOUUUU

  • @BibinJony
    @BibinJony Год назад +1

    My render error got fixed once after restarting the PC. Thank you 😊

  • @FredBeyer
    @FredBeyer 2 года назад +1

    LIFE SAVER! I LVOE YOU

  • @Rylop_
    @Rylop_ 2 года назад +1

    the another render dosnt worked for me, but the restart fixed that, thank you

  • @TrapiTronMusic
    @TrapiTronMusic 3 года назад +2

    Love you Man, I wasted lots time due to this error and now its fixed...

  • @CodeMonkeyMike
    @CodeMonkeyMike 2 года назад +1

    That last one about changing the sequence settings, is what just helped me to solve the rendering in timeline issue. However, I now have an issue with my export, that I am still trying to solve.

  • @KevinElamMusic
    @KevinElamMusic 2 года назад +1

    awesome video, thank you for compiling these solutions! also your voice is nice to listen to.

  • @theprofila
    @theprofila Год назад +1

    Thanks to your video, I just solved mine. I was given the time stamp in the error message but the time stamp didn't match the time stamp on my timeline. However, it also mentioned the effect (Stabilizer) in the error message and so I disabled the effect and the rendering did complete.

  • @mysticwizard101
    @mysticwizard101 2 года назад +3

    I swear I was losing my mind. Nothing was working until FINALLY copying the entire project onto another sequence worked!

    • @Storysium
      @Storysium  2 года назад

      Happy to hear it's solved. Thanks for sharing!

  • @nauczsiegrac
    @nauczsiegrac 3 года назад +18

    nothing except render by media encoder, every other fails. But media encoder doing it a little bit longer 6 min vs 17 min. (with cuda on) I don't know why it happend, yesterday everything was ok..

    • @yildizalper
      @yildizalper 3 года назад +3

      I have same problem. How did you solve it?

  • @fotografoday5715
    @fotografoday5715 4 месяца назад +1

    Thanks pal, I could solve it by installing Media Encoder. I exported media without any issues. Thanks again for your informative video.

  • @ashketchumvalorant5476
    @ashketchumvalorant5476 3 года назад +2

    I had this issue with my game clip .
    I removed the adjustment layer on top of it and it worked !! Thnx

  • @INGALIL
    @INGALIL Год назад +1

    Thank you so much. Creating a new sequence did the trick for me.

  • @Jakeyosaurus
    @Jakeyosaurus 3 года назад +7

    Thank you very helpful!

  • @warped..
    @warped.. 2 года назад +2

    Tysm! The disable cuda one worked for me 😁😁

  • @SteliosRcdrift
    @SteliosRcdrift 2 года назад +2

    Thanks for the video!i made a very short video but with 50% speed all the way from the beginning.once i removed the slow motion it worked

  • @vvinoth514
    @vvinoth514 3 года назад +3

    2nd Method Worked For Me :) i deleted some photos(slideshow) on that particular timestamp shown on the eroor dialogue box and put another set of images... Rendered SuccessFully..

    • @Storysium
      @Storysium  3 года назад

      Great 👍 thanks for sharing

  • @julierodriguez7840
    @julierodriguez7840 2 года назад +1

    I can't believe restarting my computer worked!! Thank you!

    • @Storysium
      @Storysium  2 года назад

      Glad it helped! thanks for sharing

    • @julierodriguez7840
      @julierodriguez7840 2 года назад

      @@Storysium After it worked, another error popped up. The fix was to change from Hardware to Software. Easy!!

  • @Rei-gd5ip
    @Rei-gd5ip 3 года назад +1

    Thank you for helping me out. I really thought i wasted a whole day on a video which i cannot export. Fr tho u saved my effort. Thank u

  • @anotherdimension323
    @anotherdimension323 3 года назад +1

    #2 helped me ! Found the point where the video wasn’t rendering and just extended that clip a few seconds. Error was fixed !

  • @RenLuuk
    @RenLuuk 3 года назад +2

    gelukkig nieuwjaar!! All great ideas! That #2 tip was great - never thought about just exporting a clip. And putting the effect on an adjustment layer has definitely worked for me. But took me about an hour to figure that one out 😂. As always, great vid my friend.

  • @OFORIOS
    @OFORIOS 3 года назад +2

    Using Media encoder worked for me! Thank you so much!!

    • @Storysium
      @Storysium  3 года назад +1

      Awesome. Thanks for sharing

  • @ProjectTOYO
    @ProjectTOYO 3 года назад

    The 3rd solution worked for me 02:19 - Export with Media Encoder
    Thanks for the tutorial!

    • @Storysium
      @Storysium  3 года назад +1

      Glad it helped! Thanks for coming back and letting us know!

  • @Mrsumusic38
    @Mrsumusic38 3 года назад +1

    thanks sir

  • @maringavideoprodutora168
    @maringavideoprodutora168 3 года назад +9

    My solution was to go back to the CC 2018 version, I don't waste time or projects, which gains in productivity compensates for any new option I have in the latest version.

    • @MeruemEditor
      @MeruemEditor Год назад

      Vale mais a pena premier 2018 do que o de 2022?

    • @maringavideoprodutora168
      @maringavideoprodutora168 Год назад +1

      @@MeruemEditor Não vale. Hoje vale a pena o 2022 ! Está excelente!

    • @MeruemEditor
      @MeruemEditor Год назад

      @@maringavideoprodutora168 e o 2021 vale a pena também?

    • @maringavideoprodutora168
      @maringavideoprodutora168 Год назад +1

      @@MeruemEditor Todos são bons. Gosto e uso o 2022, porque já tem a interface dos mais modernos.

  • @BenoniPro
    @BenoniPro 2 года назад +1

    Changing the Editing mode worked for me, thanks.

  • @zig_YT
    @zig_YT 2 года назад +1

    OMG TYSM. I was editing a pretty big video and it was due but I came upon this error and i didn't know what to do. The very simple Retry, Reboot method worked perfectly for me and it uploaded successfully. You have my many thanks.

  • @Hobbitainment
    @Hobbitainment 2 года назад

    I closed the premiere pro, and cleared the temp files and started again. Then the playback problem solved. Thank you...

  • @hexx_5787
    @hexx_5787 3 года назад +7

    basically all of this was unapplicable to me, i was already doing everything, but instead of using cuda, i switched it to gpu acceleartion and that fixed it i believe.

    • @despecc
      @despecc 3 года назад +1

      This worked. Thank you!

    • @Trippingthroughadventures
      @Trippingthroughadventures 3 года назад

      I did that but it completely remove the rendering bars so idk if it is actually renderable

  • @HOSTLESS
    @HOSTLESS Год назад +1

    i know this is an old video but thanks, this helped

  • @AbhishekKumar-os4tt
    @AbhishekKumar-os4tt 3 года назад +1

    Hey man hats off to you... Your 4th trick helped me.. It took time but the video got rendered... Keep growing..

    • @Storysium
      @Storysium  3 года назад +1

      Glad it helped, thanks for sharing :)

  • @1nv1nc1bleczars
    @1nv1nc1bleczars 3 года назад +1

    Media encoder seemed to fix it for me! Thank you!

  • @NoStressMarkets
    @NoStressMarkets Год назад +1

    Thank you sir! Disabling CUDA worked for me!

  • @tabasco4930
    @tabasco4930 2 года назад +1

    Thanks!!!! That last one about changing the sequence settings save me

  • @ShahirUsmani
    @ShahirUsmani 3 года назад +1

    I was having a problem with a transition. Shortening the in/out with one frame each and then nesting the affected parts solved the issue. Thanks

    • @Storysium
      @Storysium  3 года назад +1

      Nice, thanks for sharing.

  • @encantadauk544
    @encantadauk544 2 месяца назад

    Thank you with every fibre of my being! I've been trying to export my video for over a week since the error first started. I'd been rendering each section individually and although the render worked, it still wouldn't export - it's about 38mins long aswell! 😮‍💨
    I found the timestamp, adjusted some of the effects - I'm using transitions on multiple layers as well as text and I just couldn't find the exact effect that was causing the issue although I could see which part of the video was causing the problem (around25mins), which was a separate nested sequence in a longer one.
    I created a new sequence making sure all the settings were exact, copied and pasted the sequence into there and put this new nested sequence into the full video.
    I used Media encoder to then export the sequence. It took a lot longer than in Premiere to export but now I finally cracked it!
    PHEW! I found that changing from Mercury playback software only made a whole load of changes to my text layers so I couldn't use this fix at all. Hope my issues help to fix someone else's, hence the detailed description.
    Thanks again, I've liked, subscribed and saved this video for future reference just in case!🤩

  • @STIPEZURA
    @STIPEZURA Год назад +2

    One of the solutions is also to change sequence settings /video previews/ preview file format from "I-frame only MPEG" to "Quicktime"

  • @iftikh
    @iftikh 3 года назад +2

    Wow! What a timing! Was searching for a solution as I was getting error while exporting a video today. Thanks

    • @Storysium
      @Storysium  3 года назад

      Awesome. Please let us know what fixed your error.

  • @naz7758
    @naz7758 3 года назад +1

    I did the second step when I saved the project and closed the program and it worked , thx

  • @ashishngupta
    @ashishngupta 3 года назад +1

    Preferences reset and new project export worked for me.. thank you so much

    • @Storysium
      @Storysium  3 года назад

      Glad it helped, thanks for sharing.

  • @s6nyi
    @s6nyi Год назад +1

    I switched it off CUDA to software, relaunched premiere and changed it back to CUDA and it worked :P

  • @Eduardo-zh5eb
    @Eduardo-zh5eb 3 года назад

    The error message says the exact time the error occurs. I removed the "Dip to White" transition in this particular shot, reinserted, and voilá! Thank you so much.

    • @Storysium
      @Storysium  3 года назад

      Nice one! thanks for sharing

  • @syahrurieramadhani
    @syahrurieramadhani 2 года назад +1

    Man, Thank You so much. you save my college assignment, btw the first solution work for me.

    • @Storysium
      @Storysium  2 года назад

      Glad it helped! Thanks for sharing.

  • @yoinking4244
    @yoinking4244 3 года назад +1

    extending something a few frames did somehow work for me, thanks man

  • @carlospuigcerver9589
    @carlospuigcerver9589 3 года назад +2

    Im sure this video will help me! Yesterday I received the error and the reboot helped me but its good to know another suggestions. Thanks for your help!! Regards!

  • @KennyHunteX
    @KennyHunteX Год назад +1

    Thanks after not using it for 2 months a restart fixed the issue

  • @jddktech
    @jddktech Год назад +1

    Restarting and then using. A new sequence worked for me

  • @KingRobRool
    @KingRobRool Год назад +1

    Solution 9 did it for me! Lifesaver!!!