INTERACT FORUM

More => Old Versions => JRiver Media Center 31 for Windows => Topic started by: Manfred on November 22, 2023, 03:26:32 am

Title: Tagging Error [Solved]
Post by: Manfred on November 22, 2023, 03:26:32 am
I have 4 files in my library with tagging error.

Filename is like:                 \\?\P:\AR-10\Audio\Classical\Saint-Saëns, Symphony No. 3 in C Minor ''Organ Symphony'', Introduction et rondo capriccioso in A Minor & La muse et le počte (2015-Stern)\02 - La muse et le počte für Violine, Violoncello und Orchester e-moll op. 132, R. 208 - La mus….flac
If I want to correct it into:       P:\AR-10\Audio\Classical\Saint-Saëns, Symphony No. 3 in C Minor ''Organ Symphony'', Introduction et rondo capriccioso in A Minor & La muse et le počte (2015-Stern)\02 - La muse et le počte für Violine, Violoncello und Orchester e-moll op. 132, R. 208 - La mus….flac

MC has a tagging error. Any Idea?

I have enabled extra long file names.
Title: Re: Tagging Error
Post by: zybex on November 22, 2023, 05:46:53 am
The \\?\ prefix is normal and is needed when the total filepath length is over 258 chars.
Tagging should still work. Check the read-only attribute in windows explorer.
Title: Re: Tagging Error [Solved]
Post by: Manfred on November 22, 2023, 08:05:50 am
I counted the file length with Power Shell Command:

get-childitem -File -Recurse | select-object Name, @{N="Length";E={$_.Name.Length}}

There was only a small overflow of 2-4 characters. So I decided to use the Folder Name AR10-A instead of AR-10\Audio.
Title: Re: Tagging Error [Solved]
Post by: zybex on November 22, 2023, 10:00:39 am
That prints only the actual filename length, but I was referring to the full path length including filename (FullName).
That you have files where just the actual filename is already over 258 chars is really asking for trouble :-X Many apps and some filesystems won't support anything above 255. That said, MC should be able to tag files with very long paths using the \\?\ prefix (but perhaps not those with filename length over 255).

get-childitem -File -Recurse | select-object FullName, @{N="Length";E={$_.FullName.Length}}

I'm also not sure if MC likes those filenames ending in ....flac - check if all failing files end in multiple dots.
Nevermind, that's actually an ellipsis. It should work.

Edit: NTFS is one of those where each PATH component (and the filename) cannot exceed 255 characters.
Edit2: Check if LongFileNames are actually enabled (https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later) in windows