INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: There is no file with too long filename, but MC insists on import & MC Crash  (Read 3188 times)

Al ex

  • Citizen of the Universe
  • *****
  • Posts: 551

Trying to fix an issue with too long filenames. After library import, MC tells me "Skipped 62 files (filename too long)."

Below an example:

Skipped (filename too long):
    D:\6 Musik\3Stars\Johann Sebastian Bach - Bach Edition, Volume 18_ Cantatas_Kantaten, Volume IX (disc 1_ Cantatas _ Kantaten BWV 195, 1 & 63 (Holland Boys Choir; Netherlands Bach Collegium; Pieter Jan Leusink, conductor)) - 01 - I. Dem Gerechten muß das....mp3


Trying to locate this file in Windows 10, but there is no file of such a name?

I am currently using .23
MC .27 is permanently crashing 1-2 minutes after start.
Also had to roll back on my second laptop, as i got .Net Framework errors with .27, and two times BSoD.

The problem files are definitely not new, I am having them for years now.
I suppose that in some of the last versions of MC (24-27), something minor, but fundamental was changed that probably the too long filenames are causing these problems?

Is it possible that Windows 10 is hiding too long filenames???

Thanks.

Logged

Al ex

  • Citizen of the Universe
  • *****
  • Posts: 551

I donīt know why the too long filenames were not visible in Windows Explorer, however, with 3rd party tools, they are visible.

I used "Cut Long Names" in order to batch-shorten the filenames of 74 files to less than 250 characters: http://www.replsoft.com/cutlongnames.html

After that, I upgraded from .23 to the latest .29, no crashes anymore, my "musicbox" is rocking again flawlessly, problem solved :)
Logged

glynor

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 19608

I donīt know why the too long filenames were not visible in Windows Explorer, however, with 3rd party tools, they are visible.

Because Windows Explorer itself is subject to the 256+4 character path-length limit:
https://yabb.jriver.com/interact/index.php?topic=101754.msg705954#msg705954

(That's one of the main reasons MC has to respect it as well, because otherwise some file operations on the files would fail.)
Logged
"Some cultures are defined by their relationship to cheese."

Visit me on the Interweb Thingie: http://glynor.com/

flac.rules

  • Regular Member
  • Citizen of the Universe
  • *****
  • Posts: 1268

Because Windows Explorer itself is subject to the 256+4 character path-length limit:
https://yabb.jriver.com/interact/index.php?topic=101754.msg705954#msg705954

(That's one of the main reasons MC has to respect it as well, because otherwise some file operations on the files would fail.)

It is a bit on side of the topic, but I find it incredible that this hasn't been fixed yet, it was a stupid thing that should have been fixed 10 years ago. It was annoying already then.
Logged

Ogana Angela

  • Member
  • *
  • Posts: 1

I think you can use a simple tool. Long Path Tool. It will help you a lot.
Logged

Arindelle

  • Citizen of the Universe
  • *****
  • Posts: 2772

I think you can use a simple tool. Long Path Tool. It will help you a lot.

Here's another that I use ... just drag your main music directory and it will find the files https://sourceforge.net/projects/tlpd/ its fast on local drives
Logged
Pages: [1]   Go Up