INTERACT FORUM

More => Old Versions => JRiver Media Center 22 for Windows => Topic started by: Manfred on January 12, 2017, 01:11:46 pm

Title: Failed to import - filename too long?
Post by: Manfred on January 12, 2017, 01:11:46 pm

I got the error message:
Failed to import:
    M:\Audio\Kansas City Symphony & Michael Stern\Saint-Saëns_ Symphony No. 3 in C Minor Organ Symphony, Introduction et rondo capriccioso in A Minor & La muse et le poète\Cover - Saint-Saëns_ Symphony No. 3 in C Minor Organ Symphony, Introduction et rondo capriccioso in A Minor & La muse et le poète.jpg
    M:\Audio\Kansas City Symphony & Michael Stern\Saint-Saëns_ Symphony No. 3 in C Minor Organ Symphony, Introduction et rondo capriccioso in A Minor & La muse et le poète\Booklet - Saint-Saëns_ Symphony No. 3 in C Minor Organ Symphony, Introduction et rondo capriccioso in A Minor & La muse et le poète.pdf

The .jpg and  the .pdf file are separate files in the directory.
What is wrong? Does MC concatenate the path to the folder + the filename?
I have enabled the experimental long file names.

Title: Re: Failed to import - filename to long?
Post by: BillT on January 12, 2017, 02:17:06 pm

Yes, the filename is too long. NTFS has a filename length limitation of about 255 characters and a path limit of about 259 characters. Your names seem to be 301 characters long.

I come across this sometimes with CDs that have stupidly long metadata in the downloaded track data, and I don't notice. (I tend to just use a short name like cover.jpg for cover images stored in the same folder as the music files. The name doesn't have to have a detailed description as there'll only be one cover file in each music directory.)

Title: Re: Failed to import - filename to long?
Post by: MikeO on January 13, 2017, 04:30:47 am

Without being rude why would you want file names to so descriptive. Especialy folder names.jpeg

I can only think it could be to use as a direct USB drive attached to a streamer.

Even then every file name you load takes processor speed.

I am not suggesting file1234 but something brief and then use tags to add "war &peace"

I often use a USB drive directly on cambride audio cxn , big names sloooow things down. I learned the hard way

Mike

Title: Re: Failed to import - filename too long?
Post by: Manfred on January 13, 2017, 06:20:01 am

I simply bought these at HighRes Audio - it was not my idea to have this long filenames.

Title: Re: Failed to import - filename too long?
Post by: Matt on January 13, 2017, 07:43:11 am

This was a funny one.  I thought we had already sorted all the long filename issues, but we had not.

So coming next build:
Fixed: Long filenames still didn't import reliably (even with the long filename option set).

Title: Re: Failed to import - filename too long?
Post by: Manfred on January 13, 2017, 08:51:35 am

Thank's  :).

In principle I could also rename it no big issue - First I only wnated to understand why it failed.

It would be nice now because you don't break the process:
download the file via HighResMgr from HighResAudio->Store it automatically->NAS//M:...->MC runs autoimport in the background -> every thing is fine-> listen to the music.