Skip navigation
Currently Being Moderated

Render always fails

Jun 18, 2013 6:05 PM

Tags: #error #premiere #export #render #cc

I'm trying to render a project of about 1 hour long, and it always fails.

 

If render from Premiere Pro, I get a dialog box that just says:

"Error rendering project

unknown error"

 

If I try to render from Adobe Media encoder, I get tthe following logs.

 

 

 

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

- Encoding Time: 00:03:54

06/18/2013 05:32:42 PM : Encoding Failed

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

Export Error

Error compiling movie.

 

 

Unknown error.

 

 

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

- Encoding Time: 00:03:59

06/18/2013 05:52:11 PM : Encoding Failed

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

Export Error

Error compiling movie.

 

 

Unknown error.

 

 

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

- Encoding Time: 00:08:08

06/18/2013 07:54:40 PM : Encoding Failed

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

Export Error

Error compiling movie.

 

 

Unknown error.

 

 

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

 
Replies
  • Currently Being Moderated
    Jun 18, 2013 8:35 PM   in reply to alraz.exe

    The problem with Unknown Errors is that their cause is unknown.  Without knowing a cause, we can't really provide a solution.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 18, 2013 10:00 PM   in reply to alraz.exe

    Try rendering small segments. Perhaps 10% of the timeline each time. That might lead you to the section of the timeline that is causing you the problem.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 19, 2013 8:42 AM   in reply to alraz.exe

    Try it without that.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 19, 2013 9:50 AM   in reply to alraz.exe

    I would try in a sample project with a small video file.  If that fails, you can post a link to that sample file - we can take a look and see if we can determine the cause of the failure.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 19, 2013 8:43 PM   in reply to alraz.exe

    I've had no trouble rendering several of the Lumetri Looks so far on two different machines, applied both to the clips directly and to ALs, using both the MPEG I-Frame codec and the DNxHD codec.  I've also had no issues exporting the effect under any circumstances.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 19, 2013 8:46 PM   in reply to alraz.exe

    Downloading now...

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 19, 2013 9:38 PM   in reply to alraz.exe

    Rendered fine here, and yes I'm using nVidia.

     

    Max Render Quality won't do anything but slow you down when using GPU acceleration.  I turned it off before rendering.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2013 5:55 AM   in reply to Jim Simon

    Not correct!

     

    Lets go through two examples that show the difference here:
     
      1. A HD clip in a SD timeline with scale-to-framesize and accelerated 3-way effect
     
      CPU: Gaussian low-pass sampled with bilinear
      CPU MRQ: Variable-radius bicubic
      GPU: Lanczos 2 low-pass sampled with bicubic
      GPU MRQ: Lanczos 2 low-pass sampled with bicubic
     
      In this case the MRQ setting will only affect CPU based renders.
     
      2. A HD clip in a SD timeline with scale-to-framesize and a non-accelerated twirl effect
     
      CPU: Gaussian low-pass sampled with bilinear
      CPU MRQ: Variable-radius bicubic
      GPU: Gaussian low-pass sampled with bilinear
      GPU MRQ: Variable-radius bicubic
     
    Because scale-to-framesize happens before effects and there is a non-accelerated effect, here the scaling will be done in software during a GPU render. During a GPU render the MRQ setting will thus apply to any software rendering done as part of the GPU render, determined on a segment-by-segment basis.
     

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2013 7:07 AM   in reply to Harm Millaard

    OK, yes...there may be situations where rendering falls back to the CPU and MRQ will help.

     

    In this case, that didn't apply.

     

     

     

    Because scale-to-framesize happens before effects and there is a non-accelerated effect, here the scaling will be done in software during a GPU render.

     

    What makes you think that?

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2013 7:23 AM   in reply to alraz.exe

    Not sure it's a bug yet.  Given the other issue, it may just be something wrong on your machine.  Finding someone else with AMD graphics to test would help.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 26, 2013 1:51 PM   in reply to alraz.exe

    Hey, I'm having the same problems when I apply Lumetri Looks to clips and then render out with gpu acceleration I get the exact same error messages you do. I am using an AMD FirePro V7900, a cadilac in the graphics cards world. So this is a definte bug.

     

    I never had this problem in Speed Grade CS6 but I hated having to export from Pr to Sp, then back to Pr and Export again for En and render yet again to IMG files. Adding Lumetri Looks to Pr was a great idea and a big time saver. When I heard Adobe was optimizing Pr for AMD cards I was real excited. But this glitch really slows down my work flow again. If Adobe could add a patch for this it would be great.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 2, 2013 3:16 AM   in reply to rexomus

    Im getting the same error with nvidia 680

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 2, 2013 11:49 AM   in reply to Tony Hulten

    Tony: Because the error is generic and provides no pointers to the cause of the problem, the fact the you hit the same error means almost nothing. In other words, a variety of issues can lead to the same error message. Therefore, it's best to treat each case separately. Once enough details are on the table, it may turn out that your case is a dead ringer for a known scenario.

    So I suggest that you start a separate thread and provide as much detail as possible.

    One point to clarify right out of the gate: are you exporting a sequence or rendering it within Premiere? If you're exporting, then you'll probably be better off posting on the AME forum rather than Premiere's. Regardless, this page for AME will be a better guide to what information to provide than PPRO's: http://forums.adobe.com/thread/1011883.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 7, 2013 1:07 PM   in reply to alraz.exe

    DId you ever find a resolution to this alraz? AMD FirePro M5950 and I am running into a very similar issue. I'm exporting a sequence from Premiere Pro CC using the Sepia Lumetri Look.

    If I do a project of less than 1 minute it will render at but the video usually gets garbeled after 45 seconds or so. If the project is more than 1 minute long it does not usually complete the render or if it happens to I will gradually lose all video clips with the effect applied to it after 1 minute and be left with a nice bright green screen.

    These wonderfully helpful "unknown error" things are a joy to track down.

     

    EDIT: Found some notes pertaining to render Max Bit Depth and Max Render Quality. Trying those options now...

     

    Message was edited by: JesseYost

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 7, 2013 1:45 PM   in reply to JesseYost

    Sadly, I never found a solution

     

    Up to this day, I'm still unable to use the lumitry filter in premiere

    I've changed the video card (from Radeon HD 6970 to Radeon HD7990), the motherboard, the cpu (from AMD to higgher level AMD), windows (from 7 to 8) but still nothing seems to work

     

    Looks like a problem with Premiere itself and not my computer.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 7, 2013 1:58 PM   in reply to alraz2

    I might be misstaking but I think the culprit for me was bad gpu drivers.. But I have nvidia, they came with an update and things was running again. Maybe you can try an older version of the drivers to your gpu.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 7, 2013 2:35 PM   in reply to JesseYost

    The only solution I found is to stop using lumetri effects in PrePro.

     

    The problem is Adobe claimed that PrePro CC was developed for AMD graphics cards. Sadly, that hasn't proved true. For whatever reason Adobe hasn't made this issue a priority or haven't found a solution.

     

    It's annoying that Nvidia cards work fine but AMD do not. If I were AMD I would be very angry.

     

    How come Andrew Kramer from Videocopilot can make a plugin for Ae that fully exploits any graphics card render engine(both AMD and Nvidia) yet has no issues but Adobe can't make one effect work with AMD cards?

     

    I know one thing for sure; we don't have the full story.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 7, 2013 2:39 PM   in reply to alraz.exe

    I wonder if this is even in Adobe's bug list...

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 7, 2013 3:24 PM   in reply to alraz2
     
    |
    Mark as:
  • Currently Being Moderated
    Oct 7, 2013 3:30 PM   in reply to Jim Simon

    Submited

     

    Hope they actually read that

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 7, 2013 3:31 PM   in reply to alraz2

    They do read them all.  Doesn't mean you'll get immediate or even timely satisfaction, but they do read them.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 1, 2014 1:43 PM   in reply to alraz.exe

    Hi

     

    here is a quick update:

    I manged to workaround this bug by changing the audio codec before exporting.

    If you use MPEG for audio instead of AAC, the render should succeed. The only problem now would be that Windows Media Player will refuse to play the exported file.

     

    However, Media Player Home Classic plays it just fine.

     

    I hope someone at Adobe is reading this and works on figuring out what part of the AAC codec is conflicting with the Lumitri effect.

     

    Regards

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 1, 2014 1:51 PM   in reply to alraz2

    Another quick update:

     

    By selecting AAC as audio format and AAC+ Version 1 as audio codec, I was able to make it work too.

     

    AAC+ Version 2 also worked, but in my case, it introduced some weird artifacts in the sound and also made windows media player refuse to play the file.

     

    So, you may want to give both options a try and see if they work for you.

     

    Adobe, please work up on this and help is fix it!

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points