[FFmpeg-user] help with file paths under windows
barsnick at gmx.net
Fri May 15 13:12:50 CEST 2015
On Thu, May 14, 2015 at 17:39:46 +0200, lorenzo angeli wrote:
> Now, this seems all to be working fine under linux, but on winows, I
> started finding a bunch of issues.
> first this :
> I have fixed on my side, but doesn't really look nice....
I dont think you have:
> [Parsed_lut3d_0 @ 0000000002f22ea0] Setting 'interp' to value '/Python27/lib/site-packages/efesto_review/resource/luts/Cineon-to-SLog.3dl'
> [lut3d @ 0000000005a80060] [Eval @ 000000000022e6e0] Undefined constant or missing '(' in '/Python27/lib/site-packages/efesto_review/resource/luts/Cineon-to-SLog.3dl'
> [lut3d @ 0000000005a80060] Unable to parse option value "/Python27/lib/site-packages/efesto_review/resource/luts/Cineon-to-SLog.3dl"
I recommend you change your command line from
> C:\Users\efesto\Desktop>ffmpeg -threads 0 -y -start_number 1798 -i E:\A012C006_101030_L1O3\A012C006_101030_L1O3.%4d.dpx -c:v libx264 -crf 18 -preset slow -strict -2 -movflags faststart -filter_complex "[0:v]lut3d='C\\:/Python27/lib/site-packages/efesto_review/resource/luts/Cineon-to-SLog.3dl',lut3d='E\\:/efesto/efesto-review/resource/config/K_TONEVintage_KODACHROME.cube',ut3d='C\\:/Python27/lib/site-packages/efesto_review/resource/luts/SLog-to-sRGB.3dl',scale=1920:1080[clip];[slate][clip] concat=n=2:v=1, scale=1920:1080, fps=25[v]" -map [v] "C:\Users\efesto\Desktop\out.mov" -v trace
ffmpeg -threads 0 -y -start_number 1798 -i E:\A012C006_101030_L1O3\A012C006_101030_L1O3.%4d.dpx -c:v libx264 -crf 18 -preset slow -strict -2 -movflags faststart -filter_complex "[0:v]lut3d=C\\:\\\\Python27\\\\lib\\\\site-packages\\\\efesto_review\\\\resource\\\\luts\\\\Cineon-to-SLog.3dl',lut3d='E\\:\\\\efesto\\\\efesto-review\\\\resource\\\\config\\\\K_TONEVintage_KODACHROME.cube,ut3d=C\\:\\\\Python27\\\\lib\\\\site-packages\\\\efesto_review\\\\resource\\\\luts\\\\SLog-to-sRGB.3dl,scale=1920:1080[clip];[slate][clip] concat=n=2:v=1, scale=1920:1080, fps=25[v]" -map [v] "C:\Users\efesto\Desktop\out.mov" -v trace
I think the may difference of your command line to the trac ticket: You
added single quotes within the arguments. It may be sufficient to omit
> Then I have a problem with the luts, even if I format the full path to the
> lut correctly, it fails loading it with a strange message, which I can't
> undestand if it's given by the content of the lut, or the path itself.
No, as the message says, it still can't parse the argument to the
filter. Until you fix the issue of finding the files, the filters
aren't yet being applied.
Windows paths are a PITA, admitted.
More information about the ffmpeg-user