Opened 14 months ago

Last modified 13 months ago

#8885 reopened enhancement

Windows 10 long path support

Reported by: stax76 Owned by:
Priority: wish Component: build system
Version: git-master Keywords:
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no


I would like to request long path support in Windows 10. Currently, long paths work only with long path prefix
?\ or 8.3 names. I would like to request native long path support that don't need a prefix or 8.3 (short) name.

This is frequently requested by staxrip users.

Change History (8)

comment:1 by Carl Eugen Hoyos, 14 months ago

Component: ffmpegundetermined
Keywords: Win10 removed
Resolution: needs_more_info
Status: newclosed
Type: enhancementdefect

Please reopen this ticket if you can explain how the issue you see can be reproduced, either show the command line you tested together with the complete, uncut console output or provide source code.

comment:2 by stax76, 14 months ago

Resolution: needs_more_info
Status: closedreopened

Samples> ffmpeg -i 'C:\Users\frank\long path\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\fitness.mkv' -hide_banner
C:\Users\frank\long path\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\fitness.mkv: No such file or directory

The file exists, it works when the file is prefixed, so it's likely sufficient to modify the manifest info to make it work.

Desktop> ffmpeg -i '\\?\C:\Users\frank\long path\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\fitness.mkv' -hide_banner
Input #0, matroska,webm, from '\\?\C:\Users\frank\long path\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\fitness.mkv':
    encoder         : libebml v1.3.4 + libmatroska v1.4.5
    creation_time   : 2017-05-18T11:30:45.000000Z
    Writing frontend: StaxRip
  Duration: 00:00:21.58, start: 0.000000, bitrate: 1117 kb/s
    Stream #0:0: Video: h264 (Main), yuv420p(tv, bt709, progressive), 1280x720 [SAR 1:1 DAR 16:9], 29.59 fps, 29.59 tbr, 1k tbn, 59.18 tbc (default)
Last edited 14 months ago by stax76 (previous) (diff)

comment:3 by Carl Eugen Hoyos, 14 months ago

The unavoidable question is now: What on earth is a manifest when discussing FFmpeg source code?

Please understand that -hide_banner makes every bug report invalid unless you want to report an issue with the option.

in reply to:  3 comment:4 by Marton Balint, 14 months ago

Replying to cehoyos:

The unavoidable question is now: What on earth is a manifest when discussing FFmpeg source code?

So this ticket is about the inclusion of a long path aware manifest in ffmpeg.exe executable.

comment:5 by stax76, 14 months ago

I've looked at a ffmpeg build made by Patman (media-autobuild_suite based I think) using Resource Hacker and it contains a manifest without long path support enabled.

My question is where is this manifest added? I've searched the ffmpeg and media-autobuild_suite source code and didn't find any manifest file.

comment:6 by stax76, 13 months ago

Technical details from projects that have solved the issue:

comment:8 by Carl Eugen Hoyos, 13 months ago

Component: undeterminedbuild system
Priority: normalwish
Type: defectenhancement
Version: unspecifiedgit-master

Apparently not as unrealistic as I thought.

Note: See TracTickets for help on using tickets.