8000 Feature: Support for Exporting in FCPXML for Improved Compatibility with DaVinci Resolve and Other Editing Programs · Issue #139 · antiboredom/videogrep · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Feature: Support for Exporting in FCPXML for Improved Compatibility with DaVinci Resolve and Other Editing Programs #139
Open
@neopiccolorat

Description

@neopiccolorat

The classic XML works but is not as versatile as the FCPXML format.
And with DaVinci Resolve, the pathurl has to be manually edited in the XML file because it will throw an error with:
"The clip was not found."

<pathurl>file://d:\VideoGrep\output.mp4</pathurl>

Image

Changing the path to just <pathurl>output.mp4</pathurl> works just fine, but the video has to be in the same folder as the XML file.

Which is fine, but the audio and video are unlinked for all of the clips. When you have more than 10 to link manually, it can be really painful.
Maybe it works well in Final Cut Pro, but not with the free version of Resolve.

Image

The imported FCPXML timelines don't have this type of problem. For example, auto-editor has a --export resolve option. It exports an FCPXML file, and all the clips are linked, as shown in this screenshot:

Image

VideoGrep is extremely useful, but these little things make it difficult to use in a non-destructive way.

Thank you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0