Audacious-Bot
commented
5 months ago Original Redmine Comment Author Name: Michael Schwendt Original Date: 2018-12-30T12:14:56Z
My advice: Don't "switch", but introduce a separate input plugin for a new MOD backend lib.
The rationale is simple. Hardly any MOD player lib is perfect. There are many thousands of MOD files. (Side-note: when I use the term "MOD" I don't refer to only the ancient .mod files from the late 80's and early 90's, but also the many derivatives that have been published later.) Typically, authors of new MOD playing libs start with a new set of test files, such as their favorite ones and new problematic ones pointed out in bug reports. A lib would need to be really popular for more users to give it a try and test it with old and new files in their own mod file collections.
Audacious runs fine with multiple MOD input plugins installed. Users may choose to disable individual plugins. No harm is done, if keeping alternative input plugins for some time.
About XMP and its plugin for Audacious: The plugin has been ported to Audacious 3 a long time ago and continues to work fine. I'm not aware of any immediate maintenance requirements. Libxmp is in a fine state and continues to receive fixes for problematic files when they come up. I don't think it supports the .dsm format of your test file. In modplug 0.8.9, some of the samples sound slightly out of tune here.
Author Name: Jonathan Rubenstein Original Redmine Issue: https://redmine.audacious-media-player.org/issues/848 Original Date: 2018-12-02
I posted this before as note #303-6, however that bug is quite old (on top of being rejected) and I probably did not get noticed, so I am making a new report as a feature request.
Libmodplug is Audacious' library of choice for its official module playing input plugin, it enables playback of many old formats such as xm, it, mod, and others. Unfortunately, libmodplug appears to be only sporadically maintained, the most recent commit listed on sourceforge as being "9357867":https://sourceforge.net/p/modplug-xmms/git/ci/9357867a5cf10e601499146013270dee95acc9bd/log/, dated June 2nd, 2017, and on GitHub, "af00e21":https://github.com/Konstanty/libmodplug/commits/af00e21737839465d0dc253cf356d2b9c7554eed, dated August 2nd, 2018. As listed on #303, it does have some playback issues with some modules, one of which I've attached to this report. Generally, it also plays modules back with a low amplitude, however that could be the result of Audacious' plugin's implementation.
In #303-2, libxmp was discussed, however the mentioned audacious plugin (#303-5) is no longer maintained, and libxmp itself appears to be sporadically maintained as well. The latest commit, "2a16cdf":https://github.com/cmatsuoka/libxmp/commits/2a16cdf69e4cd1d96d51a68b65ce2304203bdc4f, is dated Oct 14th, 2018.
So, I suggest switching to "libopenmpt":https://lib.openmpt.org/libopenmpt, a cross-platform module playback library based off of "OpenMPT":https://openmpt.org, which is itself based off the open source release of ModPlug Tracker. It's actively maintained, (latest revision is "rev 10998":https://source.openmpt.org/browse/openmpt/trunk/OpenMPT/libopenmpt/?op=log&rev=10998&peg=10998 dated November 25th, 2018) and should have better support for playing back modules accurately. The types of modules it supports should be equivalent or greater than libmodplug, a list of supported modules can be found on the "features page":https://openmpt.org/features. For example, libopenmpt handles the problematic module attached to this report flawlessly. Chris Spiegel has created a working audacious plugin for this already, however his repo does not currently feature a code license. https://github.com/cspiegel/audacious-openmpt You might be able to get into a dialog with him about absorbing it into the audacious-plugins repo. His email listed in the git commit log is cspiegel at gmail.
I've used his plugin for a while and it works great in my experience, and the amplitude seems to be correct, so the modules don't sound so quiet compared to my other music files.