[FFmpeg-devel] Problem with "-f concat" and mixed path types on Windows.

[Steinar Apalnes]

> >>> Hi,
> >> > It looks like the -f concat options has a problem when mixingUNC paths in
> >> > the concat file and local concat file path in command line:
> >> >
> >> >
> >> > Concat file:
> >> >
> >> > ffconcat version 1.0
> >> > file '\\server\CanonXF\CONTENTS\CLIPS001\AA4002\AA400201.MXF'
> >> > file '\\server\CanonXF\CONTENTS\CLIPS001\AA4002\AA400202.MXF'
> >> > file '\\server\CanonXF\CONTENTS\CLIPS001\AA4002\AA400203.MXF'
> >> > file '\\server\CanonXF\CONTENTS\CLIPS001\AA4002\AA400204.MXF'
> >> > file '\\server\CanonXF\CONTENTS\CLIPS001\AA4002\AA400205.MXF'
> >> >
> >> >
> >> > Full command:
> >> >
> >> > "D:\FFMpeg\x64\ffmpeg.exe" -f concat -safe 0 -i "d:\temp\AA4002.mxf.concat"
> >> > -map 0 -c copy -y "d:\temp\AA4002.mxf"
> >>
> >> As a quick workaround you can use forward slashes instead of backslashes
> >> in the paths you use.
> >>
> >> Regards,
> >> Marton
> >
> > I'm sorry but I've already tried this:
> >
> > file '//server/CanonXF/CONTENTS/CLIPS001/AA4002/AA400201.MXF'
> > file '//server/CanonXF/CONTENTS/CLIPS001/AA4002/AA400202.MXF'
> > file '//server/CanonXF/CONTENTS/CLIPS001/AA4002/AA400203.MXF'
> > file '//server/CanonXF/CONTENTS/CLIPS001/AA4002/AA400204.MXF'
> > file '//server/CanonXF/CONTENTS/CLIPS001/AA4002/AA400205.MXF'
> >
> > I've also tried changing the slashes in the ffmpeg parameters but it
> > really does not help
> > and I get the same bug. Maybe I'm doing it wrong.
>
> Try "file 'file://server/..'"
>
> > If so, could you supply a notation that you know for a fact to be working?
>
> Not really :)
>
> Also, please use the ffmpeg-user mailing list for similar questions.
>
> Thanks,
> Marton

Thanks Marton, specifying "file:" for each entry did it:-) Also, I
could keep the slash the original way so chaning slash obviously had
no effect. Anyway, thanks again!

I used the devel list because I considered, and still consider this as
a bug, and not a user "how-to" question. Or does the concat work as
intended when it's adding the prefix with a letter: before the share
path?

-steinar