Possible for 2 Listens to Be Recorded When Playing TIDAL Content from Plex
Noah0504 opened this issue · 3 comments
When playing TIDAL content that has been added to a local music library, 2 separate events will be sent via webhooks and can result in 2 listens being recorded for the same song.
An event is sent by PMS when the progress during listening hits 50%. An event will also be sent by the "Plex media cloud server" when playback progress is 100%.
Is it possible to have an option for Eavesdrop.FM to filter out events sent from the cloud server? There may be a better way to handle this as some users may want these plays to be recorded if listening to TIDAL content within Plex that has not been added to their local library.
Thanks for the issue report.
I'll take a look and see what can be done. It'll largely depend on the content within the Plex webhook payload. If I can differentiate between the two events, it should be pretty straightforward to resolve.
On the other hand, there's a good argument to be made that this is actually unexpected behaviour on the Plex side, so I'll see if someone there might be interested in a better fix on their end 👍
I'll let you know the outcome either way.
Hello, I'm having this same issue when playing Plex music via the Symfonium music player.
When playing TIDAL content that has been added to a local music library, 2 separate events will be sent via webhooks and can result in 2 listens being recorded for the same song.
An event is sent by PMS when the progress during listening hits 50%. An event will also be sent by the "Plex media cloud server" when playback progress is 100%.
Is it possible to have an option for Eavesdrop.FM to filter out events sent from the cloud server? There may be a better way to handle this as some users may want these plays to be recorded if listening to TIDAL content within Plex that has not been added to their local library.
Ever find a workaround?