Played# update using upnp mode

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: Played# update using upnp mode

Re: Played# update using upnp mode

by nohitter151 » Tue Sep 03, 2013 2:54 pm

http://www.ventismedia.com/mantis/view.php?id=7086
There are actually 2 other problems:

1) Some clients seek end of file for another reason than playback
-> this is resolved by increasing the play counter only if client requests portion at 90% of the file
2) Some clients pre-buffers the file, it means that 90% of the file can be buffered although user could abort the playback
-> we can hardly do something about it
http://www.ventismedia.com/mantis/view.php?id=7837
http://www.ventismedia.com/mantis/view.php?id=8615
As described in 0007837, play count over DLNA are often inaccurate because many clients will buffer the entire file and appear to play it even if the user stopped it after 1s.

Re: Played# update using upnp mode

by Lowlander » Mon Sep 02, 2013 2:37 pm

I'm just stating what the developers have stated, not what I think. No need to attack.

Re: Played# update using upnp mode

by mcow » Mon Sep 02, 2013 12:03 pm

It has been discussed, and refuted.

I can't help it if you won't hear the solution. But given that you can't code, and don't know anything about coding, maybe you should just stand down, and not be making declarations about what is or isn't possible.

Re: Played# update using upnp mode

by Lowlander » Sat Aug 31, 2013 11:27 pm

Many clients ask the end of a file prior to playing (to get meta data). Clients may also buffer track prior to playing, which means MMW doesn't know if users actually ended up playing the file. This has been discussed several times already.

Re: Played# update using upnp mode

by dtsig » Sat Aug 31, 2013 10:08 pm

Lowlander wrote:As MMW doesn't know when a track is played by a client this is impossible.
You say this but i just don't understand. SOMETHING in *mm* must know when the files is being played by ANYTHING in that MM gets the file and *streams* it.

If MM doesn't *know* (mmw or service) the could you explain to me the series of events that happens when:

1) start my blu-ray player
2) Select to connect to MediaMonkey ... get list of *nodes*
--> so at this point MM knows
3) select TV ... get list
--> so at this point MM knows
4) select series .. get list
--> so at this point MM knows
5) select A series ... get list of eps
--> so at this point MM knows
6) select an ep ... player starts playing
-- SO you are saying at this point MM does not know ... it does not read the file ... it does not start streaming ...

If MM doesn't know and isn't reading the file and isn't streaming it .. the what is doing that?

I really am interested. After being a sw jockey for 30+ years I am very interested in what other thing is doing the reading/streaming.

Thanks
Dsig

Re: Played# update using upnp mode

by mcow » Sat Aug 31, 2013 9:13 pm

It is not impossible. MMA and MMW could be better integrated and enable this feature.

Re: Played# update using upnp mode

by Lowlander » Sat Aug 31, 2013 12:40 pm

As MMW doesn't know when a track is played by a client this is impossible.

Played# update using upnp mode

by geoker » Sat Aug 31, 2013 6:17 am

Hi
When using MM on the PC the played count only increments when you have played the complete track, using upnp on the android version updates the played count immediately which means that if I only listen to a song intro to remind myself of the music it counts as a complete played track.

It would be better if the android app followed the same rules as the main system and only updated track played count after the complete track has played...

Motorola Xoom M604 --> Android 4.1.2,
LG - P880 --> Android 4.03
Asus ME301T --> Android 4.2.1

MM --> 4.1.0 1656

Apart from that minor niggle everything is working amazingly well. This is the app I have been looking for... :D

Regards
Geoff

Top