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 believe it is the dynamic line manager that is actually the problem. I have to output about a 100 promos a session. Seems like a great reason to use the "Render que". After getting about 15 spots into the Render que, Premire starts to hang up (like I can't "goto inpoint") and Encoder will stop adding to the que. At this point I have to reboot and resend everything back into the que. Most days I just render the spots one at a time. This has become a huge waste of time.
MacPro (trash Can), High Sierra
64gb, 2 D700,
Adobe 2018 apps

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.

This appeared to be a bug and a rather frustrating one to work out.

Exporting a sequence from Premiere 14.9 would result in audio effects (applied in audio track mixer) being rendered out properly, but when the sequence was sent to a queue in Media Encoder 14.1, the audio effects weren't applied.

I couldn't figure this out initially and had to re-render my hours worth of material via manually exporting from the export window.

After speaking to someone on the Australian AVPUG on facebook, they explained that it can happen if there's a mismatch between versions, and indeed there was.
Updating ME fixed the issue.

However I don't know if this is a bug or not.
Seems to me that it could easily happen a lot to users.

I set up an overnight batch export to make proxy files. Upon returning the following morning Media Encoder insisted on quitting over and over and over and over again. No matter how many times I told it I didn't want to quit, it kept popping up asking me if I wanted to quit. This also froze all exports so basically nothing had actually happened overnight.

Why did this happen? Because Creative Cloud automatically logged me out, for absolutely no reason!

If your software hinges entirely on me being signed in CONSTANTLY, that is unacceptable. I lost time on this project because of stupid authentication.

I can no longer trust that my overnight exports will complete. Batches? Now I have to babysit them to make sure they complete properly and don't fail on some stupid technicality. My Premiere export also failed because a "font went offline" - Why did it go offline? Because the fonts are tied to my profile and when CC logged me out, my fonts disappeared as well.

THIS IS NOT HOW THIS SHOULD WORK

If CC needs to log me out for another pointless update, then the programs should recognize a 30 day grace period.

Get your act together Adobe. You make billions off of our subscriptions and then compromise our projects.

Still waiting on that M1 support...