Skip to main content
B
B.Schoemel
Known Participant
May 17, 2017
Question

WARP STABILIZER & EXPORT FAILURE

  • May 17, 2017
  • 8 replies
  • 23622 views

Since a few weeks now I keep having issues with exporting my timeline from different projects on different PC's!!!

"Fehler beim Export Fehler beim Kompilieren des Films.Fehler beim Rendern

Schreiben mit Exporter: H.264

Schreiben in Datei: fildame.mp4

Dateityp wird geschrieben: H264

Um Timecode: 00:01:04:11

Rendering bei Offset: 63,760 Sekunden

Komponente: H.264 vom Typ Exporter

Selektor: 9

Fehlercode: -1609629695"

This is happening all the time now and I ONLY have warip stbailizer and a simple lumetri color correction on the HD 25p files from gh4 and canon 5D 4.

This is soooo annoying!!!! And yes, I have enought storage and space! Also tried different harddrives, filenames, computers... nothing works once this bug is there!!!!

PLEASE SOLVE THIS ISSUE!!!!

If I delete ALL the audio and resave the file, same same!!!

    8 replies

    P
    Petr Mk
    Known Participant
    September 4, 2025

    I can't believe this is still an issue. I still can't export a 30-second sequence just because I added a simple zoom effect. I've been searching for a solution for over an hour now, and nothing helps. Premiere is such incredibly sh*tty software. Every f*ckup like this reminds me of the importance of moving far away from Adobe

    upslon
    upslon
    Participating Frequently
    December 13, 2023

    Here i'm having a similar problem. I'know that its probabely becouse i have mixed footages (1080p@120, 1080@30, 4K@30) on a sequence of 1080@30. But when i changed the progect engine from GPU to CPU when i'm about to render, i could deliver an prores422LT.

      D
      Dyani26355798kcc9
      Participant
      October 17, 2024

      Hey there.

       

      October/2024 and even though I try my best to stay far away from Premiere pro, my editor uses it. This is still a problem.
      The only way I got around it was removing all warp stabilizers and exporting it, then using Davinci Resolve's automatic clip selection tool and stalibizing it there. Absolutely no issues with Davinci.

       

      Get your sh*t together adobe, this is way to expensive to be worse than a free program.

        Blazekiss
        Blazekiss
        Participant
        September 11, 2023

        2023 and is still a probleam............. @adobe this is a joke. A simple warp effect on a 3 seconds file cause an export probleam doesnt matter mac stuido...or pimped up mcbook or an other high end pc i am working on still a probleam.

        SOLUTION that only works for me is to edit the one small piece of video with the warp stabilizer export each of teh sequence that needs than re import in premier than exchange the mp4 file to the raw video than i can export the 30 second video file with the needed stabilized footages. 

         

        It is stil a joke that we have such a trouble after soo long and seeing how old this tread is...

        V
        Viodi
        Participating Frequently
        September 26, 2023

        The issue seems to be with the transition. What seems to work is to eliminate the transition and put the clips on two different tracks, overlap the clips, and apply the transition to each clip. 

         

        It is unclear whether the clip needs to be pre-rendered as suggested earlier. 

        K 11 films
        K 11 films
        Participant
        July 24, 2023

        Hi If you are still facing the issue.
        THE SOLUTION I got for this is make your sure your footage fps and timeline fps matches if you are using warp with 24fps footage on 30,50 or 60 fps timeline this error will occur again.

        Convert your timeline to the same as the max shots and then shift it to hardware encoding.
        this helped me and saved hours.

          R
          ronenc55097022
          Participant
          September 8, 2023

          thank you very  much! this sloved the prob with  the best original solution!
          this is very strange adobe did fix this prob from such a long time.
          thank you again. saved me lots of time

            J
            johannese53661908
            Participant
            June 16, 2023

            I was able to fix the problem with the help of the Adobe support. Here is how I do it on my MacBook Pro:

             

            1.  Mark your movie with an in point and an out point
            2.  Klick "Sequence" in the menu on the top of the screen and then choose the option "Render In to Out"
            3.  Let it render until the error appears
            4. Now you see on the green line in the timeline where it stopped rendering. Where the green line ends, it stopped rendering
            5. Make a right click on the clip where the green line stopped and choose the option "Render and replace..."
            6. Then a window appears, klick ok
            7. Now wait at let it render the replacement
            8. After it rendered klick on the same clip than before and choose the option "Restore Unrendered"
            9. Navigation with the finder to the place where your original footage is. Near the original clip should be a .mxf and a .xmp file. The name if these files start with the name of the original clip. Delete this .mxf and a .xmp files, so you don’t get a mess or your hard drive.
            10. Now try to export the part of your movie with that clip you just rendered and replaced. Best is, when you only render the part of the movie with this clip. In my case it works now and the error -1609629695 does not appear again in this particular part of the movie. 
            11. After this go back to part two and follow part 2 to 10 until there is no crashing clip anymore. 
              G
              GaryTajudin
              Participant
              May 23, 2023

              I just came to the same issue yesterday and spent all night trying to fix it because I'd have to start the video all over again. I tried everything and even tried to transfer everything over and render it on another computer to have the same message pop up. Extremely frustrating. I've tried to even uninstall and reinstall the software and same thing comes up. 

               

              MY SOLUTION: On the clip with the stabilizer effect and anything else. I need you to delete the effect and nest the clip first and then add the warp stabilizer in afterwards! And try rendering it out and tell me if it works! It worked for me. It's a bug. 

              Extremly frustrating that a paid software is having issues like this I've been having issues for years with adobe premiere. By this point I personally feel like that free app called CapCut is a better replacement for the time being with all these bugs! LOL just sad. 
              Adobe, respectfully PLEASE fix your software for the love of god this is just straight up sad that bugs constantly happens even on the most powerful work stations. 

                N
                Neyens5ED6
                Participant
                January 16, 2023

                Meanwhile it's 2022 and the problem still hasn't been solved, I can't render or export my project because of this exact same problem and none of the mentioned steps are working...

                  O
                  Oliver5FD8
                  Participating Frequently
                  January 31, 2023

                  Agreed still no resolution here. Trimming and cutting to get around this isnt acceptable Adobe.

                  Vidya Sagar
                  Adobe Employee
                  Vidya Sagar
                  Adobe Employee
                  May 17, 2017

                  Hi tobiasj,

                  Sorry for the Export issue.

                  Since a few weeks now I keep having issues with exporting my timeline from different projects on different PC's!!!

                  1. Is this happening with one sequence in different projects or with all sequences with Warp Stabilizer applied on it?

                  2. Have you tried to change the Renderer in Project Settings? File > Project Settings > General > Renderer to Mercury Playback Engine Software only mode & Export?

                  3. Have you tried to export one file with Warp Stabilizer applied from a new project?

                  Please provide us more information related to the issue.

                  Thanks,

                  Vidya Sagar

                  B
                  B.SchoemelAuthor
                  Known Participant
                  May 19, 2017

                  will someone answer???

                  megacinn
                  megacinn
                  Inspiring
                  May 21, 2018

                  I’m still having this issue and I’ve tried used encoder and no go.

                  Export Error

                  Error compiling movie.

                  GPU Render Error

                  Unable to process frame.

                  Writing with exporter: H.264

                  Writing to file: /Volumes/lidf_slow_fall_cinema/Danielle/Entire Ceremony.mp4

                  Writing file type: H264

                  Around timecode: 00:16:21:18 - 00:16:22:03

                  Rendering effect: AE.ADBE SubspaceStabilizer

                  Rendering at oExport Error

                  Error compiling movie.

                  GPU Render Error

                  Unable to process frame.

                  Writing with exporter: H.264

                  Writing to file: /Volumes/lidf_slow_fall_cinema/Danielle/Entire Ceremony.mp4

                  Writing file type: H264

                  Around timecode: 00:16:21:18 - 00:16:22:03

                  Rendering effect: AE.ADBE SubspaceStabilizer

                  Rendering at offset: 982.732 seconds

                  Component: EffectFilter of type GPUVideoFilter

                  Selector: 9

                  Error code: -1609629695ffset: 982.732 seconds

                  Component: EffectFilter of type GPUVideoFilter

                  Selector: 9

                  Error code: -1609629695

                  The only thing that works is eliminating WARP. I mean, how long does it take to fix this bug?

                  im running in a MacBook Pro, mid 2015 and using Premiere CC version v12 build 224.  The odd thing is that warp actually works on some clips but not all clips. This does not help because I really need to use warp and now I’m basically processing short two minute segments to confirm whether warp works or will it error out.


                  ... is it possible that you are working with 29,97 / 30p material (timeline). !?

                  In case ,yes, I have/had the same issue for a longer time and it got worst with the latest update (which I downgraded weeks ago).

                  My , ever working solution was , to find the, im the error message, mentioned clip.

                  That is easy in case the sequence starts at the very beginning of the timeline. If you have set in/out markers for rendering, the given timecode in the error is totally crap and misleading.

                  So, if you can determine the affected clip, trim the head and/or tail for around 1-2 frames (shorten the clip at the end or beginning for 1-2 frames).

                  In my case, it solves always the problem.

                  The reason behind is, that there is some miscalculation on the drop frame /non drop frame tc.

                  As I remember that causes in my case that around every 33sec in my sequence that clip with applied warpstabilizer which is at that very tc , will /was causing that same error as you described it.

                  Annoying.... the problem got worse with every version..in fact it still exist since CC15 but went totally useless in the latest cc18 release (only one of many reasons to avoid the use of premierepro 12.1.x).

                  maybe it helps in your case too.....

                    Terms & ConditionsAccessibility statement
                    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices