WARP STABILIZER & EXPORT FAILURE

Report · May 17, 2017

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!!!

Report · 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

Report · May 17, 2017

hi,

thanks for the fast response.

1. this is happening with different projects, differenc sequences, differen computers. So in general this is happening. Some footage hast Warp Stabilizer & Lumetri, some only Lumetri. Transitions like "Film Transition" seems to be a big issue too, but when i delete them the problem just moves to another place in the project.

2. I haven't tried Software only, as rendering takes forever and that is not the solution for me. As I am working on different PC's with different graphic cards, this can't be graphoc card related too.

3. exporting with Wrap Stabilizer works fine on single clips....

the strange thing is, I am editing and exporting and all works, and from one minute to the other it then doesn't work anymore.

I try everything... renaming, different drives, different PC's but once the bug is there, I have to re-apply all the effects! So now I am saving a edit with NO effects as a safety... but still... imaginge re-adding all the stabilizers and lumetris to a 30min edit with tons of corrections!!! this is inacceptable.

PS: Premiere CC2017 11.0.2 (47), BUT I had the same issue with the new update too. I just re-downgraded because of GH5 files not playing back... but THIS is a whole other topic.

Report · May 19, 2017

will someone answer???

Report · May 19, 2017

Best is to contact support:

support

Select Creative Cloud to begin with not Premiere.

FAQ: How do I contact Adobe Support? |Adobe Community

Report · May 19, 2017

that's not going to help... because the support via chat can't do anything... this is a major BUG that others are having too!!!

Report · May 19, 2017

I have to agree with the OP. I get a very similar error fairly regularly when exporting through AME. Mine is "Error code: -1609629690" which isn't identical, but pretty close. And it's under the same circumstances: trying to export h.264 with accelerated effects applied to the timeline. Remove the effects OR change to "Software Only" and the export works. The latter is insanely slowly, of course. The former is useless because I want the effects applied.

Something has been farked up with the MPE since around December or so. This is either due to a change w/Premiere and AME, or something NVidia introduced with a driver change last year. Either way, it's obnoxious and the last bit of my brown hair is turning grey due to it.

Report · May 29, 2017

Hi jasonvp,

Please change the following setting in Adobe Media Encoder Preferences & try export.

Adobe Media Encoder Preferences > General > Preferences > Uncheck Import Sequences natively.

Queue the export again from Premiere Pro & try export.

Thanks,

Vidya.

Report · May 30, 2017

Adobe Media Encoder Preferences > General > Preferences > Uncheck Import Sequences natively.
Queue the export again from Premiere Pro & try export.

That appears to be helping, at least from my limited (so far) testing. Thanks Vidya.

Report · May 31, 2017

That appears to be helping, at least from my limited (so far) testing. Thanks Vidya.

I spoke too soon. It's still not working; I'm going to back-grade and try some older versions of Pr.

Report · Jun 09, 2017

Hi,

no doesn't work for me either...

Report · Dec 15, 2017

I have been having the same problem for a while now, has there been any progress on finding a solution?

Report · Dec 17, 2017

Hi lauras80404938,

Sorry for the inconvenience. Could you please elaborate the issue with system specifications?

Instructions: FAQ: What information should I provide when asking a question on this forum?

Have you tried exporting using both Premiere Pro & Media Encoder?

Is there any error message? If yes, share us a screenshot.

Thanks,

Vidya.

Report · 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.

Report · May 21, 2018

... 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.....

Report · Jun 13, 2018

Thanks for the tip, megacinn! This worked great.

Report · Nov 28, 2023

this seems to be the fix for this problem, I looked through the sequence and found 1 empty frame between the clips. Once this was removed, it rendered fine with no errors.

Report · May 23, 2017

Adobe??? What is the matter???!!!

Report · May 29, 2017

Hi tobiasj,

I am sorry for the delay in response. Have you tried all the steps in this article?

How to fix issues that cause errors when rendering or exporting

Please let us know.

Thanks,

Vidya.

Report · Jan 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...

Report · Jan 31, 2023

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

Report · Jan 31, 2023

Interestingly I just managed to find a work around. I am using After Effects Compositions in my PP timeline. I removed the Warp Stab from PP and applied it to the AE comp in AE. I did also change it to 'no movement' rather than 'smooth' but I dont think that made a difference. Anyway it exported fine! So for me its either a clash between PP and AE or direct problem with PP that I havent come across when stablising before.

Hope this helps.

Report · 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.

Report · Jun 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:

Mark your movie with an in point and an out point
Klick "Sequence" in the menu on the top of the screen and then choose the option "Render In to Out"
Let it render until the error appears
Now you see on the green line in the timeline where it stopped rendering. Where the green line ends, it stopped rendering
Make a right click on the clip where the green line stopped and choose the option "Render and replace..."
Then a window appears, klick ok
Now wait at let it render the replacement
After it rendered klick on the same clip than before and choose the option "Restore Unrendered"
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.
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.
After this go back to part two and follow part 2 to 10 until there is no crashing clip anymore.

Report · Jul 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.