Feature Request: Saving statistics to tag

[ghost]

hey guys, is there any major reason why statistics cant be saved to tags?

[sighook]

@XIncognito10
What statistics do you mean?
And what about the torrents? By changing the tags, we will change the files, and torrent will overwrite them.
I wouldn't mind this feature as optional, because

1. I like when torrent controls the consistency of the files and redownloads if the file(s) is(are) broken; hard drives are unreliable;
2. The settings are too individuals; is there a need to transfer statistics between music players?

[ghost]

I meant like the fields in the settings under the statistics heading. Things like last play, added, play count, skip count, ect. Is there a particular reason why these couldnt be under a gmusicbrowser specific tag in the music so that there is less dependency on the database? because whenever my files are changed or moved externally, all of this data gets wiped

[RomanHargrave]

It's not a bad idea. If disk IO is a concern, generating a unique ID for each track in the database and adding it to the file would not be a bad idea either, in order to prevent disassociation from moving/external changes.

[MigueLesPaul]

I have a little data base management script that does this exactly. When it started, it was just a little text file with colummns and needed a way to relate the files in the entries. Then I discovered Gmusicbrowser, ahem, fell in love with it and re-wrote the entire thing to handle song statistics from the default database file. For personal use, it works using a number based on the seconds since the epoch. Whenever you add a file, or a group of files, this ensures the ID is unique. I guess.

[ghost]

Hey @MigueLesPaul do you still have this script?