conquerist wrote:
>
> To "fix" the existing .flac files, the extension portion of their 8.3
> filenames needs to be set to .FLA, and an easy way to do that is to
> place the following batch script into the *music root directory* as
> *fix_8dot3.bat* and executing it with the necessary privileges (e.g.
> right click -> run as administrator). The script iterates over all .flac
> files in the directory in which the script is located (including
> subdirectories) and changes the extension portion of their 8.3 filename
> to .FLA. This strictly speaking works independently of the registry
> setting above, however without having Win95TruncatedExtensions set to
> "1", new files will continue to be created with .FL~ and on these
> analysis will fail until their 8.3 file extension is changed to .FLA,
> e.g. by running the batch script again.
> >
Code:
--------------------
> > for /r %%A in (*.flac) do (
> fsutil file setshortname "%%~A" %%~snA.FLA
> )
--------------------
> >
>
> Personally, I used the second method (registry and batch script),
> because it fixes the problem for files for files that already exist as
> well as those that are created after performing the fix, all while
> retaining a .flac extension. However, the first method doesn't require
> modifying the registry or executing a batch file from the internet.
>
> I hope this helps anyone who's still having this problem. Why "still"?
> As a follow-up, Windows 10 seems to default back to the pre-Windows 7
> behavior concerning .FLA and .FL~, so this thread is especially
> relevant for Windows 7, or more precisely, for .flac files that were
> either created on a Windows 7 machine and not touched afterwards by a
> non-affected OS as well as for files that have been renamed or copied
> in Windows 7.
Wow, great work figuring that out after all those years!
If I may add yet another twist to the problem: my flac files are on a
Linux server and shared with my windows PC via an SMB share. When I try
to run the batch file, I get
Code:
--------------------
A local NTFS volume is required for this operation.
--------------------
I guess that this means that SMB shares don't support 8.3 filenames at
all? That would seem a bit strange though. I would rather expect "the
opposite" as it were, i.e. Samba only supporting 8.3... Or maybe it
means that Samba already did the conversion internally and wont let
anyone interfere? In that case, what could be a workaround? (Except for
the obvious (and older) one: copying all files to the NTFS HDD and then
back.)
*Server*: LMS 7.9.3 on an Ubuntu 18.04 virtual machine
*Players*: Radio, Touch, Duet (Receiver & Controller), 2 Booms
*Remote control apps*: SqueezePad (iOS), Squeezecontroller (Android)
*Important plugins*: Trackstat, Spicefly Sugarcube, Lazy Search Music,
Custom Browse, Multi Library, Material Skin
------------------------------------------------------------------------
chaug's Profile: http://forums.slimdevices.com/member.php?userid=47641
View this thread: http://forums.slimdevices.com/showthread.php?t=96392
_______________________________________________
ripping mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/ripping
