[kdeconnect] [Bug 469617] MPRIS receivers/controllers are ignoring playback rate to extrapolate current play position

2024-06-03 Thread Double Jumper
https://bugs.kde.org/show_bug.cgi?id=469617 Double Jumper changed: What|Removed |Added CC||doubjumper+...@gmail.com -- You are receiving

[kdeconnect] [Bug 469617] MPRIS receivers/controllers are ignoring playback rate to extrapolate current play position

2023-05-23 Thread Andy Holmes
https://bugs.kde.org/show_bug.cgi?id=469617 --- Comment #3 from Andy Holmes --- Fair enough, I don't do a lot of podcasting so I hadn't considered that. In that case I would suggest a slightly simplified way of communicating this, in the form of a triplet like `[rate, min, max]`. If the field

[kdeconnect] [Bug 469617] MPRIS receivers/controllers are ignoring playback rate to extrapolate current play position

2023-05-12 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=469617 --- Comment #2 from b...@mogwai.be --- (In reply to Andy Holmes from comment #1) > ... > It would very much preferable to just have clients update the position > property more frequently in this case, rather than try to support more of > the MPRIS

[kdeconnect] [Bug 469617] MPRIS receivers/controllers are ignoring playback rate to extrapolate current play position

2023-05-11 Thread Andy Holmes
https://bugs.kde.org/show_bug.cgi?id=469617 --- Comment #1 from Andy Holmes --- I'd like to put in my two cents here, having struggled with many players claiming MPRIS compliance. The reality is that there 1-2 players at any given time that correctly implement the full interface, especially when