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

Generate path_url for asset in xml file

Explorer ,
Oct 25, 2022 Oct 25, 2022

Hi!

 

If I export a project to xml, I have a path_url with value is something like 

`file://localhost/Volumes/Macintosh%20HD/Users/phongvu/Downloads/test2/2.jpg`
 
The same if I want to import xml to premiere pro, I need to declare asset with the path_url with the format above. My question is how can I generate that path programatically with javascript?
 
Thanks!
TOPICS
Export , Import , SDK
597
Translate
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 , Oct 27, 2022 Oct 27, 2022

From within a panel, it is definitely possible to:

  • Create a project
  • Import valid FCP XML, referencing both media and sequences
  • Import media directly, without wrapping it in valid FCP XML.


Trying to do that from a web app, without panel integration, is impossible; you could conceivably write valid FCP XML, which the user could then manually import.
 

Any item to be imported into a PPro project must be available at one of the following:

  • Local path
  • Mounted network volume (MacOS)
  • Mapped network dr
...
Translate
Adobe Employee ,
Oct 25, 2022 Oct 25, 2022

If you know the path of the media you'd like to import, why not just import it, instead of creating the FCP XML wrapper first?

Translate
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
Explorer ,
Oct 26, 2022 Oct 26, 2022

The context is I have an web app that allows users to create their PPRO project, then export to xml and import it to PPRO.

 

The problem with web app is browsers aren't allowed to get user's local file path. Also file path for PPRO seems to have unique format.

Translate
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 ,
Oct 26, 2022 Oct 26, 2022

I'm unclear as to why it would ever be desirable to put that functionality in a web app, instead of a CEP panel, hosted within PPro...? 

Were you to do so, you could use PPro's API to create the new project, import all media, and even assemble a rough cut sequence.

Translate
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
Explorer ,
Oct 26, 2022 Oct 26, 2022

Because business logic requires to operate in a web app, we have many more functions that need to handle in web app

Translate
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 ,
Oct 27, 2022 Oct 27, 2022

You're aware that hundreds of PPro panels run web apps, right? 🙂

 

 

Translate
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
Explorer ,
Oct 27, 2022 Oct 27, 2022

Please just tell if my question is possible or not 🙂

Translate
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 ,
Oct 27, 2022 Oct 27, 2022
LATEST

From within a panel, it is definitely possible to:

  • Create a project
  • Import valid FCP XML, referencing both media and sequences
  • Import media directly, without wrapping it in valid FCP XML.


Trying to do that from a web app, without panel integration, is impossible; you could conceivably write valid FCP XML, which the user could then manually import.
 

Any item to be imported into a PPro project must be available at one of the following:

  • Local path
  • Mounted network volume (MacOS)
  • Mapped network drive (Windows)
  • UNC path


A path_url, as you've described, will not work.

As mentioned, hundreds of partners (including basically all media asset management providers) use panels in PPro to integrate their services, as web apps, into PPro. Happy to help further, with any panel development.


Translate
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