[Alsa-devel] 0.9.0rc6 envy24control problem
I am running alsa 0.9.0rc6. Apparently Jaroslav Kysela has made changes to envy24control from rc5 allowing the user to set the internal clock rate. I am using a Hoontech ST Audio DSP24 card. I have found that in order to change the master clock setting I have to first switch to S/PDIF In and then to another setting. If I just switch between settings (ie 44100 to 48000) the radio buttons change but the change is not saved. Obviously the workaround is to always switch to S/PDIF In prior to switching to another mode but this is not an ideal situation. On trying to debug the code I found that changing to or from S/PDIF In mode causes a call to control_input_callback which then calls master_clock_update. Merely calling master_clock_update from internal_clock_set does not alleviate this problem. Checking on the reasons I have found that the call to snd_ctl_elem_read(ctl, internal_clock) in master_clock_update resets the value returned by snd_ctl_elem_value_get_enumerated(internal_clock, 0) to the previous setting. That is, if the enumerated value is 8 then a call to internal_clock_set(int xrate) with xrate set to 9 will change the value returned by snd_ctl_elem_value_get_enumerated(internal_clock, 0) to 9. A subsequent call to snd_ctl_elem_read(ctl, internal_clock) will cause the value returned by snd_ctl_elem_value_get_enumerated(internal_clock, 0) to be 8. To get down to brass tacks a call to snd_ctl_elem_read immediately following a call to snd_ctl_elem_write seems to reset the master clock value to what it was prior to the call to snd_ctl_elem_write. As I said, I have a workaround but I'm sure that someone with more experience in this code (I just started an hour ago) would be able to fix this one fairly quickly. Sorry if the above is a bit confusing. V/R Jan Depner --- 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] usbaudio won't do 24-bit or 32-bit i/o...
Takashi Iwai wrote: At Sat, 21 Dec 2002 07:00:45 +0900, Patrick Shirkey wrote: Takashi Iwai wrote: hmmm, it seems that the problem is on usb-uhci driver. mysteriously, the midi part of quattro causes the kernel panic. the audio part seems ok. you can avoid this either by using uhci driver or by commenting out the entry for quattro in alsa-kernel/usb/usbquirks.h. I am trying it out on my ohci machine too and the latest driver has fixed the problem with not being able to capture from all the input. Thanks. I have commented out the midi quirk though in alsa-kernel/usb/usbquirk.h I will be saving this cvs for sure. The 24_3le support in arecord still captures the left channel maxed and the right at normal volume on pcm0 and pcm1. did you update the alsa-lib, too? there was a bug regarding 24bit conversion both on alsa-driver and alsa-lib. I updated all the cvs files and recompiled alsa-driver, alsa-lib and alsa-utils. I will try again soon. -- Patrick Shirkey - Boost Hardware Ltd. For the discerning hardware connoisseur Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Being on stage with the band in front of crowds shouting, "Get off! No! We want normal music!", I think that was more like acting than anything I've ever done. Goldie, 8 Nov, 2002 The Scotsman --- 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] Converted "Writing an ALSA Driver" to DocBook.
Takashi Iwai wrote: In case any one was curious, I converted Takashi's "Writing an ALSA Driver" document to DocBook/SGML. It's available for download here: http://www.kevindumpscore.com/download/writing-an-alsa-driver.sgml I have downloaded it to add to the site. I will render it to html so we can provide a nice way to browse it online. nice. if you finish the set up, please let me know the url. i'll add it as the reference to the new version. After playing around with the docbook install for a few hours it's probably more appropriate if Kevin can put the html versions on line for me to download. I will be here for a while doing this otherwise. -- Patrick Shirkey - Boost Hardware Ltd. For the discerning hardware connoisseur Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Being on stage with the band in front of crowds shouting, "Get off! No! We want normal music!", I think that was more like acting than anything I've ever done. Goldie, 8 Nov, 2002 The Scotsman --- 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: alsasound init script (Re: [Alsa-devel] possible problems withrc6 aplay )
Takashi Iwai wrote: At Fri, 20 Dec 2002 23:53:13 +0100, Pedro Lopez-Cabanillas wrote: Clemens, I remember that /proc/asound/cards returned this bus/device information for USB MIDI devices some time ago (rc3?), like it does for my SB 128 PCI. it would be nice to provide a new generic proc file which shows the low-level hardware information as the card number, the module name and the PCI/ISA-PnP/USB/PCMCIA IDs like: 0 snd-ens1371 0x0123 0xABCD 1 snd-usb-audio 0x 0x Could you add to that the irq number? -- Patrick Shirkey - Boost Hardware Ltd. For the discerning hardware connoisseur Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Being on stage with the band in front of crowds shouting, "Get off! No! We want normal music!", I think that was more like acting than anything I've ever done. Goldie, 8 Nov, 2002 The Scotsman --- 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] Old Debian patches
On Mon, Dec 23, 2002 at 03:19:11PM +0100, Takashi Iwai wrote:
> thanks for the patches!
Thanks for reviewing :)
> > > After initialisation of ALSA version 0.9b12 the depmod complains about
> > > problems in snd-isapnp module.
> > >
> > > The following patch should get rid of the problem:
> >
> > --- isapnp.cSat Feb 9 19:30:13 2002
> > +++ isapnp.c.fixMon Apr 8 11:18:13 2002
> > @@ -2094,7 +2094,7 @@
> > static void isapnp_release_resource(struct resource *res)
> > {
> > if (res) {
> > - release_resource(res);
> > + isapnp_release_resource(res);
> > kfree(res);
> > }
> > }
> >
> > We never got feedback from the user when we took over ALSA, so it was
> > never applied. I don't know if it's needed/valid.
> apparently this will cause an infinite loop, won't it?
> i haven't seen any isapnp-problems on my 2.2 environment...
> so, skipped now.
Ok. As I said, I've asked the submitter to check against recent alsa
verisons and never got new feedback, so we'll just close the bug. If
it's still there he can always reopen.
Jordi
--
Jordi Mallach Pérez -- Debian developer http://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/~jordi/
msg05758/pgp0.pgp
Description: PGP signature
Re: [Alsa-devel] Old Debian patches
Hi Jordi,
thanks for the patches!
At Sat, 21 Dec 2002 16:17:22 +0100,
Jordi Mallach wrote:
>
> Hello!
>
> As promised, we've been trying to track down some of the old patches
> lying around in our package for quite soem time. We'd like you guys to
> see if they are still needed so you can apply them upstream, or we can
> get rid of them.
>
> Bug#141114: improper call to snd_power_lock in ppc (reported against
> beta12).
already fixed.
>
> Jack Howarth reported:
>
> > On debian ppc sid, the new alsa-source 0.9beta12-1 doesn't build
> > the powermac sound driver properly. The current source has an
> > improper call to snd_power_lock which has changed its api. Also
> > the powermac driver builds with unresolved symbols for udelay
> > and mdelay. The attached patch needs to be added to the current
> > alsa-source 0.9+beta12 debian sources to resolve these issues.
> > With this patch the powermac sound module builds and operates fine
> > under Linux 2.4.19pre5.
>
>
> --- alsa-driver-0.9.0rc5.orig/alsa-kernel/ppc/keywest.c Mon Feb 25 20:50:13 2002
> +++ alsa-driver-0.9.0rc5/alsa-kernel/ppc/keywest.c Sun May 12 20:56:25 2002
> @@ -21,6 +21,7 @@
>
> #include
> #include
> +#include
> #include
> #include
> #include
applied to cvs now.
> -
> Bug#167633: usbaudio fails to build on 2.2 kernels (reported against
> rc5)
>
> Aaron M. Ucko provided the following fix:
>
>
> --- /usr/src/modules/alsa-driver/usb/usbaudio.c~2002-10-10 08:25:03.
> +++ /usr/src/modules/alsa-driver/usb/usbaudio.c 2002-11-03 19:43:22.0 -0
> @@ -171,6 +171,7 @@
>
> void snd_compat_usb_driver_claim_interface(struct snd_compat_usb_driver *driver
> {
> + struct snd_usb_reg_table *tbl;
> if ((tbl = find_matchingUsb_driver(driver)) != NULL)
> usb_driver_claim_interface(&tbl->driver, iface, ptr);
> }
already fixed.
> -
> Bug#142693: depmod problem with provided isapnp (reported against
> beta12)
>
> "K-Bay" reported:
>
> > After initialisation of ALSA version 0.9b12 the depmod complains about
> > problems in snd-isapnp module.
> >
> > The following patch should get rid of the problem:
>
> --- isapnp.cSat Feb 9 19:30:13 2002
> +++ isapnp.c.fixMon Apr 8 11:18:13 2002
> @@ -2094,7 +2094,7 @@
> static void isapnp_release_resource(struct resource *res)
> {
> if (res) {
> - release_resource(res);
> + isapnp_release_resource(res);
> kfree(res);
> }
> }
>
> We never got feedback from the user when we took over ALSA, so it was
> never applied. I don't know if it's needed/valid.
apparently this will cause an infinite loop, won't it?
i haven't seen any isapnp-problems on my 2.2 environment...
so, skipped now.
thanks,
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
Re: [Alsa-devel] How to set ppq?
Hi, At Mon, 23 Dec 2002 14:19:38 +0100, Gerald Grabner wrote: > > Hi, > > I'm trying to set PPQ for the alsa sequencer queue but it doesn't > work. Here is the piece of code: > >snd_seq_queue_tempo_set_tempo (queue_tempo, tempo) ; >snd_seq_queue_tempo_set_ppq (queue_tempo, ppq ) ; >snd_seq_set_queue_tempo (seq_handle, queue_id, queue_tempo) ; > > It works for tempo, but not for ppq. Does anybody know how I could > also set ppq? the ppq cannot be changed during the queue is running although the tempo can be varied. you can set the ppq before starting the queue, or after stopping the queue. ciao, 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
Re: [Alsa-devel] Converted "Writing an ALSA Driver" to DocBook.
At Mon, 23 Dec 2002 22:19:01 +0900, Patrick Shirkey wrote: > > Kevin Conder wrote: > > In case any one was curious, I converted Takashi's "Writing an ALSA > > Driver" document to DocBook/SGML. It's available for download here: > > > > http://www.kevindumpscore.com/download/writing-an-alsa-driver.sgml > > > > > > I have downloaded it to add to the site. I will render it to html so we > can provide a nice way to browse it online. nice. if you finish the set up, please let me know the url. i'll add it as the reference to the new version. 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
Re: [linux-audio-user] Re: [Alsa-devel] alsaplayer not working with alsa?
Hi, if you're using a ppc snd-powermac driver, then it's likely a long-standing bug of alsa-lib (somehwere deep inside). it appears only on ppc with alsaplayer. the maintainer is me, but, sorry, atm i haven't had a hardware for debugging this... have a merry christmas! Takashi At 23 Dec 2002 05:46:45 -0800, Mark Knecht wrote: > > Thanks Steve. Merry Xmas! > > On Mon, 2002-12-23 at 05:34, Steve Harris wrote: > > On Sun, Dec 22, 2002 at 01:19:05 -0800, Mark Knecht wrote: > > > [mark@Godzilla mark]$ alsaplayer > > > alsaplayer: pcm.c:6293: snd_pcm_unlink_ptr: Assertion `0' failed. > > > AlsaPlayer interrupted by signal 6 > > > [mark@Godzilla mark]$ > > > > > >alsaplayer works very well when jack is running. > > > > > >Anyone else seeing this? > > > > Yes. > > > > I suspect that Fernando needs to update alsaplayer. > > > > - Steve > > > > > --- > 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 > --- 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: alsasound init script (Re: [Alsa-devel] possible problems with rc6 aplay )
At Fri, 20 Dec 2002 23:53:13 +0100, Pedro Lopez-Cabanillas wrote: > > Clemens, I remember that /proc/asound/cards returned this bus/device > information for USB MIDI devices some time ago (rc3?), like it does for my SB > 128 PCI. it would be nice to provide a new generic proc file which shows the low-level hardware information as the card number, the module name and the PCI/ISA-PnP/USB/PCMCIA IDs like: 0 snd-ens1371 0x0123 0xABCD 1 snd-usb-audio 0x 0x 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
Re: [linux-audio-user] Re: [Alsa-devel] alsaplayer not working withalsa?
Thanks Steve. Merry Xmas! On Mon, 2002-12-23 at 05:34, Steve Harris wrote: > On Sun, Dec 22, 2002 at 01:19:05 -0800, Mark Knecht wrote: > > [mark@Godzilla mark]$ alsaplayer > > alsaplayer: pcm.c:6293: snd_pcm_unlink_ptr: Assertion `0' failed. > > AlsaPlayer interrupted by signal 6 > > [mark@Godzilla mark]$ > > > >alsaplayer works very well when jack is running. > > > >Anyone else seeing this? > > Yes. > > I suspect that Fernando needs to update alsaplayer. > > - Steve --- 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] usbaudio won't do 24-bit or 32-bit i/o...
At Sat, 21 Dec 2002 07:00:45 +0900, Patrick Shirkey wrote: > > Takashi Iwai wrote: > > > > hmmm, it seems that the problem is on usb-uhci driver. > > mysteriously, the midi part of quattro causes the kernel panic. the > > audio part seems ok. > > you can avoid this either by using uhci driver or by commenting out > > the entry for quattro in alsa-kernel/usb/usbquirks.h. > > > > I am trying it out on my ohci machine too and the latest driver has > fixed the problem with not being able to capture from all the input. > > Thanks. > > I have commented out the midi quirk though in alsa-kernel/usb/usbquirk.h > > I will be saving this cvs for sure. > > The 24_3le support in arecord still captures the left channel maxed and > the right at normal volume on pcm0 and pcm1. did you update the alsa-lib, too? there was a bug regarding 24bit conversion both on alsa-driver and alsa-lib. 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
Re: [Alsa-devel] Converted "Writing an ALSA Driver" to DocBook.
Kevin Conder wrote: In case any one was curious, I converted Takashi's "Writing an ALSA Driver" document to DocBook/SGML. It's available for download here: http://www.kevindumpscore.com/download/writing-an-alsa-driver.sgml I have downloaded it to add to the site. I will render it to html so we can provide a nice way to browse it online. -- Patrick Shirkey - Boost Hardware Ltd. For the discerning hardware connoisseur Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Being on stage with the band in front of crowds shouting, "Get off! No! We want normal music!", I think that was more like acting than anything I've ever done. Goldie, 8 Nov, 2002 The Scotsman --- 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] How to set ppq?
Hi, I'm trying to set PPQ for the alsa sequencer queue but it doesn't work. Here is the piece of code: snd_seq_queue_tempo_set_tempo (queue_tempo, tempo) ; snd_seq_queue_tempo_set_ppq (queue_tempo, ppq ) ; snd_seq_set_queue_tempo (seq_handle, queue_id, queue_tempo) ; It works for tempo, but not for ppq. Does anybody know how I could also set ppq? Thanks a lot! Gerald BTW: It's on a SuSE 8.1 box that comes with alsa-0.9.0rc3, cvs20020903. --- 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: alsasound init script (Re: [Alsa-devel] possible problems with rc6 aplay )
At 18 Dec 2002 05:11:36 -0800, Mark Knecht wrote: > > On Wed, 2002-12-18 at 03:17, Takashi Iwai wrote: > > At Wed, 18 Dec 2002 11:46:45 +0100, > > I wrote: > > > > > > > It would be better to make the alsasound script more robust (and > > > > independent of the startup order) and able to deal with partially loaded > > > > modules, so instead of just checking for the /proc/asound directory it > > > > would actually see what modules are already loaded and only load those > > > > that are not. It does not look too easy, it seems that /proc/asound does > > > > not provide a list of loaded modules (rather a list of cards that are > > > > not associated with module names). > > > > > > agreed. a scenario i can imagine now is that the script just takes a > > > look at /proc/asound/cards and checks the numbers at the first column. > > > this should correspond to the card indices which have been already > > > loaded. then the script will try to load the modules snd-card-X but > > > skip the numbers listed in the above... > > > i'll try to rewrite as this way. > > > > after reconsideration: it would be much simpler to create a new proc > > file which shows the modules already loaded. > > > I was wondering what would happen in this process if someone had two r > three identical USB devices, like the MidiMan 2X2? OR also two identical > cards like the RME HDSP 9652? when a module is loaded and two or more identical (or supported) devices are connected, the module will initialize the all such devices at once. for multiple devices, you can specify the options separated by commas, options snd-hdsp index=1,2,3 id="hdsp1","hdsp2","hdsp3" if there is no index option given for a device, as mentioned before, an empty slot is probed from the index 0. thus, if you don't set any index options for all modules, that's fine, except for that the order of devices is not guaranteed. (cards_limit option must be enough large, or you need to apply my patch.) for keeping the order of devices, giving the index option for each device would be better. > It is important that the system recognize the same hardware as the same > sound device every time the machine booted, and whether the machine is > warm or cold booted. in the case of usb, it's not 100% sure, because it's anyway hotpluggable. but usually the order of probing is identical, so it's ok. Takashi --- This SF.NET email is sponsored by: The Best Geek Holiday Gifts! Time is running out! Thinkgeek.com has the coolest gifts for your favorite geek. Let your fingers do the typing. Visit Now. T H I N K G E E K . C O Mhttp://www.thinkgeek.com/sf/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] Dell OEM Soundblaster Live 5.1 with different PCI ID
At Thu, 19 Dec 2002 19:38:05 -0800, Jeff Ridenour wrote: > > Just as an update, when I try to use aplay to play a sound, I get this > error: > > [root@beall-dell-01 sounds]# aplay phone.wav > Playing WAVE 'phone.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, > Stereo > aplay: pcm_write:999: write error: Input/output error > [root@beall-dell-01 sounds]# this is likely an interrupt problem. if you set "pnp os" to yes on the bios, try to set it to "no". but even without interrupts, you should be able to hear CDs. this is a mixer mis-configuration in most cases. you'll need to adjust the volume of "Line Playback" and unmute it. in addition, the volume of "AC97 Playback" must be adjusted and unmuted. of course, "PCM" and "Master" must be adjusted and unmuted, too. to hear WAV, "Wave" must be adjusted and unmuted, too. Takashi --- This SF.NET email is sponsored by: The Best Geek Holiday Gifts! Time is running out! Thinkgeek.com has the coolest gifts for your favorite geek. Let your fingers do the typing. Visit Now. T H I N K G E E K . C O Mhttp://www.thinkgeek.com/sf/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: alsasound init script (Re: [Alsa-devel] possible problems withrc6 aplay )
Takashi Iwai wrote: > Mark Knecht wrote: > > I was wondering what would happen in this process if someone had two r > > three identical USB devices, like the MidiMan 2X2? OR also two identical > > cards like the RME HDSP 9652? > > when a module is loaded and two or more identical (or supported) > devices are connected, the module will initialize the all such devices > at once. > > for multiple devices, you can specify the options separated by commas, > > > It is important that the system recognize the same hardware as the same > > sound device every time the machine booted, and whether the machine is > > warm or cold booted. > > in the case of usb, it's not 100% sure, because it's anyway > hotpluggable. but usually the order of probing is identical, so it's > ok. It is possible to force USB devices to a specific index with the vid/pid parameters for the vendor/product id, even when hotplugging. However, this won't work when you hotplug two identical devices (with the same product id). Clemens --- This SF.NET email is sponsored by: The Best Geek Holiday Gifts! Time is running out! Thinkgeek.com has the coolest gifts for your favorite geek. Let your fingers do the typing. Visit Now. T H I N K G E E K . C O Mhttp://www.thinkgeek.com/sf/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] usbaudio won't do 24-bit or 32-bit i/o...
Takashi Iwai wrote: hmmm, it seems that the problem is on usb-uhci driver. mysteriously, the midi part of quattro causes the kernel panic. the audio part seems ok. you can avoid this either by using uhci driver or by commenting out the entry for quattro in alsa-kernel/usb/usbquirks.h. I am trying it out on my ohci machine too and the latest driver has fixed the problem with not being able to capture from all the input. Thanks. I have commented out the midi quirk though in alsa-kernel/usb/usbquirk.h I will be saving this cvs for sure. The 24_3le support in arecord still captures the left channel maxed and the right at normal volume on pcm0 and pcm1. -- Patrick Shirkey - Boost Hardware Ltd. For the discerning hardware connoisseur Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Being on stage with the band in front of crowds shouting, "Get off! No! We want normal music!", I think that was more like acting than anything I've ever done. Goldie, 8 Nov, 2002 The Scotsman --- This SF.NET email is sponsored by: The Best Geek Holiday Gifts! Time is running out! Thinkgeek.com has the coolest gifts for your favorite geek. Let your fingers do the typing. Visit Now. T H I N K G E E K . C O Mhttp://www.thinkgeek.com/sf/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: alsasound init script (Re: [Alsa-devel] possible problems with rc6 aplay )
On Friday 20 December 2002 21:09, Clemens Ladisch wrote: > Takashi Iwai wrote: > > Mark Knecht wrote: > > > I was wondering what would happen in this process if someone had two r > > > three identical USB devices, like the MidiMan 2X2? OR also two > > > identical cards like the RME HDSP 9652? > > > > when a module is loaded and two or more identical (or supported) > > devices are connected, the module will initialize the all such devices > > at once. > > > > for multiple devices, you can specify the options separated by commas, > > > > > It is important that the system recognize the same hardware as the same > > > sound device every time the machine booted, and whether the machine is > > > warm or cold booted. > > > > in the case of usb, it's not 100% sure, because it's anyway > > hotpluggable. but usually the order of probing is identical, so it's > > ok. The probing order is the same if you plug everytime the same device at the same USB bus/port. Hotplug agent also receives an environment variable, DEVICE=/proc/bus/usb/001/002 or something like this, being the last numbers the USB bus and device numbers. > It is possible to force USB devices to a specific index with the vid/pid > parameters for the vendor/product id, even when hotplugging. > However, this won't work when you hotplug two identical devices (with the > same product id). The vid/pid parameters work well for me, as i have two USB MIDI devices from different vendors. It works regarding the plug order, or the USB port used. Perhaps another parameter like usbdev=001/002 or something else could be useful in case that someone has several identical devices? Clemens, I remember that /proc/asound/cards returned this bus/device information for USB MIDI devices some time ago (rc3?), like it does for my SB 128 PCI. Regards, Pedro -- ALSA Library Bindings for Pascal http://alsapas.alturl.com --- This SF.NET email is sponsored by: The Best Geek Holiday Gifts! Time is running out! Thinkgeek.com has the coolest gifts for your favorite geek. Let your fingers do the typing. Visit Now. T H I N K G E E K . C O Mhttp://www.thinkgeek.com/sf/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] How to play different audio data on the left and right channel at the same time?
Hi, I want to play different wave file on two channel at the same time, that's one wave file for left channel, and the other for right channel, can I achieve this with the alsa lib on linux? Need I open the sound device twice? Thx! Walter _ Add photos to your e-mail with MSN 8. Get 3 months FREE*. http://join.msn.com/?page=features/featuredemail&xAPID=42&PS=47575&PI=7324&DI=7474&SU= http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_addphotos_3mf --- This SF.NET email is sponsored by: Order your Holiday Geek Presents Now! Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap, MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Old Debian patches
Hello!
As promised, we've been trying to track down some of the old patches
lying around in our package for quite soem time. We'd like you guys to
see if they are still needed so you can apply them upstream, or we can
get rid of them.
Bug#141114: improper call to snd_power_lock in ppc (reported against
beta12).
Jack Howarth reported:
> On debian ppc sid, the new alsa-source 0.9beta12-1 doesn't build
> the powermac sound driver properly. The current source has an
> improper call to snd_power_lock which has changed its api. Also
> the powermac driver builds with unresolved symbols for udelay
> and mdelay. The attached patch needs to be added to the current
> alsa-source 0.9+beta12 debian sources to resolve these issues.
> With this patch the powermac sound module builds and operates fine
> under Linux 2.4.19pre5.
--- alsa-driver-0.9.0rc5.orig/alsa-kernel/ppc/keywest.c Mon Feb 25 20:50:13 2002
+++ alsa-driver-0.9.0rc5/alsa-kernel/ppc/keywest.c Sun May 12 20:56:25 2002
@@ -21,6 +21,7 @@
#include
#include
+#include
#include
#include
#include
-
Bug#167633: usbaudio fails to build on 2.2 kernels (reported against
rc5)
Aaron M. Ucko provided the following fix:
--- /usr/src/modules/alsa-driver/usb/usbaudio.c~2002-10-10 08:25:03.
+++ /usr/src/modules/alsa-driver/usb/usbaudio.c 2002-11-03 19:43:22.0 -0
@@ -171,6 +171,7 @@
void snd_compat_usb_driver_claim_interface(struct snd_compat_usb_driver *driver
{
+ struct snd_usb_reg_table *tbl;
if ((tbl = find_matchingUsb_driver(driver)) != NULL)
usb_driver_claim_interface(&tbl->driver, iface, ptr);
}
-
Bug#142693: depmod problem with provided isapnp (reported against
beta12)
"K-Bay" reported:
> After initialisation of ALSA version 0.9b12 the depmod complains about
> problems in snd-isapnp module.
>
> The following patch should get rid of the problem:
--- isapnp.cSat Feb 9 19:30:13 2002
+++ isapnp.c.fixMon Apr 8 11:18:13 2002
@@ -2094,7 +2094,7 @@
static void isapnp_release_resource(struct resource *res)
{
if (res) {
- release_resource(res);
+ isapnp_release_resource(res);
kfree(res);
}
}
We never got feedback from the user when we took over ALSA, so it was
never applied. I don't know if it's needed/valid.
That's all for the moment.
Jordi
--
Jordi Mallach Pérez -- Debian developer http://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED] http://www.sindominio.net/
GnuPG public key information available at http://oskuro.net/~jordi/
msg05742/pgp0.pgp
Description: PGP signature
Re: [Alsa-devel] Dell OEM Soundblaster Live 5.1 with different PCI ID
Am Freitag, 20. Dezember 2002 16:02 schrieb Takashi Iwai: > this is likely an interrupt problem. > if you set "pnp os" to yes on the bios, try to set it to "no". I tried various different bios-settings, none did help > but even without interrupts, you should be able to hear CDs. > this is a mixer mis-configuration in most cases. > you'll need to adjust the volume of "Line Playback" and unmute it. > in addition, the volume of "AC97 Playback" must be adjusted and > unmuted. > of course, "PCM" and "Master" must be adjusted and unmuted, too. > to hear WAV, "Wave" must be adjusted and unmuted, too. Everything unmuted and all sliders up - no sound (only the volume level of background noise going up and down when I move the sliders in the mixer). Do you have any other ideas what to try next? Thorsten --- This SF.NET email is sponsored by: Order your Holiday Geek Presents Now! Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap, MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] How to play different audio data on the left and right channel at the same time?
On Sat, Dec 21, 2002 at 08:02:19PM +0800, ??? ??? wrote: > Hi, > I want to play different wave file on two channel at the same time, that's > one wave file for left channel, and the other for right channel, can I > achieve this with the alsa lib on linux? Need I open the sound device twice? > Thx! > Well, there are 2 ways to do this: 1. The Programming Way: Just interleave the samples from each wav, in other words, lets call your 2 files left.wav and right.wav. Feed your soundcard a stream of samples that go left.wav[sample0], right.wav[sample0], left.wav[sample1], right.wav[sample1], etc... Just remember that it goes left, right, left, right, etc. 2. The Non-Programming Way: Open up your favorite wav editor and assign one wav to the left channel and one wav to the right channel and save it. This is the way you'd do it if you only had a few of these double wav's that you wouldn't have to change much. If you have a lot of them and need to make fast decisions about what you're doing, you can use the command line program SoX to pan each in either direction and play them simultaneously. I can't think of the specific options but you can find them in the SoX manpage, SoX seriously does *every* simple operation you'd want to perform on an audio file. I hope this helps, 784 - Michael C. Piantedosi - [EMAIL PROTECTED] --- This SF.NET email is sponsored by: Order your Holiday Geek Presents Now! Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap, MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty. T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] serialmidi problem
hi everybody,
testing a serial midi synth (Yamaha QY70) with alsa-0.9.0rc6,
linux-2.4.18,
and pmidi-1.5.5, and I noticed that the first notes of score where
lost/jammed,
whereas the rest sounded ok
After a couple of printk in snd-serialmidi.o, it seems that
serialmidi::tx_loop
happens to be executed by 2 concurent threads, one on behalf of
the serial driver via its line discipline, the other called by
snd_serialmidi_output_trigger (I assume it has to do with applicative
snd_seq_drain_output). The preemption probably occurs in the write
function
of the tty driver
these concurent threads both peek the same block of data from rawmidi,
and write it to the tty driver (that could be not that serious
if the block matches exactly an atomic midi event: its is simply sent
twice,
for example the same note), but both as well ack the writing, removing
the sent
event and the next to send (even if it has not been submited yet!)
I fixed this problem with a coarse hack in tx_loop, calling
snd_rawmidi_transmit_ack BEFORE tty->driver.write (that is not that
risky,
as far as the upper layer (rawmidi) and the lower layer (tty driver)
already
agreed on count), but I think a spinlock or whatever kernel artefact
would be more appropriate to avoid concurency in the first place
I join 4 files:
- a midi file containing an arpeggio: C3/E3/G3/C4, 120bpm, each half
note
- a version of tx_loop crowded with printk
- a run of the arpeggio with pmidi, dumped from /var/log/messages
- a dump of the same run of pmidi, with the hack
best regards
MThd ÀMTrk Z ÿ? ÿX ÿQ¡
?
static void tx_loop(serialmidi_t *serial)
{
static int __nb__nb__ = 0;
struct tty_struct *tty;
char buf[64];
int count;
printk("%d: entry in tx_loop: serial %lx\n", __nb__nb__++,
(long)serial);
tty = serial->tty;
count = tty->driver.write_room(tty);
while (count > 0) {
printk("%d: write_room: %i\n", __nb__nb__++, count);
count = count > sizeof(buf) ? sizeof(buf) : count;
count = snd_rawmidi_transmit_peek(serial->substream_output, buf,
count);
printk("%d: peek: %i\n", __nb__nb__++, count);
if (count > 0) {
#ifdef MY_HACK
snd_rawmidi_transmit_ack(serial->substream_output, count);
#endif
count = tty->driver.write(tty, 0, buf, count);
printk("%d: tx_loop tty %lx: written: %i: ",
__nb__nb__++,
(long)tty, count);
{ int i;
for (i = 0; i < count; i++)
printk("%.2x ", buf[i] & 0xff);
printk("\n");
}
#ifndef MY_HACK
snd_rawmidi_transmit_ack(serial->substream_output, count);
#endif
count = tty->driver.write_room(tty);
} else {
clear_bit(TTY_DO_WRITE_WAKEUP, &tty->flags);
break;
}
}
printk("%d: exit from tx_loop\n", __nb__nb__++);
}
Dec 22 00:19:13 synprez kernel: snd_serialmidi_output_trigger: up=0
Dec 22 00:19:13 synprez kernel: snd_serialmidi_output_trigger: up=1
# first thread: ok
Dec 22 00:19:13 synprez kernel: 0: entry in tx_loop: serial cb150760
Dec 22 00:19:13 synprez kernel: 1: write_room: 4095
Dec 22 00:19:13 synprez kernel: 2: peek: 3
Dec 22 00:19:13 synprez kernel: ldisc_write_wakeup
# second thread, the same data are read from rawmidi: oops...
Dec 22 00:19:13 synprez kernel: 3: entry in tx_loop: serial cb150760
Dec 22 00:19:13 synprez kernel: 4: write_room: 4095
Dec 22 00:19:13 synprez kernel: 5: peek: 3
# legal C3 on
Dec 22 00:19:13 synprez kernel: 6: tx_loop tty c9c39000: written: 3: 91 3c 3f
Dec 22 00:19:13 synprez kernel: 7: write_room: 4092
Dec 22 00:19:13 synprez kernel: 8: peek: 0
# first exit, the second thread resumes
Dec 22 00:19:13 synprez kernel: 9: exit from tx_loop
# duplicate C3 on: the ear does not notice, because the note is simply stroke
# twice in the same millisec
Dec 22 00:19:13 synprez kernel: 10: tx_loop tty c9c39000: written: 3: 91 3c 3f
Dec 22 00:19:13 synprez kernel: 11: write_room: 4092
Dec 22 00:19:13 synprez kernel: 12: peek: 0
# second exit
Dec 22 00:19:13 synprez kernel: 13: exit from tx_loop
# at this point, 6 bytes (thice the same 3) where played and acked
Dec 22 00:19:14 synprez kernel: snd_serialmidi_output_trigger: up=1
# here the C3 off should be sent, but is was lost, so the C3 key remains on
Dec 22 00:19:14 synprez kernel: 14: entry in tx_loop: serial cb150760
# from this point, every is ok
Dec 22 00:19:14 synprez kernel: 15: write_room: 4095
Dec 22 00:19:14 synprez kernel: 16: peek: 3
Dec 22 00:19:14 synprez kernel: 17: tx_loop tty c9c39000: written: 3: 91 40 3f
Dec 22 00:19:14 synprez kernel: 18: write_room: 40
[Alsa-devel] alsaplayer not working with alsa?
Hi, When running alsaplayer version 0.99.73 without jack, I'm seeing this failure: [mark@Godzilla mark]$ alsaplayer -v alsaplayer 0.99.73 [mark@Godzilla mark]$ alsaplayer alsaplayer: pcm.c:6293: snd_pcm_unlink_ptr: Assertion `0' failed. AlsaPlayer interrupted by signal 6 [mark@Godzilla mark]$ alsaplayer works very well when jack is running. Anyone else seeing this? Thanks, Mark --- 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] Converted "Writing an ALSA Driver" to DocBook.
In case any one was curious, I converted Takashi's "Writing an ALSA Driver" document to DocBook/SGML. It's available for download here: http://www.kevindumpscore.com/download/writing-an-alsa-driver.sgml = -- kwconder at yahoo dot com __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --- 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
