Evgeny S

I suppose the same thing goes for playing similar tracks when an album ends and daily mixes. This is very desirable to have.

+1 for the custom mixer, the same as MPD "null" mixer option.

Looks like the issue is caused by librespot sending Notify response without waiting for the track to Load. It is less noticable when the track is already cached.

@michaelherger, no yet and I'm not sure where to look as well. I thought it might be caused by rpi3 not having an exact 44.1 clock, but for 5 minute...

Yes, there's also an end_of_track event which notifies Spotify that track has finished playing, but in my case it's not triggered, the server sends Load command before end_of_track happens.

From what I can tell from spirc communication - Windows client sends two notification events: one to ack the load command, another when loading is complete. I've added an additional...

@michaelherger, I've made changes in alsa backend. It's not compatible with current librespot version as I'm using alsa-sys crate which has required functions to implement hardware volume control.

It should be mentioned in the documentation that copas-mode code must run inside copas.addthread

fail2ban or similar could be used but the problem is that the disconnect log entry is missing client's IP address.