by mcow » Wed Mar 27, 2013 10:18 pm
Now that's this issue is fixed (at least, I think it is -- anyone confirm?), there's the other side of the coin - no increase in last-played or playcount unless you play all the way to the end. This is the same as MMW, and easier to deal with.
Barry4679 wrote:The MMA UI is fairly hair triggered, and it is very easy to accidentally trigger a track play while browsing an album.
It's generally too easy to do all sorts of things that can't be easily undone. In particular, far too easy to interrupt a playing track.
I would like to see two-factor UI: either a tap in two separate locations on the screen, or a gesture, for any action that will affect music playing either by starting or stopping it, other than taps on the actual Play/Prev/Next buttons. The idea proffered in another topic, of dragging left to skip forward in the playlist but not actually skip until a confirmation tap, is an example. Similarly when browsing tracks: don't start just because a tap hit the song entry.
As for the alleged difficulties with MMW UPnP server immediately updating last-played on first access: caching doesn't mean anything in this context. The UPnP spec adopts a general eventing framework, and it would be -- well, not simple, but quite doable -- to have the MMA client publish an eventing service that notifies about its actions, like Play Completed, and to have the MMW server to subscribe to it. I don't care if other UPnP clients don't also publish like that; MMW can treat them as it currently does. I wouldn't be surprised if there is already a set of events publicly defined for exactly this purpose.
Now that's this issue is fixed (at least, I think it is -- anyone confirm?), there's the other side of the coin - no increase in last-played or playcount unless you play all the way to the end. This is the same as MMW, and easier to deal with.
[quote="Barry4679"]The MMA UI is fairly hair triggered, and it is very easy to accidentally trigger a track play while browsing an album.[/quote]
It's generally too easy to do all sorts of things that can't be easily undone. In particular, far too easy to interrupt a playing track.
I would like to see two-factor UI: either a tap in two separate locations on the screen, or a gesture, for any action that will affect music playing either by starting or stopping it, other than taps on the actual Play/Prev/Next buttons. The idea proffered in another topic, of dragging left to skip forward in the playlist but not actually skip until a confirmation tap, is an example. Similarly when browsing tracks: don't start just because a tap hit the song entry.
As for the alleged difficulties with MMW UPnP server immediately updating last-played on first access: caching doesn't mean anything in this context. The UPnP spec adopts a general eventing framework, and it would be -- well, not simple, but quite doable -- to have the MMA client publish an eventing service that notifies about its actions, like Play Completed, and to have the MMW server to subscribe to it. I don't care if other UPnP clients don't also publish like that; MMW can treat them as it currently does. I wouldn't be surprised if there is already a set of events publicly defined for exactly this purpose.
