Adobe Media Encoder bug with Cineform .avi

I encoded an HDV m2t file to Cineform intermediate in Sony Vegas. I added that file to Adobe Media Encoder's render cue. No matter what export format I choose, AME fails to recognize the source file's pixel aspect ratio of 1.33:1 and produces a horizontally squashed image.
Even the source window incorrectly shows the file as having a PAR of 1:1. Premiere Pro CS4 won't load the source file properly. I can import it into AE CS4. From there, I exported it to the same Cineform intermediate, and then it works fine in AME.
Why can't AME and Premiere Pro recognize the proper PAR in the Vegas-encoded Cineform file?

I'm not even sure if this qualifies as a "bug". The only thing at issue (if I understand correctly) is that AME is failing to recognize the PAR of the file. AFAIK, there is no "standard" for flagging PAR in AVI files (aside from DV footage, which can have simple boolean 16x9 flag).
Adobe has their RIFF headers -- but this is by no means a standard across the entire industry. There is no indication that your file contains any PAR information whatsoever.
If you open the file in Premiere, you should be able to right-click on the clip in the Project window, go to Interpret Footage and select the correct PAR of 1.333.
The problem is that the standalone version of AME does not have an "Interpret Footage" option to override PAR assumptions for AVI files, etc. that are added to queue. This is a good idea for a feature request for future versions of AME.

Similar Messages

  • Adobe MEdia Encoder Crashes with big files inputed

    Hello,
    There isn't a forum for the Adobe Media Encoder, so I thought this would be a good spot. I am an after effects and Premiere user who likes the idea Adobe seems to have of using the media encoder to cover all my encoding needs.
    My typical workflow, especially since these days I'm doing more shorter form animations, is to render out to a Quicktime Animation codec file as my main archive file. From there, output all the various different web versions, flv, etc from that core archive file. Since my projects usually aren't running more than 5 minutes, this leaves me with a nice 3 - 7gig file.
    Problem: I'm running CS4 and the media encoder crashes when I input files that are in this file size range. The program locks up when I push start que, and then eventually crashes. Works fine with smaller size files that are about under a gig.
    I can run a render out of after effects, which seems to be more stable. But I'd love to be able to use this great new tool.
    Here's my machine specs if it helps:
    PC
    Intel Quad Core Q9550 @ 2.83 ghz
    4gB RAM
    Windows Vista 64 bit ultimate
    All updates current for CS4 apps as of 01/30/08
    Running Adobe Media Encoder V 4.01.078
    Hard drives are nothing special. 7200 rpm western digital internal and external. I've tried all sorts of hard drive configurations, where the input is coming from, where it's going, etc. No difference.
    I have been experimenting with using Lossless AVI's as my "uncompressed" archive file. Works well, but same crashing with the Media Encoder.
    Also tried experimenting with frame size alterations during encoding, no difference there. Also, whatever the output codec is, be it FLV, H264, etc. no difference.
    Anyone have any thoughts or have experienced similar issues? I hope all my MAC friends aren't right, seems like all my attempts to streamline my workflow with this CS4 and beefy PC combo are crashing and burning.
    Anyone else feeling this pain, or have recommendations?
    Thanks,

    Thomas, thanks for your suggestions on Vista optimization. That Sheer Codec looks nice, but hard justify the cost when I've been working for years with essentially uncompressed codecs that work well. Will play more though to see if the cost would actually pay off in the long run though.
    In general I made a decision that it was too early to throw in the towel on my old uncompressed codecs. The Quicktime animation codec has always been for me the safest, most universally accepted, and most reliable "uncompressed" codec. It's always worked in the past, not gonna give up just cuz media Encoder CS4 has troubles.
    Mylenium, thanks for the reminder about the silly platform wars. I've always felt the same as you, but when I'm stressing sometimes the silly propaganda can get to me. Makes me forget that no matter what system ya got, it never works perfect!
    Here's an update. I have trying my best to learn more about the bug and have come to some interesting realizations. The AME does work with larger files, just not the larger files that I had been using at the current moment. Older files of mine as big as 20GB can be inputed into AME with fine results.
    This being said, it scratches out most of the RAM overload thoughts with AME.
    The difference with my current files that were causing AME crashes: larger than a few GB, came from AE, had the 1.21 pixel aspect ratio metadata.
    When I re-interpreted the file in AE into a square pixel aspect ratio, exported it, it was then successfully inputed into AME.
    I have read just now that there were changes in After Effects widescreen pixel aspect ratio interpretation in CS4. Can this change be causing problems in my AME. Not positive, but I'm now thinking after many days of testing that the bug could have its roots somewhere in this ball park.
    If anyone from Adobe is reading this, I would love any ideas you might have on this issue. In general, there is really no support for the Adobe Media Encoder itself. This is not good, considering how it is so necessary for AE and Premiere users like myself.
    Thanks,

  • Adobe Media Encoder - Issue with exporting file

    When I send a file to Adobe Media Encoder and I hit queue I get an error, "could not read from source file, please check if it has been moved or deleted".
    The source file location that the AME is trying to use is C:\Users\User Name\AppData\local\temp\file name.prproj
    Is this file location correct?
    Why is not using my scratch disk file?
    How do I change the file that AME is trying to use?
    I have not been able to export a video since I have purchased Premiere CS4.
    Any help with this would be greatly appreciated.

    If you want a quick work-around do not try exporting from Premiere, just save and exit the project after you are through editing.  Open AME and under File, select Add Premiere Pro Sequence, browse for your project file and click on it once--have patience Adobe's feedback here is lousy--your sequence will finally appear in the Sequence window, click on it and then click on OK.  Select your Format,.Preset and Output location.  If you want to tweak your settings just click on the Settings button.  Then hit Start Queue.
    Do you have the project on an external removable drive?

  • Premiere and Media Encoder CC with Cineform(converted files have static for audio)

    Hi there,
    using Media Encoder CC to convert 7D and 5DMKIII video files to Cineform .avi and all I'm getting at the other end for audio is loud static.  Video is fine but audio is corrupt.  Anyone run into this with CC?  I didn't have this problem before CC.

    Do you have the same problem with other AVI codecs?  What about non-AVI options?

  • Latest Update of Adobe Media Encoder Issue with C4D Source

    Updated Media Encoder to Build 8.0.0.173 this AM when the Adobe notification came through and it now refuses to encode any project with C4D source.   The issue is codec agnostic.   Tried with both C4D R15 and R16.  No joy.  Any clue?  Would like to roll back to the previous version but not sure that option is available within the uber-slick CC Adobe world.

    I'm confused. You say that you updated ths morning, but then you give the version number for the previous version (8.0), rather than the current version for AME (8.1).
    I just tried rendering and exporting an After Effects composition containing a .c4d scene file through AME 8.1, and it works fine for me on Windows and Mac OS.

  • Adobe Media Encoder Error with MPEG2 Formats [../../src/Command.cpp-2519]

    I am trying to use some of my presets using MPEG2 format and it is giving me this error: [/Volumes/BuildDisk/builds/ame602_mac/main/app/frontend/prj/mac/../../src/Command.cpp-251 9]. I try the system presets that use MPEG2 and I get the same error. I notice if I try to make a new preset, I do not even have the option to choose MPEG2. I only get MPEG4 or MPEG4 (Legacy). I am using AME 7.0.2; if anyone has an idea on why I can't use MPEG2 please let me know.
    Thanks,
    Mike

    Hi mboory,
    Please mention the exact version of Media Encoder CS6 that you are using and also the version of operating system. Please check the below link as well.
    http://forums.adobe.com/message/4402558
    Regards,
    Vinay

  • Adobe Media Encoder Streaming with Mac

    I really want to use a mac to broadcast internet radio. I
    notice that the streaming media encoder only seems available for
    PC. Am I missing something? I have Flash CS3 and other Adobe CS3
    software. Is there anything I can do to stream Flash Media from a
    Mac.
    I suppose I could use a Windows computer just to handle the
    stream, but how do I get the stream from the mac to the Windows
    computer if I do that.
    I'm planning on using a Streaming service for the actual
    streaming but I'm just trying to get it from my computer in the
    best possible way.

    how about connecting an audio cable form the mac to the pc?
    But seriously, it's a shame that FME isn't available to OSX.
    if you have an Intel Mac, you could use bootcamp or Parallels
    desktop (just an example) to run Windows apps on top of OSX (we've
    done this)

  • Adobe Media Encoder freezes with one second left

    Hi all,
    All of a sudden now, when I export from Premiere CS4 to AME, regardless of what codec I use, AME hangs with just one second left to go. It will not finish encoding, no matter how long I wait. When I hit "Stop Queue" the program itself hangs, and I have to "Force Quit" to start over.
    I have installed the 4.0.1 update for both Premiere and AME. Running on a Macbook Pro 2.5 GHz, 4 GB RAM. Anyone else have this problem and figured out a solution?

    Sounds like the empty timeline or premiere's 'black video' freeze issue.
    For some reason the encoder freezes when the timeline encounters any 'blank' frames. By blank I mean either an empty timeline, or any of the Premiere generated color mattes, title cards, bars and tone, etc. (if this is overlaid with 'real' video footage it does not seem to be an issue).
    So if your project ends with a fade to black, or some black footage at the end, that may be the culprit. Is this happening in your case?
    Solution: I've generated a black video file (i created and exported this in After Effects) that I have now laid on the first (bottom) layer of every Premiere project I start. I have a 5 second video file that I just stretch over the duration of the project before I render. This has solved the freeze issue for me. If you search the forum there is other mention of introducing opacity keyframes into your generated footage as another work around. I haven't tried this way myself, so I can't fully comment.
    Good luck!

  • Adobe Media Encoder won't start

    Not OP, but I have the same problem. AME just won't run. Double click, it's loading, I can see the process in Windows Task Manager but it just goes away again. Tried deleting that watch folder .xml but not working. Here's my spec from the FAQ:
    What version of Adobe Media Encoder? Include the minor version number (e.g., Adobe Media Encoder CS6 with the 6.0.1 update).AME CC from premiere cc 7.0.1
    What other Adobe applications do you have installed, and what application are you using Adobe Media Encoder with?Premiere Pro. Premiere Pro
    Have you installed the recent updates? (If not, you should. They fix a lot of problems.)Used creative cloud to update to latest version
    What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".Windows 7. All update patch installed.
    Are you using Adobe Media Encoder through a Creative Cloud Membership subscription?Yeah
    What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime".N/A. App won't launch
    If you are getting error message(s), what is the full text of the error message(s)?No error message
    Is the problem only occurring with a specific output format or encoding preset? If so, which one? If this is a custom preset not included with AME, then upload the preset file to a file-sharing site and provide a link.No.
    What were you doing when the problem occurred?Booted up the computer. Launch AME.
    Has this ever worked before?Yes.
    What other software are you running?Google Chrome
    Do you have any third-party codecs installed?Avid DNxHD, Cineform Studio
    Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU).Regular desktop
    Are you using Mercury Playback Engine GPU Acceleration in Premiere Pro?Yes.

    I have a problem like this:
    Anybody HELP?
    Process:         Adobe Media Encoder CC [16188]
    Path:            /Applications/Adobe CC/*/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
    Identifier:      com.adobe.ame.application
    Version:         7.2.0.43 (7.2.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [253]
    Responsible:     Adobe Media Encoder CC [16188]
    User ID:         501
    Date/Time:       2014-02-05 01:15:39.418 +0100
    OS Version:      Mac OS X 10.9.1 (13B3116)
    Report Version:  11
    Anonymous UUID:  7E5DC048-8DD8-5DA9-CFD0-539F29161D59
    Sleep/Wake UUID: D2BBCDCA-68C3-4C86-B34D-57E4C884FDD8
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    terminating with uncaught exception of type dvacore::filesupport::dir_create_exception: $$$/dvacore/filesupport/DirCreate=The directory '@0' could not be created. Please check the parent directory protection or permission rights.
    abort() called
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib                  0x00007fff8a1c2866 __pthread_kill + 10
    1   libsystem_pthread.dylib                 0x00007fff8998835c pthread_kill + 92
    2   libsystem_c.dylib                       0x00007fff8f10dbba abort + 125
    3   libc++abi.dylib                         0x00007fff95124141 abort_message + 257
    4   libc++abi.dylib                         0x00007fff95149aa4 default_terminate_handler() + 240
    5   libobjc.A.dylib                         0x00007fff9413c322 _objc_terminate() + 124
    6   libc++abi.dylib                         0x00007fff951473e1 std::__terminate(void (*)()) + 8
    7   libc++abi.dylib                         0x00007fff95146e6b __cxa_throw + 124
    8   com.adobe.dvacore.framework             0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
    9   com.adobe.AMEAppFoundation.framework          0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
    10  com.adobe.Batch.framework               0x0000000105c0a842 AMEBatch::Initialize() + 2194
    11  com.adobe.ame.application               0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
    12  com.adobe.ame.application               0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
    13  com.adobe.exo.framework                 0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
    14  com.adobe.ame.application               0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
    15  com.adobe.ame.application               0x0000000100056a38 main + 424
    16  com.adobe.ame.application               0x0000000100003f74 start + 52
    Model: MacBookPro11,3, BootROM MBP112.0138.B02, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.19f3
    Graphics: Intel Iris Pro, Intel Iris Pro, Built-In, 1024 MB
    Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (6.30.223.154.49)
    Bluetooth: Version 4.2.1f2 12982, 3 services, 23 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en0
    Serial ATA Device: APPLE SSD SM1024F, 1 TB
    USB Device: Internal Memory Card Reader
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: BRCM20702 Hub
    USB Device: Bluetooth USB Host Controller
    Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1

  • Adobe Media Encoder pausing rendering while working in Premiere Pro

    Hello everyone,
    So I am redering a video in Adobe Media Encoder and at the same time I am editing a new one in Premiere Pro.
    I noticed that AME is constantly pausing the rendering and did not know why. It turns out that while I'm editing a video in Premiere Pro, I am constantly pressing the space bar to start/pause the video I'm editing. While I do that, AME keeps pausing/unpausing the rendering. Somehow, pressing the space bar in PP has an effect in AME.
    I have no clue why it does that because the Premiere Pro window has the focus, not the AME one.
    Has anyone ever seen that?
    I use Windows 8 and Adobe CC.

    Hi Rallymax,
    Yes I do queue footage by having an Autowatch set up on the directories where the video is written to.  I rarely do a direct export unless testing new settings.
    Don't take this as gospel but I too had a feeling that GPU acceleration didn't happen with AME, only direct export.  Not sure where that came from, I did watch some of the recent Adobe TV Web Seminar's about new features of CC products etc, so maybe on one of those?
    I found this while trying to find out where I had seen it but it is from AMD site not Adobe so whether it's fully 100% correct I dunno:
    Adobe Media Encoder
    The Adobe Media Encoder (AME), with support for OpenCL™ and GPU acceleration, automates the production of multiple encoded versions of source files, sequences, and compositions in Premiere Pro CC. With the GPU-accelerated AME and AMD graphics technology, editors can quickly encode projects and output files for virtually any destination. AMD GPUs handle the heavy lifting, freeing the system’s CPU to perform other functions.
    I will try the same test as Jason, if I can find any AVHCD video and see what the results are.  Will be interesting.

  • Adobe Media Encoder CS5 doesn't work anymore (WHY? WHAT's WRONG?)

    The system I use is Adobe Production Premium CS5.
    I have often used Adobe Media Encoder CS5 started from the export of a film sequence in Adobe Premiere Pro CS5.
    On the 31st of December 2013 my computer crashed and dumped more or less at the end of a process of Adobe Media Encoder CS5. There was no complete output.
    Since then this program Adobe Media Encoder CS5 cannot start up anymore.
    It stops at the start-up saying that the program does not work anymore and that there will be looked for a solution. But then it finishes saying that it will be reported if a solution becomes available in the future.
    I have tried the following:
    - Run Adobe Media Encoder CS5 (exe) from directory C:\Program Files\Adobe\Adobe Media Encoder CS5 => same problem.
    - Stop security control AVG while not online with internet => run Adobe Media Encoder CS5 => same problem.
    - Reinstalled complete Production Premium CS5 suite => same problem.
    - Removed complete directory C:\Program Files\Adobe\Adobe Media Encoder CS5 and then reinstalled Adobe Premiere Pro CS5 => the full directory C:\Program Files\Adobe\Adobe Media Encoder CS5 with contents was there after the install, but subsequent running of Adobe Media Encoder CS5 => same problem.
    - Removed complete contents of D:\mediacache\database\Media Cache and D:\mediacache\Media Cache Files => same problem.
    What more can I do ??????
    I would be very grateful for a solution.
    Regards, Arie de Jong, Rotterdam

    Hi Jim,
    Thank you very much for the suggestions for a solution. First I considered
    re-installing Win 7 Pro, because I did not have a fall-back point
    predefined. So I could not try to reload a previous system environment. But
    for your information the following.
    Yesterday my son suggested that there could be some corruption in a control
    file of Adobe Media Encoder, because re-installing that program did not
    give a solution. Obviously that then would have to be a file which is not
    affected by a program re-install.
    What he then did for me is to remove directory
    Users\owner\ AppData\Roaming\Adobe\Adobe Media Encoder    (he actually
    renamed it to hide that directory for Media Encoder).
    Thereafter we ran program Media Encoder from Premiere. The result was that
    a new directory ......\ Roaming\Adobe\Adobe Media Encoder with proper
    control files was automatically generated and the problem was solved.
    Regards from Arie de Jong

  • No Sound When Converting to Cineform AVI with Adobe Media Encoder

    I've found that I totally prefer to convert my AVCHD files to Cineform AVI, it looks great and is much easier to edit for sure! I did it using the trial version of Neoscene but found I can do it via Premiere and the Adobe Media Encoder. so, I tried the later two.
    When I first tried with Neoscene I didn't have sound with the converted files. I tried to trouble shoot this in a couple of ways that were suggested online. The thing that finally worked was downloading and installing some ac3 thing...
    When I later converted using adobe media encoder it didn't have audio. I can't seem to find a resolve anywhere for this. It does however have audio if I do it through Premiere. But, that would be a tedious process to convert a lot of files through premiere, it would be profoundly easier using the media encoder.
    So, does anyone know how i can fix this?

    I haven't posted on the cineform website, I assume they want people to straight up buy their stuff and prefer people are ignorant to the fact they can do it through AME for free (provided they already have it). It's convienent for them that it is broken, encouraging people to buy their software... (assuming they think like this;).
    I don't know what HDLink is... I don't know what you mean by "the AC3 thing" either...
    Thanks for the prompt posting, I would love to know how to resolve this!!!

  • Adobe Media Encoder Fails to convert the H264 movs from may Canon 5D mark 2, to Cineform AVI's

    It fails no mater what codec settings I have tried.....forcing me to use the HD Link that came with NeoScene( Cineform)....Once converted by HDLink, the Adobe Media Encoder is fine transcoding the Cineform avi's to any format it normally works with.
    While not a huge problem--certainly I "can" always use HDlink to convert the mov's....I would like to get this fixed.....
    And then there is the issue of what should be the appropriate way to metalog when I dump 300 new clips into the system that were just shot.....Of course it is easy with the mov files, but really I would think they should all be transcoded to Cineform AVI's before doing anything...Thoughts?
    Dan Volker

    I'm not even sure if this qualifies as a "bug". The only thing at issue (if I understand correctly) is that AME is failing to recognize the PAR of the file. AFAIK, there is no "standard" for flagging PAR in AVI files (aside from DV footage, which can have simple boolean 16x9 flag).
    Adobe has their RIFF headers -- but this is by no means a standard across the entire industry. There is no indication that your file contains any PAR information whatsoever.
    If you open the file in Premiere, you should be able to right-click on the clip in the Project window, go to Interpret Footage and select the correct PAR of 1.333.
    The problem is that the standalone version of AME does not have an "Interpret Footage" option to override PAR assumptions for AVI files, etc. that are added to queue. This is a good idea for a feature request for future versions of AME.

  • Adobe Media Encoder CC 7.2.0.43 still crashes after beginning of encoding - bugs for months now!

    Adobe Media Encoder CC 7.2.0.43 is still crashing after beginning of encoding! In my case this bug exists for months now and Adobe is not able to get rid of its own programming faults! The user pays a lot of money for the license and doesn't get a functioning software! I spent days to get a solution now, but NOTHING of your suggested help works!
    This is my 'support' history beginning in AUGUST (!):
    Sent: Thursday, August 15, 2013 ...
    Subject: Bug Report
    Product: Adobe Media Encoder
    Product Version: CC
    Operating System : Windows 7
    OS version: Service P1
    Concise problem statement: Steps to reproduce bug:
    1. Go to Premiere Media Export
    2. Stating Media Export Parameters for ME
    3. Starting ME
    4. Define video title and path
    5. Start Media Encoder CC rendering
    6. ME states 'Preview not available'
    7. Rendering aborts after about 15 sec.
    8. Media Encoder CC crashes, no matter which kind of video! Every time.
    9. Direct 'Export' from Premiere CC is possible with all the same parameters, but CC AME crashes!
    10. Also installed Premiere CS 6 Media Encoder WORKS without any problems, but not the CC Media Encoder!!
    Expected results: Media Encoder CC WORKING. This is still my expected result as a paying customer!
    My steps to solve these problems (with Adobe's help) were / are:
    - Cleant every suggested media cashes.
    - Tried to render the sequences also without audio.
    - Tried to render as one pass.
    - Even if I try just to export ONE simple standard SONY PMW EX1 mp4 file which should never cause problems it chrashes, also without audio.
    - Also if I clean all preferences and caches before, EVERY file type crashes, no matter if I try to export a video or a still picture.
    - This is not happening in Adobe AME CS6 with the same files, but in CC!! CS6 still renders reliably with preview, but CC crashes without being able to show any preview.
    - Held the Shift key down while starting AME. This should reset preferences and so on...
    - Deleted suggested "7.0" directories as described in other forum posts concerning this topic.
    - Logged out of my CC account.
    - Deinstalled and reinstalled PPro, After Effects, InDesign, Flash, using Adobe Creative Cloud Cleaner Tool. All is the newest version 7.2.
    - Set GPU renderer to "Software Only".  Some video cards have issues when GPU is set to "OpenCL" or "CUDA".
    - Checked updates available for video driver. Latest is installed.
    - Turned off "Enable Native Premiere Pro sequence import" in AME prefs.
    - AMEEncodingErrorLog.txt doesn't have any content, not a single line.
    NOTHING WORKED OR HELPED!
    Windows Crash log:  WER3A92.tmp.WERInternalMetadata.xml:
    <?xml version="1.0" encoding="UTF-16"?>
    <WERReportMetadata>
        <OSVersionInformation>
            <WindowsNTVersion>6.1</WindowsNTVersion>
            <Build>7601 Service Pack 1</Build>
            <Product>(0x3): Windows 7 Home Premium</Product>
            <Edition>HomePremium</Edition>
            <BuildString>7601.18247.amd64fre.win7sp1_ ... private data erased here ...</BuildString>
            <Revision>1130</Revision>
            <Flavor>Multiprocessor Free</Flavor>
            <Architecture>X64</Architecture>
            <LCID>1031</LCID>
        </OSVersionInformation>
        <ParentProcessInformation>
            <ParentProcessId>9168</ParentProcessId>
            <ParentProcessPath>C:\Program Files\Adobe\Adobe Media Encoder CC\32\dynamiclinkmanager.exe</ParentProcessPath>
            <ParentProcessCmdLine>&quot;C:\Program Files\Adobe\Adobe Media Encoder CC\32\dynamiclinkmanager.exe&quot;</ParentProcessCmdLine>
        </ParentProcessInformation>
        <ProblemSignatures>
            <EventType>APPCRASH</EventType>
            <Parameter0>Adobe Media Encoder.exe</Parameter0>
            <Parameter1>7.2.0.43</Parameter1>
            <Parameter2>52a18991</Parameter2>
            <Parameter3>libmmd.dll</Parameter3>
            <Parameter4>12.0.12.2</Parameter4>
            <Parameter5>5073ba44</Parameter5>
            <Parameter6>c0000005</Parameter6>
            <Parameter7>00000000000bfd76</Parameter7>
        </ProblemSignatures>
        <DynamicSignatures>
            <Parameter1>6.1.7601.2.1.0.768.3</Parameter1>
            <Parameter2>1031</Parameter2>
            <Parameter22>4c50</Parameter22>
            <Parameter23>4c50fbaed87d7d2a6adc173c5da6a755</Parameter23>
            <Parameter24>28b8</Parameter24>
            <Parameter25>28b834131666732fe13a476b5fa8febe</Parameter25>
        </DynamicSignatures>
        <SystemInformation>
            <MID> ... private data erased here ... </MID>
            <MarkerFile>1043_ASUSTEK_G74SX_V20_WIN7</MarkerFile>
            <SystemManufacturer>ASUSTeK Computer Inc.</SystemManufacturer>
            <SystemProductName>G74Sx</SystemProductName>
            <BIOSVersion>G74Sx.203</BIOSVersion>
        </SystemInformation>
    </WERReportMetadata>
    Adobe team, I'm at my wits' end now and don't know how to continue. Can you help me?

    https://www.youtube.com/watch?v=oJ0hz9JkLgM

  • Problems rendering Every-line Composer texts with Adobe Media Encoder

    I find the text paragraph setting "Adobe Every-line Composer" a huge time saver when dealing with large amounts of text in after effects. I rarely have to do any manual tracking or line breaks to make it look good, as opposed to working with the standard Single-line Composer.
    The problem is that when I render through Adobe Media Encoder (which I'm forced to do since they removed H264-mp4 support from AE:s internal renderer) the text is treated like single-line composed text. So the final render doesn't look like my AE project.
    I've found two solutions to this problem:
    1. Render a lossless video file in the AE renderer and then compress it with Media Encoder. This takes more time and HDD space, and it doesn't allow me to continue working in AE while rendering.
    2. Only use Single-line composed text and make all adjustments manually, the old school way. This would not be a problem if I had not already used, and fallen in love with, the Every-line option.
    Is there anyone that can think of a third, and preferably better, solution?
    I use the CC 2014 versions of AE and AMC.

    No, the text doesn't animate at all. It's just a normal static text box. The text part is extremely simple. All animations are done in other layers and pre-comps, combined with pre-rendered 3D graphics from Cinema 4D, rendered as image sequences. My problem is a bug, plain and simple. Or perhaps you could call it a "lack of feature support" or an "incompatibility between AE and Adobe Media Encoder".
    My problem appears only when my AE project has text boxes with the "Every-line Composer" option enabled (press the menu button in the Paragraph window to find it), AND the project is rendered through Adobe Media Encoder, no matter which output format I use. I have no problems what so ever inside of after effects, or when rendering Single-line Composer text in AMC.
    So, the problem is that Media Encoder doesn't recognize Every-line composed text. Instead it changes it to Single-line composed text, messing up text tracking and line breaks.
    To clarify: the Adobe Every-line Composer is analyzing the entire text box instead of only the current line. That way it can automatically change the tracking of individual lines to better distribute the line breaks and build a better whole, avoiding those stray words on the last line for example. Extremely handy, if you could only render it.
    I never wrote anything about animating text or that the codec is related to the text problems in any way. AMC is the problem. The codec is only a secondary problem since its the lack of mp4 H264 support that forces me to use Media Encoder in the first place, instead of using the AE render queue as I did in previous versions of AE. I like many things about rendering through AMC, like being able to continue working in AE while rendering, but there are still way too many glitches. And of course, there's the inability to render flv-files in AMC CC 2014, and Adobe's inability to provide a solution other than "Use an older version of AMC". Flv is their own damn format for christ's sake.
    Well, enough rambling.
    To put it simple:
    Has anyone had a problem with "Every-line Composer" in combination with Adobe Media Encoder? Did you find a solution other than the two less-than-perfect ones in my first message?
    Thanks!

Maybe you are looking for