Bug media encoder

Bonjour,
Je me permet de poster un message sur ce forum dans le but d'obtenir de l'aide... comme bon nombre d'entre nous je suppose!
Je directeur de production, et j'ai un problème avec Media encoder.
Lorsque je rentre dans les preset de configuration d'encodage, le logiciel plante.
J'ai déjà eu ce bug et mon directeur de post prod de l'époque l'avait résole en supprimant des fichiers de settings media encoder.
Il m'est impossible de le joindre et je ne sais pas de quel il s'agit.
Je me tiens disponible pour apporter plus de précisions,
Merci par avance,
Jeremy.
CS4 - Mac Pro G5

I meant to open the Export Settings dialog in AME after queuing from Premiere Pro.
So steps would be like following (the additional steps in step 5 and 6).
(1) highlight all the source clips in the project window
(2) press Ctrl +M - which opens up the export window
(3) select the format to export, in this case it was XAVC source converted to DNxHD
(4) press queue which opens up the Media Encoder with all the clips to be encoded with their new names and destination folder
(5) In AME, click the queued job. This opens up the Export Settings dialog. Do you see the correct timecode here?
(6) Close the Export Settings dialog.
(7) press the green button to batch encode.

Similar Messages

Media Encoder CC - Bug or just finicky?

I'm confused about Media Encoder, and hoping someone can help.
I have a short film that's primarily 4K ProRes augmented with some "flashbacks" that are 1920 by 1080 h264 files. All edits beautifully in my 4K ProRes timeline.
I have some Magic Bullet B&W corrections on the 1080 footage. On the 4K footage, I just have an overall grade in an Adjustment Layer (for now). I can play in Software Mode (CUDA won't work on my Retina Mac - separate thread!) at 1/4 resolution. The 4K stuff looks great, the 1080 pretty bad.
I've been outputting by matching sequence settings. The file is TITANIC, but looks great. I use that file to make various smaller files in APPLE COMPRESSOR. I find it better and more flexible (especially with cropping for 2.35, etc.) What can I say. All in all, the workflow works for me.
So here's the problem. Today I wanted to use In and Out to export a small section for music review with a colleague. No need to have a huge file, I just used Media Encoder in a Vimeo SD mode.
In the first attempt, the 1080 stuff oddly looked terrible. Just as it does when viewed at 1/4 resolution. To make sure everything was okay, I outputted that section at Matched Sequence settings. All good - the 1080 stuff had the Magic Bullet B&W look working great.
Then I tried again with the Vimeo SD setting. Only this time I checked Render at Maximum Resolution. Took FOREVER, but all good again. The 1080 stuff was fine.
Next I renendered "in to out" in my sequence (I hadn't done so previously - I was working "red line"). Output without checking Max Render Quality. Back to the horrible 1080 stuff.
Finally, I chose "use previews", but not max render. All good again.
So, at last a question. Does this make sense? I never before had to use either Maximum Render OR Use Previews to get acceptable quality with "device" settings. Is this a bug? Or related to my disparate picture sizes? Or something else? Thank you all!

[Moved to AME forum.]
I can see where this would be expected behavior.

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>"C:\Program Files\Adobe\Adobe Media Encoder CC\32\dynamiclinkmanager.exe"</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

Pixel Aspect Ratio bug in Media Encoder export

Having a weird bug in media encoder exports that I can't seem to figure out. I have a 1080p sequence with a mix of 1080p footage and PAL DV assets. The PAL assets have a pixel aspect ratio of 1.0940. When I format them in my Premiere sequence, I am able to scale them correctly and they look fine. When I export them directly from premiere to broadcast standards it's also fine.
However, when I try to export these sequences in Media Encoder via File->Export->Media-> Queue using the same exact settings (I'm using a preset), Media Encoder formats the PAL assets as if they have square pixels. Thus, half of the footage in my sequences gets horizontally "squished." Note that this does not happen for footage that natively has square pixels, such as my 1080p camera footage.
Has anyone encountered this bug? It seems strange to me that Media Encoder would treat items in a sequence differently that Premiere during export, I was under the impression they were using the same rendering engine... It's really a problem as I'm going to have to crank out multiple versions of this 48-minute film and not being able to queue those exports is going to be a huge headache.
Using latest version of CC 2014.1 (8.1.0).

Screenshot of Premiere Export (fills screen):
Screenshot of Media Encoder export: (notice the pillar-boxing)

Bug report: Adobe Media Encoder (CS5) has encountered an error (WinFile.cpp-759)

I have a 714 MB Xvid file that I want to split into smaller pieces. I have gone successfully through a similar process earlier with a larger Xvid file using the same version of Adobe Media Encoder (CS5). It appears that no matter which output video format I choose, the process crashes with the following error message shown in a new pop-up dialog:
"Adobe Media Encoder has encountered an error. [..\..\Src\Win\WinFile.cpp-759].
(Even the source program file line number 759 in the above error message is always the same, regardless of my chosen output file format.)
The only option available from this point onwards is the "Continue" button. When I click Continue the program terminates with the Windows program crash message "Adobe Media Encoder CS5 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. <Debug> / <Close program>"
My search for other similar problem reports revealed that some user(s) has/have experienced a very similar problem in CS4, but the source line number was slightly different in CS4. Both problems are probably caused by the same error in Adobe's software. The small difference in source line numbers is probably due to some (minor) and probably unrelated changes to this C++ source module (WinFile.cpp).
It might of course be the case that this particular input video file has some rare encoding or other embedded problem. However, the fact that I can view the video without problems using Windows Media Player does not support this theory.
Apart from this message board I could not find any other avenue to report this bug to Adobe (without paying for support - which I am obviously not going to do as this is clearly a programming bug in the software). Hopefully some Adobe developer responsible for Media Encoder maintenance will read this forum from time to time and would subsequently inspect the source module for any obvious defects. I could supply the source video file with which this problem can be reproduced at will.
Regards
Jouni Juntunen

OK, I've reported the bug in the linked location. However, I had to use "Creative Suite" as the application, because "Adobe Media Encoder" was not an available option.
Jouni Juntunen

Premiere, AE, Media Encoder and title bug?

I think I've run into a possible bug.
I'm editing Canon 7D material with my first clip in the timeline being dynamic linked to AE. On the videotrack above I got a title. Everythings is prerendered ( greenbar above timeline).
Exporting directly in Premiere ( with matched sequence setting ) works like a charm. Fast.
Exporting to Media Encoder works great until it reaches the title above my dynamic linked clip. The render speed drops incredibly.
When I redo this without the title it works in ME. So there seems to be something going on with titles above dynamic linked clips and ME.
Can anyone confirm this?

So, just to be clear, you're having a problem playing the sequence within Premiere when it reaches the embbeded After Effects file, or encoding the file through Media Encoder simply slows down when it reaches the portion of the timeline where the AE file is embedded? If it's the latter, then it's just a matter of the encoder having to process a more robust file. It's common when there's an embedded AE sequence, and/or when there are a lot of effects applied.

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.

Media Encoder issue or bug? 720p50 to 720i50

Can anyone confirm a Media Encoder issue, happening when converting progressive 50-fullframe (or 60 for ntsc) to 50-interlaced frames?
I tried to convert DVCProHD 720p50 clips to PAL DVD wich uses 576i50 (25 frames devided to 50 interlaced frames). The result was, that every second frame of the source clip was skiped, so I received a PAL clip in 25 full-frames (25p). And it didn't matter which field-order I choosed (upper/lower/progressive) - the result was always the same.
when converting p50 to i50 I would expect, that AME would convert these 50 full-frames to 50 interlaced-frames with the field order I choosed. For example Canopus Procoder is working this way.
Btw, I lost the link, where to report Premiere bugs to adobe. Can anyone post it, please?

See:
FAQ:How/Where do I report a bug?
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Premiere, Media Encoder and Flash Cue Points - bug?

I've been encoding a number of FLV On2 VP6 videos recently and using the new Media Encoder. For this project we need flash cue points (nav and event). I've discovered some weird things in Media Encoder - it's been duplicating cue points (or maybe the export from Premiere is buggy with cue points?).
I've seen the first couple of cue points getting duplicated with the first letter of the name capitalised and moved a frame on in time - very weird.
Anyone else seen this behaviour?
Paul.

OK, I think I've found out why - not a bug - user misunderstanding!!! (although tricky to find!)
Some of my source footage was created in After Effects. It turns out that there were a couple of cue points in the AE comp that had similar names to the cue points in Premiere - the AE comp was saved out to an AVI (with metadata enabled I think).
Premiere wasn't seeing this metadata and the cue points, but Media Encoder was (and it couldn't be deleted in ME - just kept coming back).
So - moral of the story - be careful with metadata!!!
I guess that Premiere should really show this embedded data though?
Paul.

Video/audio editing bug in Media Encoder

I have a large MOV file that contains multiple film
presentations, one after the other. They are separated by a few
seconds of dead air. I'm using Video Encoder's built-in edit tool
to slide to the end of a presentation and then export that to FLV.
Using my arrow keys, I can pinpoint the exact millisecond I want it
to stop.
However, when I export these to FLV files, audio (but not
video) continues to play for several seconds even past the point at
which I had set the cutoff.
I tried duplicating the same thing using Flash 8 Video
Encoder, and didn't have a problem. It only appears to be an issue
with Flash CS3 Video Encoder.
Can anyone duplicate what appears to be a bug?

Screenshot of Premiere Export (fills screen):
Screenshot of Media Encoder export: (notice the pillar-boxing)

A serious bug of render "PAL" timeline by "Media Encoder"

I use premiere cc2014 at PC/Mac, I find a serious bug when I complete a job in a "PAL" setup time line (720x570 25fps (PAL) aspect ratio 4:3), if i export to a mpeg 2 file with same setup to "Media Encoder", the out put file become a "4:3" Pillarbox file (left and right become a black bar). But If I export file without using "Media Encoder", the file is prefectly same as the timeline setup. Since I always output timeline(s) in "batch", so I must need to use Media Encoder. Please help to fix that bug. P.S., I have try in CS5.5, CS6, there is no that bug in Media Encoder.

Hi MRJay,
I had a similar issue only when using 3rd party plugin (Creative Impatience) that would go all catywhumpus on Encoder Queue outputs...it would mess with certain images or text that were not necessarily matching the project proportions (e.g. crop them, or ignore 1/2 of my Feathered Crop, etc.)
The solution was bizarre, and likely source-code default setting based...
After going to Media-->Export and when in the Encoder interface--before Queueing-- find a section on your timline with the scroll controls where the graphic is, make sure you are in Source Tab (top left), goto Crop Proportions; Use the drop down tab to actually set the Output dimension to what your sequence is (you won't have to actually export with this setting) and then switch to the Output tab. Does it now appear correct? That's it...undo the Crop Prop. and output normally. Hope this helps...

Possible Media Encoder CS5 BUG???

Since the Media Encoder has no "official" home that I could find on the forum I thought this would be the best place to post this since my videos are exported from After Effects. If it isn't the correct location I apologize.
Here's the issue:
When I encode an H.264 (.MP4) video from a .mov file with Media Encoder CS5 the Data Size and Data Rate attributes do not show up in the Apple QuickTime Movie Inspector. I can convert the exact same video with the CS4 version and it shows up. I've made sure I have all the same settings selected on both versions. I have noticed on the CS5 version there is a new Metadata button next to the "OK" button. I looked at all the properties in there and did not see any feature to enable data rate and data size as if those were metadata features rather than something QuickTime calculates. It must be something that the encoder includes onto the file after compression is complete. Otherwise, why would the Movie Inspector not display that information for only MP4's created with Media Encoder CS5? This is important to me because I put a lot of videos on the web and data rate is extremely important in this process. I've noticed the data rate I specify in the encoder is slightly off from the number I see in QuickTime so I consider QuickTime's number to be more accurate. It would be nice if you could view video properties with the Media Encoder like you can with QuickTime.
This is the setup I've tested on:
Worked
Windows XP AND Windows 7
Adobe Media Encoder CS4
QuickTime Player v7.6.7(1675)
Does Not Work
Windows XP AND Windows 7
Adobe Media Encoder CS5
QuickTime Player v7.6.7(1675)
The process I use each time I compress a video:
A .mov file is handed off to me by one of our "video guys" who uses After Effects
I import the video into Adobe Media Encoder CS4 or CS5
Apply my settings and compress the video
After compression has completed, I play video in QuickTime and view Movie Inspector.
Maybe I'm over looking the setting on CS5 to enable those two features. There's not a whole lot of documentation on this product. Any assistants would be helpful.
Thanks,
Eric

Tim,
Thanks for logging the issue and giving more insight! I tried to research what version of QuickTime I have but couldn't really find a definite answer. I'll take your word for it that I have the 32-bit version. It looks like there is a 64-bit version out there but only for Snow Leopard I think (QuickTime X). Not sure when that will make it to the Windows world if it is true.
If there was some type of "movie inspector" built into AME that would completely eliminate my need for QuickTime. But, I'm sure it would be much easier for you guys at this point to add those two changes to the process already in place that talks to QuickTime. I will definitely put in a request or two for features. I think AME is a great tool now and could also become much more.
If you ever need a tester for newer versions of AME, just give me a shout.
Thanks,
Eric

MEDIA ENCODER BUG??

whenever I encode individual clips the timecode is carried across as per the original source file, but when I export then queue a number of files they are all encoded with 00:00:00:00 timecode.

I meant to open the Export Settings dialog in AME after queuing from Premiere Pro.
So steps would be like following (the additional steps in step 5 and 6).
(1) highlight all the source clips in the project window
(2) press Ctrl +M - which opens up the export window
(3) select the format to export, in this case it was XAVC source converted to DNxHD
(4) press queue which opens up the Media Encoder with all the clips to be encoded with their new names and destination folder
(5) In AME, click the queued job. This opens up the Export Settings dialog. Do you see the correct timecode here?
(6) Close the Export Settings dialog.
(7) press the green button to batch encode.

Adobe Media Encoder (CS5) has encountered an error (WinFile.cpp-759)

I have a 714 MB Xvid file that I want to split into smaller pieces. I have gone successfully through a similar process earlier with a larger Xvid file using the same version of Adobe Media Encoder (CS5). It appears that no matter which output video format I choose, the process crashes with the following error message shown in a new pop-up dialog:
"Adobe Media Encoder has encountered an error. [..\..\Src\Win\WinFile.cpp-759].
(Even the source program file line number 759 in the above error message is always the same, regardless of my chosen output file format.)
The only option available from this point onwards is the "Continue" button. When I click Continue the program terminates with the Windows program crash message "Adobe Media Encoder CS5 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. <Debug> / <Close program>"
My search for other similar problem reports revealed that some user(s) has/have experienced a very similar problem in CS4, but the source line number was slightly different in CS4. Both problems are probably caused by the same error in Adobe's software. The small difference in source line numbers is probably due to some (minor) and probably unrelated changes to this C++ source module (WinFile.cpp).
It might of course be the case that this particular input video file has some rare encoding or other embedded problem. However, the fact that I can view the video without problems using Windows Media Player does not support this theory.
Apart from this message board I could not find any other avenue to report this bug to Adobe (without paying for support - which I am obviously not going to do as this is clearly a programming bug in the software). Hopefully some Adobe developer responsible for Media Encoder maintenance will read this forum from time to time and would subsequently inspect the source module for any obvious defects. I could supply the source video file with which this problem can be reproduced at will.
Regards
Jouni Juntunen

CS4 Adobe Media Encoder & FMLE are two different softwares - you can post your query here:http://forums.adobe.com/community/ame

Adobe media encoder in PP CS3

Hi there
I'm using Premiere Pro CS3, when I try to launch Adobe media encoder or Matrox media encoder, the program bugs. Any help? I'm very new in this field.
Thanx

Pull the Matrox out. Try with a standard project and likely your problems are solved.
Matrox cards are best used in a fashion they were designed for, as a doorstopper.

Bug media encoder

Similar Messages

Maybe you are looking for