All pastes #751755 Raw Edit

Unnamed

public text v1 · immutable
#751755 ·published 2007-10-27 18:05 UTC
rendered paste body
Hi,

I am William Pitcock and I am one of the main maintainers of audacious (the player core) and contributors to audacious-plugins, which until just a few moments ago had support for projectM 1.x.

We have been forced to remove projectM 1.x from our plugins collection because of many stability issues which have been experienced during the testing phase of our upcoming release series, audacious/audacious-plugins 1.4.

There's several reasons why we came to the decision to nuke it entirely from our repository:

Firstly, it crashes on a large majority of the maintainers' machines. Our plugin code is derived from projectm-xmms, so there is no reason why it shouldn't work (we haven't actually tried your code in XMMS, and there's in our opinion no reason to seeing that problems have been reported upstream in the libvisual plugin, and that the crash comes internally inside your own library).

Secondly, you have switched to CMake. We have found that CMake-based projects generally have a lack of success in being packaged in various repositories. This adds an unresolvable dependency to many distributions, and as such, may cause unfortunate delays in getting audacious-plugins packaged. Since this is uninteresting to us, we decided that is a reason to drop too.

Thirdly, there is concern about whether or not projectM is actually interested in the userbase of projectM which chooses to use Audacious. Considering that the website advertises "projectM running on XMMS on Gentoo", and that Gentoo removed XMMS, indicates a conscious decision to use XMMS over the Gentoo recommendation of Audacious. As such, we are concerned that any problem reports from Audacious users who use your visualization library would be ignored.

Due to these issues, we are considering dropping projectM 0.x support too, because of concerns that projectM 0.x having no future (which is a shame because it works a lot better than projectM 1.x does for at least us).

Hopefully, we can resolve the technical problems, and get clarification to our other concerns before an unfortunate decision is made.

Regards,
William Pitcock (nenolod)
audacious core development team