I have this issue fixed now - at least for my configuration. Hopefully
this information will be useful for someone else. Here is the summary:
I was running piCorePlayer v1.18b with the Synology distribution of LMS
7.7.3 and everything was working fine. Since Synology doesn't seem to
keep up with the latest versions of LMS, I decided to use pinkdot's LMS
Repack to upgrade to v7.9.0. After the upgrade, I was having problems
playing TuneIn Radio streams. Those streams look like they default to
AAC if your version of LMS supports it, i.e.
http://opml.radiotime.com/Tune.ashx?id=s33552&formats=aac,ogg,mp3,wmpro,wma,wmvoice&;.....
If I played the MP3 stream it played fine but AAC streams would not.
All my players (3 RPi & 1 Squeezebox Radio) are sync'd. Since all I
would get from AAC streams was popping and squeals occasionally, it
looked like a format conversion problem. If I turned off all decoding
of AAC streams except ACC -> ACC=Native, no AAC streams would play.
That shouldn't happen as all my players should support AAC. If I used
faad to convert the AAC stream to FLAC or MP3, I would get the squealing
and popping but no playback (except occasionally it would work for a few
minutes and then die :rolleyes:).
I removed one RPi from the sync group and and tried to play an AAC
stream on it which failed. I upgraded Squeezelite to v1.7 on that RPi
and it didn't help. I then upgraded the entire piCorePlayer from v1.18b
to v1.21g_RPi. With that upgrade made, that one RPi would now play AAC
streams. I put it back in the sync group and all players failed with an
AAC stream. I then upgraded the remaining RPis to the latest version,
put them all back into the sync group with my Squeezebox Radio and they
are all working fine now. I've been playing the Radio Paradise AAC 128K
stream for several hours now with no problems.
Apparently there was some change made between LMS v7.7.3 and v.7.9.0
that the RPis with v1.18b of piCorePlayer didn't like. The piCorePlayer
upgrade upgrades the underlying Tiny Core Linux O/S and that appears to
be where the problem existed. I also learned that when you put your
players in a sync group, a failure of any one of those players can
affect the entire group, so for testing it is best to limit things to
one player running independently until the problem is narrowed down.
------------------------------------------------------------------------
MCQ's Profile: http://forums.slimdevices.com/member.php?userid=65020
View this thread: http://forums.slimdevices.com/showthread.php?t=103636
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
