Forum Replies Created

  • Ole Jessien

    March 20, 2012 at 12:54 pm in reply to: AE CS5 Mac stole my Export to WMV

    Hi Marco

    The short answer is: no.

    In AE you export a lossless and then you create the WMV via Quicktime.

    This should also have been obvious from reading the thread.

  • Ole Jessien

    May 23, 2010 at 2:14 pm in reply to: AE CS5 Mac stole my Export to WMV

    Wow. Thanks for some very fulfilling replies. I’m very impressed that I’m getting in direct contact with you the developers. That’s awesome!

    Just as suggested my current workflow is to first do a default render and then take it through AE CS4 for the WMV export (which btw allows me all the multipass settings etc. that I want).

    If adding WMV to the server is “feasible” then that would be a great solution… if that would give full access to the same settings that I had on export in CS4.

    Of course it would be brilliant to have all the quicktime plugins right there in export as usual.

    Seeing as I’m not a programmer I just don’t understand why a 64bit program can’t wrap around 32bit execution… Oh well 🙂

  • Ole Jessien

    April 6, 2010 at 9:04 am in reply to: Render to 1280×768 mpeg-2 problems (AE CS4)

    I actually never succeded in delivering as a .mov.
    After talking to the media bureau it was uncovered that the encoding needed to be either mpeg2 or wmv.
    .mov is as far as I’ve understood only a container.
    This means the you can practically have any encoding in a .mov. Only thing is that when you use an Apple .mov encoder you are ensuring that you’re only using compliant codecs in the .mov container.

    As Dave LaRonde points out in the first reply a standard PAL MPEG2 has a resolution of 720×576. I would suspect that Apple adheres strictly to this standard in the Quicktime encoder.

    In case your primary requirement on delivery is that it be .mov then try using the mpeg4 encoder in the quicktime options if you need to compress your end file as this will accept custom resolutions.
    If you have neither size nor codec requirements you could always export as the default .mov (See: https://forums.creativecow.net/readpost/2/950714 ) and send that to your client.

  • Ole Jessien

    June 9, 2009 at 7:47 am in reply to: Render to 1280×768 mpeg-2 problems (AE CS4)

    Oh and: This creates an .m2v file that you just have to rename to .mpg
    🙂

  • Ole Jessien

    June 9, 2009 at 7:46 am in reply to: Render to 1280×768 mpeg-2 problems (AE CS4)

    Hi again

    Since I’ve got it working here’s the exact settings I’ve used in Adobe Media Encoder to export an MPEG2 at 1280×768:

    Format = MPEG2 (from the drop-down list)

    Preset = Edit Export Settings

    Note: I have unticked “Export Audio” since my settings are for presentation screens.

    Export Settings – “Video” tab:
    Basic Video Settings
    Quality = 5
    TV Standard = PAL
    Frame Width = 1280
    Frame Height = 768
    Frame Rate = 25
    Field Order = None (Progressive)
    Pixel Aspect Ratio = Square Pixels (1,000)
    Profile = Main
    Level = High

    Bitrate Settings
    Bitrate Encoding = CBR
    Bitrate = 12 (Which was the target I had to meet)

    GOP Settings
    M Frames = 3
    N Frames = 12
    Closed GOP every = 0
    Automatic GOP placement = unticked

    Advanced Settings
    Left this untouched.

    I hope this helps someone 🙂

  • Ole Jessien

    February 10, 2009 at 10:01 am in reply to: Render to 1280×768 mpeg-2 problems (AE CS4)

    Hi guys.
    Thank you very much for your responses.

    I ended up rendering the file in AE as a quicktime movie (Animation, Best quality, 25fps). Which by the way is default “lossless”.
    I then used Adobe Media Encoder which very smoothly exported as an m2v.
    Now it just has me wondering how it achieved making it only 14MB as the source was 120MB… It’s a 10 second clip so it might be just right though…
    I tested the m2v in VLC and it played smoothly.

    Thanks for the help 🙂

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