Paul Webster wrote: > However, if that is checking a URL (which it appears to be based on the > variable name) then I think it is quite possible for a genuine AAC to > not have a dot. > If correct then would it mean that real AAC content would not > necessarily be detected properly?
Here is my take: The problem here is that the last three characters of the stream url -http://strm112.1.fm/reggae_mobile_aac- suggest that it might be -aac-, but it actually has -Content-Type- correctly identifying it as -audio/mpeg-, i.e. MP3. But LMS overrides that and deems it to be -aac-. Which doesn't work. I don't think you can guarantee a win when dealing with misconfigured servers. But this server is not misconfigured. It is LMS's attempt to deal with other misconfigured servers that is breaking a correctly configured server. And the reason seems to be that LMS's 'test' for misconfiguredness is, perhaps, one dot shorter than it might be. I'd suggest that LMS should not break a correctly configured stream. ------------------------------------------------------------------------ mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=113719 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
