Skip to content

Allow disabling contentdb [PERFECTIVE]

Matti Tiainen requested to merge mvtiaine/uade:disable-contentdb-option into master

If using external songlengths db, the contentdb is not really useful.

Also one might not want to mess up with users own contentdb in $HOME.

Another issue is that for example with audacious-uade there are separate libuade "probe" instances for populating playlist meta data and when the playlist size grows to 100000+ entries just saving the contentdb with every uade_cleanup_state() starts to get quite slow. And it's not really "thread safe" with multiple instances doing that concurrently.

Merge request reports