Skip to main content
Participant
October 16, 2026
Needs More Info

I created a Premiere project. I had to end up converting to a Team Project. Now that's happened, I keep getting metadata errors when I create new proxies within this Team Project.

I created a Premiere project. I had to end up converting to a Team Project. Now that's happened, I keep getting metadata errors when I create new proxies within this Team Project. The error being “File importer detected an inconsistency in the file structure of “file name”. Reading and writing this file’s metadata (XMP) has been disabled.

When I converted the project back to a normal project, the proxies created just fine! This has been an issue I’ve been dealing with for hours. 

    3 replies

    Participant
    October 16, 2026

    Premiere version: 26.5.2 (Build 5)

    Media encoder version: 26.5.2 (Build 2)

    Operating system: macOS Sequoia Version 15.7.9

    Chip: Apple M3 Pro

    Source clip/format/codec: It happens with almost every clip just in the team project, not in regular project. Codecs: Timecode, Apple ProRes 4444

    Dimensions: 3840 × 2160

    Proxy preset: ProRes Quicktime Proxy-Half

    The original media is online and accessible. 

    In the teams project, the erros pop up only in premiere yet still complete the proxies. I would like a private upload link to share a screen recording please. 

    Translate
    Amy the Stuv
    Community Manager
    Community Manager
    October 16, 2026

    Hello ​@creative_care70b5 

    Welcome to the Premiere Forums. Thanks for including the exact warning and noting that proxy creation succeeds after converting the project back to a regular project. That comparison is helpful, but it doesn’t yet identify whether the problem is specific to the Team Projects workflow or tied to a particular clip, preset, or destination.

    Could you add a few details so we can try to reproduce it?

    • Premiere Version
    • Media Encoder Version
    • Operating System: Specify Windows or macOS, along with the version.
    • Chip (Mac Only): Specify which M-series Chip or CPU/GPU combo.
    • GPU and Driver (Windows only): Please let us know your video card and driver version. We recommend updating to the most recent version; for NVIDIA users, we strongly recommend the Studio version of the driver.
    • The source clip’s format/codec, and whether this happens with one clip or every clip
    • The proxy preset/format and where you’re saving the proxies
    • Whether the original media is online and accessible

    As a safe test, try one eligible online video clip in a copy or disposable Team Project, using a built-in proxy preset and a local destination folder. Also try a second known-good clip in that same test project. Please note whether Media Encoder starts the job and capture the error in Premiere’s Progress panel or Media Encoder’s queue if it recurs. Proxy creation has eligibility limits: the source must be online video, and clips with captions or growing files aren’t supported. Create proxies in Premiere

    If the same clip works in a regular project but fails in a test Team Project, please include the exact steps and, if possible, a short screen recording. To avoid sharing private or copyrighted source media publicly, I can DM you a private upload link. Let me know if you need one.

    Hoping to help,

    Amy

    Translate
    Participant
    October 16, 2026

    Premiere version: 26.5.2 (Build 5)

    Media encoder version: 26.5.2 (Build 2)

    Operating system: macOS Sequoia Version 15.7.9

    Chip: Apple M3 Pro

    Source clip/format/codec: It happens with almost every clip just in the team project, not in regular project. Codecs: Timecode, Apple ProRes 4444

    Dimensions: 3840 × 2160

    Proxy preset: ProRes Quicktime Proxy-Half

    The original media is online and accessible. 

    In the teams project, the erros pop up only in premiere yet still complete the proxies. I would like a private upload link to share a screen recording please. 

    Translate