Re: [Alsa-devel] kaconnect question and enhancement request
At 24 Feb 2003 19:12:52 -0800, Mark Knecht wrote: Hi, I'm sorry, but I'm not at all sure who developed kaconnect. Matthias Nagorni [EMAIL PROTECTED] I like this little app quite a bit, however, it won't allow one thing I'd certainly like - to be able to hook a MIDI input to its corresponding MIDI output. Why doesn't this work? no idea.. doesn't aconnect in alsa-utils work? 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] [PATCH] Edirol UA-20 PCM support
Hi Clemens, At Mon, 24 Feb 2003 18:17:45 +0100 (MET), Clemens Ladisch wrote: Frank Barknecht wrote: I'm getting a bit tired from being Edirol's laboratory animal. Why didn't they implement the standard they wrote? The Windows USB audio driver (tries to) handle all devices marked as standard compatible. If a device offers capabilities which are implemented buggily or not at all in Microsoft's driver (such as MIDI in Win2K), it has to be marked as vendor-specific to prevent the Microsoft driver from loading so that the vendor's bug-free driver can access the device. It says: Sub=03 Prot=00 Driver=(None) at the Edirol, whereas the other interfaces are claimed by snd-usb-audio. That's a bug in my patch. I'll have to rewrite it. could you resend the patch if finished? or, the previous patch is enough? 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] [PATCH] Edirol UA-20 PCM support
Takashi Iwai wrote: Clemens Ladisch wrote: That's a bug in my patch. I'll have to rewrite it. The header descriptor in if #0 doesn't mention if#3, so we'd need a composite quirk and a new quirk type to call snd_usb_create_streams. That code would be cleaner if the descriptorss would be read from host_if-extra instead of the seperately allocated buffer. could you resend the patch if finished? or, the previous patch is enough? In the current CVS, we get MIDI but no PCM. With my previous patch, we get PCM but not MIDI. I don't have time today for this, but I think I'll have finished it Thursday. Clemens --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] [PATCH] envy24control for GTK+ 2.0
At Mon, 24 Feb 2003 13:55:18 +0100 (CET), Ronny V. Vindenes [EMAIL PROTECTED] wrote: Here's a trivial patch against cvs that converts envy24control to use gtk2, it doesn't fix any of the gui problems so envy24control is still fundamentally broken with regards to translation, theme font handling. I'm tempted to write a proper gnome 2.0 version (with tray icon goodness) if there are no plans to update this. so far we have no plan for that. at least, i don't want to drop the gtk1 support at this moment. but please feel free to fork a new version of envy24control for gtk2. 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] kaconnect question and enhancement request
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Takashi Iwai Sent: Tuesday, February 25, 2003 2:10 AM To: Mark Knecht Cc: Alsa-Devel Subject: Re: [Alsa-devel] kaconnect question and enhancement request no idea.. doesn't aconnect in alsa-utils work? Takashi-san, Thanks. I tried aconnect, and read through the --help stuff, but couldn't figure out the command to hook together two ports. Could you give an example? Everything I tried resulted in error messages. I also wondered about hooking a single input to multiple outputs, so if you could show an example of that, I would appreciate it. 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
Re: [Alsa-devel] kaconnect question and enhancement request
At Tue, 25 Feb 2003 07:43:59 -0800, Mark Knecht wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Takashi Iwai Sent: Tuesday, February 25, 2003 2:10 AM To: Mark Knecht Cc: Alsa-Devel Subject: Re: [Alsa-devel] kaconnect question and enhancement request no idea.. doesn't aconnect in alsa-utils work? Takashi-san, Thanks. I tried aconnect, and read through the --help stuff, but couldn't figure out the command to hook together two ports. Could you give an example? Everything I tried resulted in error messages. try man aconnect :) i think there are some online documents about this, too. suppose you having the sequencer ports 64:0 and 64:32. for connecting between the same input and output, just run like % aconnect 64:0 64:0 I also wondered about hooking a single input to multiple outputs, so if you could show an example of that, I would appreciate it. call aconnect several times, % aconnect 64:0 64:0 % aconnect 64:0 72:0 for removing the connection, use -d option, % aconnect -d 64:0 64:0 basically, kaconnect does these things in GUI. hence, if aconnect doesn't work, likley kaconnect won't work, too. 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] MIDI port names
At Thu, 20 Feb 2003 21:19:19 +0100 (CET), Jaroslav wrote: On Thu, 20 Feb 2003, Takashi Iwai wrote: At Thu, 20 Feb 2003 15:14:45 +0100 (CET), Jaroslav wrote: If there is a way to determine the connection between sequencer port and rawmidi device, I'm ok with any solution. Otherwise, please, solve this problem. one of the advantages of the sequencer is that it hides the lowlevel implementations, regardless of mpu401 or wavetable. hence, there is no explicit link between the lowlevel device and the sequencer client/port, so far. there are only bit flags indicating what kind of functions are supported by the port. it's not bad to have such an attribute, though. but if we have that, it will be an addition. We can use different name for client like: RawMIDI - %s Where %s is whatever you want ;-)) card-shortname, card-id or anything else. The card number can be calculated from the client address and device / subdevice from the port address. done. now everthing became more verbose :) 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] VIA 8233A, 8235 with ALC650 codec
At Mon, 24 Feb 2003 00:50:27 +0300, Anton Worshevsky wrote: All working fine with this for VIA8235 + ALC650 It does not affect on VIA8233A as you remembered. =) What chip combination is working wrong with this ? TI no idea. i hope both via8233 and 8233c follow to the same rule. I suggest to add ALC650 specific control for 0x6a.14 Slot Modify (see my patch). I think this will make a life of future testers a little bit easy. There is also small fix (i think) for ac97_patch.c in my patch. that would be nice. applied a similar patch to the cvs. I found that Exchange Center/LFE is not working on my hardware. After changing bit 0x6a.3 by snd_ac97_write_cache() it still has 0 value. All other controls for 0x6a register works fine ( Duplicate Front, Mic As Center/LFE, Line-In As Surround, Center/LFE Down Mix, Surround Down Mix and my new Slot Modify ). I think that bit 0x6a.3 can not be set on my combination of hardware. Is it possible ? Or just another software bug ? i believe it's a hardware bug (or feature). 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] VIA 8233A with ALC650 codec
At Mon, 24 Feb 2003 08:34:15 +0100, p z wrote: This weekend i tested via8233a + alc650. Surround output jack is swaped with center/LFE jack (but not controls in mixer - surround control controls volume of center/LFE, ..) Please change condition in via82xx.c unsigned short val; if (runtime-channels 4) /* slot mapping: 3,4,7,8 */ val = 0; to if (runtime-channels 5) then everything works ok. thanks for the report. i changed again and the hack above was removed from the kernel driver. the bit is controlled via pcm hook of alsa-lib now. could you update the cvs alsa-kernel and alsa-lib and give a try? 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
[Alsa-devel] M-Audio Revolution 7.1 support
Hi, i split the ICE1724 (Envy24HT) part from ice1712 driver to an indepdenent ice1724 driver, together with the support of M-Audio revolution 7.1. so far, the driver works with aplay and many oss applications. however the following don't work properly yet. - ALSA mmap mode - mpg123 (mpg321 works fine) envy24control doesn't support this chipset yet, so you need to use alsamixer to change the mixer setting. i believe this doesn't break the existing ice1712 driver and the AMP support, but please test the latest driver if you have an ice1712 card or an AMP card to make sure. 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
[Alsa-devel] ALSA CVS and JACK?
can jaroslav or takashi fill me in on the current state of ALSA CVS with respect to JACK? there have been many, many reports of JACK crashing machines when run with recent ALSA CVS in real-time mode, and mentions here on alsa-devel of configure-time JACK detection that causes certain code to be commented out, or something like that. we are about to do a cross-DAW benchmark of ardour with most commercial apps, and the people running the test need to install ALSA. since they will run JACK in RT mode, i need to be sure that this is not going to crash their system, and would like to be able to provide assistance to others in this matter. --p --- 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] ALSA CVS and JACK?
On Tue, 25 Feb 2003, Paul Davis wrote: can jaroslav or takashi fill me in on the current state of ALSA CVS with respect to JACK? there have been many, many reports of JACK crashing machines when run with recent ALSA CVS in real-time mode, and mentions here on alsa-devel of configure-time JACK detection that causes certain code to be commented out, or something like that. Can we see reports? I don't see any reason for crashes. Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project, SuSE Labs --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] ALSA CVS and JACK?
can jaroslav or takashi fill me in on the current state of ALSA CVS with respect to JACK? there have been many, many reports of JACK crashing machines when run with recent ALSA CVS in real-time mode, and mentions here on alsa-devel of configure-time JACK detection that causes certain code to be commented out, or something like that. I don't find those mentions, and I don't find the code either. (Though my CVS is not 100% uptodate). I believe that the only configure-time JACK detection is related to the pcm_jack plugin. If jack is not present it should not be compiled, because it will cause link errors. I also have experienced crashed (well, freezes) with jack in RT mode, but I don't think it has to do anything with alsa. Maarten --- 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] ALSA CVS and JACK?
can jaroslav or takashi fill me in on the current state of ALSA CVS with respect to JACK? there have been many, many reports of JACK crashing machines when run with recent ALSA CVS in real-time mode, and mentions here on alsa-devel of configure-time JACK detection that causes certain code to be commented out, or something like that. I don't find those mentions, and I don't find the code either. you're right. i misread the message i was thinking of. but i am sure jaroslav said something about not understanding why a certain piece of code was a problem with/without JACK. I also have experienced crashed (well, freezes) with jack in RT mode, but I don't think it has to do anything with alsa. all the evidence we have on jackit-dev points to this. people can switch between ALSA versions, and it crashes with a newer copy and not with an earlier one. there are some suggestions that its a kernel+ALSA problem. the fact that it only happens in RT mode suggests some interaction of SCHED_FIFO scheduling and kernel locking or something like that. --p --- 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] ALSA CVS and JACK?
Can we see reports? I don't see any reason for crashes. nobody that this has happened to so far has had an oops trace. they are always running graphical apps and do not have a serial console. i am too nervous (:) to try it myself (hence i still have ALSA CVS from way back). apparently it may it also be connected to a particular kernel version. i would say that at least 6-8 people on jackit-dev have reported this. --p --- 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] ALSA CVS and JACK?
On Tue, 2003-02-25 at 14:00, Paul Davis wrote: can jaroslav or takashi fill me in on the current state of ALSA CVS with respect to JACK? there have been many, many reports of JACK crashing machines when run with recent ALSA CVS in real-time mode, and mentions here on alsa-devel of configure-time JACK detection that causes certain code to be commented out, or something like that. I don't find those mentions, and I don't find the code either. I have this problem on my crusoe laptop. I am using kernel 2.4.20+pre+ll, alsa with cvsdate 20030218.141220, and jack 0.51.1. kernel and alsa are built by me, jack is from Planet CCRMA. I have no serial port on this laptop, just a USB/serial converter, but I will be happy to run whatever test anyone might describe to help find the problem. -- (jfm3 2838 BCBA 93BA 3058 ED95 A42C 37DB 66D1 B43C 9FD0) --- 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] AC3 passthru intel8x0 + cs4299
Hi,
as soon the non audio bit is set to 1 at reg AC97_CSR_SPDIF there come up a error
message in the kernel log
ALSA ../alsa-kernel/pci/intel8x0.c:521: codec_semaphore: semaphore is not ready
[0x1][0x100]
ALSA ../alsa-kernel/pci/intel8x0.c:553: codec_read 0: semaphore is not ready for
register 0x56
I'm in stuck :-(
CU
Bernd Zierath
-Original Message-
From: Peter Heatwole [mailto:[EMAIL PROTECTED]
Sent: Mon 2/24/2003 7:24 PM
To: [EMAIL PROTECTED]; Zierath Bernd; Peter Heatwole
Cc:
Subject: RE: [Alsa-devel] AC3 passthru intel8x0 + cs4299
Peter Heatwole wrote:
I would recommend looking into setting up a mixer function
Here's some more info of what I mean:
http://www.alsa-project.org/~iwai/writing-an-alsa-driver/c765.htm
(BTW, what would be the standard mixer name used for AC3 passthru?)
http://www.alsa-project.org/~iwai/writing-an-alsa-driver/x1152.htm
I suppose the proper answer would be IEC958 Raw? This would make more
sense
that AC3-something since this would apply to DTS-passthru and other forms of
digital output.
HTH,
-- Peter Heatwole
Murphy was just a well known pessimist.
áË ë^¨¥Ë)¢{(ç[É8bAzEÊzÚ yé!y«m§ÿí)äç¤r¿±ð%±§^½éfj)b
b²Ð%±§^½éeËl²«qç讧zØm¶?þX¬¶Ë(º· ~àzwþX¬¶ÏåËbú?j[uëÞ
RE: [Alsa-devel] AC3 passthru intel8x0 + cs4299
Peter Heatwole wrote: Peter Heatwole wrote: I would recommend looking into setting up a mixer function First off, I apologize for replying to my own reply to myself. But, for those of you that may be following this thread, I would like to revoke that other statement. Apparently things have changed since I last had time to check on the cs46xx driver, which is where I got the idea for a mixer control to enable/disable IEC958 passthru. It seems that a more refined method is currently in use, in which the software requests iec958 passthru (correct?), which definitely seems to be a better choice. -- Peter Heatwole Murphy was just a well known pessimist. --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
RE: [Alsa-devel] Midisport 2x2 spawns before Alsa, taking thedevice0 slot event though modules.conf puts snd-usb-midi as 3rd device -result potential hardlocks when opening dsp
Thank you very much for your assistance! Ico -Original Message- From: Fernando Pablo Lopez-Lezcano [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 25, 2003 8:56 PM To: Ivica Bukvic Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [Alsa-devel] Midisport 2x2 spawns before Alsa, taking thedevice0 slot event though modules.conf puts snd-usb-midi as 3rd device -result potential hardlocks when opening dsp I was just wondering how can I force snd-usb-midi to assume device 2 slot, rather than the default 0 when spawning, since at boot time on my machine USB gets initialized before alsa and therefore if I have Midisport 2x2 hooked up, it ends up being my default /dev/dsp device (which actually does not exist) and that makes apps like pd hardlock my machine if trying to access them. So my question is twofold: 1) Is there anything I can configure about my boot process, where Alsa gets initialized before USB (I am assuming not, since Alsa does not start until someone logs in, please correct me if I am wrong). Alsa is started (in the configurations I've seen) as a service and that happens at boot time if the alsasound service is started (how that is configured depends on the distro - redhat uses the chkconfig program). If sound is only loaded when you are logging in then the alsasound script is not being executed on startup. You could blacklist the usb audio related modules so that they are started latter in the boot process by the alsasound script (just add usb-midi, audio and snd-usb-audio to /etc/hotplug/blacklist). 2) Is there anything I can specify in my modules.conf or elsewhere in order to force the device to be used as snd-card-2 and not snd-card-0 (1 I would like to reserve for hdsp). alias snd-card-1 snd-usb-audio alias sound-slot-1 snd-card-1 and then... options snd-usb-audio index=1 this assumes cards_limit=2 in options snd -- Fernando --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] Midisport 2x2 spawns before Alsa, taking the device0 slot event though modules.conf puts snd-usb-midi as 3rd device - result potential hardlocks when opening dsp
Hi all, I was just wondering how can I force snd-usb-midi to assume device 2 slot, rather than the default 0 when spawning, since at boot time on my machine USB gets initialized before alsa and therefore if I have Midisport 2x2 hooked up, it ends up being my default /dev/dsp device (which actually does not exist) and that makes apps like pd hardlock my machine if trying to access them. So my question is twofold: 1) Is there anything I can configure about my boot process, where Alsa gets initialized before USB (I am assuming not, since Alsa does not start until someone logs in, please correct me if I am wrong). 2) Is there anything I can specify in my modules.conf or elsewhere in order to force the device to be used as snd-card-2 and not snd-card-0 (1 I would like to reserve for hdsp). Obviously the quick and dirty fix is to hook-up the midisport once I've logged in and if the device was already hooked-up simply restart alsa once the midisport was removed (which I am doing), but that seems like a real hacky solution to this issue and does not address the root of the problem. Any help is greatly appreciated! Sincerely, Ivica Ico Bukvic, composer, multimedia sculptor, programmer, webmaster computer consultant http://meowing.ccm.uc.edu/~ico To be or not to be - Shakespeare To be is to do - Socrates To do is to be - Sartre Do be do be do - Sinatra 2b || ! 2b - ? I am - God --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] RE: Midisport 2x2 spawns before Alsa, taking the device0 slot event though modules.conf puts snd-usb-midi as 3rd device - result potential hardlocks when opening dsp
Forgot to include my modules.conf, so here it is: #load hdsp mem before everything else options snd-hammerfall-mem enable=1 options snd-hdsp line_outs_monitor=1 alias net-pf-4 ipx alias autofs autofs4 probeall scsi_hostadapter ide-scsi alias eth0 3c59x #alias sound-slot-0 i810_audio alias ieee1394-controller ohci1394 alias /dev/nvidia* NVdriver # ALSA portion alias char-major-116 snd alias char-major-14 soundcore alias snd-card-0 snd-intel8x0 alias snd-card-1 snd-hdsp alias snd-card-2 snd-usb-midi options snd major=116 cards_limit=4 device_mode=0666 device_gid=0 device_uid=0 options snd-usb-midi vid=0x763 pid=0x1001 index=1 # OSS/Free portion # CS4205 alias sound-slot-0 snd-card-0 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 #HDSP alias sound-slot-1 snd-card-1 alias sound-service-1-0 snd-mixer-oss alias sound-service-1-1 snd-seq-oss alias sound-service-1-3 snd-pcm-oss alias sound-service-1-8 snd-seq-oss alias sound-service-1-12 snd-pcm-oss #MIDISPORT alias sound-service-2-1 snd-seq-oss alias sound-service-2-8 snd-seq-oss probeall usb-interface usb-uhci #thought if I did usb-interface last that it would be superseded by #the alsa, but that did not work --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
[Alsa-devel] RE: [Alsa-user] Midisport 2x2 spawns before Alsa, taking the device0 slot event though modules.conf puts snd-usb-midi as 3rd device - result potential hardlocks when opening dsp
Ivica, Welcome to _MY_ nightmare!!! I've been dealing with this for months!! Actually, your nightmare is a little different, but in my version, just before the Frankenstein monster shows up, my HDSP 9652 won't initialize, the system saying it doesn't have enough memory. Then, just as the monster raises its arms to grab me, I do a warm boot and the monster goes away. Alsa and Jack work wonderfully and the sky is blue... Oh yes, and sometimes my 1394 drives cannot be used either, until after the same warm boot. Mark -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ivica Bukvic Sent: Tuesday, February 25, 2003 3:26 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [Alsa-user] Midisport 2x2 spawns before Alsa, taking the device0 slot event though modules.conf puts snd-usb-midi as 3rd device - result potential hardlocks when opening dsp Hi all, I was just wondering how can I force snd-usb-midi to assume device 2 slot, rather than the default 0 when spawning, since at boot time on my machine USB gets initialized before alsa and therefore if I have Midisport 2x2 hooked up, it ends up being my default /dev/dsp device (which actually does not exist) and that makes apps like pd hardlock my machine if trying to access them. So my question is twofold: 1) Is there anything I can configure about my boot process, where Alsa gets initialized before USB (I am assuming not, since Alsa does not start until someone logs in, please correct me if I am wrong). 2) Is there anything I can specify in my modules.conf or elsewhere in order to force the device to be used as snd-card-2 and not snd-card-0 (1 I would like to reserve for hdsp). Obviously the quick and dirty fix is to hook-up the midisport once I've logged in and if the device was already hooked-up simply restart alsa once the midisport was removed (which I am doing), but that seems like a real hacky solution to this issue and does not address the root of the problem. Any help is greatly appreciated! Sincerely, Ivica Ico Bukvic, composer, multimedia sculptor, programmer, webmaster computer consultant http://meowing.ccm.uc.edu/~ico To be or not to be - Shakespeare To be is to do - Socrates To do is to be - Sartre Do be do be do - Sinatra 2b || ! 2b - ? I am - God --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user --- 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] Midisport 2x2 spawns before Alsa, taking thedevice0 slot event though modules.conf puts snd-usb-midi as 3rd device -result potential hardlocks when opening dsp
I was just wondering how can I force snd-usb-midi to assume device 2 slot, rather than the default 0 when spawning, since at boot time on my machine USB gets initialized before alsa and therefore if I have Midisport 2x2 hooked up, it ends up being my default /dev/dsp device (which actually does not exist) and that makes apps like pd hardlock my machine if trying to access them. So my question is twofold: 1) Is there anything I can configure about my boot process, where Alsa gets initialized before USB (I am assuming not, since Alsa does not start until someone logs in, please correct me if I am wrong). Alsa is started (in the configurations I've seen) as a service and that happens at boot time if the alsasound service is started (how that is configured depends on the distro - redhat uses the chkconfig program). If sound is only loaded when you are logging in then the alsasound script is not being executed on startup. You could blacklist the usb audio related modules so that they are started latter in the boot process by the alsasound script (just add usb-midi, audio and snd-usb-audio to /etc/hotplug/blacklist). 2) Is there anything I can specify in my modules.conf or elsewhere in order to force the device to be used as snd-card-2 and not snd-card-0 (1 I would like to reserve for hdsp). alias snd-card-1 snd-usb-audio alias sound-slot-1 snd-card-1 and then... options snd-usb-audio index=1 this assumes cards_limit=2 in options snd -- Fernando --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
