I always get a green screen when encoding MP4's - but only happens after a while. I posted a similar bug in the Premiere forum but nobody has answered - and I am not the only one with this issue with the spec I have.

It happens with any MP4 from my camera, creating Proxies and such like. Even if I use the software render. Please please please can someone look into my issue. It really affects my workflow.

The green screen affects all my Mac (i.e. Safari MP4 videos). I have to restart for it to return to normal. It has happened for well over a year. Still a problem!

iMac (Retina 5K, 27-inch, Late 2015)
Using macOS Catalina 10.15.1 (19B88)
4 GHz Quad-Core Intel Core i7
AMD Radeon R9 M395X 4 GB
32 GB 1867 MHz DDR3

This is an observation of problems with AME 2018 exports after many hours of paintstaking work late at night to try to produce a H264 Based Blu Ray disc through Encore 6, but I suspect other authoring SW would have same issue.

I know Encore 6 is a legacy product and out of support - but AME version 2017 encoded H264 blu ray files which always worked fine.

There is also a thread on Encore Community Forums about this issue where other people have found same problem as well.

Today I see no way to produce a Blu Ray H264 based disc with files encoded from Media Encoder 2018. This newer version has caused problems.

Whilst Adobe may feel Blu Ray discs are defunct and we should use Streaming ... this problem with Media Encoder 2018 needs fixing as in some cases we need to produce Blu Ray discs of our project/work.

Adobe Engineering Team : can you have a quick look at the difference between H264 encoded Blu Ray files from AME 2017 to AME 2018 please. Why is it broken ..and fix it please.

Feedback welcomed.

I'm seeing a tremendous number of problems on long transcodes with camera cuts in the dailies. I'm working on a doc feature including a lot of Hi8 and MiniDV tapes. The source tapes are captured in long chunks, often over an hour. Within this are camera cuts, crash recorded blank tape spots, etc - the usual amateur issues. The source clips are all perfect on import. However, most of the transcodes (to ProRes 1080 @23.98) have serious problems as follows:

• clips can be truncated, i.e. can be 30 mins or more shorter than source clip.
• clips have internal problems. The audio continues correctly, but 20 mins of video will disappear. The means from this point in the transcoded clip on, the clip is completely out of sync, and the picture is permanently missing. Resulting clip is shorter than source.

Most of these problems seem to occur on the above mentioned recording errors, but not always. Often in the middle of a continuously recorded conversation, 20 mins will have just disappeared.

The result is a nightmare as I have to go back and create new, shorter Quicktime sources from the master source clip, then transcode these until I can get a clip that works.

AME 13.1 Build 173 APPEARS to run the CPU to max capacity which APPEARS to trip some safety system on the motherboard which then shuts down the computer - BSoD for Windows, Shut Down on a Mac.

See Forum Posting for More Detail > https://forums.adobe.com/message/11121422#11123448

This obviously needs more testing, because it just seems weird that software that has been around this long would cause a situation like this, but changing the settings in Windows seems to have fixed the issue, so I don't know what other conclusions to draw.

The suggested improvements would be:
1. Just throttle AME at around 95% or so on the back end of the software.
2. Allow the users to throttle it in preferences, with a default setting of 95% or so.
3. Put up some warnings and instructions on how to adjust the computer settings for your major (read: Windows and MacOS) operating system clients.

I've been transcoding a tremendous quantity of DV (sources both MiniDV and Hi8 via Digital8 camera), and I'm discovering that the transcodes have often failed to transcode the entire source clip - often coming up 30 mins short or skipping entire multi-minute chunks within the clip (leaving audio wildly out of sync). But no warning was ever issued, and so having spent two weeks managing the ingest, I now have to check every clip in Premiere against the raw source, only to discover something is missing. Simply retranscoding with the same preset usual works, but not always. There needs to be some way to at error check that what's transcoded at least matches the duration of the source, or indicating if any errors occurred in the transcode.

I have a weird issue. Constant crashes in AME (Media Encoder) CC 2019. Latest update...

The crashes are on two of my systems.

System 1:

Threadripper 12-core

64 GB RAM

RTX 2070

3 x m.2 SSD (System + storage)

3 x SATA SSD (Cache + exports)

1 x 6-bay Netgear NAS, 10 Gbit (raw files)

System 2

AMD 2700X

32GB RAM

GTX 1070

2 x m.2 SSD

2 x SATA SSD

I don't use network storage with this system

On both systems i tried AME, but it crashes. But it's at the point that all RAM is maxed out. It's the same behavier on both systems. Render starts... memory fills up... up to the point of 99%... than it freezes. CUDA or not doesn't seem to matter. Closing all apps... doesn't matter. All RAM gets filled.

The strange thing is: if I render directly from Premier the behavier is normal. On both systems.