yeomanspc wrote: > Hi, > I have a few server setups. Main ones are QNAP running LMS 8.3. I also > have an Odroid U2 (like a pi) running Max2play 211022 - this is running > LMS 8.2 (cant seem to get it to install8.3). Last week this was on > 7.9.4. The players are Squeezebox classic (3?) and also old SB 2. I > get same or similar whether I run off main QNAP servers or Odroid. > Versions as follows: > > Logitech Media Server Version: 8.2.0 - 1627922070 @ Tue Aug 3 11:39:20 > CEST 2021 > Hostname: max2play114 > Server IP Address: 192.168.11.3 > Server HTTP Port Number: 9000 > Operating system: Debian - EN - utf8 > Platform Architecture: armv7l-linux > Perl Version: 5.18.2 - arm-linux-gnueabihf-thread-multi-64int > Audio::Scan: 0.95 > IO::Socket::SSL: 1.965 > Database Version: DBD::SQLite 1.34_01 (sqlite 3.7.7.1) > > Z100 WHTZ-FM has 4 streams - shoutcast; shoutcast secure; HLS and HLS > secure. I have tried all. I agree this afternoon I have not seen so > much the issues on ads, but I am seeing the spot block end message in > the shoutcast streams and right now no track names (maybe tag names are > missing) HLS seems (for the most part) to be displaying correct track > name and number. > Attaching a couple of screen shots - one from IPeng, and one of the > player. > Let me know if I can supply anything else. I guess I am looking for it > to display track info, and in all other scenarios, to display the > station name (ie discard tags if not track name
Thanks for the updated info - all are up to date and so it is not an old PlayHLS issue. I will do nothing with shoutcast streams. I'll look at PlayHLS to minimise the ad format messages which are specific to iHeart. Other stations use different formatting so it is functionality I'd prefer not to be in the HLS plugin as it will get out of control. Your info confirms that ad behaviour is quite varied and there are multiple cases. I don't usually test with Touch/Squeezeplay or Material UIs so I need to check if perhaps "adContext" display is somehow a UI specific artifact. General advice - the system that has IO::Socket::SSL version of 1.* needs to be updated to a 2.* - https connection will fail as 1.9* is very old in security terms. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=108466
_______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
