Most of the file names that are created from TVHeadend recordings are in the correct format ie .
ELEVEN-Supernatural.2015-02-02.20-33.ts
GO!-The Big Bang Theory.2015-02-01.21-01.ts
but occasionally I get file names created thus .
G62FD3~6.TS
Looks like what Windows does (or used to) with long file names to make them readable in old MS-DOS format.
Anyone noticed this before and what causes it?
It's because the file name contains characters that are 'illegal' under Windows naming convention (e.g. apostrophes) - but they're acceptable to Unix naming. So, if you view the file under a Linux shell, you'll see the real name, but Windows (SMB, rather) has to give it an alias to be able to see it.
There are options in tvh to 'Remove All Unsafe Characters From Filename' (which strips out everything 'unusual' - 3.4 and 3.9.x) and 'Use Windows-compatible filenames' (which only strips out what Windows would otherwise choke on - 3.9.x only).
(2015-02-02, 13:42)Prof Yaffle Wrote: [ -> ]It's because the file name contains characters that are 'illegal' under Windows naming convention (e.g. apostrophes) - but they're acceptable to Unix naming. So, if you view the file under a Linux shell, you'll see the real name, but Windows (SMB, rather) has to give it an alias to be able to see it.
There are options in tvh to 'Remove All Unsafe Characters From Filename' (which strips out everything 'unusual' - 3.4 and 3.9.x) and 'Use Windows-compatible filenames' (which only strips out what Windows would otherwise choke on - 3.9.x only).
Agree with Prof Yaffle, I would also select the "replace whitespace with (-)" option in the TVHeadEnd
settings.