Skip navigation
getho
getho
Currently Being Moderated

rhyme or reason with rendering still images

Jul 20, 2011 4:43 PM

I've got a project that ends with a zoom in on a still image.  the image is sized so it can be rendered via the graphics card.  It plays back fine (in realtime yellow render bar), but when it comes to export it keeps crashing the enocder with an "unknown error". The file exports but its missing the section with the image.  To test I expoted just that section, and it exported most of it except the last few seconds.

 

I tried rendering the work area and it crashed premiere at frame 3218 of 3333

 

Sometimes still images seem to cripple premiere.  What could be going on here, and how can I make it reliable?

 

BTW the still image is nested, it has an animated gausian blur and opactiy change, and then this layer is stacked on itself twice - one with a blur, opacity and screen layer mode and once with blur , opactiy and multiply and masked.

3391 Views   9 Replies   Latest reply: getho, Aug 19, 2011 10:44 PM
 
Replies
  • davidbeisner2010
    Currently Being Moderated
    1. davidbeisner2010,
    Jul 21, 2011 8:44 AM   in reply to getho
    Report

    How big is your image? I recently did a wedding slideshow and wanted to do some zoomed-in pans across some of their engagement pictures, so used pictures sized around 3k on a standard 1920x1080 sequence. It crashed AME's encoder every time as soon as it hit that first big picture. I downsized the first big picture, tried again, and it crashed on the second big picture. I downsized all of them and redid my pans and zooms, and it exported fine. Didn't get quite the same look that I had wanted cause the pics were smaller, but it worked.

     
    |
    Mark as:
  • getho
    Currently Being Moderated
    2. getho,
    Jul 28, 2011 7:43 PM   in reply to davidbeisner2010
    Report

    I'm still getting this issue (thanks david, but already downsized them. Current one thats crashed premiere is 3500x1500), and besides up until a week or so ago it was exporting OK.

     

    Is the graphics card use for the final render?  Is it worth switching off the cuda stuff?

     

    Also the behaviour is inconsistent - sometimes if wil lmake it throught to the end (or near it), sometimes it'll crash as soon as it gets to the still

     
    |
    Mark as:
  • getho
    Currently Being Moderated
    3. getho,
    Jul 28, 2011 8:27 PM   in reply to getho
    Report

    I just cleaned the media cache, renamed the old media cache folders, copied the sequence and pasted it into a clean new project. and it paused for ages at roughly where it crashed, then completed.

     

    So not sure what worked out of those, would love to hear opinions

     
    |
    Mark as:
  • getho
    Currently Being Moderated
    4. getho,
    Jul 31, 2011 7:59 PM   in reply to getho
    Report

    And came back to it this monring after noticing a sync issue and I get

     

    2011-08-01_125712.jpg

     

    hard to stay calm and collected with this number of errors and flaky behaviour.  Would really appreciate some suggestions as to what might be the route cause, or how I can go about ascertaining that.

     
    |
    Mark as:
  • Todd_Kopriva
    Currently Being Moderated
    5. Todd_Kopriva,
    Jul 31, 2011 11:56 PM   in reply to getho
    Report

    As this document suggests, toward the end, you should perform the general troubleshooting steps when you get the message "Error compiling movie. Unknown error.".

    http://kb2.adobe.com/cps/906/cpsid_90670.html

     
    |
    Mark as:
  • wonderspark
    Currently Being Moderated
    6. wonderspark,
    Aug 1, 2011 12:32 AM   in reply to getho
    Report

    If you also have After Effects, you might want to try using that instead. I did a three month timelapse with 70,000 stills (plus or minus a few hundred) that were 4928x3264 and had no problems. I was able to zoom, pan and layer stills upon stills for blur masks, effects and so on.

     

    I tried using Premiere first, but I only got about four days into the timelapse before the system choked on it. Importing images as a sequence in AE solved all my problems, and allowed me to export one massive video clip with close to 100 layers (at 4928x3264 resolution, by the way) which then imported into Premiere CS5 with no problems.

     

    I only have 16GB of RAM, but at the time I also had three 7200rpm drives in a RAID0 stripe (separate from my OS drive) and I think that helped a lot.

     

    I should also add this was not using my GTX 285, but rather my ATI 5870, which seems to work better in After Effects.

     
    |
    Mark as:
  • davidbeisner2010
    Currently Being Moderated
    7. davidbeisner2010,
    Aug 1, 2011 5:13 AM   in reply to getho
    Report

    I'm thinking one or more of your images are still too big.

     

    Try duplicating your timeline (so you don't lose any work) and then press A

    and hold down Shift and click on your first clip. That should select all

    clips on all layers. Then right click on the first one, and select "Scale to

    Frame Size." If you've already used that command, selecting it again will

    turn it OFF for all layers you turned it on. (If you've not already used

    that command, then ignore the next bit because it will have worked). If you

    have already used it, right click a second time and select "Scale to Frame

    Size" and it will turn it ON for all layers. If that export works, then you

    know you've got an image too big somewhere.

     

    Also if you render as mpeg and not H.264, you'll be able to watch through

    you're failed export until you hit the frame that killed it, which will tell

    you exactly where your problem is. Mpeg doesn't require a full render to mux

    the video and audio together to give you your finished .mp4 file.

     
    |
    Mark as:
  • getho
    Currently Being Moderated
    8. getho,
    Aug 19, 2011 8:25 PM   in reply to davidbeisner2010
    Report

    thanks for suggestions, I'm locked into using premiere for these projects, yes I'll use AE for my own timelpase stuff.

     

    I dont know how the images could be too big - they play back in realtime!  Surely if they play in realtime they should be able to be rendered? They are 3,500 pixels wide.1.5 ish MB jpegs, using adobe RGB colourspace.

     

    The helpfile led to this document:

    http://kb2.adobe.com/cps/822/cpsid_82252.html

     

    full of general system tweaking stuff.  I'm sure its all helpful, but not immediately so.  I know exectly what image is causing the crash (i export to FLV, which also seems to give me a viewable file right up to the frame that caused the crash).  I'm currently looking at a frozen progress box for a completely different project.

     
    |
    Mark as:
  • getho
    Currently Being Moderated
    9. getho,
    Aug 19, 2011 10:44 PM   in reply to getho
    Report

    in desparation I switched off the mercury playback engine, and rendered a test avi (instead of FLV). That worked. (but OH so slowly)

    So I rendered a test FLV. Which also appears to be working as I type this.


    So I think I can safely say its an issue with the graphics card.  Next question then is:

     

    Can I disable the mercury playback features just for rendering? (ie is there an "off switch" in the export settings, or do I have to switch it off in project settings each time?

     

    edit:

    final postscript. update to most recent drivers (280.26) makes no difference.  Rendering with mercury off takes about 5 times as long

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Incoming Links

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