"offline media detected and will be encoded using proxies"

I will send you a private message with instructions. Thanks!

I'll be happy to share and help you, @eckiAMETeam , get this fixed.
Guide me on what files and where to share.
Turns out the new AME render didn't use proxies, and didn't give any warning before starting the queue. But it did give the rendered file additional text in the filename (underlined in the log below) and a warning once the queue was finished about some problems:

02/22/2023 06:41:13 PM : File Encoded with warning
------------------------------------------------------------
File importer detected an inconsistency in the file structure of filename_AMEnewSetting.mp4. Reading and writing this file's metadata (XMP) has been disabled.

PS I might add that this Premiere Pro project was created in december, last year (2022). I just brought it back to adjust a small text detail in the end poster. Rendering was not a problem before.

Regards

PolkaFever

There is no risk involved. It is just using a different code path to handle Premiere Pro projects.

Would you be able to share a small project with media that illustrates the issues? I would like to create a bug for the issue you encountered to fix it.

Hi eckiAMETeam,
I'm on:
Premiere v23.2 build 69
AME v23.2 build 63
Windows 10 Enterprise 64bit v22H2/build19045.2604
64GB ram/Intel(R) Xeon(R) W-2102 CPU @ 2.90GHz 2.90 GHz

I though you ment natively import the sequence from AME, but that gives same error/warning.
But now I realize "import sequences natively" is a preferences setting.
Once I unchecked that the sequence imported without any offline files and proxy replacements. Don't know what I risk by this, but the problem seems to be solved.

Thanks for looking into this.

Looks like a bug. Which AME & PPro versions are you using? Which system are you on?

Can you try toggle "import sequences natively" to work around this?