philippe_44 wrote: > While I was writing my previous post, the problem happened on my system, > so I was able to track it. In fact, it's a potential rare risk I have > identified and well documented (glad I take the time to write comments > in my code) where I don't have a good solution. It's exactly when > samples are missing to do the crossfade so the decided action is to wait > for more but that fails when the samples of the *finishing* song have > already been sent to the player. It's a difficult to explain race > condition, but that fits 100% with CPU overload which means sample > starving. It probably also happens with streaming services because, in > addition, with those, I need to query the next track pretty late before > the current one finishes or they see a too large download pause and > think that the connection is broken ... well, congratulation, you've > line up the perfect storm :-)
haha, lucky me! If it can't be fixed I can also live without the crossfade. It's a nice to have thing not to have silences between tracks. Another thing that just popped my mind is that I can write a watchdog. If the state is playing but progress didn't update for X seconds or something like that. ------------------------------------------------------------------------ marcelveldt's Profile: http://forums.slimdevices.com/member.php?userid=66909 View this thread: http://forums.slimdevices.com/showthread.php?t=110449 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
