Windows 10 long path support

Issue #569 new
Janani T E created an issue

Reported by "stax76" on "2020-09-05T16:16:04.237086+00:00"

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

[https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#maximum-path-length-limitation](https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#maximum-path-length-limitation)

[https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#short-vs-long-names](https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#short-vs-long-names)

[https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#enable-long-paths-in-windows-10-version-1607-and-later](https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#enable-long-paths-in-windows-10-version-1607-and-later)

This is frequently requested by staxrip users.

`avs2pipemod[info]: writing 638 frames of 200000/6759 fps, 1280x720,                   sar 0:0, YUV-420-planar-8bit progressive video.y4m  [info]: 1280x720 fps 200000/6759 i420p8 unknown frame countx265 [error]: failed to open output file <C:\Users\frank\Desktop\long path\aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb\ccccccccccccccccccccccccccccccccccccccccccccccccccc\eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee\ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff\ggggggggggggggggggggggggggggggggg\hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh\iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii\jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj\kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk\fitness_temp\fitness_new_out.hevc> for writingavs2pipemod[info]: finished, wrote 1 frames [0%].avs2pipemod[info]: total elapsed time is 0.025 sec.avs2pipemod[error]: only wrote 1 of 638 frames.

Comments (2)

  1. Log in to comment