Bugzilla – Bug 768
Unable to play an OGG file with a very long name?
Last modified: 2011-03-16 04:19:54 UTC
My slimserver, when faced with this one file, flashes between "Unable to contact slimserver. Check that the software is running" and normal display. No sound comes out. I have tried to investigate, but have not found anything strange in either the packet dumps or in the file, except that it is the longest filename in my collection (145 characters). The information is below, copied from the slimserver Web UI: Title: Feierlich und gemessen, ohne zu schleppen - Sehr einfach und schlicht wie eine Volksweise - Symphony No 1 in D major Artist: London Symphony Orchestra Album: Mahler : Mahler Symphonies 1 & 2 - Disc 1 Genre: (empty) Track: 3 File Format: Ogg Vorbis Duration: 10:58 File Length: 8,550,629 Bytes Bitrate: 112kbps CBR Location: file:///home/samba/musikk/hta/ogg/London Symphony Orchestra/Mahler : Mahler Symphonies 1 & 2 - Disc 1/London Symphony Orchestra - Feierlich und gemessen, ohne zu schleppen - Sehr einfach und schlicht wie eine Volksweise - Symphony No 1 in D major.ogg (Download) Date Modified: Thursday, December 9, 2004, 20.47 The firmware version is 39 - this was not on the dropdown list for "version".
if you think its the long name, why not rename it or retag it to confirm? also try using d_source debugging from the server settings and see if you are getting something. this could simply be a corrupt ogg file.
I copied the file to where the URL was file:///home/samba/musikk/hta/testfile.ogg - and it played beautifully. Thanks for the question!
I'm just curious on whether this is a long pathname problem, or a special character problem. If you simply remove the : and & from the paths, does it work? can you try playing this file with d_source checked in the server settings, debugging. then paste a bit of the log when you try to play the track? default log location in linux is /tmp/slimserver.log also, remarking this bug as a slimserver bug. There should now be a dropdown for the appropriate server version. Are any of the characters in the filename accented?
Dan thinks that this is fixed in the 6.0 beta. Please verify and reopen if it's still an issue.
Verified that it works in version 6.0.2 - trunk (never figured out how to get hold of a beta). Thanks!