Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows HandBrakeCLI - Long file names/paths supported? #2157

Closed
HaveAGitGat opened this issue Jun 21, 2019 · 6 comments

Comments

3 participants
@HaveAGitGat
Copy link

commented Jun 21, 2019

Description of the problem

I was just wondering if HandBrakeCLI supports 260+ character file paths/names? It doesn't seem to but thought I'd ask in case there's a specific way. Thanks.

HandBrake version (e.g., 1.0.0)

CLI 1.2.2

Operating system and version (e.g., Ubuntu 18.04 LTS, macOS 10.14 Mojave, Windows 10 1809)

Windows 10 17763

@woodstockathbf

This comment has been minimized.

Copy link

commented Jun 21, 2019

If you have not enabled long path name support in Win10, the limit is still present in the operating system.

@HaveAGitGat

This comment has been minimized.

Copy link
Author

commented Jun 21, 2019

@woodstockathbf sorry forgot to add, I've enabled long path name support but HandBrakeCLI doesn't seem to be working with long paths.

@woodstockathbf

This comment has been minimized.

Copy link

commented Jun 21, 2019

Have you tried the work-around for CMD.EXE mentioned in some of the Microsoft pages of prefacing paths with "\?" to force use of the 64-bit file path API? What I'm reading indicates that CMD.EXE still uses the 32-bit API even on a 64-bit installation, if drive letters are used. The "\?" in front of the path overrides that.

I can't test, because I don't have anything with super-long paths anymore.

OK, let me try this differently - the work around prefix is two backslashes, a question mark, and another backslash. I guess to enter it here I have to use \\?\ to have it display correctly.

@sr55

This comment has been minimized.

Copy link
Contributor

commented Jun 23, 2019

This may also apply: https://stackoverflow.com/questions/40083284/resolving-long-path-260-char-limitation-for-accessing-files-folders-in-latest

However, I don't know off the top of my head if any of our 3rd party libraries are using older API's which don't support long paths.

@woodstockathbf

This comment has been minimized.

Copy link

commented Jun 23, 2019

I pulled the latest handbrake-master source and there is no place that MAX_PATH is used to set a 260-character limit.

A good test to see if it's CMD.EXE doing the limitation would be to try running under PowerShell, which supposedly gives you access to the full Win32 API. Although I have not seen any of the "break the limit" messages mention PowerShell...

@HaveAGitGat

This comment has been minimized.

Copy link
Author

commented Jul 16, 2019

@sr55 @woodstockathbf

Thanks for the help. I tried the suggestions - enabled long paths, used \\?\, used Powershell - but still no luck so closing this as I don't think it's possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.