Adobe Media Encoder encoding single "Media Offline" frames

[philippb29246088]

Hello there,

I am using Adobe CC 2017 Software on a Workstation running on Windows 10 and hoping to find help regarding one particularly strange AME CC 2017 issue I am struggling with:

I exported my sequence to AME from AE. I imported the Sequence to After Effects from a PP Project (Import -> Premiere Pro Project -> sequence name) which I used to cut the Material and to do Sound Editing & Mastering in Audition and a little in Wavelab. After Effects was used to do Color Correction (SA CF 3) as well as to add a Start- & End-Sequence and Logo embeds.

The length of the final film - a recording of a panel discussion - is a little over 1h 54m. The source material is stored on a NAS and accessed via local Network (.mov files recorded on an AJA KiPro).

My issue is this:

I export H.264 1920x1080 25p, the encoding takes about 15 hours 'til it's done, and while I am watching the final result, with which I am initially rather happy with, I stumble upon a single one of these wonderfully classical  "Media Offline" Frames at about 11m 18s. I am importing the file to premiere to double check, and yup, there it is. Then I stumble upon another one at about 15m 17s and starting at 1h 35m 23s the network source was seemingly completely lost, this time not displaying the classical "media offline" image but, maybe more appropriate for a cause as lost as this one, the color bar test image for the rest of the video with the file name of the PP Project displaying in the upper left corner, at which point I know for sure I will have to encode the whole thing all over again.

No errors were displayed by AME.

Now I would like to make sure that this does not happen again. I found and gladly checked the box "Don't encode sources containing offline media" in the Premiere Pro section of AME General Preferences and am hoping for the best and maybe some help from a fellow media encoder.

Why I would want to "encode sources containing offline media" in the first place is completely beyond me by the way, and why AME is seemingly, at least in my case, set do so by default even further out beyond. As I was exporting the file using AE I am wondering if there is an AE Preference setting hidden somewhere else which I need to watch out for or if anybody else was experiencing something along the same lines and found a way to reliably fix it.

All the software I was using to do this is up to date.

regards

philipp

[Joost van der Hoeven]

Glad you found the checkbox. The reason to keep it unchecked is if you want to export regardless of missing footage. Because it will also not render you movie if the footage that is offline has Opacity set to 0%.

Having that checkbox on by default is a good suggestion. You can file your request here:

adobe.com/go/wish

[philippb29246088]

Thank you for your reply, sorry for my delayed response!

This turned out to be even more time consuming a - in least in my understanding - bug than I excepted, as the checkbox went back to the default unchecked state without me noticing, rendering my files useless along the same lines of encoded media offline frames.

I guess for now I'll have to check the general settings tab every time i start my ME queue.

[philippb29246088]

OK, unfortunately, my issue has now definitely turned into some sort of frustratingly annoying bug:

Media Encoder is still delivering video files containing random and isolated Offline Media Frames in spite of said check box being checked.

No errors are being displayed or to be found in the AMEEncodingLog.txt or AMEEncodingErrorLog.txt files.

[dand57215607]

Just ran in this problem also. In my case all the files are local so online and should not have any issues.

One of the clip used was made with AE.

OK got the answer on youtube lol the guy had the same problem ang got his answer from tech

close all adobe apps

in windows at the bottom left in the search box enter

%appdata%

a window will open with the search results

click on the adobe folder

then rename the common folder to folder1 or something 

reboot, voila !!!!

cheers