On Sun, Nov 27, 2005 at 07:22:35PM +0100, Tobias Diedrich wrote:
Diego Biurrun wrote:
IMHO this makes the documentation a bit unclear, based on this I'd expect "-ao oss:mixer-device=/dev/mixer:dsp-device=/dev/dsp" to work...
Before my change, after my change or either way?
Hmm, I'm not going to claim that the current description is perfect, but I don't see the problem you describe. Other output drivers are documented in the same way and where option=<value> syntax is expected, this is written explicitly. I was also hoping that the <> would make clear that it should be replaced by a concrete value...
I think it was more clear before the change. Most drivers use either the suboption parser or support only one parameter. The syntax explanation suggests that the suboption order is not important. Before it was made clear that oss is an exception in that the order _is_ important, but maybe thats just me. :-)
I understand what your problem is now. I'd say it needs a more general fix, though.
I think it might be good to convert oss to use the suboptionparser (breaks compatibility)
Definitely. Breaking compatibility should not be a problem since this has only been in the CVS version so far. Diego