WyattBlue / auto-editor

Auto-Editor: Efficient media analysis and rendering
https://auto-editor.com
The Unlicense
2.71k stars 402 forks source link

DaVinci Resolve export "Clip was not found" due to `<pathurl>` having back slash instead of forward slash #448

Closed prollygon closed 4 months ago

prollygon commented 4 months ago

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?

Version: 3.12.2 64-bit
Platform: Windows 10 amd64
FFmpeg Version: N-110322-g0c25da5a28-g1440bf15e2+1
FFmpeg Path: C:\Users\Kris\AppData\Local\Programs\Python\Python312\Lib\site-packages\ae_ffmpeg\Windows\ffmpeg.exe
Auto-Editor Version: 24w09a

What command did you use

`auto-editor video.mkv --margin 0.11sec --export resolve`

What properties does your input video have?


FFmpeg Version: N-110322-g0c25da5a28-g1440bf15e2+1
FFmpeg Path: C:\Users\Kris\AppData\Local\Programs\Python\Python312\Lib\site-packages\ae_ffmpeg\Windows\ffmpeg.exe
Auto-Editor Version: 24w09a
PS C:\Users\Kris> auto-editor info "E:\Stream VODS 2024 Q1-2\2024-03-10_13-52-45.mkv"
E:\Stream VODS 2024 Q1-2\2024-03-10_13-52-45.mkv:
 - video:
   - track 0:
     - resolution: 1536x864
     - aspect ratio: 16:9
     - pixel aspect ratio: 1
     - pix fmt: yuv420p
     - color range: tv
     - color space: bt709
     - color primaries: bt709
     - color transfer: bt709
     - timebase: 1/1000
 - audio:
   - track 0:
     - codec: aac
     - samplerate: 48000
     - channels: 2
 - container:
   - duration: 9434.233
   - bitrate: 6278503

   Input #0, matroska,webm, from 'E:\Stream VODS 2024 Q1-2\2024-03-10_13-52-45.mkv':
  Metadata:
    ENCODER         : Lavf60.3.100
  Duration: 02:37:14.23, start: 0.000000, bitrate: 6278 kb/s
  Stream #0:0: Video: h264, yuv420p(tv, bt709, progressive), 1536x864 [SAR 1:1 DAR 16:9], 30 fps, 30 tbr, 1k tbn
    Metadata:
      DURATION        : 02:37:14.233000000
  Stream #0:1: Audio: aac, 48000 Hz, stereo, fltp
    Metadata:
      title           : Track1
      DURATION        : 02:37:14.112000000```

### Comments

_No response_
prollygon commented 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.