From: John G. <jgr...@te...> - 2002-02-21 16:56:56
|
Hi all, Firstly, there's something in xine I find very annoying - the fact that it sets the volume control for the PCM level in the mixer to just under 50% on my system - I presume it does this for everyone, and yet I can't find a good reason for it. Is there one? Secondly, my soundcard (ES1373, sold as a SoundBlaster PCI128, supported by the kernel OSS ES1371 driver) is capable of outputting two distinctly seperate audio streams at once - they do however share the same mixer. So, when the card starts up, it registers two dsp devices (/dev/dsp0 and /dev/dsp1 on my system) and one mixer device (/dev/mixer0). I usually leave xmms playong on /dev/dsp1 so that my system sounds, unreal tournament etc. will play without waiting for the default dsp device (/dev/dsp which is symlinked to /dev/dsp0) to become available. All these apps I listed will open the device dsp0 without interfering with the output from xmms on dsp1, except xine. When xine opens the device the output from xmms becomes corrupted, and stays corrupted until xmms closes and reopens dsp1. I presume this is probably an error in the sound card module, but I need a bit more info about how xine opens the dsp device before I can report it to the author. What can you tell me that may be relevant about how xine opens the device? Of course, it might be a xine bug :) Cheers, John |