Quoting Drake Wilson <[EMAIL PROTECTED]>:
I don't know whether this is considered a bug in the vocoder plugin, in the Musepack plugin, or in some central xform chaining that (silently?) fails to recognize that a numeric format conversion before the effects chain to make it resolve, so I'm assigning this to xmms2 and letting the xmms2 maintainer decide where it goes from there.
This is a known bug, although I didn't find a bug report from xmms2 database. You are absolutely right, this is hard to categorize. It is not a bug in the musepack plugin for sure, it could be fixed in the vocoder plugin and actually vocoder uses floats internally. The 16-bit format was chosen as input and output only because it's the most commonly used and writing conversions for each type is a lot of useless code.
The right way to fix it though would be in xmms2d, letting it throw the converter plugin in to the chain every time there is an effect with an unsupported input type. However because the audio conversions always degrade sound quality, that should be made optional. The optionality of it makes the implementation slightly more complicated, but still doable. No one has just done it because the effect plugins are not so widely used I guess. Can you open a bug also to http://bugs.xmms2.xmms.se/ since I'm now travelling and it's not so convenient for me.
Juho Vähä-Herttua -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
