Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: aliumalik bullshit split (Read 2743 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

aliumalik bullshit split

Peter, I have been reading a couple of threads where most people tend to agree that frequent writing of tags can result in corruption. Even though it is a slight possibility wouldn't it be prudent to store tags like last played, play count, rating etc in a separate database which would not warrant the writing of tags again and again for storage. I know right now the tracks are stored in a separate database but the data is based on file path. I suggest that something similar to foo_playcount_sql be adopted for storage of such data to minimize the rewriting of current files.
 

aliumalik bullshit split

Reply #1 –
Quote from: aliumalik on
I know right now the tracks are stored in a separate database [...]. I suggest that [a separate database] be adopted [...] to minimize the rewriting of current files.
So... what? Are you deliberately contradicting yourself or don't really understand what you are talking about?
Full-quoting makes you scroll past the same junk over and over.

aliumalik bullshit split

Reply #2 –
I meant a separate database format which would allow for movement of library folder or would carry over statistics for files moved between folders instead of writing tags to the file and then moving it...

aliumalik bullshit split

Reply #3 –
you can preserve statistics if you use file operations for managing folders (inside media library path)