Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libxmp output plugin #274

Open
ghost opened this issue Apr 14, 2015 · 2 comments
Open

libxmp output plugin #274

ghost opened this issue Apr 14, 2015 · 2 comments

Comments

@ghost
Copy link

ghost commented Apr 14, 2015

Another one for the low-priority request department. :)

As compared to modplug, xmp has more accurate playback, supports a wider range of formats, and seems to be more frequently updated:

http://sourceforge.net/projects/xmp/files/libxmp/4.3.8/

@flyingmutant flyingmutant changed the title libxmp as backend for tracker music libxmp output plugin Apr 14, 2015
@velusip
Copy link

velusip commented Apr 14, 2015

I would vouch for libxmp as well. Many of the features are inspired by the BASS library which can't be beat for module playback. While BASS is free for non-commercial use, the non-GPL license only makes some details of redistribution and forking complicated, so libxmp is the best thing for this context.

@tidux
Copy link

tidux commented Feb 16, 2022

Bumping this from beyond the grave for a reason. The refusal to implement layered plugins in #923 means that all the tens of thousands of modules shipped as zip/lharc on modarchive, aminet, etc. can't be opened with the modplug plugin without doing major filesystem surgery - and because most of those archives also contain multiple files it'd be a manual process. libxmp handles archive parsing internal to itself, which would avoid the issue for tracker modules where this gap is most keenly felt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants