Not mangling names renders music unplayable on Windows 10 Samba

Asked Jul 24 '17 at 21:09

Active Jul 25 '17 at 18:27

Viewed 46 times

I have set up a very basic file server on linux. I used the Samba setting mangled names=no to disable to make sure the files are legiable under Windows, but once I do that, all the wav files I have stored in the folder are unreadable/unmovable/unplayable.

I cannot use different files, the script I am using can only generate .wav files.

An example of the file name would be 2017-07-24 12:54.wav, which otherwise gets mangled as 2BB0Y9~4.WAV.

edited Jul 25 '17 at 18:03

Chris Davies

116,213
16
160
287

asked Jul 24 '17 at 21:09

BarrowWight

See https://unix.stackexchange.com/q/381538/243257 for an example of mangling. – BarrowWight Jul 24 '17 at 22:22
Whoops. It is a date time string of format y-m-d h:m:s – BarrowWight Jul 24 '17 at 23:04
"2017-12-24 12:23.wav" – BarrowWight Jul 24 '17 at 23:16
The other question isn't really a duplicate, but the new answer there covers this – Michael Mrozek Jul 25 '17 at 18:27

Not mangling names renders music unplayable on Windows 10 Samba

0 Answers0

Linked