Wondering if anyone has come across this. A station that uses our service gets this every now and then (usually specific DJ connections, When this happens, there are times the connection for drops. Might anyone know what is causing this?

2018-12-15 16:30:47   WARN   [DST  xxx.xxx.xxx.xxx:xxxxx sid=1] Frame settings changed, could cause playback problems: bitrate 80(128) samplerate 22050(44100)
2018-12-15 16:30:47   WARN   [DST xxx.xxx.xxx.xxx:xxxxxsid=1] Frame settings changed, could cause playback problems: samplerate 22050(44100)
2018-12-15 16:30:47   WARN   [DST xxx.xxx.xxx.xxx:xxxxx sid=1] Frame settings changed, could cause playback problems: bitrate 128(80)
2018-12-15 16:30:47   WARN   [DST xxx.xxx.xxx.xxx:xxxxx sid=1] Frame settings changed, could cause playback problems: bitrate 80(128) samplerate 22050(44100)
2018-12-15 16:30:47   WARN   [DST xxx.xxx.xxx.xxx:xxxxx sid=1] Frame settings changed, could cause playback problems: samplerate 22050(44100)
2018-12-15 16:30:47   WARN   [DST xxx.xxx.xxx.xxx:xxxxx sid=1] Frame settings changed, could cause playback problems: samplerate 22050(44100)
2018-12-15 16:30:47   WARN   [DST xxx.xxx.xxx.xxx:xxxxx sid=1] Frame settings changed, could cause playback problems: samplerate 22050(44100)
2018-12-15 16:30:47   WARN   [DST xxx.xxx.xxx.xxx:xxxxx sid=1] Frame settings changed, could cause playback problems: samplerate 22050(44100)
2018-12-15 16:30:47   WARN   [DST xxx.xxx.xxx.xxx:xxxxx sid=1] Frame settings changed, could cause playback problems: samplerate 22050(44100)
2018-12-15 16:30:47   WARN   [DST xxx.xxx.xxx.xxx:xxxxx sid=1] Frame settings changed, could cause playback problems: samplerate 22050(44100)

 what version of sc_serv2 do you use?

Downgrade to shoutcast v 2.5 for fix it

what version of sc_serv2 do you use?

2.5.5.733

Downgrade to shoutcast v 2.5 for fix it

Which build?