Thank you for the report. We have reproduced the issue and are investigating a fix. ... View more

Unfortunately it is limited to VBR 1-pass currently. ... View more

Ok, that's easier to explain: 2 pass is not supported for hardware acceleration (that's a limitation of the hardware, not the software). ... View more

markusw90010395  wrote It answers my question, Rameez. It does not help me understand why "Intel® Xeon® Processor E3 family, introduced in 2011, supported H.264 hardware-based encoding for the first time." Supposedly Xeon processors have had H.264 hardware encoding  support since 2011... While that is a true statement it is unfortunately not that simple. If you refer to Intel's site detailing which CPUs support QS (Intel® Product Specification Advanced Search ) you will see there are more Xeons that don't support QS than ones that do. That is our first barrier to being able to use hardware acceleration. There are a few more things down the line that can determine support, but without the supported hardware it's a non-issue. ... View more

For this release we trimmed the list to be a much smaller, more concise list of presets. This has a couple advantages: The list of presets went from 110 to about 30. This makes it much easier for you, the user, to navigate and find a preset that will work for your needs. Instead of maintaining a very long list of device-specific presets we have moved to a more generic preset for mobile devices, for example. Devices have come a long way in the last few years and there isn't as much of a need to differentiate between Apple-centric settings and Android-centric settings. All that said, if you still would like to use an older preset they are still supported. You would just need to export them from a previous version. If there is a specific preset you think is crucial to keep around I'd be happy to discuss it with you so I can better understand if it is something we need to put back. ... View more

I can't tell you why this happens as that is in an area of the code I am not familiar with but we are looking in to it. However I can tell you that the warning is not an error and there is nothing wrong with the file that was created. Thank you for your input and I will add your notes to our investigation. ... View more

Looks to me like you want the XDCAM HD 50 NTSC 60i preset. ... View more

Thanks for retesting. I'm glad that particular issue is sorted. As for the clips coming in as audio-only we are aware of the issue and have our developers looking at it. For now, the workarounds that you noted mirror our recommendations. Please stand by. ... View more

Thank you for providing the samples. This is interesting because I can see the silent part at the beginning (that's another bug I'm tracking down), but not the end. I have tried 3 different machines and both Mac and Windows. Are you using the 2017.1 release? And if you had previously imported them in an older release then updated I would suggest deleting your cache and reimporting them. I would like to know if anyone else can reproduce this issue in the 2017.1 release as well with the media provided. ... View more

Let's go ahead and make it a high priority. However I have not been able to reproduce this issue with any of our media in-house. Would you be able to send me a sample that exhibits this problem so I can have a developer take a look? ... View more

That is correct. Updating the 10.3 version will give you 10.4, not 11.0. ... View more

Would you be able to provide a small sample for us to look at? ... View more

Premiere Pro 6.0.5 didn't have support for Sony XAVC. You will need a newer version of Premiere Pro to import those files. ... View more

As you are sending from AE 2017, I wonder if there isn't an unrelated issue causing you some pain. A bug was introduced in the CC2017 version where AE comps queued to AME would export at whatever resolution the comp was set to instead of defaulting to always export at Full Resolution as it has in the past. Could you please verify that your comp's resolution setting is at Full and try the export again? ... View more

Well there's going to be a certain amount of variation to the actual bitrate due to it being variable so I'm not too worried that it isn't coming in at exactly 1128kbps. What does concern me is that you are clearly seeing a drop in the quality. When I go back and encode the same source across multiple versions I get basically the same quality which leads me to a possible source of the issue: I've seen cases in the past where the source file was the determining factor in whether a certain quality bug appeared or not. Would it be possible for you to re-encode the example above that is good using a more recent version of AME? If that one comes out clean then my suspicion may be correct (but it would still be a bug). If it comes out bad then I'd like you to re-encode it in an older version (maybe CC 2014) to see if it is any better. Something goofy is going on here. It will just take a bit of trial and error to figure out what. ... View more

You can certainly file a bug report here: Feature Request/Bug Report Form but there is no guarantee you will get a response. These forums are your best bet to get help on the issue and the team does watch the forums from time to time. Also, as it is a user to user forum, the other users here are pretty good at helping each other out. Can you give us some more details about what source you are exporting and what preset you are using? ... View more

Glad you got it figured out. Just as a head's up for anyone else that hits this issue: it sounds like a problem with a bad preference file. Most likely you can move the Presets and Logs folders (if you want to keep them) out of that location and then on your next launch, hold down the Shift key. That will clear the preferences without having to reinstall. Then close AME and replace the Presets and Logs folders. You should be good to go then. If anyone has this problem and confirms that my assumption is correct and that you can resolve without re-installing please let me know and I will update this as the Correct solution. It would also be helpful if you could message me so we can gather some information that may help us resolve the issue that is preventing the launch. ... View more

If you create a copy of that project and remove the Sugar FX subtitles does it work? That would give us something solid to go on. ... View more

What previous version are you comparing your results against? ... View more

Fnord Software has created free plug-ins for both WebM and Ogg.  You can find more information about their WebM plug-in on their blog: http://fnordware.blogspot.com/2015/04/webm-for-premiere.html You can find more information about their Ogg plug-in here: https://github.com/fnordware/AdobeOgg ... View more

For anyone experiencing the issue, please download the Premiere Pro and AME 2015.4 updates that were just released tonight. We believe we have fixed the issue in that update. Ultimately, as Takuya noted, the problem stems from the Premiere and AME Lumetri directories not being completely in sync. That said, if the update does not resolve the issue, please let me know and we will investigate further as from your reports there are possibly a couple issues at play. Thank you all for your reports. ... View more

Chad, what version of Premiere/AME are you using? I've heard mixed reports as to whether this is working in the latest version (10.3) and would love to narrow it down. If it is 10.3 that you saw this issue I'd love to talk to you more offline so we can fix the bug properly on our side without you needing a workaround. ... View more

Hey guys, I'm trying to reproduce the issue so we can get a bug logged, but so far I have not had the same results. Would it be possible for one of you to post a small sample source files and exact steps to repro the issue (including effect and export settings)? Thanks! ... View more

While I would normally recommend doing so, in this case it isn't necessary as we already have this one logged. ... View more

I would also like to mention this is now fixed in the CC 2015 release. ... View more

Hey all, we are aware of this issue and are investigating. I apologize for the inconvenience. Please stand by. ... View more