There is a bug that I have yet to see explained exactly the same as I am experiencing it. I'm trying to transcode some MP4 h.264 files into a higher compressed h.264 file to better fit in it's playback medium. I thought the issue was the computer going to sleep pausing the render, even though that should not have been the case.
-Fresh install of Windows 10 1809
-drop multiple mp4 files into AME, hit start and it will go for a while.
-after a few minutes it stops rendering. No error, no immediate crash. Just no movement, no change in Remaining time. Even the elapsed timer is locked up and not changing.
-Trying to stop the cue causes AME to become unresponsive, causing me to force quit it.
-checked all power settings and changed them to keep computer and monitor awake all the time, etc.
-Same issue persists.
-Tried adding in just one file instead of the multiple from before.
-Same issue, and funny enough, the Elapsed time is stuck at EXACTLY the same point as it was the last time (8:51)...... Computer never went to sleep.

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 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.

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.

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.

Since customers pay monthly for a product (software) that should work - then I propose in future that any software problems introduced into new code (that did work in previous versions, which gets broken) should be directly discounted each month by Adobe to compensate customers .

eg The more bugs introduced and not fixed, this increases the percentage discount for customers monthly - yes ?
This is a sort of reverse bonus scheme which focuses the minds of both software developers and Quality assurance teams and Management.
The benefit of getting it right is happy customers, more references for Adobe and more money for them. Happy days.
However, not meeting the needs of customers has the reverse effect since this drains Adobe revenue !
Any comments on this new idea anyone?.

OK cynical maybe, but we are still feeling pain of problems not even acknowledged by Adobe let alone fixed !!. But good old customers keep on parting with the cash each month for broken software.
Something is not right somewehere here ???