Be able to disable the playcount and last play metadata fields from updating in .rbdata file

[Bjorn]

Could we please have an advanced option to disable the .rbdata including info about last play and playcount? And any other tags that are updated each time a track is played?

We've migrated to using .rbdata file and like we're using multiple computers, we're using a program called SyncThing to sync the .rbdata files across all computers so that any changes made to the mix points in one studio, replicates to the next.

The issue with the playcount and last play tags is that there are hundreds of files updated daily, and we often have sync conflics when a few studios play the same song.

We only want manual things we update in track tool to populate the .rbdata file basically.

We've tired using other databases in the past, but we've found .rbdata files to be our best bet.

This would be amazing.


Cheers,
Bjorn

 

[djsoft]

The issue with the playcount and last play tags is that there are hundreds of files updated daily, and we often have sync conflics when a few studios play the same song.

In this case, when multiple computers access the same data, it is preferrable to use the MySQL option: https://manual.djsoft.net/radioboss/en/additional-information-storage.htm

Without saving Last Played tag, most repeat protection features may fail to work properly.

 

[Bjorn]

Correct, but the my SQL option is much more config work, and it's still flooding the database with many track changes that can also conflict. We often have the same playlists playing at the same time, so the database is being updated at the same time for the same files, but on different machines.

We don't utilise those repeat protection features etc, so this wouldn't be an issue for us.

An advanced option is probably the best way... even if there is a way for us to configure that in the program files manually?

 

[djsoft]

Correct, but the my SQL option is much more config work, and it's still flooding the database with many track changes that can also conflict

You can install MariaDB - the default configuration will suffice. There will be no conflicts as all access is queued and data integrity is ensured. This is not the case when use file-based storage (.rbdata) and multiple machines access it: what happens if two or more computers write to the same file at the same time, is unpredictable.

An advanced option is probably the best way...

It still wouldn't work reliably. File access is meant to be used by a single instance on one machine.