Copy link to clipboard
Copied
Hi!
If I export a project to xml, I have a path_url with value is something like
1 Correct answer
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
Copy link to clipboard
Copied
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?
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
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.
Copy link to clipboard
Copied
Because business logic requires to operate in a web app, we have many more functions that need to handle in web app
Copy link to clipboard
Copied
You're aware that hundreds of PPro panels run web apps, right? 🙂
Copy link to clipboard
Copied
Please just tell if my question is possible or not 🙂
Copy link to clipboard
Copied
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.

