• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

MXF file dragged into bin creating clip with parent folder name

Community Beginner ,
Jul 14, 2021 Jul 14, 2021

Copy link to clipboard

Copied

Hey all! We are seeing some odd behavior in Premiere when dragging an MXF file into the bin. The file is added to the bin with the parent folder name as the clip name, instead of the name of the actual MXF file. We discovered this because we have a PPRO extension that brings files into the bin with this API call, and we’re seeing the same behavior. This is happening to a customer of ours and we have not been able to reproduce it on our end. Could this possibly be happening because of some metadata alongside the MXF file, or due to the structure of the files, or maybe some setting in PPRO?

TOPICS
Formats , Import , SDK

Views

230

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Jul 15, 2021 Jul 15, 2021

Happy to pursue further, given steps to follow that elicit the behavior.

Votes

Translate

Translate
Adobe Employee ,
Jul 14, 2021 Jul 14, 2021

Copy link to clipboard

Copied

Bizarre!

I'm not seeing that. In what version(s) have you tested?

Steps: 

0 Launch PPro

1 New empty project

2 From ExtendScript, call app.project.importFiles( ['/Users/bbb/Movies/aaa.mxf']);

 

Result: Name of project item = 'aaa.mxf', not 'Movies'.

Steps: 

0 Launch PPro

1 New empty project

2 Drag /Users/bbb/Movies/aaa.mxf from Finder window, to PPro project window.

 

Result: Name of project item = 'aaa.mxf', not 'Movies'.

Once the .mxf file is imported, PPro will create a .xmp file next to it, but that happens after the import.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 14, 2021 Jul 14, 2021

Copy link to clipboard

Copied

Our customer is seeing this behavior in PPRO 15.2.0. And yes, it is bizarre, our team has been trying to reproduce but unsucessful so far.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jul 14, 2021 Jul 14, 2021

Copy link to clipboard

Copied

You said above that "we’re seeing the same behavior"...?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jul 14, 2021 Jul 14, 2021

Copy link to clipboard

Copied

Sorry, let me clarify

 

When we drag an MXF file manually into a bin or use the API call (via our extension)- we do not see the behavior.

 

When our customer drags an MXF file manually into a bin or uses the API call (via our extension)- they do see the behavior.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jul 15, 2021 Jul 15, 2021

Copy link to clipboard

Copied

LATEST

Happy to pursue further, given steps to follow that elicit the behavior.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines