Skip to main content
A
anl46165065
Participant
June 26, 2015
Answered

Premiere Pro CC Encoding Failed A low-level exception occurred in: Lumetri Color (AEVideoFilter)

  • June 26, 2015
  • 47 replies
  • 92487 views

Trying to export video to DVD format (MPEG2-DVD).. It starts to render video "normally" up to 10-50 minutes.. Tried multiple times, changed video quality and changed output drive, always interrupting with same error code..

Is there something to do..?

- Encoding Time: 02:22:33

06/26/2015 09:40:48 PM : Encoding Failed

------------------------------------------------------------

A low-level exception occurred in: Lumetri Color (AEVideoFilter)

Export Error

Error compiling movie.

Unknown error.

    This topic has been closed for replies.
    Correct answer Kevin J. Monahan Jr.

    Hello,

    If you have a solution that you found, please return to the thread and let us know. We can only assume that you solved your issue. Typically, one will get these kinds of errors when you've exhausted system resources like VRAM, system RAM, or both.

    The solution or workaround is to use Software Only mode for the Mercury Playback Engine. You can also purchase additional hardware which may assist the job.

    Thanks,

    Kevin

    47 replies

    Show previous replies
    R
    radhap12982409
    Participant
    July 2, 2016

    I'm having the same issue - it's crashing every time I try to delete a vertex and click ''ctrl'' key! So frustrating! If anyone knows how to delete blue points on mask without this happening please share!!!!

    E
    Elbrusoid
    Participating Frequently
    May 18, 2016

    I managed to solve this problem the following actions. Created a new project and imported it in sequence where it was a video with Lumetri - eventually the error stopped appearing, just needs to be re-rendered

    E
    Eugene Epstein
    Participating Frequently
    May 18, 2016

    Nothing works with lumetri.

    In my case the solution is: delete lumetri + cut sequnce on one minute parts and render separately

    Please explain me what is a difference between performance and memory?

    E
    Elbrusoid
    Participating Frequently
    May 18, 2016

    By default, Premiere Pro renders video using the maximum number of available processors, up to 16. However, some sequences, such as those containing high-resolution source video or still images, require large amounts of memory for the simultaneous rendering of multiple frames. These sequences can force Premiere Pro to cancel rendering and to give a Low Memory Warning alert. In these cases, you can maximize the available memory by changing the rendering optimization preference from Performance to Memory. Change this preference back to Performance when rendering no longer requires memory optimization.

      Kevin J. Monahan Jr.
      Community Manager
      Kevin J. Monahan Jr.Community ManagerCorrect answer
      Community Manager
      May 16, 2016

      Hello,

      If you have a solution that you found, please return to the thread and let us know. We can only assume that you solved your issue. Typically, one will get these kinds of errors when you've exhausted system resources like VRAM, system RAM, or both.

      The solution or workaround is to use Software Only mode for the Mercury Playback Engine. You can also purchase additional hardware which may assist the job.

      Thanks,

      Kevin

      Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
        E
        Eugene Epstein
        Participating Frequently
        May 16, 2016

        Same problem! All the time the same "A low-level exception occurred in: (Lumetri Color)"

        GPU - GTX 970

        I've bought a license month ago.

        Any suggestions?? Or maybe i should go to MAC + Final Cut ??

        Kevin J. Monahan Jr.
        Community Manager
        Kevin J. Monahan Jr.Community Manager
        Community Manager
        May 16, 2016

        Hello Seg,

        Same problem! All the time the same "A low-level exception occurred in: (Lumetri Color)"

        GPU - GTX 970

        • Is Mercury Playback Engine GPU Acceleration enabled or not?
        • If so, does it work OK in Software Only mode for Mercury Playback Engine?
        • Are you using the current drivers?
        • What is your source footage and dimensions?
        • How long is your Timeline?

        Thanks,
        Kevin

        Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
          E
          Eugene Epstein
          Participating Frequently
          May 17, 2016
          • Is Mercury Playback Engine GPU Acceleration enabled or not?
          • If so, does it work OK in Software Only mode for Mercury Playback Engine?
          • Are you using the current drivers?
          • What is your source footage and dimensions?
          • How long is your Timeline?

          1. Doesn`t matter (same in both)

          2. All drivers is up to date (latest)

          3. 4K

          4. 200s

          i bought extra 8GB, so now i have 24Gb, waiting for results....

          Rustic Media
          Rustic Media
          Known Participant
          May 13, 2016

          Experiencing consistent Low-Level Exceptions and occasional Premiere Pro CC crashes with Warp Stabilizer applied to footage with Lumetri Color grades - no LUTs.

          27" iMac, Mid 2011, 3.4 Intel Core i7, AMD Radeon HD 6970M 2048 MB, El Capitan 10.11.14.

          Premiere Pro CC 2015.2 9.2.0 (41) Build.

          C300 footage (MXF) transcoded into ProRes 422.

          Mercury Playback GPU Acceleration (OpenCL).

          Workaround, switch renderer to Software Only & export directly from PP CC, do not send to Encoder standalone.

          Kevin J. Monahan Jr.
          Community Manager
          Kevin J. Monahan Jr.Community Manager
          Community Manager
          May 16, 2016

          Hi RM,

          Workaround, switch renderer to Software Only & export directly from PP CC, do not send to Encoder standalone.

          What is the source footage's frame size?

          What is the length of your Timeline?

          Have you applied these effects to most every clip?

          Thanks for more info!

          Kevin

          Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
          E
          Eugene Epstein
          Participating Frequently
          May 17, 2016

          What is the source footage's frame size? - 4K

          What is the length of your Timeline? - 200s

          Have you applied these effects to most every clip? Yes

          transformationmemphis
          transformationmemphis
          Participant
          May 6, 2016

          Another user with "A low-level exception occurred in: Morph Cut (AEVideoFilter)"  when running Media Encoder.

          Running Windows 8.1 64 bit all updates installed including vid drivers. 

          i7 3630QM  w Nvidia GTX 660M  24M RAM.

          Any progress on this?

          S
          Shai Schcolnik
          Participating Frequently
          March 11, 2016

          Well, Me too. Happening with morph cut.

          not only during render but also during normal work on the timeline.

          The weird thing is that I applied the cuts, continued editing a few more hours without any problem and then suddenly PP started crushing time after time

            S
            Silicon Pixel Glassworks
            Inspiring
            March 11, 2016

            ‌I've been working a lot with the lumetri effect with and without LUTs applied. I've found it particularly troublesome and had a number of crashes which for me is unusual in Premiere (Windows 10). I've also found that LUT support is a bit hit and miss. One set I was using just refused to output - the LUT was simply missing from the encoded footage but with no error messages etc.

            Paul.
            ckwaller
            ckwaller
            Participant
            March 2, 2016

            Anyone else experiencing this issue? Any movement on Adobe's front? i've discovered the Morph Cut function also appears to be affected by this, as well.

            ckwaller
            ckwaller
            Participant
            February 22, 2016

            I've been experiencing this issue ever since I installed the PPCC 2015.2 (9.2.0 (41) Build) update. I'm running OSX Yosemite 10.10.2

            My issue occurs during video editing -- every time I try to apply a LUT in the Lumetri panel, I receive the "low-level exception" message. I've dumped my preferences, cleared my cache, and even uninstalled-reinstalled the program, to no avail. Prior to the 2015.2 update, Lumetri and LUTs worked flawlessly and without issue.

            Any word on a potential fix from Adobe??

              Dennis Weinmann
              Adobe Employee
              Dennis Weinmann
              Adobe Employee
              February 22, 2016

              Can you share some detailed system specs + Premiere Project/Sequence settings (OpenCL,Cuda, Resolution, File formats etc)  ?

              ckwaller
              ckwaller
              Participant
              February 22, 2016

              Hi Dennis,

              My system specs are as follows:

              Project Settings:

              Footage came from a Sony HXR-NX5U Camcorder. Footage was shot @ 1080p30. Footage was transcoded via Adobe Media Encoder to DNxHD codec.

              Additionally, I revisited a previous (two-month old) project that I completed. This project was completed prior to upgrading to PP2015.2

              The project settings for this older project remain the same. However, the footage was captured on a Canon EOS 6D @ 1080p24. Footage was ingested into Premiere Pro natively. LUTs were added via Lumetri panel without issue. Upon opening up that project today in PP2015.2, I received the low-level exception immediately when trying to switch to a different LUT.

              LUTs for both projects were applied/attempted to be applied in the "Creative" panel of Lumetri.

              C
              chrisz55220373
              Participant
              January 4, 2016

              To anyone still having this issue. I wasn't so much able to remedy it, as I was able to work around it. If you export via Premiere, and don't send through media encoder, it seems to work without getting those low level exception errors (mine was always happening on Morph Cut).

              Hope this helps,

              Chris

              P.S. I'm on a Windows 7 machine using premiere version 2015.0.2

                A
                Adobetina
                Participant
                January 8, 2016

                Thank you so much Chris - this workaround was effective for me as well.  Exporting with same settings with Media Encoder queue gave me an output with intermittent glitches.  When I did the direct Export Media on the sequence in PP it looks great AND I didn't have to remove my lumetri color corrections (which was going to be my next option).  There are actually a couple threads following this issue and hadn't seen this solution before.  Thanks again!

                _Christina

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