Hello Antonis, On Mon, Jun 13, 2016 at 11:06 AM, Antonis Tsolomitis <[email protected]> wrote: > so a reasonable question is whether there must be a patch or not.
I don't think a patch would be a good idea, unless it covers all possible platforms and device instances. But how can we tell what device someone is actually using? Systems nowadays usually have more than one sound device. On-board analogue, on-board digital, in/out/duplex, HDMI for feeding screens with speakers, etc. If I use my (on-board) /dev/dsp4.1 as the main playback device on FreeBSD, it doesn't mean that this is the same for every FreeBSD user. Someone else might use /dev/dsp7.0 instead because they want to use the the builtin speakers of their screen, hooked up via HDMI. On top of that, the situation is different for each OS. On FreeBSD, we have for example /dev/dspX.Y, whereas Solaris has only /dev/dsp and /dev/dspX (with X and Y equal or greater than 0). Solaris also has an /dev/audio, which is completely missing on FreeBSD 10, but existed in earlier releases. Both FreeBSD and Solaris have a /dev/sndstat, but the devices are behaving differently. No idea about these things on the Linux side, but I bet they are looking different from both FreeBSD and Solaris. > If it can't be fixed I will have to add a wiki page. I think some general instructions on the Wiki would be much more useful, yes. Kind regards, Martin Etteldorf ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ cdesktopenv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
