Ian,
hehe ok. That's good. I guess I got the wrong impression from reading some of your other posts.
Kynes,
Well, I believe that there needs to be a balance of features vs simplicity. If you have too many features, you alienate users, and if you have too few, you alienate as well. I'm fairly happy with the featureset of xmplay, but I still think there's room for improvement
(that's a good thing btw).
While there may be people out there who are 'less qualified' users, that doesn't mean they shouldn't be stretched a bit now and then. We can't just dumb everything down to their level all the time. Its not like they'll be confused by two extra sliders on the EQ, or a few extra resample settings. Its not like the player won't work if you don't understand what they are. That's what default settings are for
.
Dirk,
No, I'm not. I wish I was a good enough coder to write something like that, though. The closest I get is playing around with the q2 source, haha.
Hyperdrive,
Cool to see you share my views
. While relative binary size doesn't mean much to me (except in those cool demoscene contests), I do appreciate fast, well-written code.
BoggyB,
While supporting additional stream formats sounds nice, it kind of pollutes the purpose of the player. As it is, I still have to use modplug (or the original tracker software) for some formats because xmplay doesn't support them. In XMplay, I think this should take priority over stream formats. Let those be supported by plugins as you say. But the core ideology of the player should be built-in as much as possible
. In the case of XMplay, that would be modules (right?). Again, just my opinion.
