Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro AME export from PPro differs from preview on timeline?

  • AME export from PPro differs from preview on timeline?

    Posted by Jimmy Brunger on September 14, 2011 at 10:31 am

    Hi all,

    Trying to export some SD sized h264 QTs for client approval (of my 1920×800 timeline) and I’m getting some very odd results….

    Sequence in question has 720×576 DVPAL QT source footage scaled up and pan/scanned in my HD Cinemascope timeline.

    When previewed (using GPU acceleration – all yellow lines) it looks as expected.
    When SD letterboxed output is viewed from within AME it looks as expected.

    However the resulting 720×404 h264 looks TOTALLY different! Clip is scaled up 2x more than it should and in some cases the video is just displayed by torn black & white noise.

    I’ve tried exporting with and without ‘use previews’ and checking maximum render quality on and off…to no joy.

    Currently I have to export a full-size uncompressed QT and then scale it down via Quicktime Pro Player to an SD h264. Not and ideal workflow when I have 70+ sequences to o/p.

    Any thoughts guys?

    Thanks,
    Jim.

    ——————————-
    Production Premium CS5.5 – Mocha v1.5
    MacPro 3,1 8-core 3.2GHz / 32GB RAM / NVidia Quadro 4000 / OSX 10.6.8
    Decklink Extreme+ 3D / 3TB RAID-0 local / 6TB XServe + United Digital RAID on 10GbE

    Jimmy Brunger replied 14 years, 8 months ago 2 Members · 7 Replies
  • 7 Replies
  • Jon Barrie

    September 14, 2011 at 11:09 am

    Hi Jim,

    Using SD upscaled to 1080 and then pan and scanned is never a good idea, but if this is what you need to do then I suggest instead of outputting a FullHD version and then converting it, try this.

    As a test, create a new timeline that matches the dimension specs of your intended final clip. Then add the sequence of the edit to it so it is nested. Then right click on the sequence (as nested clip) and choose to “scale to frame” if this doesn’t fit the dimensions perfectly and I don’t think it will as 16×9 HD doesn’t actually fit to Widescreen SD (as it isn’t true 16×9). So you may need to tweak the scale setting instead.

    I think the value for FullHD down to SD is somewhere around 54.5%. Tweak it so it fits properly. 🙂

    Then find the area that looked really bad on the original export and find an in point, then hit Cmd+[ to set the work area in and Cmd+] at the playhead position to set the work area out.

    Then hit Cmd+M to export. You will see the yellow bar on the bottom left has wrapped around the set work area in and outs and should only render out this small ‘test’ area.

    Setup the export settings and Export or Send to the Queue. Let us know whether the result is any better. If so, you can set the export area (from the work area) to fit by zooming the timeline out all the way with the backslash key ‘\’ under backspace. When you see the whole timeline content double click on the current work area to reset the work area to the full length of the “edit”.

    Then export again (Cmd+M) and the last settings used will still be there for export. And proceed to export the whole edit this way.

    Hope it works out better for you. 🙂

    – JB

    Jon Barrie
    Adobe Video Solutions Consultant ANZ
    Jon’s YouTube Tutorial Page
    follow Jon with twitter

  • Jimmy Brunger

    September 14, 2011 at 11:44 am

    Hi Jon,

    Thanks for your speedy reply!

    Just tried what you suggested (new sequence @720×300 square pix > drop HD seq in + scale to frame size)…..

    I am now getting the ‘tearing’ problem in the preview of timeline. HOWEVER – when I select the motion tab in effect controls – i.e: select the clip’s transform handles – it looks as it should. As soon as I deselect Motion it goes back to nasty white noise!

    I then switched off Mercury GPU acceleration and then rendered the now red work area – all fine!?!

    So looks like a Mercury/CUDA/Quadro problem?

    Anyone had this before? The quadro has been amazing for me throwing multiple formats together and editing/scaling/messing with clips on the fly, so ideally don’t want to have to go back to rendering every time I want to view an output.

    ——————————-
    Production Premium CS5.5 – Mocha v1.5
    MacPro 3,1 8-core 3.2GHz / 32GB RAM / NVidia Quadro 4000 / OSX 10.6.8
    Decklink Extreme+ 3D / 3TB RAID-0 local / 6TB XServe + United Digital RAID on 10GbE

  • Jon Barrie

    September 14, 2011 at 11:58 am

    At least you get to see the “issue” in the timeline now. And that you can export decently with Mercury in Software Mode. The GPU Acceleration forces all colourspace into Linear which can cause some visual problems where blurs etc come into play. Thankfully there appears to be a work around.

    However…

    The resolution you are outputting to is non standard, perhaps you have found a bug that hasn’t been tested before! Great! Seriously, that’s a good thing. File a bug report to adobe with as much detail regarding clips format codec export seq settings etc so they can replicate it and hopefully get to a fix.

    Link here:
    https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

    – JB

    Jon Barrie
    Adobe Video Solutions Consultant ANZ
    Jon’s YouTube Tutorial Page
    follow Jon with twitter

  • Jimmy Brunger

    September 14, 2011 at 12:17 pm

    Will do! Thanks for your help Jon.

    ——————————-
    Production Premium CS5.5 – Mocha v1.5
    MacPro 3,1 8-core 3.2GHz / 32GB RAM / NVidia Quadro 4000 / OSX 10.6.8
    Decklink Extreme+ 3D / 3TB RAID-0 local / 6TB XServe + United Digital RAID on 10GbE

  • Jimmy Brunger

    September 14, 2011 at 12:29 pm

    Bizarrely I’ve just gone back in to PPro to recreate the problem with GPU on and it’s not doing it now!?!

    However I am now getting a ‘Error compiling movie. Unknown error’ message when trying to export from AME again!

    IT just gets weirder…..

    ——————————-
    Production Premium CS5.5 – Mocha v1.5
    MacPro 3,1 8-core 3.2GHz / 32GB RAM / NVidia Quadro 4000 / OSX 10.6.8
    Decklink Extreme+ 3D / 3TB RAID-0 local / 6TB XServe + United Digital RAID on 10GbE

  • Jon Barrie

    September 14, 2011 at 12:41 pm

    Alright. Open the project. Go to preferences under premiere pro.

    Select media, the click clean cache.

    Then quit premiere pro. Wait a minute for all the bg bits to close and relaunch PPro.

    If you see the conforming on the bottom right building with the yellow bar let it finish before operating any further. Shouldn’t take long. Once its done attempt another export.

    Cheers JB

    Jon Barrie
    Adobe Video Solutions Consultant ANZ
    Jon’s YouTube Tutorial Page
    follow Jon with twitter

  • Jimmy Brunger

    September 15, 2011 at 2:56 pm

    Had to restart machine aswell, but all working now – even the problems I initially had!?

    Contrary GFX card methinks….

    ——————————-
    Production Premium CS5.5 – Mocha v1.5
    MacPro 3,1 8-core 3.2GHz / 32GB RAM / NVidia Quadro 4000 / OSX 10.6.8
    Decklink Extreme+ 3D / 3TB RAID-0 local / 6TB XServe + United Digital RAID on 10GbE

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy