[Alsa-devel] usb midi devices.
Could someone send me a list of all the usbmidi devices that require firmware to be inserted. I am redesigning the docs for these cards. -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Apparently upon the beginning of the barrage, the donkey broke discipline and panicked, toppling the cart. At that point, the rockets disconnected from the timer, leaving them strewn around the street. Tethered to the now toppled cart, the donkey was unable to escape before the arrival of U.S. troops. United Press International Rockets on donkeys hit major Baghdad sites By P. MITCHELL PROTHERO Published 11/21/2003 11:13 AM --- 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
On Sun, 14 Dec 2003, Frank Barknecht wrote: 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? We use USB mixer device defaults at the moment so it's ok. Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- 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] Newbie driver prgrmmr
Coen Leermakers wrote: Hi all, Does anyone here know where to find some good manuals and howto's on driver programming? I myself have some programming experience, and want to take this some further. Since I have a sound card which is not (yet) compatible with ALSA, I decided the ALSA-Dev mailing list was to be my staging ground :) There is a detailed howto available via the documentation page. -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Apparently upon the beginning of the barrage, the donkey broke discipline and panicked, toppling the cart. At that point, the rockets disconnected from the timer, leaving them strewn around the street. Tethered to the now toppled cart, the donkey was unable to escape before the arrival of U.S. troops. United Press International Rockets on donkeys hit major Baghdad sites By P. MITCHELL PROTHERO Published 11/21/2003 11:13 AM --- 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] usb midi devices.
On Sun, Dec 14, 2003 at 06:32:58PM +0900, Patrick Shirkey wrote: Could someone send me a list of all the usbmidi devices that require firmware to be inserted. I am redesigning the docs for these cards. snd-usb-audio with MidiSport firmware loader: MidiSport 1x1, 2x2, 4x4, 8x8, KeyStation, Oxygen, Radium, Uno, and maybe MidiSport 2x4. (It's the latest list from http://usb-midi-fw.sf.net). snd-usb-usx2y with usx2yloader: Tascam US122, US224 ( 224 needs fw, but we have no driver:-( ), US428 And there are some other cards (Sonica, ...) which need a firmware download, but there's no linux loader available. martin --- 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] Re: [Alsa-user] support for audigy ls soundcard
On Sat, 13 Dec 2003, Dirk Vornheder wrote: Hi ! Is the creative soundcard Audigy LS supported by the alsa driver ? No. This chip is different from emu10k1 (Live) and emu10k2 (Audigy) and we have no information about it. Ask Creative for help (documentation). Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- 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] Newbie driver prgrmmr
You should buy the O'Reilly book Linux Device Drivers. It's excellent. Jan On Sun, 2003-12-14 at 04:08, Patrick Shirkey wrote: Coen Leermakers wrote: Hi all, Does anyone here know where to find some good manuals and howto's on driver programming? I myself have some programming experience, and want to take this some further. Since I have a sound card which is not (yet) compatible with ALSA, I decided the ALSA-Dev mailing list was to be my staging ground :) There is a detailed howto available via the documentation page. -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Apparently upon the beginning of the barrage, the donkey broke discipline and panicked, toppling the cart. At that point, the rockets disconnected from the timer, leaving them strewn around the street. Tethered to the now toppled cart, the donkey was unable to escape before the arrival of U.S. troops. United Press International Rockets on donkeys hit major Baghdad sites By P. MITCHELL PROTHERO Published 11/21/2003 11:13 AM --- 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 --- 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] no sound with 1.0.0 release
Hallo, Noel Bush hat gesagt: // Noel Bush wrote: I am using the planetccrma-core distribution. Recently I tried upgrading, via that distro, to the alsa 1.0.0 packages. I found that after this upgrade, I was unable to hear any sound when using any app (simplest test, using aplay on a wav file). I have no real idea why this is so, but here often it helped to remove the file /etc/asound.state while ALSA isn't running and then start ALSA again. 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 timer slippage
While trying to track down the source of some poor timing in sequencing, I've noticed that my ALSA sequencer queue timer has a tendency to fall suddenly behind. I have a little test program (available on request) that just starts a queue and every second or so compares the queue timer against real time as returned by gettimeofday(). It doesn't mind if the two don't quite match, but it does complain if the difference between the two timers changes dramatically between two sample points. When I run it, it never lasts for more than about a minute before the ALSA queue timer suddenly slips by anything from 10 to 60 milliseconds. This is a non-low-latency kernel so I'm not surprised that there may be some occasional timing issues, but 60ms is a lot on an unloaded machine, and I am vaguely surprised that the timer doesn't notice it's fallen behind and recover -- instead all events on the queue continue to be delivered late forever. This obviously makes for some disconcerting audible effects. The system is SuSE 9.0 on a dual 2GHz Athlon using SuSE's stock SMP kernel. I have tried both ALSA 0.9.6 (from SuSE) and 1.0.0rc2 drivers and libraries. I haven't managed to reproduce it using a PlanetCCRMA SMP kernel on the same machine, nor on my uniprocessor laptop. I've surveyed a few other people on rosegarden-devel and nobody's corroborated my findings, so I guess it might be related to using a dual-processor machine. Any thoughts on this, anyone? I'm finding it a little depressing that I can't play even a minute of 4/4 beats from an ALSA test program without the timing slipping audibly at least once. I'm ready to delve cluelessly into the timer code to take a look, but (glancing at alsa-kernel/core/timer.c) I'm not at all sure how far I'd get... Chris --- 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] Re: alsa timer slippage
Jan Depner [EMAIL PROTECTED] writes: On Sun, 2003-12-14 at 08:07, Chris Cannam wrote: While trying to track down the source of some poor timing in sequencing, I've noticed that my ALSA sequencer queue timer has a tendency to fall suddenly behind. I have a little test program (available on request) that just starts a queue and every second or so compares the queue timer against real time as returned by gettimeofday(). It doesn't mind if the two don't quite match, but it does complain if the difference between the two timers changes dramatically between two sample points. When I run it, it never lasts for more than about a minute before the ALSA queue timer suddenly slips by anything from 10 to 60 milliseconds. If I'm not mistaken the timing for your audio is coming from your sound card not your system clock. The gettimeofday is from the system clock. They probably won't match. That's true. However, you typically see a gradual drift, not a sudden jump. -- Måns Rullgård [EMAIL PROTECTED] --- 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] alsa timer slippage
On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote: If I'm not mistaken the timing for your audio is coming from your sound card not your system clock. Is that so? Obvious though it is, that simply hadn't occurred to me. I mentally ruled out a hardware problem quite early on because I wasn't seeing this problem when using a low-latency kernel on the same hardware -- but maybe I just hadn't done enough testing with the low-latency kernel. I'll give it another shot. The other points that brings to mind are, what if you have more than one soundcard or no soundcard at all (only say USB devices)? and what if the soundcard's just a chip on the motherboard, as mine is -- wouldn't it get its own timing from the system clock? It's plausible that this crappy i810 could have a crappy timer, though this example would be unusually crappy. Chris --- 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] alsa timer slippage
On Sunday 14 Dec 2003 2:34 pm, Chris Cannam wrote: On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote: If I'm not mistaken the timing for your audio is coming from your sound card not your system clock. [...] I mentally ruled out a hardware problem quite early on because I wasn't seeing this problem when using a low-latency kernel on the same hardware -- but maybe I just hadn't done enough testing with the low-latency kernel. I'll give it another shot. No, definitely no such problem visible when using the CCRMA kernel. Chris --- 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] alsa timer slippage
Multiple soundcards usually have to use word clock or some proprietary method of syncing the cards. Usually one card will be the master and the others slaves. I know you can put up to 4 ST Audio DSP24 cards in one system and set one up as master. I believe the same is true for the M-Audio Delta 1010. As for having a bad timer on a system, I've worked a lot with realtime systems and sometimes you just get a lemon. Jan On Sun, 2003-12-14 at 08:34, Chris Cannam wrote: On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote: If I'm not mistaken the timing for your audio is coming from your sound card not your system clock. Is that so? Obvious though it is, that simply hadn't occurred to me. I mentally ruled out a hardware problem quite early on because I wasn't seeing this problem when using a low-latency kernel on the same hardware -- but maybe I just hadn't done enough testing with the low-latency kernel. I'll give it another shot. The other points that brings to mind are, what if you have more than one soundcard or no soundcard at all (only say USB devices)? and what if the soundcard's just a chip on the motherboard, as mine is -- wouldn't it get its own timing from the system clock? It's plausible that this crappy i810 could have a crappy timer, though this example would be unusually crappy. Chris --- 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] listing devices.
I'm looking but I can't find a way to get the list of all available devices including virtual devices defined in the .asoundrc Is there any function that provides this? If not has there been any thought put into how it can be accomplished? -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Apparently upon the beginning of the barrage, the donkey broke discipline and panicked, toppling the cart. At that point, the rockets disconnected from the timer, leaving them strewn around the street. Tethered to the now toppled cart, the donkey was unable to escape before the arrival of U.S. troops. United Press International Rockets on donkeys hit major Baghdad sites By P. MITCHELL PROTHERO Published 11/21/2003 11:13 AM --- 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] listing devices.
Patrick Shirkey wrote: I'm looking but I can't find a way to get the list of all available devices including virtual devices defined in the .asoundrc Is there any function that provides this? If not has there been any thought put into how it can be accomplished? Sorry missed the thread on query devices in a non blcking way from a few days ago. I'll pick it up there. -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Apparently upon the beginning of the barrage, the donkey broke discipline and panicked, toppling the cart. At that point, the rockets disconnected from the timer, leaving them strewn around the street. Tethered to the now toppled cart, the donkey was unable to escape before the arrival of U.S. troops. United Press International Rockets on donkeys hit major Baghdad sites By P. MITCHELL PROTHERO Published 11/21/2003 11:13 AM --- 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] Query devices in a non-blocking fashion
If we have a DB of info how would we define the abilities of each device? I assume this info is available in the driver layer because there is a point where ALSA will return false eg. if a card is not able to run at 48000Hz My opinion is that a simple function could be included in alsactl which scans for available devices, makes a list of their abilities. Everyone uses post-insert alsactl restore in the modules.conf file so it would be essentially a non issue from a user perspective. Couldn't this be saved in the config settings for alsactl? -- Patrick Shirkey - Boost Hardware Ltd. Http://www.boosthardware.com Http://www.djcj.org - The Linux Audio Users guide Apparently upon the beginning of the barrage, the donkey broke discipline and panicked, toppling the cart. At that point, the rockets disconnected from the timer, leaving them strewn around the street. Tethered to the now toppled cart, the donkey was unable to escape before the arrival of U.S. troops. United Press International Rockets on donkeys hit major Baghdad sites By P. MITCHELL PROTHERO Published 11/21/2003 11:13 AM --- 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] confirmed working EDIROL - PCR 30
Hi I know it's no big news for a USB Midi device to be working but I thought I may as well announce this anyway. The Edirol PCR-30 Midi Keyboard Controller (with sliders, knobs, buttons e.t.c..) works perfectly the USB audio module (snd-usb-audio). This most likely means the PCR-50 and PCR-80 also work. NOTE: The device must be set to use the Generic USB driver and not the Original driver (aka FPT) cheers -- Allan Klinbail [EMAIL PROTECTED] --- 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] Query devices in a non-blocking fashion
My opinion is that a simple function could be included in alsactl which scans for available devices, makes a list of their abilities. Everyone uses post-insert alsactl restore in the modules.conf file so it would be essentially a non issue from a user perspective. i think it needs to be slightly more complex than that (because of the way the configuration space is reduced as various parameters are set). we need a structure that is somewhat equivalent to hw_params. the program fills it out, in effect asking for 16 bit, stereo, 48kHz, 1024 frames/period and then queries to see what devices can satisfy that. it will be hard for the program to use this if it thinks it can handle multiple configurations, but there are not many programs that work this way: most know what configuration they want, and just want to find devices that can work that way. otoh, one may counter that the plughw layer in alsa-lib is there to allow *any* h/w device to be used with *any* configuration, so this is all a bit ridiculous. of course, the devices may be busy, so the program needs to be ready for that as well (this applies to multiopen cards just the same, even if its much less likely that they are fully busy). --- 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] Query devices in a non-blocking fashion
On Mon, 15 Dec 2003 01:17:26 +0900, Patrick Shirkey [EMAIL PROTECTED] wrote: If we have a DB of info how would we define the abilities of each device? I assume this info is available in the driver layer because there is a point where ALSA will return false eg. if a card is not able to run at 48000Hz My opinion is that a simple function could be included in alsactl which scans for available devices, makes a list of their abilities. Everyone uses post-insert alsactl restore in the modules.conf file so it would be essentially a non issue from a user perspective. Couldn't this be saved in the config settings for alsactl? This whole database thing seems like overkill to me, to be honest. This is dynamic information would best be obtained from cards during operation, the only problem is that you have to lock the device. A better design would be to, if possible, allow the configuration space to be read even when a device is streaming. I dont know the dirty details of writing drivers, but would this be a problem? Perhaps we could differ between read-locked and write-locked configuration, so there would be inclusive read access to the device, and totally exclusive access if it is to be modified. Hope some of this makes sense Arve Knudsen --- 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] Query devices in a non-blocking fashion / 3D capabilties.
Hi, While writing a advanced capabilities (positional audio) interface for ALSA, i encountered this same problem. So far i have architected the thing like this: - The ALSA driver loads as usual. - When OpenAL or whatever fires up, it queries the device for capabilties, using a well defined control for that purpose. - Depending on what capabilties are reported as supported, the library uses a series of kcontrols to modify hardware settings for advanced capabilties (HRTF, ITD, filters, etc). If this can't be performed in a asyncronous (non-blocking) i wouldn't be able to use controls. I looked into alsa-kernel/core/control.c and after finding out that every control interaction does a control lookup (iterated through all controls), i don't feel very confortable about using kcontrols to update hardware parameters in at tens of milisecond intervals. Then i discovered the ALSA /proc interface, but the docs read use for debugging. They have a lot less overhead. Would it be OK to use them for hardware parameter update ? And if so, why don't you use this interface for queries ? They seem to give much more freedom about locking and other issues. I really need feedback :) Best Regards On Sun, 2003-12-14 at 12:46, Arve Knudsen wrote: On Mon, 15 Dec 2003 01:17:26 +0900, Patrick Shirkey [EMAIL PROTECTED] wrote: If we have a DB of info how would we define the abilities of each device? I assume this info is available in the driver layer because there is a point where ALSA will return false eg. if a card is not able to run at 48000Hz My opinion is that a simple function could be included in alsactl which scans for available devices, makes a list of their abilities. Everyone uses post-insert alsactl restore in the modules.conf file so it would be essentially a non issue from a user perspective. Couldn't this be saved in the config settings for alsactl? This whole database thing seems like overkill to me, to be honest. This is dynamic information would best be obtained from cards during operation, the only problem is that you have to lock the device. A better design would be to, if possible, allow the configuration space to be read even when a device is streaming. I dont know the dirty details of writing drivers, but would this be a problem? Perhaps we could differ between read-locked and write-locked configuration, so there would be inclusive read access to the device, and totally exclusive access if it is to be modified. Hope some of this makes sense Arve Knudsen --- 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 --- 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] alsa timer slippage
On Sunday 14 Dec 2003 2:34 pm, Chris Cannam wrote: On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote: If I'm not mistaken the timing for your audio is coming from your sound card not your system clock. [...] what if you have more than one soundcard or no soundcard at all And of course I can trivially test that by disabling my soundcard in modules.conf. So I did, and now I have no cards (at least, that's what /proc/asound/cards says) and yet the queue timer test program still runs and the queue timer still goes screwy. So it's not a problem with the soundcard, unless ALSA is magically sync'ing from a soundcard I haven't told it about. Chris --- 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] plz fix this before alsa 1.0.0 get's released
alsa won't compile on kernel 2.6 removing sndversions.h in vxp440.c and vxpocket.c does the trick. /home/lupus/alsa-driver-1.0.0rc2/pcmcia/vx/vxp440.c:6:31: linux/modversions.h: Onbekend bestand of map /home/lupus/alsa-driver-1.0.0rc2/pcmcia/vx/vxp440.c:7:25: sndversions.h: Onbekend bestand of map make[3]: *** [/home/lupus/alsa-driver-1.0.0rc2/pcmcia/vx/vxp440.o] Fout 1 make[2]: *** [/home/lupus/alsa-driver-1.0.0rc2/pcmcia/vx] Fout 2 make[1]: *** [/home/lupus/alsa-driver-1.0.0rc2/pcmcia] Fout 2 make[1]: Weggaan uit map `/lib/modules/2.6.0-0.test11.1.102/build' make: *** [compile] Fout 1 --- 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] Re: plz fix this before alsa 1.0.0 get's released
Kristof vansant [EMAIL PROTECTED] writes: alsa won't compile on kernel 2.6 removing sndversions.h in vxp440.c and vxpocket.c does the trick. /home/lupus/alsa-driver-1.0.0rc2/pcmcia/vx/vxp440.c:6:31: linux/modversions.h: Onbekend bestand of map /home/lupus/alsa-driver-1.0.0rc2/pcmcia/vx/vxp440.c:7:25: sndversions.h: Onbekend bestand of map That's the Dutch message for No such file or directory, right? It's nice to set the language to English when posting error messages. -- Måns Rullgård [EMAIL PROTECTED] --- 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] ALSA sequencer changes?
Ryan Pavlik wrote: 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. No problems here with 1.0.0rc2. Your test reports events and times like before. Try using other client/port, check your cables, interfaces, etc... Regards, Pedro -- ALSA Library Bindings for Pascal http://alsapas.alturl.com --- 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] alsa timer slippage
On Sun, 2003-12-14 at 06:48, Chris Cannam wrote: On Sunday 14 Dec 2003 2:34 pm, Chris Cannam wrote: On Sunday 14 Dec 2003 2:02 pm, Jan Depner wrote: If I'm not mistaken the timing for your audio is coming from your sound card not your system clock. [...] I mentally ruled out a hardware problem quite early on because I wasn't seeing this problem when using a low-latency kernel on the same hardware -- but maybe I just hadn't done enough testing with the low-latency kernel. I'll give it another shot. No, definitely no such problem visible when using the CCRMA kernel. Or maybe it is just 10 times smaller. The Planet CCRMA kernel is compiled with HZ=1000 (instead of the normal HZ=100). -- Fernando --- 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] OpenAL - ALSA interface proposal. I request for comments...
Hi, Since there is almost nothing else to do to support the Aureal Vortex 3D processor on Linux, just as i announced some time ago i started designing a OpenAL interface for ALSA. The design is meant to be applicable to other hardware too. I made a preliminary description, from what i have done so far, because i want to allow other more experienced people to comment and give input to this. I posted it in plain text. I hope that is compatible enough. http://galadriel.mat.utfsm.cl/~mjander/aureal/alsa/OpenAL-ALSA.txt Well, please give it a read, and tell what do you think about. Thank you very much. Best Regards -- Manuel Jander mjander(at)users(dot)sourceforge(dot)net -- Manuel Jander mjander(at)users(dot)sourceforge(dot)net --- 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] ALSA sequencer changes?
On Mon, 15 Dec 2003 02:03:53 +0100 Pedro Lopez-Cabanillas [EMAIL PROTECTED] wrote: 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. No problems here with 1.0.0rc2. Your test reports events and times like before. Try using other client/port, check your cables, interfaces, etc... Hmm, odd... I finally got it working though. I think the MTP/AV driver may have needed reloading or something. I thought it was a bit more forgiving, but I may have just had the mtpav on all the time. thanks, -- Ryan Pavlik [EMAIL PROTECTED] Mr Pibb, Dr Pepper, I'm on to you... - 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
Re: [Alsa-devel] alsa timer slippage
Chris Cannam wrote: While trying to track down the source of some poor timing in sequencing, I've noticed that my ALSA sequencer queue timer has a tendency to fall suddenly behind. I have a little test program (available on request) that just starts a queue and every second or so compares the queue timer against real time as returned by gettimeofday(). It doesn't mind if the two don't quite match, but it does complain if the difference between the two timers changes dramatically between two sample points. When I run it, it never lasts for more than about a minute before the ALSA queue timer suddenly slips by anything from 10 to 60 milliseconds. Please, send me your test program. This is a non-low-latency kernel so I'm not surprised that there may be some occasional timing issues, but 60ms is a lot on an unloaded machine, and I am vaguely surprised that the timer doesn't notice it's fallen behind and recover -- instead all events on the queue continue to be delivered late forever. This obviously makes for some disconcerting audible effects. The system is SuSE 9.0 on a dual 2GHz Athlon using SuSE's stock SMP kernel. I have tried both ALSA 0.9.6 (from SuSE) and 1.0.0rc2 drivers and libraries. I haven't managed to reproduce it using a PlanetCCRMA SMP kernel on the same machine, nor on my uniprocessor laptop. I've surveyed a few other people on rosegarden-devel and nobody's corroborated my findings, so I guess it might be related to using a dual-processor machine. Any thoughts on this, anyone? I'm finding it a little depressing that I can't play even a minute of 4/4 beats from an ALSA test program without the timing slipping audibly at least once. I'm ready to delve cluelessly into the timer code to take a look, but (glancing at alsa-kernel/core/timer.c) I'm not at all sure how far I'd get... The ALSA MIDI sequencer can use several timer sources. By default, it uses the Linux system timer functions, see: http://hegel.ittc.ukans.edu/topics/linux/man-pages/man9/init_timer.9.html Other timer sources are PCM devices and the RTC timer. The module snd-rtctimer provides this functionality. To compile it for a 2.4.x kernel, you need to patch your rtc driver (and rebuild), see alsa-driver/utils/patches You can set a system-wide alternate timer in your /etc/modules.conf, for instance: options snd-seq seq_default_timer_device=1 alias snd-timer-1 snd-rtctimer Or your program can select an alternate timer source for a single queue. See: http://www.mail-archive.com/[EMAIL PROTECTED]/msg09048.html Regards, Pedro -- ALSA Library Bindings for Pascal http://alsapas.alturl.com --- 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] OpenAL - ALSA interface proposal. I request for comments...
Since there is almost nothing else to do to support the Aureal Vortex 3D processor on Linux, just as i announced some time ago i started designing a OpenAL interface for ALSA. The design is meant to be applicable to other hardware too. I made a preliminary description, from what i have done so far, because i want to allow other more experienced people to comment and give input to this. I posted it in plain text. I hope that is compatible enough. http://galadriel.mat.utfsm.cl/~mjander/aureal/alsa/OpenAL-ALSA.txt Well, please give it a read, and tell what do you think about. Thank you very much. i think this is not a very good idea. if you want to wrap OpenAL around ALSA, then wrap it around alsa-lib. don't go messing with the kernel API, that just doesn't make any sense. but more importantly, i don't see how any of what you are proposing aids the use of the aureal vortex 3d processor. a device driver isn't a library, its code that writes data to registers and handles interrupts. nothing about OpenAL deals with that side of things. --p --- 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] OpenAL - ALSA interface proposal. I request for comments...
Manuel Jander wrote: Hi, Since there is almost nothing else to do to support the Aureal Vortex 3D processor on Linux, just as i announced some time ago i started designing a OpenAL interface for ALSA. The design is meant to be applicable to other hardware too. I made a preliminary description, from what i have done so far, because i want to allow other more experienced people to comment and give input to this. I posted it in plain text. I hope that is compatible enough. http://galadriel.mat.utfsm.cl/~mjander/aureal/alsa/OpenAL-ALSA.txt Well, please give it a read, and tell what do you think about. Thank you very much. Best Regards It does not seem like you have read much about alsa. The interface between alsa-kernel and alsa-lib is liable to change at any point whereas the alsa-lib to application api might change, but will always ABI compatible. If there are features of a sound card that you cannot access via alsa-lib, just find ways to add them to alsa-lib first. Everything needed on the hardware should be accessible via alsa-lib. Cheers James --- 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
