Closed bonelifer closed 2 months ago
Okay, once the db update process finished, it created tag_cache, which I assume is the name you chose for the mpd db.
Hello, yes, it is configured like this in a simple generate configuration file. See the snippet I got from a running instance:
database {
plugin "simple"
path "/db/tag_cache"
}
Do you need the path to be configurable? If so, I assume you only need to change the "tag_cache" part, is that right?
No, my library has grown to 50,000+ tracks. So I'm not used to db file not showing up immediately. After it finally finished updating and it appeared, with that large a library it took awhile.
Also I just wanted to point out those three settings:
HTTPD_OUTPUT_ENCODER=wave
HTTPD_OUTPUT_ENCODER_BITRATE=128k
HTTPD_OUTPUT_ENCODER_QUALITY=3
don't make a lot of sense together. Bitrate/Quality are not required for wave. If you want wave as default, I would change the defaults in the compose like this:
- HTTPD_OUTPUT_ENCODER=${HTTPD_OUTPUT_ENCODER:-wave}
- HTTPD_OUTPUT_ENCODER_BITRATE=${HTTPD_OUTPUT_ENCODER_BITRATE:-}
- HTTPD_OUTPUT_ENCODER_QUALITY=${HTTPD_OUTPUT_ENCODER_QUALITY:-}
so bitrate and quality are empty unless set in the env. Also the port is not needed with host networking, but you can change the exposed port using the variable MPD_PORT if you don't want it on port 6600.
Just my 2 cents.
No, my library has grown to 50,000+ tracks. So I'm not used to db file not showing up immediately. After it finally finished updating and it appeared, with that large a library it took awhile.
so no changes are needed for this issue, is that so?
I also noticed that the file does not appear until the scan is over. I assume this is done in order to avoid lots of i/o. The data are probably kept in memory and written as the final step of the scan.
Just setting this up. In the db folder I only see Stickers, State and not the mpd db.
docker-compose.yml
:.env
: