Re: [Alsa-user] cannot mmap /dev/dsp with Audiophile2496 (ice1712)
On Wed, 8 Jan 2003, [EMAIL PROTECTED] wrote: > Hi, > > I've just installed a new Audiophile 2496 in my RedHat 8.0 box, and I've > set up the 0.9.0rc6 drivers properly as far as I can tell. Sound output > is OK in most apps (gnome-cd, xmms), however, sound fails to initialise in > quake3-engined games (RTCW and quake3 itself) with the error message > > Cannot mmap /dev/dsp > > I have an SBLive! Value in my box as well (currently /dev/dsp1) and when I > configure these games to use /dev/dsp1 as the output device, sound inits > fine. > > Does anyone know why the Audiophile cannot mmap /dev/dsp or know of any > workarounds? I don't think this is an OSS emulation problem because sound > output from xmms using the OSS output driver works fine. Any help would > be really appreciated because then the SBLive! is no longer needed and can > be put in another machine ... OSS API is very simple and mmap() won't work for ICE1712 based cards because DMA buffers are different than usual stereo cards have. Try to get the ALSA output code for games (if exists). Jaroslav - Jaroslav Kysela <[EMAIL PROTECTED]> Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Screwy full duplex audio with SB Vibra16C.
On Tue, 7 Jan 2003, Jeff Pierce wrote: > I am really getting frustrated. > > I am writting a VOIP app for amateur radio which has been half duplex > sound, but now needs to go to FULL duplex. > My app uses OSS type access, ioctl calls, as many using it only have OSS > free from teh kernel distrobutions. > > Ok, I get alsa 0.9.0rc6 and compile and install it for via82c686, which > I get running with the half duplex code. No problem. I then write a > super simple app using OSS ioctl to test if full duplex will work that > way, not using alsa api. It simply reads the /dev/dsp and just writes > the buffer right back to /dev/dsp. Run it on and it works no problem. > Using alsamixer to change the line out audio on the pcm control, etc. > > Ok I have another Linux box with a SB Vibra16C to do testing between the > two boxes. I install alsa 0.9.0rc6 on it and install for sb16. I try > running my full duplex app on it. What an abortion!!! > > First, in alsamixer, where is the "mixer" control to keep mic from going > directly to output. I find "auto mic", UNMUTING it stops mic from output > with no app working. > > Then the really big problem. When running my fullduplex app, the mic > audio is once again at the output, albeit at a lower volume and the pcm > control HAS NO EFFECT on it, and the actual audio read from and written > to /dev/dsp is 5 seconds behind my speaking it, if it makes it at all. > This is the audio that the pcm control will vary. > > It seems to me the snd-sb16 has a whole lot of problems, beacause code > that works perfectly on a via82c686 alsa driver screws up on a sb16 alsa > driver. > > Even my half duplex VOIP code that runs perfectly on oss SB16 and alsa > via82c686 has problems running with alsa sb16. Run the sb16 oss drivers > and audio is IMMEADIATLY sent to the receiving machine. Run it using > alsa sb16 and sometimes it has a 5-7 second delay BEFORE it is sent. > Stop the app and restart it,nothing done to alsa drivers, and you do not > have the delay. > > What's wrong with the alsa sb16 driver? See these comments in the SB driver: * Note: This is very ugly hardware which uses one 8-bit DMA channel and *second 16-bit DMA channel. Unfortunately 8-bit DMA channel can't *transfer 16-bit samples and 16-bit DMA channels can't transfer *8-bit samples. This make full duplex more complicated than *can be... People, don't buy these soundcards for full 16-bit *duplex!!! * Note: 16-bit wide is assigned to first direction which made request. *With full duplex - playback is preferred with abstract layer. * * Note: Some chip revisions have hardware bug. Changing capture *channel from full-duplex 8bit DMA to 16bit DMA will block *16bit DMA transfers from DSP chip (capture) until 8bit transfer *to DSP chip (playback) starts. This bug can be avoided with *"16bit DMA Allocation" setting set to Playback or Capture. Jaroslav - Jaroslav Kysela <[EMAIL PROTECTED]> Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Re: Can't use timidity
On Wed, 8 Jan 2003, Alex Anderson wrote: > > > > Did you launch the ./snddevices script when installing alsa-driver ? > > > > Thanks for the reply. Yes I tried this, with the same result. > > I noticed that in my TiMidity++ (2.11.3) distribution there is a file > "alsa_a.c", which contains a reference to "/dev/snd/pcm00". Yet, after I > installed ALSA, the only devices I had with a similar name were "pcmC0D0c", > "pcmC0D0p" and "pcmC0D1p". Can anyone who has successfully made TiMidity and > ALSA talk to each other tell me what devices they have in "/dev/snd/" (or > "/proc/asound/dev/")? > Use TiMidity++-2.12.0-pre1 and you should have no problem. It *is* beta, but I haven't found any problems with it. I works with alsa 9 fine. Bill --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Re: [Alsa-devel] intel8x0: changing characteristics after an APM suspend-resume cycle
At Tue, 07 Jan 2003 15:40:10 -0500, D. Sen <[EMAIL PROTECTED]> wrote: > > Hi, > > I am using the snd-intel8x0 drivers (0.9.0rc6) on my IBM Thinkpad > running Linux 2.4.20. Everything seems to run fine until the machine > goes through a suspend/resume cycle when mono files/streams seem to get > played back at a much faster rate. > > A cold reboot resolves the problem. even after unloading/reloading the module the problem persists? Takashi --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] external midi tone generator
hi, i have an YAMAHA TG100 tone generator connected to the external midi port of my SB128 PCI. I use debian (woody), a 2.4.18 kernel, ALSA 0.9rc5-2. # lsmod [...] snd-virmidi 1312 0 (autoclean) (unused) snd-seq-virmidi 2648 0 (autoclean) [snd-virmidi] snd-seq-midi3232 0 (autoclean) (unused) snd-ens1371 9764 2 (autoclean) snd-rawmidi12864 0 (autoclean) [snd-seq-virmidi snd-seq-midi snd-ens1371] snd-seq-oss23136 0 (unused) snd-seq-midi-event 3096 0 [snd-seq-virmidi snd-seq-midi snd-seq-oss] snd-seq37484 7 [snd-seq-virmidi snd-seq-midi snd-seq-oss snd-seq-midi-event] snd-seq-device 3904 0 [snd-seq-midi snd-rawmidi snd-seq-oss snd-seq] snd-pcm-oss36100 1 snd-pcm49440 0 [snd-ens1371 snd-pcm-oss] snd-timer 10432 0 [snd-seq snd-pcm] snd-mixer-oss 9216 0 (unused) snd-ac97-codec 23236 0 [snd-ens1371] snd25704 5 [snd-virmidi snd-seq-virmidi snd-seq-midi snd-ens1371 snd-rawmidi snd-seq-oss snd-seq-midi-event snd-seq snd-seq-device snd-pcm-oss snd-pcm snd-timer snd-mixer-oss snd-ac97-codec] soundcore 3684 13 [snd] [...] # ls -la /dev/midi* lrwxrwxrwx1 root root 10 Nov 27 18:13 /dev/midi -> /dev/midi0 crw-rw1 root audio 14, 2 Nov 27 18:13 /dev/midi0 crw-rw1 root audio 14, 2 Jun 13 2001 /dev/midi00 crw-rw1 root audio 14, 18 Jun 13 2001 /dev/midi01 crw-rw1 root audio 14, 34 Jun 13 2001 /dev/midi02 crw-rw1 root audio 14, 50 Jun 13 2001 /dev/midi03 crw-rw1 root audio 14, 18 Nov 27 18:13 /dev/midi1 lrwxrwxrwx1 root root 17 Jan 7 15:41 /dev/midi10 -> /dev/snd/midiC1D0 lrwxrwxrwx1 root root 17 Jan 7 15:42 /dev/midi11 -> /dev/snd/midiC1D1 crw-rw1 root audio 14, 34 Nov 27 18:13 /dev/midi2 crw-rw1 root audio 14, 50 Nov 27 18:13 /dev/midi3 playing midi via timidity + pmidi runs fine when i use : # timidity -iA -B2,8 -Os -EFreverb=0 and then play the midi file via : # pmidi -p130:0 doing so, aconnectgui shows the connection between client 130 (timidity) and client 131 (pmidi) - fine. but as far as i understand the whole thing, the tg100 isnt accessed. how can i access external midi tone generators under linux? my second question is, how to adjust the tempo within pmidi or timidity of a midi song? thanks a lot. Thorsten -- --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Msnd-pinnacle problems...
Hi I've been having some problems with my Turtle Beach Pinnacle and ALSA and wondered if anyone has any advice or experience with this card. I have compiled/installed ALSA (0.9.0rc6) no problem, but the sound stutters whenever I try to play anything, whether its a mp3, a movie file or Quake3. I see messages like: >alsa-play: xrun of at least 0.541 msecs. resetting stream >alsa-play: xrun of at least 1.055 msecs. resetting stream >alsa-play: xrun of at least 2.657 msecs. resetting stream when using mplayer with alsa, and even with the oss emulation the sound still stutters badly. Looking at "top", its only on 20% system load so its not swamping the cpu or anything... I also see the messages in my syslog: >msnd: Enabling IRQ >msnd: Disabling IRQ >msnd: Enabling IRQ ..etc.. I've tried running from the command prompt and from X (using KDE3.1) and have the same results. I've tried the 2.4.19 kernel, and 2.4.20 with and without low-latency & preempt-kernel patches, with exactly the same results. Using the drivers in the kernel for the Pinnacle it works fine with mplayer etc.. although there is no sound in Quake3. (Quake3 says "your soundcard cannot do this".. hence my reason for trying alsa).. I know the pinnie is a ISA card, which is slow by todays standards, but has anyone got it to work ok with alsa ? Or have any suggestions for what to try next... Much appreciated! Thanks! Machine: 1ghz Celeron ASUS P3V4X motherboard 512meg Ram GeForce 2MX Turtle Beach Pinnacle System: Custom Linux From Scratch (LFS) install Kernel: 2.4.20 + low-latency & preempt-kernel patches Alsa: 0.9.0rc6 >lsmod Module Size Used byTainted: P NVdriver 1066752 10 snd-pcm-oss39012 0 (autoclean) snd-mixer-oss 13112 0 (autoclean) [snd-pcm-oss] snd-msnd-pinnacle 19424 0 (autoclean) snd-pcm64032 0 (autoclean) [snd-pcm-oss snd-msnd-pinnacle] snd-timer 12040 0 (autoclean) [snd-pcm] snd-rawmidi14464 0 (autoclean) [snd-msnd-pinnacle] snd-seq-device 4332 0 (autoclean) [snd-rawmidi] snd28748 0 (autoclean) [snd-pcm-oss snd-mixer-oss snd-msnd-pinnacle snd-pcm snd-timer snd-rawmidi snd-seq-device] soundcore 4004 5 (autoclean) [snd-msnd-pinnacle snd] 8139too15688 1 mii 2496 0 [8139too] raid1 14252 1 (autoclean) md 47040 2 (autoclean) [raid1] TinK Slightly Miffed - Now with One Leg Too Many! http://www.miffed.com/ or http://www.mp3.com/miffed/ "Either Slightly Miffed are insanely brilliant or very, very warped." --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Status of via8235 on Asus A7V8X Mobo
I was just wondering if anyone is working on getting the sound (a via8233/35 chip ... listed as a Realtek AL650 in the manual) on an Asus A7V8X Mobo working. I haven't been able to get it working and CVS (from last night) doesn't work either. -- Edward Muller Interlix - President Web Hosting - PC Service & Support Custom Programming - Network Service & Support Phone: 417-862-0573 Cell: 417-844-2435 Fax: 417-862-0572 http://www.interlix.com --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] modules doesnt load complete after boot
At Tue, 7 Jan 2003 20:48:56 +0100 (MET), [EMAIL PROTECTED] wrote: > > > At Wed, 1 Jan 2003 18:19:10 +0100 (MET), > > [EMAIL PROTECTED] wrote: > > > > > > This works! Thank you! > > > But now I get this message at boot time: depmod: *** Unresolved symbols > > in > > > /lib/modules/2.4.19-686/alsa/snd-vxpocket.o > > > > > > What does this mean? > > > > in fact, there are some unresolved symbols in the module :) > > please run "depmod -ae" and show the output. it would help for > > debugging. > > > > but anyway, it must be harmless unless you use the relevant module. > > > > > > Takashi > > > This is the output of "depmod -ae": > > depmod: *** Unresolved symbols in /lib/modules/2.4.19-686/alsa/snd-vxp440.o > depmod: CardServices_Re4eef0a4 > depmod: register_pccard_driver_R583d4ed2 > depmod: unregister_pccard_driver_Rdb348cd2 > depmod: *** Unresolved symbols in > /lib/modules/2.4.19-686/alsa/snd-vxpocket.o > depmod: CardServices_Re4eef0a4 > depmod: register_pccard_driver_R583d4ed2 > depmod: unregister_pccard_driver_Rdb348cd2 it looks like the different pcmcia stuffs are used for compilation of vx drivers. your pcmcia stuff is kernel version or external version? anyway, it's harmless for other modules. Takashi --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Status of via8235 on Asus A7V8X Mobo
On Wednesday 08 January 2003 08:49 am, Edward Muller wrote: > I was just wondering if anyone is working on getting the sound (a > via8233/35 chip ... listed as a Realtek AL650 in the manual) on an Asus > A7V8X Mobo working. > > I haven't been able to get it working and CVS (from last night) doesn't > work either. It's working on my system. Use the driver on the CD that came with the motherboard. -- Mike Payson | DawgDayz Dog Walking & Pet Sitting (206) 280-7295 | www.dawgdayz.com | [EMAIL PROTECTED] --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Status of via8235 on Asus A7V8X Mobo
I can't seem to locate that driver on the CD. The only driver I've found for linux on the CD was for the Broadcomm nic. On Wed, 2003-01-08 at 12:59, Mike Payson wrote: > On Wednesday 08 January 2003 08:49 am, Edward Muller wrote: > > I was just wondering if anyone is working on getting the sound (a > > via8233/35 chip ... listed as a Realtek AL650 in the manual) on an Asus > > A7V8X Mobo working. > > > > I haven't been able to get it working and CVS (from last night) doesn't > > work either. > > It's working on my system. Use the driver on the CD that came with the > motherboard. -- Edward Muller Interlix - President Web Hosting - PC Service & Support Custom Programming - Network Service & Support Phone: 417-862-0573 Cell: 417-844-2435 Fax: 417-862-0572 http://www.interlix.com --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Terratec Sixpack 5.1 with cs46xx
Hi everybody, I recently tried to get the SPDIF/out working on my card -- I'm using Debian Woody 3.0 with Kernel 2.4.19. The Soundcard identifies itself as "Sound Fusion CS46xx" with a "Cirrus Logic CS4297A rev 4"-chip. After upgrading from "alsa-source 0.9+0beta12-3/stable" to "alsa-source 0.9.0rc6-3/testing" an recompiling the modules I got SPDIF working -- but: now I have really flat sound without Bass (I don't know if other characteristics are also missing, the only that I heard so far was the missing Bass). It's the same with Analog-Out as well as with Digital-Out -- what could I do to solve the problem? All worked fine when I was using 0.9beta12... Do I need a special configuration in /etc/alsa? Regards, Hannes --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Terratec Sixpack 5.1 with cs46xx
Hi, that's a bug in rc6 version of cs46xx driver. The lack of bass is caused by phase reversal of one channel, i.e. wrong sign of the values of one channel. Therefore correlating sound (low frequency components are stronger correlated because of the long wavelengths) in left and right channel will cancel out more or less when using loudspeakers and the stereophonic impression is also wrong. Up to now all reports of this problem stated that this error occurs only with analog out, not SPDIF -- but perhaps other cs46xx based cards were used. The cvs version should fix this problem for analog out, perhaps also for digital out. But with cvs version SPDIF input doesn't work as it should and did with rc6 version (at least for my Terratec XFire). If the cvs version doesn't fix the bass problem then benny should know what to do :-) fe Hannes Ebner schrieb: Hi everybody, I recently tried to get the SPDIF/out working on my card -- I'm using Debian Woody 3.0 with Kernel 2.4.19. The Soundcard identifies itself as "Sound Fusion CS46xx" with a "Cirrus Logic CS4297A rev 4"-chip. After upgrading from "alsa-source 0.9+0beta12-3/stable" to "alsa-source 0.9.0rc6-3/testing" an recompiling the modules I got SPDIF working -- but: now I have really flat sound without Bass (I don't know if other characteristics are also missing, the only that I heard so far was the missing Bass). It's the same with Analog-Out as well as with Digital-Out -- what could I do to solve the problem? All worked fine when I was using 0.9beta12... Do I need a special configuration in /etc/alsa? Regards, Hannes --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Status of via8235 on Asus A7V8X Mobo
On Wednesday 08 January 2003 17:49, Edward Muller wrote: > I was just wondering if anyone is working on getting the sound (a > via8233/35 chip ... listed as a Realtek AL650 in the manual) on an Asus > A7V8X Mobo working. > > I haven't been able to get it working and CVS (from last night) doesn't > work either. It didn't work for me previously, but a combination of alsa-driver-0.9.0_rc6 and the pci=biosirq kernel flag (previously, the sound chip had an IRQ of 19, now it's 6) did the trick for me. My motherboard is an EPoX 8K5A2, with a VIA 8235 south bridge. Best Regards, --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Terratec Sixpack 5.1 with cs46xx
Hi, Friedrich Ewaldt wrote: The cvs version should fix this problem for analog out, perhaps also for digital out. But with cvs version SPDIF input doesn't work as it should and did with rc6 version (at least for my Terratec XFire). You were right, thank you a lot for your note! I recompiled with the CVS-version from 2003-01-07 and all worked fine. Regards, Hannes --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] Delta/66
So should I just throw this $350 sound card away? --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Status of via8235 on Asus A7V8X Mobo
I've got both going for me. Perhaps I should try and play with how irqs are assigned on this machine, which is loaded with add-in pci cards as well as all the onboard stuff. On Wed, 2003-01-08 at 16:03, Joachim Blaabjerg wrote: > On Wednesday 08 January 2003 17:49, Edward Muller wrote: > > I was just wondering if anyone is working on getting the sound (a > > via8233/35 chip ... listed as a Realtek AL650 in the manual) on an Asus > > A7V8X Mobo working. > > > > I haven't been able to get it working and CVS (from last night) doesn't > > work either. > > It didn't work for me previously, but a combination of alsa-driver-0.9.0_rc6 > and the pci=biosirq kernel flag (previously, the sound chip had an IRQ of 19, > now it's 6) did the trick for me. My motherboard is an EPoX 8K5A2, with a VIA > 8235 south bridge. > > Best Regards, -- Edward Muller Interlix - President Web Hosting - PC Service & Support Custom Programming - Network Service & Support Phone: 417-862-0573 Cell: 417-844-2435 Fax: 417-862-0572 http://www.interlix.com --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with Delta/66 card
> I managed to get alsa (kind of) working with my M-Audio Delta/66 sound > card but have some significant problems - would appreciate any suggestions: > > 1) All media play back too fast. A 6-minute mp3 will play in about > 5:25; a RealPlayer video stream will buffer for a number of seconds, > then get spit out at too high a rate in a couple seconds, and then start > buffering again. In all cases the audio pitch is noticeably higher. Use envy24control (a gui control program for the ice1712 chipset) that is part of alsa-tools to look at the synchronization options. Most probably it is set for external sync or fixed internal. Hmm, I guess I had not finished reading :-) > 3) (and i wonder if this has a bearing on #1), alsamixer will lock up > my system if I even touch the setting "Multitrack internal clock", which > is set at 48K. Similarly, the envy24control utility will lock my system > up as soon as I run it. That is not good. Are you sure you have all packages installed and with the same version? (alsa-driver, alsa-lib, alsa-utils, alsa-tools). I use a lot of delta 66's with omniI/O boxes with no problems. -- Fernando --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Delta/66
On Wed, Jan 08, 2003 at 05:32:00PM -0500, lloyd wrote: > > So should I just throw this $350 sound card away? I wouldn't. I have one and it's worked well with most of the alsa 0.9 versions I've tried. I'd suggest reading this page in the ALSA Wiki but it seems to only give you the index at the moment. http://alsa.opensrc.org/index.php?page=ice1712 envy24control got changed at some point and things got odd with some of the control sliders, but I never had it lock up my box. Your speed problems sound like what happens when a file with sr = 44100 is played back with sr = 48000. I don't know why that's happening. I haven't tried it lately myself, I usually use it with JACK running at 48000. -- Paul Winkler http://www.slinkp.com --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: Re: [Alsa-user] alias error
hey Richard, Thanks for the advice, look, Im running cmipci, the alsa one.. what you said makes sense to me, xmms can output sound even when 10 of them are opened, but none of other aplications (like mpg123) can do it at the same time.. can you tell me how to use the alsa driver instead of the oss one, so i can play mpg123 and xmms at same time? Regards, Giannacari, F. --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] modprobe problems; game theater XP 6.1, on board audio too
this might have already been posted, but i don't know, so i figure i would just post again using another e-mail address, one that i used to sign up to the list with. everything goes well until this part during install when i type this: modprobe snd-cs46xx;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss here's what i get: /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: unresolved symbol __write_lock_ failed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: unresolved symbol __read_lock_f ailed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: insmod /lib/modules/2.4.18-14/k ernel/sound/acore/snd.o failed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: insmod snd-cs46xx failed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: unresolved symbol __write_lock_ failed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: unresolved symbol __read_lock_f ailed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: insmod /lib/modules/2.4.18-14/k ernel/sound/acore/snd.o failed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: insmod snd-pcm-oss failed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: unresolved symbol __write_lock_ failed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: unresolved symbol __read_lock_f ailed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: insmod /lib/modules/2.4.18-14/k ernel/sound/acore/snd.o failed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: insmod snd-mixer-oss failed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: unresolved symbol __write_lock_ failed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: unresolved symbol __read_lock_f ailed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: insmod /lib/modules/2.4.18-14/k ernel/sound/acore/snd.o failed /lib/modules/2.4.18-14/kernel/sound/acore/snd.o: insmod snd-seq-oss failed after that i type: alsamixer i get: alsamixer: function snd_ctl_open failed for default: No such file or directory i have redhat linux 8.0, alsa 0.9.0 rc6, Game Theater XP 6.1, and an onboard ac97 audio chip, from via tech. thank you for your help, i can't seem to get the drivers that come with redhat to work right. :-/ --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Re: Can't use timidity
Thanks Bill, worked a treat! Alex On Wednesday 08 January 2003 11:06 am, Bill Allen wrote: > On Wed, 8 Jan 2003, Alex Anderson wrote: > > > Did you launch the ./snddevices script when installing alsa-driver ? > > > > Thanks for the reply. Yes I tried this, with the same result. > > > > I noticed that in my TiMidity++ (2.11.3) distribution there is a file > > "alsa_a.c", which contains a reference to "/dev/snd/pcm00". Yet, after I > > installed ALSA, the only devices I had with a similar name were > > "pcmC0D0c", "pcmC0D0p" and "pcmC0D1p". Can anyone who has successfully > > made TiMidity and ALSA talk to each other tell me what devices they have > > in "/dev/snd/" (or "/proc/asound/dev/")? > > Use TiMidity++-2.12.0-pre1 and you should have no problem. It *is* beta, > but I haven't found any problems with it. I works with alsa 9 fine. > > Bill --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with Delta/66 card
Thanks for the reply. Fernando Pablo Lopez-Lezcano wrote: Hmm, I guess I had not finished reading :-) :-) 3) (and i wonder if this has a bearing on #1), alsamixer will lock up my system if I even touch the setting "Multitrack internal clock", which is set at 48K. Similarly, the envy24control utility will lock my system up as soon as I run it. That is not good. Are you sure you have all packages installed and with the same version? (alsa-driver, alsa-lib, alsa-utils, alsa-tools). I use a lot of delta 66's with omniI/O boxes with no problems. I've tried several times with RPM's from FreshRPM's, source RPM's, and from source... I uninstalled everything and re-installed from sources, and I'm still getting the same problem. Given the lock-up I get whenever I touch the Internal Hardware Clock setting, I looked at the output of amixer and see: $ amixer Simple mixer control 'Multi Track Internal Clock',0 Capabilities: Mono: Can you tell me what your output of amixer is from this section? Also, are you able to change this setting in alsamixer? I'd wonder if it were a hardware problem but it works fine in Win2K. Thanks a lot --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Status of via8235 on Asus A7V8X Mobo
Sorry, you're right. The driver is not on the CD, it's on the Realtek site. See http://www.realtek.com.tw/downloads/downloads1-3.aspx?series=8&Software=True. On Wednesday 08 January 2003 11:39 am, Edward Muller wrote: > I can't seem to locate that driver on the CD. The only driver I've found > for linux on the CD was for the Broadcomm nic. > > On Wed, 2003-01-08 at 12:59, Mike Payson wrote: > > On Wednesday 08 January 2003 08:49 am, Edward Muller wrote: > > > I was just wondering if anyone is working on getting the sound (a > > > via8233/35 chip ... listed as a Realtek AL650 in the manual) on an Asus > > > A7V8X Mobo working. > > > > > > I haven't been able to get it working and CVS (from last night) doesn't > > > work either. > > > > It's working on my system. Use the driver on the CD that came with the > > motherboard. -- Mike Payson | DawgDayz Dog Walking & Pet Sitting (206) 280-7295 | www.dawgdayz.com | [EMAIL PROTECTED] --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
[Alsa-user] XMMS won't play
I've installed Alsa 0.9.0_rc6 on my Gentoo system. All appears to work in that I've unmuted and set volumes with amixer. Aplay works on wav files and I can play some streaming music with mplayer as well as play CDs with mplayer. XMMS will play a wave file. However, I can not play CDs with XMMS. XMMS evidently uses the oss mixer for CD volume and no matter what volume I put XMMS at I get no sound. I've checked /proc/asound/CMMI8638MC6/oss_mixer and get this which implies the volume is not set. How do I set it - amixer/alsamixer don't work on it. I've included my modules.conf portions, too. Thanks. oss_mixer (partial) Audio devices: 0: C-Media PCI DAC/ADC (DUPLEX) Synth devices: NOT ENABLED IN CONFIG VOLUME "Master" 0 BASS "" 0 TREBLE "" 0 SYNTH "Synth" 0 PCM "PCM" 0 SPEAKER "PC Speaker" 0 LINE "Line" 0 MIC "Mic" 0 CD "CD" 0 modules.conf ### modules-update: start processing /etc/modules.d/alsa # Alsa 0.9.X kernel modules' configuration file. # $Header: /home/cvsroot/gentoo-x86/media-sound/alsa-driver/files/alsa-modules.c onf-rc,v 1.1 2002/12/21 06:31:52 agenkin Exp $ # # ALSA portion # alias char-major-116 snd alias snd-card-0 snd-interwave alias snd-card-0 snd-cmipci # # OSS/Free portion # alias char-major-14 soundcore alias sound-slot-0 snd-card-0 # # Card 1 # alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss alias /dev/mixer snd-mixer-oss alias /dev/dsp snd-pcm-oss alias /dev/midi snd-seq-oss # Set this to the correct number of cards. options snd major=116 cards_limit=1 ### modules-update: end processing /etc/modules.d/alsa -- Brett I. Holcomb --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
Re: [Alsa-user] Problems with Delta/66 card
> >>3) (and i wonder if this has a bearing on #1), alsamixer will lock up > >>my system if I even touch the setting "Multitrack internal clock", which > >>is set at 48K. Similarly, the envy24control utility will lock my system > >>up as soon as I run it. > > > > That is not good. Are you sure you have all packages installed and with > > the same version? (alsa-driver, alsa-lib, alsa-utils, alsa-tools). I use > > a lot of delta 66's with omniI/O boxes with no problems. > > I've tried several times with RPM's from FreshRPM's, source RPM's, and > from source... I uninstalled everything and re-installed from sources, > and I'm still getting the same problem. > > Given the lock-up I get whenever I touch the Internal Hardware Clock > setting, I looked at the output of amixer and see: > > $ amixer > > > Simple mixer control 'Multi Track Internal Clock',0 >Capabilities: >Mono: > > > Can you tell me what your output of amixer is from this section? Also, > are you able to change this setting in alsamixer? I get the same thing... I can change the setting in alsamixer (or envy24control) with no problems. -- Fernando --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
