Bugs in AME 4.0.1

Every working day i'm discovering more and more bugs in AME 4.0.1
It doesn't really crash very often, but sometimes produces unexpected (bad) results. I often get 4 to 5 exactly same output files (with suffix _1,_2,_3,_4...) from one source, red random blocks on the output mpeg when exported from a timeline that contains ~60 swf files, misproportional "crop" effect if i use resizing in AME, sometimes the project loads for encoding too long - about 30 minutes while in premiere it loads in a minute, AME sometimes doesn't save the output directory.
Low quality small resolution output is the final and the most important issue for me. The logic shows that if you have a project in HD and you want to get SD from it then the downscale should be of very high quality, instead the quality decreases... gets blurred and undetailed. "render at maximum quality" doesn't helps at all, only slows down everything 4 times. yes, i have tried to make SD sequence, put HD sequence inside it and scale it down to 54%. but all my crop effects were messed up after this. The quality turned out better (more detailed) but still far from perfect.
I'm getting these errors on seperate workstations, all of them are Vista x64, quad core, 8 gb ram, AME 4.0.1
There were more errors but i can't remember them right now ;)
Any solutions, bugfixes in the near future?
p.s. why still no jpeg image output?

Hi Patrick,
it happens inside the validation context (page 4316), but not within regions (page 4651) or items (page 4311).
Concerning the other item that i scrapped, i understood why i was puzzled:
initially i didn't define the item as "required" in the settings, but i added a not null (conditional) validation for two items in two distinct regions (displayed alternatively). Then i turned one of the items into required, without deleting the not null validation.
At this point i saw a messages telling me that "2 errors occurred" but only message was showing inline with the item and i thought the missing one was in the other hidden region. However i later realized that having a not null explicit validation rule and a required condition on the same field causes this situation where just one message is shown inline, but two errors are reported in the notification area.
Flavio
http://oraclequirks.blogspot.com

Similar Messages

Found a major bug in AME 6.0.1 - Anyone else experiencing this?

When exporting media from Premiere 6.0.1 on a Windows 7 64bit machine with an I7 Quad core with Hyperthreading and 16GB of Ram with NVidia Cuda card (Mercury Engine Acceleration enabled) I encounter an issue where AME hangs. I can export media fine under all but one circumstance. If the media has no "Accelerated" effects added, I can export either directly in Premiere or queued in AME with no problems. As soon as I add any ACCELERATED effects to a clip, whether it's rendered entirely or not, I can no longer export the clip in AME, yet it will export just fine in Premiere. Upon attempting to export in AME, it looks like it starts, though I see no preview of the export and the remaining time indicated just keeps climbing very quickly. A clip that will export with accellerated effects in a matter of seconds in Premiere will climb to hours remaining in AME. If I click 'Stop' on this export in AME, AME just hangs (not responding) and I must close it entirely.
This happens with various types of files exporting to any number of different codecs. The only way I can get the file to export properly with the accelerated effects in AME, is to switch the Mercury Engine Playback to Software (Cuda disabled) in Premiere first, and then encoding takes longer. Never encounted this in CS5 on the exact same machine.
One other small bug I found, is that if I create a preset with given settings for exporting having first unselected "Keyframe every 'X' frames" under the advanced settings in the video tab, when I later select that preset, the box next this setting is rechecked, despite it being unchecked when creating the preset. Also, sometimes I notice this box rechecks itself even if I just make changes under the audio settings tab.

I use the GeForce GTS 360M - of course, not a supported card, though using the CUDA hack, so guessing most people will attribute it to this. Though did not have this issue with CS5. Found someone here with the exact same problem, though with an officially supported card:
http://www.indiev.org/2012/premiere-pro-cs5-5-workarounds/
Looks like I will just have to use this work around, by rendering my timeline first with MPE CUDA enabled, then disable it, select "keep previews," then export - at least for any clips with accelerated effects.
Not entirely sure why it would matter what the preferences are set to in Premiere when sending an export to AME. Oh well. Maybe a future update will fix this.
If I didn't travel so much, would simply build a desktop with a supported card. My Asus G51JX laptop with 8 logical cores and 16GB of ram is sufficient for the work I do, though I know some people may chime in here and say I need a system with at least 24GB of ram and a minimum of 17TB of HD space in various raid arrays.
Anyways, if anyone does find a solution, please let me know. Thank you.
-Sam

Is there a bug in AME CC 2014 re Queued items and headless premiere pro instances?

Hi,
Last night I had a render out of three sequences. All three sequences had the exact same first 7 minutes, and then a different final 4 minutes (internal corporate communication video). Output files were H.264 at 480p, 1.5mbps, VBR 2-pass, Source was a mix of AE dynamic linked compositions and dnxhd 720p.
Machine: Mac Pro (mid 2012) 3.2 Quad, 6Gb RAM (I know it needs more). ATI HD 5770 GPU.
First item took 3 hours, second item took 6 hours, third item took 9 hours. CPU wasn't taxed all the way at all. I know I need more RAM for this machine (in a corporate environment it isn't the easiest of things to get), however it should have been very similar render times for all three videos (the final four minutes are very similar in composition).
What I noticed in activity monitor was separate PProHeadless instances for each item queued, and they weren't shut down after the resulting item. Is this expected behaviour, and shouldn't it either use the same instance, or shut the instance down after the corresponding item completes?
Thoughts?

Yes, AME was working properly before. It seems to have happened after I installed the very latest update to AMECC14, however. I'm not sure if that's what did it in though.
This is what I'm seeing – "Presets" isn't even a folder, it is an alias file. Could that be my problem? Will AME re-create those files if I just erase all of the "8.0" folder's contents and re-launch AME? I'm confused, because I assumed uninstalling AMECC14 and doing a fresh re-install would do the trick, but maybe not.
Here are my Adobe folder permissions, Adobe Media Encoder folder's permissions, and the 8.0 folder's permissions. I am seeing Read & Write permissions for my username, but for "everyone" it says "Read Only" – could that be an issue as well?
Thanks so much for your help MMeguro!

Importing m4v files in AME fails....help?

Hi,
I have a problem that I have been unable to solve after months of trying. I'm desperate for an answer or any help someone could provide.
I am using Mac Handbrake (Version 0.9.5 x86_64) to covert a few unprotected DVD's to .M4V (with video Codec: H.264).
I am then trying to bring these files into AME CS5 (Ver. 5.0.0.402 64-bit) to convert over to an .FLV or .F4V file for the web. When I bring these files into the AME, no matter how long the videos are (typically 5-15 minutes long) it is showing the imported video as 3 seconds in length. And when I go to render the .FLV file it renders, but only the 3 seconds.
Just for giggles I thought I would try the same thing in an older version of Adobe Flash CS3 Video Converter -- it had no problem importing the .M4V files and outputting the .FLV files at their full lengths.
Obviously, I would like to be able to use the new AME CS5, but have just been frustrated as all can be.
One additional point, when using Handbrake and using a different setting (Codec MPEG-4) the videos are recognized by AME CS5 at their full lengths, however the video quality is poorer.
Is there an issue with H.264 and AME CS5?
Any help would be greatly appreciated.
DMASH

What specific settings are you using in Handbrake? (Screenshots of the settings dialogs would work well to communicate this.)
Can you post a sample of the H.264 output from AME that we could try?
AME should be able to import the H.264 file. There could be a problem with the file Handbrake is creating, there could be a problem with your installation of AME, there could be a bug in AME, or it could be something else entirely.

Rendering Quicktime using H264 BUG confirmed - LUCKILY there's an easy work around

I thought making this a thread might help more people. Basically when you export media from Premiere with the intent on making a 'Quicktime with H264 or Sorenson' file. Adobe Media Encoder RESETS the bitrate you manually entered when it starts up.
Once you set it you never think to recheck it. This only happens when export from Premiere not when you import a project or use AME as a standalone which is why it worked fine for some people and not others.
Brian Dombrowski figured it out here's what he said. Thanks Brian this helps a lot. I'm glad there;s a way to make it work right now there's alot of uses for h264 quicktimes especially for web use. Anyway here's Brian.
"Brian Dombrowski - 7:51am Dec 5, 08 PST (#11 of 13)
I've seen the same thing this week for a client that requested some HD video to be FTP'd in QuickTime H.264 at 15mb. There is a *bug* with AME in CS4 with the bitrate setting for QuickTime H.264. No matter what you set it too, it keeps getting reset to 1000kb (yes 1k bit per second) resulting in low quality video and small .mov file sizes.
Here is the workaround I found:
1) In Premiere Pro CS4, Export-Media to get in Media Encoder and set to your QuickTime Format and then go down to Video tab to set h.264 codec. Scroll down to the bitrate settings and check set bitrate, you'll see it defaults 1000kb. Change it to something higher, like 15,000. Then hit OK button.
2) When AME opens up, you'll see your job in the queue. Click on your job on the Preset column where it says "Custom". This will load up a new window with the encoder settings again. Go down to Bitrate Settings again in that window and notice the bit rate has been reset to 1000kb. This is the problem (bug in AME.) If you change it here on this page, and hit OK, and then your bitrate settings will hold true in AME. Start the job queue and verify the generated .mov quality is as desired.
I guess what is probably happening is that when PP CS4 launches AME, AME resets the codec settings. Adobe can send me some free store credit for finding their stinking bug. I need AE anyway."

In Premiere File - export - media.
Export setting pop up. First choice is FORMAT: (here you pick Quicktime)
There's only 5 presets no matter which of the 20 or so codecs you pick so you have to set everything yourself. Under the Video tab there's a drop down menu called VIDEO CODEC: (here you pick H264 or sorenson)
I'm only talking about quicktime .mov files your screenshot has you using the flv format not quicktime. So it shouldn't be a problem for you.

PP & AME Renders AE Clips Incorrectly

Hello, I've run into a problem I can't seem to resolve and think it may be a bug with AME or with QuickTime. I have a series of animated titles rendered from AE at sequence resolution in the Animation codec. When I bring them into PP and add them to my sequence they all play correctly. However, when I render the sequence, one of the transitions turns blue. The rest render correctly.
This occurs when rendering the sequence in the .Mov container format with the Animation, Motion JPEG, or ProRes 422 codecs, but not when I create an MP4 file through AME or use Dynamic link to send the sequence to Encore.
I've included screen grabs from QuickTime showing the original (warm sepia) version and the AME rendered version (blue).
I've encountered this problem on both a MacBook Pro (2.33 GHz Intel Core 2 Duo) running 10.6.5 and PP CS 5.5 and a Mac Pro tower 2 x 3.2 GHz Quad-Core Intel Zenon running 10.6.5 and CS 5.5.
Any help you can provide would be greatly appreciated.
Thanks,
Jay

Dennis,
Thanks for your advice. I've deleted the cache files, rendered everything in the work area and exported a couple of versions. The problem isn't resolved, but at least we have some more information to troubleshoot.
The timeline is built at 1024x768 30fps (primary output is digital projector). If I export the clip at 1280x720 the blue doesn't crop up. When I export at native size 1024x768, or half resolution 512x384, the blue appears.
Opening it in QuickTime 7 doesn't help any. I can see the blue clip in QTX, QT7, AME's preview window and in a H.264 version exported from Sorenson Squeeze 6.5.
In PPCS4, I had a similar problem with certain clips if Maximum Render Quality was checked. It doesn't seem to have a bearing on this clip as I get the blue shift with and without Maximum Render Quality Checked.
What's really puzzling to me is that the four transition segments (three of which render correctly) are generated from the same AE comp. I simply turn on and off the necessary layers and render the segment I need. If it was a problem with the AE comp or project, I would think the problem would occur consistently between all four clips.
Lastly, the clip previews correctly in the PP timeline.
What do you suggest as a next step? In the meantime, I'm going to try and replace the affected clip with a direct link to the AE comp and see if that helps.
Best regards,
Jay

AME renders incomplete output MPEG2 files from my h264 footage

I'm trying to crrate Mepg2-DVD files for output to dvd, from canon DSLR footage, but somhow AME does not render the whole work area an loses the last 30-40secons of the clip on export.
Any help?
MY AME settings are : Codec : Mainconcept Mpeg Video - quality 5
Tv Standard : PAL
Frame Rate : 25
Fioeld order : progressive
Pixel aspect ratio stanard 4:3(1,094)
Bitrate encoding : VBR Two Pass
Min Bitrare 3
Target bitrate: 3.69
Max bitrate : 4
GOP settings : m Frames 3
n Frames 12
Source range : work area
Working on an 3.5ghx i7 an a gtx 670 for cuda ( with the ammended text file for enabling cuda on this card)
MPE with CUDA acceleration turned on.
This happens in both 1 pas an 2 pass vbr, but not when I export to h264 ....this seems to be a bug in AME! Is it possble though? How long has these codecs been around!! ?

Ok, I see this is a Quicktimeplayer mistake .... somehow Quicktime player does not play the wholf of the file. It all seemed fine once I opened it in MPEG streamclip! ^&%$%*$ Half a day waste thinking AME is broken and then it ends up being Apple ... Their software is just getting WORSE!

Adobe Media Encoder CC outputs black video

I've been having problems with AME for quite some time, such that I don't even use it except for very short videos. If I export video in AME, the first half is good, but the second half is black video only. If I export directly from Premiere Pro, all is well every time. It's most frustrating to be paying for a product monthly that does not work, so please overlook my frustration. Has anyone successfully gotten a discount from Adobe for the failure of software to work as advertised?
Here's another issue I have: there is no way to file a bug for AME as it is not available in the drop down list on Adobe's support site. (How is that even possible?) I would have reported a bug long ago if this was available.
Has anyone seen this? I've tried many different things the last few weeks but have given up using AME altogether. This week I have a little time to troubleshoot.

Ask in the AME/ Premiere forum and by all means provide some solid technical info - system specs, sequence settings, render settings, footage used. Nobody can help you without that.
Mylenium

Can't keep the original size of the video (Resize Video option is stuck on 640 x 480h)

I am importing .mp4 files set at 874 x 480h. Somehow AME makes the output size 640 x 480h, which significantly vertically compresses the video.
I tried so many different ways of uncheking the Rewsize Video box, checking it again and specifiying 874 x 480h. Best I got is 874 x 480h with black borders left and right and the actual video to be rendered in output tab is still at 640 x 480h.
It seems that Resize Video option is stuck on 640 x 480h and can not be changed.
Is there some bug in AME I have to work around? Or is it a problem with the original video? If the problem with an original video what exactly do I ask my client to rerender it like if I already receive it in 874 x 480h, can view/play it in this size, AME recognizes the original video to its true size, shows it to its true size if 1x1 pixel preview is selected. However will show a distorted 640 x 480h version if Aspect Ratio Corrected Preview is selected (even with the Resize Video box unchecked)?

Hi Marion,
Thanks very much for your message. I have downloaded that program and it's definitely handy for examining the details of the original file. You mentioned in your message about not having to recode the file - The file I'm editing is originally from a Q3 Zoom video recorder and I can use their in-built software (handyware) to trim the file - this doesn't recode the file and so the file size just reduces by the required amount. Unfortunately there is no facility to crop the file with this software - I've looked for other software that would allow cropping without having to recode the file but I haven't found anything suitable for a simple procudure like this - do you know of any software that allows you to crop a file without recoding? Thanks.

Downgrade from CS5.5 to CS5

Is it possible to downgrade and use CS5 to open files saved in CS5.5? I think there is a major bug in AME CS5.5.
Thanks

Yes, you can open them.... at least simple projects, anyway. It'll ask you to save a new copy of the project with the _1 attachment, like it does going from CS5 to 5.5... I've successfully gone back to CS5 with a 5.5 project when I had issues with 5.5 giving me a successful export with corrupted video drivers (since fixed that problem, and it wasn't a problem in 5.5... it was a problem on my system).
However, as shooter says, I wouldn't recommend it as best practice, and I wouldn't be surprised if some of your bigger projects would end up getting corrupted or missing bits of information...

Media encoder is killing my file

I have a windows video file that works fine when I run it.
I used the Adobe Media Encoder CS5.5 to try to convert it into flv format.
It attempts to load the file, but gives up, saying that the file has a bad header.
After that, the file HAS a bad header, and no longer works.
Luckily I had back up copies so I was able to replace the 12 +megabyte file.
I can reproduce the problem every time, using my back up copies.
The file is on line at http://www.slaithwaitemoonraking.org/images/movies/MoonRaking2.wmv
Other files encode to .flv with no problem, so it must be a problem this file alone.
Regardless of a file error, Media Encoder should not make changes to a file just by accessing it.
Has anyone else had this problem?

Can also confirm this on Windows7, although it doesn't happen when I import in into AME CS6 on the Mac. One clue might be the non-western characters that show up in the Inspector when I open it in Quicktime X, see attached screenshot.
I'll log a bug about AME altering the header of this file on Windows, we shouldn't be doing that...

Audition CC's huge export time? (please help)

I just posted this on a much older thread but I worry it will never be seen. I have recently switched over to Audition from Logic. I have designed a soundscape that is approximately 1 minute and 10 seconds long, using about 30 tracks many of which are loaded with effects and automation. I accept that huge export times are exacerbated by things like that, however I still feel like the current time is unprecedented.
This is becoming a serious problem for me. We are about to churn out about 100 - 200 different videos with slightly varying soundscapes and the export time (and inability to queue exports) from Audition will cripple the workflow.
For anyone reading or planning to reply (which would be hugely appreciated!) I press 'Export' and it shows the little dialog box saying that it is exporting, however it stays on 0% for a huge portion of the entire process, and during this time I can see that no file has been created in the destination folder.
Also, I was very keen to queue exports in Media Encoder, so that even if the waiting time was huge at least they could be stacked, however I can't find a way to do this, so the exports must be done one by one. I have obviously searched for a media encoder functionality, assuming I must be missing something, but can't find anything. If anyone at least knows how to do this I would appreciate the information SO much, as the ability to queue the exports up together would really help.
Thanks so much,
Ben.

There's currently a bug in AME CC with 2-pass VBR H.264 encoding.
I'd say to try the export again, using the exact same settings, except change "2-pass VBR" to "1-pass VBR". See what happens.
As the Adobe staff member states in the referenced thread, 2-pass (even if it was buggy) really does nothing to improve the rendered video. It then surprises me that many of their included presets (including the YouTube ones) are all set to 2-pass.

OS X - Copy Paste doesn't seem to Work Here!

Hi...
In AME, I strive to set an output folder. I DONT want to have to write the same name all over again
So I try to copy and paste.
So I click the output path which opens an OS X Browser. I click New Folder and hit Apple+V to paste.
Nothing happens. I have to right-click in the name field and choose PASTE to do that.
Wonder if it is my machine only or a BUG !

Whether the bug is in AME or OS X is rather inconsequential. It affects the AME experience, therefore Adobe needs to be aware of it. If our investigation shows that OS X is the cause of the problem then we can send it to Apple via their developer bug report system.
In this case, I believe it is a bug in AME. Rather, it is an unimplemented feature; it feels like the copy/paste code just never got hooked up to this dialog. Doing so is apparently the responsibility of the app developer, though I also see the argument that Apple should enable it by default. To verify that such behavior was possible, I compared AME's behavior to the same repro steps in After Effects. Copy/paste works with the similar dialog in After Effects, therefore there is reasonable expectation that we can make it work in AME.
(FWIW, that means that yes, I did file this bug already. And no, me filing the bug internally is not a good excuse for you not to do the same if you haven't already. Seriously, folks, bugs filed by customers carry more weight than bugs filed internally. It's proof that our customers are affected by the problem. That doesn't necessarily mean the bug will get fixed faster, but it does give it a better chance.)

AME Quicktime H.264 Field Type Bug ?

No matter you choose Lower or Upper Field First in the Field Type of AME Export Settings, the rendered video is Progressive.
Could anyone confirm this is a bug please ?
Regards

Thank you Colin and Brian for your testing.:)
I am used to using a small program called "Mediainfo" to see the property of a video and it shows the rendered video is Progressive no matter I set the field type to upper or lower field. I was misled by the Mediainfo program this time.
I admit this is my mistake for not confirming the video property with another more trusty programs like PP or AE.
Best Regards

Dyn Link BUG with AE and AME

Do This
1) Drag a clip into AE
2) Crop beginning of clip in comp by i.e. 200 frames
3) adjust inpoint work area
4) hit Adjust Comp to Workarea
5) save Project and open AME
6) Drag over the compostion to AME
7) render out the file
AME will NOT regard the NEW composition adjustments and thus render the 200 frames you cut off to the beginning of the movie...
Either I am doing something wrong (I hope but I don think so) or this is a BUUUUG...

You can submit bug reports here:
http://www.adobe.com/go/wish
More on how to give feedback here.

Bugs in AME 4.0.1

Similar Messages

Maybe you are looking for