Re: [Alsa-devel] trouble with dosemu and alsa oss emulation (and a fix for alsa)

2003-09-08 Thread Jaroslav Kysela
On Sat, 6 Sep 2003, Vedran Rodic wrote:

 Hi.

 I'm having trouble with latest ALSA and oss emulation. I'm using dosemu to
 play some DOS games and I've noticed that sound in DOS apps stops playing
 after short time (depending on the app).


 I'm regulary updating both alsa and dosemu, I suspected dosemu first, since
 I had no problems whatsoever with alsa oss emulation.

 It turned out that this was not dosemu problem, but alsa oss emulation problem.
 I've tracked it down to a change in  alsa-kernel/core/oss/pcm_oss.c.
 The change is here:
 http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/alsa/alsa-kernel/core/oss/pcm_oss.c.diff?r1=1.40r2=1.41

Please, try patch bellow.

Jaroslav


Index: pcm_oss.c
===
RCS file: /cvsroot/alsa/alsa-kernel/core/oss/pcm_oss.c,v
retrieving revision 1.47
diff -u -r1.47 pcm_oss.c
--- pcm_oss.c   3 Sep 2003 13:43:41 -   1.47
+++ pcm_oss.c   8 Sep 2003 07:12:58 -
@@ -1394,6 +1394,10 @@
}
if (stream == SNDRV_PCM_STREAM_PLAYBACK) {
err = snd_pcm_kernel_ioctl(substream, SNDRV_PCM_IOCTL_DELAY, delay);
+   if (err == -EPIPE || err == -ESTRPIPE) {
+   err = 0;
+   delay = 0;
+   }
} else {
err = snd_pcm_oss_capture_position_fixup(substream, delay);
}
@@ -1454,7 +1458,12 @@
} else {
if (stream == SNDRV_PCM_STREAM_PLAYBACK) {
err = snd_pcm_kernel_ioctl(substream, SNDRV_PCM_IOCTL_DELAY, 
avail);
-   avail = runtime-buffer_size - avail;
+   if (err == -EPIPE || err == -ESTRPIPE) {
+   avail = runtime-buffer_size;
+   err = 0;
+   } else {
+   avail = runtime-buffer_size - avail;
+   }
} else {
err = snd_pcm_oss_capture_position_fixup(substream, avail);
}

-
Jaroslav Kysela [EMAIL PROTECTED]
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel


[Alsa-devel] Re: [PATCH]usbus428 0.1 against alsa-driver-0.9.6

2003-09-08 Thread Takashi Iwai
At Sat, 6 Sep 2003 16:36:50 +0200,
Karsten Wiese wrote:
 
 [1  text/plain; us-ascii (7bit)]
 Hi,
 
 this uses hwdep 2 fold: 
 a) second stage firmware download
 b) interface for us428control - aplication
 
 no alsa-mixer interface yet, sorry.
 but: with us428control you can use the us428's sliders to set direct 
 monitoring levels and pcm-out level.
 
 I chose to integrate a userspace tool, so further needed steps for the us428's 
 knobs  sliders can be done in userspace until all is sorted out.
 
 see us428control  usX2Yloader in the following e-mails.

thanks for the patch.
now i commited it to cvs tree.

i put us428 stuffs into alsa-driver/usb/us428 subtree to avoid
spreading over a directory.

also, usx2y.h is put alsa-driver/usb/us428, too.  if it's necessarily
exported, we can put it to alsa-kernel/include, later.

the compilation seems ok.  please check the cvs tree later.


Takashi


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel


[Alsa-devel] [PATCH] let alsaconf work on all distros

2003-09-08 Thread Thierry Vignaud
on mandrake, lspci is in /usr/bin, not /bin.

the following patch make alsaconf search for lspci location and
factorize binary location with lsmod btw:
--- ./alsaconf.tv	2003-09-08 16:33:13.0 +0200
+++ ./alsaconf	2003-09-08 16:44:03.0 +0200
@@ -36,11 +36,12 @@
   distribution=unknown
 fi
 
-if [ -x /sbin/lsmod ]; then
-  lsmod=/sbin/lsmod
-else
-  lsmod=/bin/lsmod
-fi
+for prog in lspci lsmod; do
+	for path in /sbin /usr/sbin /bin /usr/bin;do
+		[[ -x $path/$prog ]]  eval $prog=$path/$prog
+	done
+done
+unset prog path
 
 usage() {
 echo ALSA configurator version $version
@@ -438,7 +439,7 @@
 /^[literal spaceliteral tab]*PCI: /{
 	gsub(/0x/, );
 	gsub(/=/, :);
-	x = sprintf (/sbin/lspci -n | grep ''Class 0401'' | grep %s, $2);
+	x = sprintf ('$lspci' -n | grep ''Class 0401'' | grep %s, $2);
 	if (system (x) == 0)
 		printf %s %s\n, $2, driver '$FOUND'
 }
@@ -468,7 +469,7 @@
 #
 find_device_name () {
 if expr $1 : '[0-9a-f][0-9a-f][0-9a-f][0-9a-f]:[0-9a-f][0-9a-f][0-9a-f][0-9a-f]' /dev/null; then
-	/sbin/lspci -d $1 | sed -e 's/^..:..\.. Multimedia audio controller: //g'
+	$lspci -d $1 | sed -e 's/^..:..\.. Multimedia audio controller: //g'
 	return
 elif expr $1 : '[EMAIL PROTECTED]@[EMAIL PROTECTED]' /dev/null; then
 	cardname=`grep '^Card [0-9]\+ '\'$1':' $DUMP | head -n 1 | sed -e 's/^Card [0-9]\+ '\''.*:\(.*\)'\'' .*$/\1/'`
@@ -1026,7 +1027,7 @@
 # check for TP600E
 #
 if [ ${devs_found[0]} = cs46xx ]; then
-	if /sbin/lspci -nv | grep -q Subsystem: 1014:1010; then
+	if $lspci -nv | grep -q Subsystem: 1014:1010; then
 	if $DIALOG --yesno 
  Looks like you having a Thinkpad 600E notebook.
  On this notebook, CS4236 driver should be used


[Alsa-devel] Please add snd-ice1712 problem to Known bugs page

2003-09-08 Thread Sam
Hi,

I purchased a Delta 44 for playback with my consumer grade Sony ES
receiver.  Installation of ALSA went smoothly, and I can hear music
okay, but it sometimes clips.  I believe this is because the analog
signal level is set inappropriately and there's no way using Linux
software for me to fix it.  Here's an excerpt from the Delta 44 manual:

The Delta 44 Digital Recording Interface's analog inputs and
outputs are compatible with a wide variety of audio products.
The Delta Control Panel software allows you to configure the
signal levels of each input individually, and all outputs as a
group.  Signal level settings of +4/Consumer/-10 are available.
Selecting the +4 radio button configures the channel(s) for use
with +4dBu signal levels, compatible with most musical
instruments and professional mixers.  Selecting the -10 setting
sets up the channel(s) for -10dBV nominal signal levels,
commonly used with consumer equipment such as CD, MiniDisc,
cassette tape and DAT players.  The Consumer setting is
preferred for semi-pro audio equipment and some consumer
equipment that is too hot for the -10 setting.  The Consumer
setting offers approximately 6dB more headroom than does the -10
setting.  Semi-pro and consumer devices signal levels vary from
manufacturer-to-manufacturer and even product-to-product, so a
little experimentation between Consumer and -10 settings may be
required for optimal results.

The screen shot of the Windows driver shows the choices for +4dBu,
Consumer, and -10dbV.  I was unable to find any way of setting these
using Linux software, including envy24control, and don't see any mention
of them in the ice1712 source code.

I'm disappointed because I spent extra money on this card to get good
quality playback for my music.  I would not have purchased it had I
known this is a problem.  Please make it clear on the Known bugs page or
Soundcard Matrix so no one else makes the same mistake.

Thanks,
Sam



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel


[Alsa-devel] Missing file from alsa-lib-CVS: src/userfile.c

2003-09-08 Thread Chris Rankin
 
 


Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel


[Alsa-devel] Re: /alsa-tools-0.9.6/us428controls 0.1

2003-09-08 Thread Takashi Iwai
At Sat, 6 Sep 2003 16:51:46 +0200,
Karsten Wiese wrote:
 
 [1  text/plain; us-ascii (7bit)]
 Hi,
 
 intended to be started from hotplug script,
 us428controls so far enables the sliders 1..4 for setting directmonitoring 
 levels. It also takes care of the red Mastervolume slider.
 this app can be expanded to fully enable all of the sliders+knobs.
 in userspace it is easier to recover from errors

do you think this version to be put on alsa-tools package, too?
then i'll review the code...


Takashi


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel


[Alsa-devel] Re: /alsa-tools-0.9.6/us428controls 0.1

2003-09-08 Thread Karsten Wiese
Am Montag 08 September 2003 13:19 schrieb Takashi Iwai:
 At Sat, 6 Sep 2003 16:51:46 +0200,

 Karsten Wiese wrote:
  [1  text/plain; us-ascii (7bit)]
  Hi,
 
  intended to be started from hotplug script,
  us428controls so far enables the sliders 1..4 for setting
  directmonitoring levels. It also takes care of the red Mastervolume
  slider.
  this app can be expanded to fully enable all of the sliders+knobs.
  in userspace it is easier to recover from errors

 do you think this version to be put on alsa-tools package, too?
 then i'll review the code...

no need to put this version on alsa-tools package.
Here is already a more capable one.
I'll send it, when I tested it with the CVS-built module.
Or on request, if someone likes to test-drive :-)

regards,
Karsten



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel


[Alsa-devel] RawMIDI interface programming

2003-09-08 Thread Brix
i need information about obtaining the correct rawmidi interface name (such as 
hw:0,0,1), corresponding to the MIDI synth device, from the system; i think it could 
be done by reading some files under /proc/asound, but which files?

thanks,

Marco


-- 

Hardware is never old.
People just choose the wrong OS.


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel


Re: [Alsa-devel] [PATCH] Enable SPDIF input recording on ALC650 AC97 codecs. Works for PCM and AC3.

2003-09-08 Thread Takashi Iwai
At Sat, 06 Sep 2003 03:23:21 +0100,
James Courtier-Dutton wrote:
 
 Takashi Iwai wrote:
  At Sat, 30 Aug 2003 17:49:33 +0100,
  James Courtier-Dutton wrote:
  
 [1  text/plain; us-ascii (7bit)]
 Patch attached.
 This patch enables the SPDIF input of the Realtek ALC650 chip which is 
 an AC97 compatible chip.
 It also adds some data into the proc file system ac97 
 /proc/asound/card0/ac97#0 file so one can see if the SPDIF is locked or not.
 
 I can now record AC3 non-audio data from an Optical SPDIF socket on my 
 Motherboard.
 
 This only works for ALC650 Rev.E or above, so I guess I should really 
 check for that.
  
  
  thanks, i applied to cvs with a little modification.
  
  
  Takashi
  
  
 I have just looked at the modification. Was there a reason to remove the 
 ac97_proc.c patches ?

it's there but in an if block checking the id with ALC650.


Takashi


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel