Related to viewtopic.php?f=30&t=99508
Windows 10 now supports file paths longer than 260 characters. Right now it has to be enabled by the user but long paths are highly useful for mediamonkey users with large libraries with filenames and paths constructed from metadata tags.
https://docs.microsoft.com/en-us/window ... limitation
Support Windows 10 Long Path Functionality [#18122]
Moderator: Gurus
Re: [REQ] Support Windows 10 Long Path Functionality
MediaMonkey 5 already supports longer Paths, it's MediaMonkey 4 where this isn't supported. Is MediaMonkey giving you a file Path length error?
Download MediaMonkey | License
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Re: [REQ] Support Windows 10 Long Path Functionality
A lot of files in a move operation are failing. It's not giving me a specific error but I noticed the ones that are failing tend to have very long file paths.
I'll take your word for it and let you know if I get specifics. thanks!
I'll take your word for it and let you know if I get specifics. thanks!
Re: [REQ] Support Windows 10 Long Path Functionality
Which build (Help > About) are you on?
So the files have long (240+ characters) Paths before Auto-Organize Files? Do they also get organized to long Paths afterwards? Is the database you're using from MediaMonkey 4 or did these files get added to the Library by MediaMonkey 5?
So the files have long (240+ characters) Paths before Auto-Organize Files? Do they also get organized to long Paths afterwards? Is the database you're using from MediaMonkey 4 or did these files get added to the Library by MediaMonkey 5?
Download MediaMonkey | License
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Re: [REQ] Support Windows 10 Long Path Functionality
Actually, I take that back- the problem here might be with the Auto Organize feature. It is truncating the destination path on some of the files and then it fails.
It is truncating some of my filenames to 50 characters, but it is not truncating all filenames that have more than 50 characters. It LOOKS like if the total file path exceeds some unknown limit, the filename specifically will be truncated to 50 characters.
I'm on 2420.
It is truncating some of my filenames to 50 characters, but it is not truncating all filenames that have more than 50 characters. It LOOKS like if the total file path exceeds some unknown limit, the filename specifically will be truncated to 50 characters.
I'm on 2420.
Re: [REQ] Support Windows 10 Long Path Functionality
Lowlander wrote: ↑Wed Jul 07, 2021 4:03 pm Which build (Help > About) are you on?
2420
So the files have long (240+ characters) Paths before Auto-Organize Files? Do they also get organized to long Paths afterwards? Is the database you're using from MediaMonkey 4 or did these files get added to the Library by MediaMonkey 5?
- Yes, I'm moving them from one drive to another so the first couple folders are different but the file path sizes are not super different
- Yes, except for the ones being truncated.
- I did start with MM4 many years ago but all of these files were recently downloaded with MediaMonkey 5 in the last few weeks.
Re: [REQ] Support Windows 10 Long Path Functionality
There is a bug there, added as: https://www.ventismedia.com/mantis/view.php?id=18122
Download MediaMonkey | License
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Help: Knowledge Base | MediaMonkey for Windows 5 | MediaMonkey for Android
Lowlander (MediaMonkey user since 2003)
Re: [REQ] Support Windows 10 Long Path Functionality
Yes, I can confirm that in the auto-organize dialog MM5 currently auto-cuts the long path/filename per spec in https://www.ventismedia.com/mantis/view.php?id=16505manalive wrote: ↑Wed Jul 07, 2021 4:10 pm Actually, I take that back- the problem here might be with the Auto Organize feature. It is truncating the destination path on some of the files and then it fails.
It is truncating some of my filenames to 50 characters, but it is not truncating all filenames that have more than 50 characters. It LOOKS like if the total file path exceeds some unknown limit, the filename specifically will be truncated to 50 characters.
I'm on 2420.
So if I understand properly you prefer for the auto-organize feature to not do the cut automatically, right? Or are you seeing some further issues?
Re: Support Windows 10 Long Path Functionality [#18122]
Yes, please. I don't have any problems with the long paths except in MM so I would prefer that limitation removed.
I agree with 'auto-resolving' the problems as per spec, but since the limitation, in this case, is only from MM and not windows I would prefer it was handled differently.
I agree with 'auto-resolving' the problems as per spec, but since the limitation, in this case, is only from MM and not windows I would prefer it was handled differently.
Re: Support Windows 10 Long Path Functionality [#18122]
Thanks for feedback, tracking as https://www.ventismedia.com/mantis/view ... 122#c64190