First, the bad news. In trying to test the playlist-file compatibility concern, I've discovered that at least on my system as it now exists, the default moosic configuration in the published codebase doesn't play WAV files (or anything else that relies on sox) correctly. IIRC it did work back in September, but I'm guessing something may have changed in the meantime; I've certainly done enough package upgrades for that to be plausible.
The moosic configuration from the Python-2-based instance I've been running for all these years, however, does play the files correctly. Trouble is, I don't know whether it's likely to work on a standard Debian install, or whether mine is special in some way. The difference is that the default ~/.moosic/config defines WAV files as being played by invoking 'sox $item -t ossdsp /dev/dsp' (and fails with "no handler for given file type 'ossdsp'"), and the live-environment one defines them to be played by invoking 'play $item'. This can be tested either via moosic, by adjusting the config file, or simply by invoking sox with that syntax on a WAV file which sox knows how to play. If you get a chance to test with either method on a known-baseline Debian system, and it turns out that the observed behavior is indeed not specific to my environment, please let me know; I'll be happy to either spin up a minor (micro?) release which adjusts the default config, or if preferred, just provide a patch without making a new release yet. Second, two pieces of good news. One: although the playlist-queue file doesn't seem to be identical in format to the one from the Python 2 daemon, it does seem to be quite similar, and the code which generates it hasn't changed (except for the exact syntax of catching errors). I was able to take a moosic configuration directory generated with the Python 2 daemon and load it with the Python 3 daemon, and it seems to work without issues. Two: it looks like either I was wrong in remembering that the Py2 daemon and Py3 client don't talk to one another cleanly, or I managed to fix the problem before and forgot about it. I accidentally invoked the Py3 client in a way which seems to have made it interact with the Py2 daemon, and aside from one text-encoding error message which might be cosmetic, it seems to have worked fine - including adding a file to the existing daemon's playlist in a way which the existing daemon was able to parse and handle without issues. So my previously mentioned upgrade-scenario concerns may indeed not be a problem in practice. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
