RE: [Alsa-devel] I hope the CMI9739 mixer issue is fixed before alsa 1.0 isdeclared stable
The cm9739 does not have HW PCM volume control, the reason why the Windows driver and the cmaudio OSS driver can tune PCM volume is that they change PCM data in DMA buffer. I already made a patch that works in the same manner, if you are interested, I can post it. Sincerely, ChenLi Tien -Original Message- From: lupus [mailto:[EMAIL PROTECTED] Sent: Thu 2003/12/11 PM 01:32 To: [EMAIL PROTECTED] Cc: Subject: [Alsa-devel] I hope the CMI9739 mixer issue is fixed before alsa 1.0 isdeclared stable For more info: http://www.mail-archive.com/[EMAIL PROTECTED]/msg10120.html This is the only thing stopping me from using kernel 2.6 :s Or is it all ready fixed in the CVS? Can I help with this? By giving info from /proc or so? --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel †+wzf¢–+,¦‰ìo$…ëFŠ÷›iÉ®ˆ+j`èzĺ· Šàzw…éiÊ›zj+zšèvç-Š÷ƒ¡ë"¶¥§*.r·šµæÞ×r‡^Hp1Ä,åDjwazZn²¥¥ƒ” Xœw«zm§ÿì¢êÜyú+éÞ÷h«^ü li×zYšŠX§‚X¬´ li×zYb²Û,¢êÜyú+éÞm¦Ïÿ–+-²Ê.Ç¢¸ ë–+-³ùb²Ø~ÚÆz÷¥
[Alsa-devel] Understanding duplicated Mixer Devices
Hi, I have a question regarding "duplicated" Mixer devices. I see in various mixer application, that my CS46xx soundcard has 2 "Master", "PCM", "CD", "Mic", "3D Control Center" and several more devices with the same name. On the other hand, there is only 1 "Surround", 1 "Headphone", and so on. So what is the purpose of the duplicated devices? I don't want to make it too complicated, so lets start with "Master". - The first "Master" is controlling Front volume - The second "Master" does not seem to controll anything - The "Surround" item is controlling Rear volume Some hint in the right direction would be nice, Chris PS: Currently I am wildly guessing, that the "unused" devices will get useful in the case when some special routing is done. --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] experience with Creative MP3+ usb
Hi, I am using a Creative Labs MP3+ usb sound device. mobo is VIA EPIA 800, USB is UHCI Alsa is 1.0rc2 The things works great, it's not even muted on startup (huh ?) I am running a home built music player using gstreamer 0.7.2 (source available on request). Using the oss emulation layer now, for the issues. everytime I close the sound device, I get the following "usb_control/bulk_msg: timeout" any has an explanation ? can it be avoided ? sincerely Amaury --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] experience with Creative MP3+ usb
Hallo, Amaury Jacquot hat gesagt: // Amaury Jacquot wrote: > I am using a Creative Labs MP3+ usb sound device. > mobo is VIA EPIA 800, USB is UHCI > Alsa is 1.0rc2 > > The things works great, it's not even muted on startup (huh ?) Does it have a (supported) mixer? ciao -- Frank Barknecht _ __footils.org__ --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] ALSA sequencer changes?
Hrm, I've recently updated ALSA after a few weeks of inactivity, and suddenly I'm not getting MIDI events from simple code that previously worked. I don't see any alsa-devel messages about changes, but I apparently missed the PCM API change notice. In addition to the more complex library, I tried my test code which you can find here: http://ogmo.mephle.org/test-alsa.c The problem isn't getting 0's for time (got that one sorted awhile back, but never integrated the fix)---the problem is I'm not getting anything. Anyhow, just wondering what's new or different, or if it's something else I missed. thanks, -- Ryan Pavlik <[EMAIL PROTECTED]> "If it were possible to combine my evil with spider-man's powers..." - 8BT --- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] strange via8235 problem
Hey, I have a very strange sound problem using my via p4pb400 motherboard that use a via vt8235 southbridge running Suse 9.0 (kernel 2.4.21-144). I have to run 3-4 aplay apps simultaniously to hear sound, my computer is connected to my sound system using an optical link. I am currently using alsa 1.0rc2 since I had the same problem with 0.9.8. I enabled APIC by specifying "apic" in the kernel options in grub, without that setting I was not able to hear any sound. this is my options line from /etc/modules.conf options snd-via82xx ac97_clock=48000 enable=1 index=0 id=ac97 dxs_support=0 I can only hear any sound with dxs_support values of 0,1,3,4 -- 2 does not work at all. lspci -vv reports: 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 50) Subsystem: VIA Technologies, Inc.: Unknown device b003 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- ---> /proc/asound/card0/id <--- ac97 ---> /proc/asound/card0/via82xx <--- VIA 8235 at 0xe800, irq 22 00: 04: 1341 08: ff3f 0c: 10: 14: 142ab000 18: ff3f 1c: 20: 24: 12e74000 28: ff3f 2c: 30: 34: 17437000 38: ff3f 3c: 40: 44: 166f3000 48: ff21 4c: 50: 54: 58: 5c: 60: 64: 68: ff00 6c: 70: 74: 78: ff00 7c: 80: 322cbb80 84: 88: 8c: 90: cc01 94: 98: 0800 9c: ---> /proc/asound/card0/pcm1c/sub0/prealloc <--- 64 ---> /proc/asound/card0/pcm1c/sub0/status <--- closed ---> /proc/asound/card0/pcm1c/sub0/sw_params <--- closed ---> /proc/asound/card0/pcm1c/sub0/hw_params <--- closed ---> /proc/asound/card0/pcm1c/sub0/info <--- card: 0 device: 1 subdevice: 0 stream: CAPTURE id: VIA 8235 name: VIA 8235 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 ---> /proc/asound/card0/pcm1c/info <--- card: 0 device: 1 subdevice: 0 stream: CAPTURE id: VIA 8235 name: VIA 8235 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 ---> /proc/asound/card0/pcm1p/sub0/prealloc <--- 64 ---> /proc/asound/card0/pcm1p/sub0/status <--- closed ---> /proc/asound/card0/pcm1p/sub0/sw_params <--- closed ---> /proc/asound/card0/pcm1p/sub0/hw_params <--- closed ---> /proc/asound/card0/pcm1p/sub0/info <--- card: 0 device: 1 subdevice: 0 stream: PLAYBACK id: VIA 8235 name: VIA 8235 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 ---> /proc/asound/card0/pcm1p/info <--- card: 0 device: 1 subdevice: 0 stream: PLAYBACK id: VIA 8235 name: VIA 8235 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 ---> /proc/asound/card0/pcm0c/sub0/prealloc <--- 64 ---> /proc/asound/card0/pcm0c/sub0/status <--- closed ---> /proc/asound/card0/pcm0c/sub0/sw_params <--- closed ---> /proc/asound/card0/pcm0c/sub0/hw_params <--- closed ---> /proc/asound/card0/pcm0c/sub0/info <--- card: 0 device: 0 subdevice: 0 stream: CAPTURE id: VIA 8235 name: VIA 8235 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 ---> /proc/asound/card0/pcm0c/info <--- card: 0 device: 0 subdevice: 0 stream: CAPTURE id: VIA 8235 name: VIA 8235 subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 ---> /proc/asound/card0/pcm0p/sub3/prealloc <--- 64 ---> /proc/asound/card0/pcm0p/sub3/status <--- closed ---> /proc/asound/card0/pcm0p/sub3/sw_params <--- closed ---> /proc/asound/card0/pcm0p/sub3/hw_params <--- closed ---> /proc/asound/card0/pcm0p/sub3/info <--- card: 0 device: 0 subdevice: 3 stream: PLAYBACK id: VIA 8235 name: VIA 8235 subname: subdevice #3 class: 0 subclass: 0 subdevices_count: 4 subdevices_avail: 4 ---> /proc/asound/card0/pcm0p/sub2/prealloc <--- 64 ---> /proc/asound/card0/pcm0p/sub2/status <--- closed ---> /proc/asound/card0/pcm0p/sub2/sw_params <--- closed ---> /proc/asound/card0/pcm0p/sub2/hw_params <--- closed ---> /proc/asound/card0/pcm0p/sub2/info <--- card: 0 device: 0 subdevice: 2 stream: PLAYBACK id: VIA 8235 name: VIA 8235 subname: subdevice #2 class: 0 subclass: 0 subdevices_count: 4 subdevices_avail: 4 ---> /proc/asound/card0/pcm0p/sub1/prealloc <--- 64 ---> /proc/asound/card0/pcm0p/sub1/status <--- closed ---> /proc/asound/card0/pcm0p/sub1/sw_params <--- closed ---> /proc/asound/card0/pcm0p/sub1/hw_params <--- closed ---> /proc/asound/card0/pcm0p/sub1/info <--- card: 0 device: 0 subdevice: 1 stream: PLAYBACK id: VIA 8235 name: VIA 8235 subname: subdevice #1 class: 0 subclass: 0 subdevices_count: 4 subdevices_avail: 4 ---> /proc/asound/card0/pcm0p/sub0/prealloc <--- 64 ---> /proc/asound/card0/pcm0p/sub0/status <--- closed ---> /proc/asound/card0/pcm0p/sub0/sw_params <--- closed ---> /proc/asound/card0/pc
