Closed prollygon closed 4 months ago
I'm not sure how I messed this up, but this must be user error. I tested again, and --export resolve
is working, as it produces an .fcpxml file that imports properly (whereas --export premiere
produces back slashes that do not import properly). Still, back in version 22w18a, when --export resolve
was not an option, --export premiere
did work and produced forward slashes in its pathurl. However, this is not an issue at all. Sorry for the trouble.
Bug description
I've tried
--export resolve
,--export premiere
, and--export final-cut-pro
, and it all produces the same "Clip was not found" error upon importing the XML to DaVinci Resolve 18.6.5. I can work around this issue by changing the back slashes to forward slashes in<pathurl>
.For example, Auto-Editor produces the following:
<pathurl>E:\Stream VODS 2024 Q1-2\2024-03-10_13-52-45.mkv</pathurl>
The issue goes away when I manually change it to this:
<pathurl>E:/Stream VODS 2024 Q1-2/2024-03-10_13-52-45.mkv</pathurl>
I don't know if other Resolve users have experienced the same problem with the current version of Auto-Editor. This was not an issue when I used a compiled binary that a Redditor had made based on version 22w18a.
Lastly, thank you for creating Auto-Editor! I wish I discovered this program sooner. It has been a huge help.
What's your platform?
What command did you use
What properties does your input video have?