Re: Playback Statistics component: v3.x foo_playcount
Reply #127 – 2010-09-26 05:47:02
I requested that too. But i think the big problem to implement this is that if you change the pattern for identification then the playback statistics must be erased. Just imagine a simple example: Let's say you have %artist% as pattern and you change it to %artist% %title% - how should the component know how much a title was played since it didn't track that? What I don't get is if you have shared UIDs such as %artist% %title% and you have one added last year and a new one that matches that pattern what happens to the date based data? Is %added% anchored to the oldest date? Is last played anchored to the latest date? I would have thought that the way to impliment such a method is to have both a real and a pseudo UID. So stats are gathered at the Real UID level and then shared at the Pseudo UID level. When you change the Pseudo UID the stats are redistributed accordingly. So: REAL UID: some kind of hash/fingerprint based on file data (that must always be unique). c:\music\beatles 01 help.mp3 ADDED: 01.01.10 FIRST PLAYED: 01.01.10 LAST PLAYED: 06.06.10 Played: 5 c:\music\lossless\beatles 01 help_remaster.flac ADDED: 02.02.10 FIRST PLAYED: 05.02.10 LAST PLAYED: 16.10.10 Played: 2 PSEUDO UID PATTERN: %artist% - %title% (NOT unique). Stats Component collates data from REAL UIDs taking earliest %added%, earliest %first played%, latest %last played% and sums the playcount. So we have: Beatles - Help: ADDED: 01.01.10 FIRST PLAYED: 01.01.10 LAST PLAYED: 16.10.10 Played: 7 When you change the Pseudo UID the data from the root Real UID is simply collated to fit the new Pseudo UID pattern. Couldn't that have worked? C.