Skip to main content
Participant
October 13, 2018
Question

Error Compiling Movie Error Code -1609629695 Premiere Discussion

  • October 13, 2018
  • 1 reply
  • 570 views
  • CPU: I7 7820X 3.6 Ghz
  • MOBO: MSI X299 M7 ACK
  • RAM: 2x16GB DDR4 2666 MHZ (32GB)
  • OS: Windows 10 Home
  • GPU: EVGA Nvidia GTX 1080
  • HDs:
    • Windows 10 on Samsung 970 EVO NVMe M.2 500GB
    • Adobe Products on separate Samsung 970 EVO NVMe M.2 500GB
    • Footage on external G Drive USB-C 150mbs

This thread is to resolve the increasingly common Error Compiling Movie Error Code -1609629695.

  • Footage (typically): 1080p SLR - 6K R3D
  • FX (typically):
    • Sapphire Glow
    • Sapphire Distort
    • uni VHS
    • Scaling 1080p/4K/6K footage
    • Transition Overlays (1080p/4K)
    • Lumetri Color
    • AE Dynamic Link with Rotoscoping and additional motion graphics

In my experiences the most common issue for the error code is Lumetri Color, Scaling, and sometimes S_Glow will cause error.

Attempted Fixes

  • Switching to CPU rendering only (some FX require GPU so this is not a reliable fix)
  • Restarting System
  • Reinstalling all Adobe Products and Plugins
  • Creating New Sequence
  • Creating New Project file in Different Directory

I like to keep my work intact and not be held back creatively because of exporting/rendering issues, so I only adjust my work slightly.

Only Solution:

  • Export in very small sections
    • If multiple clips being used in one frame export sections in 1 second - 5 second intervals
    • If less FX being used I usually export in a 30 second - 1 minute section
    • With all pieces I put on separate sequence
    • Export one NO-COLOR master file
    • Import this file and color, then export final
  • These steps above also require many system restarts, I have had projects that have had 20 pro res uncolored files on a sequence. Meaning I had to restart my computer 20/30 times, export 20/30 times, just to get ONE file I can color without issues.
    • Side note: usually works after system restart, then when system encounters error, requires restart to operate correctly again.

Starting this thread for others to share their system specs in relation to issue, share other solutions, and further pinpoint this issue. I've seen it occur on clips with lots of VFX at 4K/6K level, and also 1080p with minimal FX. The error has a wide range but typically applies to those that use VFX/layovers/rotoscoping/motion graphics in their videos.  Interested to see what you have all encountered! 

Final thought: After this issue being prevalent for 2-3 years now, I really feel it is on Adobe to provide a real solution. I have found countless threads and posts about this issue over the last few years, it's time for a real solution no??

This topic has been closed for replies.

1 reply

Ann Bens
Community Expert
Community Expert
October 13, 2018

If the error shows up one needs to fix what ever is on the timeline at the given time in the error message.

It can be anything: faulty clip, transition, audio, 3rd party software, you name it.

Delete clip from timeline and project.

Import, put it on the timeline and do the effects again.

If that does not help export the clip as an intermediate clip (e.g. CF) and put that on the timeline.

Participant
October 13, 2018

Thanks Ann but these answer is too generalized. As I wrote before, I can cut the video in very small segments, without having to do any of your suggested methods, and still get the file I need with the work I have done without altering it.

Ann Bens
Community Expert
Community Expert
October 13, 2018

louiel55374853  wrote

Thanks Ann but these answer is too generalized.

Yes but it works, I get my file out of the door.