Ron,
Good. No offense but I think the db is the wrong place for it. I always ended up losing all my playlists somehow and it was very discouraging that there was no good way to back them up, short of backing up the whole db. And then if there was ever a problem with the db …. well .. you had to lose all your playlists too 🙁
Any eta for this? I’d hate to do a bunch of scripting now to only have to re-write them shortly.
scram: in the short term i’m going to look at xml files. I’ll let you know if i come up with anything
FYI: i am planning to write a web-app frontend that determines the current song being streamed to a certain IP and allows you to add this song to a playlist – unless someone has already done this! I wanted to avoid using m3u files and stick to just the mt-daapd.playlist file for centralized management. For static lists I would just have ‘path is /music/file.flac ‘ etc. This way I can avoid loading the hundreds of m3u’s that I don’t want to load by default. I’m not sure if this will introduce any performance issues …
do the playlists get re-scanned during the re-scan interval? will the future mt-daapd.playlist file be re-scanned as well? It would be incredibly helpful if it was !