Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#5644 closed defect (invalid)

Concat protocol broken

Reported by: Hunny Puppy Owned by:
Priority: important Component: undetermined
Version: git-master Keywords: concat
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

Summary of the bug: This is a bug with the latest build(N-80335-gcb46b78), it was working fine from a old build that I have (N-77010-g4e31176). With the new build yesterday I'm getting this error.
How to reproduce:

ffmpeg.exe -hide_banner -probesize 100M -analyzeduration 300M -fflags +genpts -y -f concat -i "C:\temp\working1\WMV_ConcatList.txt" -map v -vcodec copy -map a -acodec copy -avoid_negative_ts 1 "C:\temp\working1\WMV_0_0.avi"
[concat @ 000000e8fb210b00] Unsafe file name 'C:\temp\working1\WMV_24_852.avi'
C:\temp\working1\WMV_ConcatList.txt: Operation not permitted

I checked the documentation and while I know the safe option exists, based on the rules specified this filename should be legal but ffmpeg doesn't seem to think so. It may be a bug or a regression not sure how to classify it but I don't think it should break.

Change History (2)

comment:1 by Nicolas George, 6 years ago

Resolution: invalid
Status: newclosed

This has nothing to do with the concat protocol, please pay attention. As for the concat demuxer, the path is not relative and contains one forbidden character, that makes two reasons it is not considered safe.

comment:2 by Hunny Puppy, 6 years ago

Sorry, I think I misread the documentation. Although it's not clear why having an absolute path would be considered "unsafe"

Note: See TracTickets for help on using tickets.