https://bugs.kde.org/show_bug.cgi?id=469617
--- Comment #3 from Andy Holmes <andrew.g.r.hol...@gmail.com> --- 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 is missing (older clients), it can be assumed `[1.0, 1.0, 1.0]`. The min/max would be required since if this is a useful feature, we will certainly want to be able to control it as well. If the value is, or falls back to `[1.0, 1.0, 1.0]` we can assume it's unsupported or not controllable and hide any UI in remote controls. -- You are receiving this mail because: You are watching all bug changes.
