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 thing
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
> 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 actuall
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 mon
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 ieee139
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
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
regi
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
>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 a
>> 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
> 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
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 J
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 com
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 work
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;
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 r
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 s
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
> -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-ut
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 & fon
Hi,
At Mon, 24 Feb 2003 13:59:53 +0100 (CET),
Ronny V. Vindenes <[EMAIL PROTECTED]> wrote:
>
> Cleanup the alsa-lib rpm spec:
> * Use standard rpm macros for build & install
> * Split package into alsa-lib and alsa-lib-devel (this is standard and
> makes offical packages play nice with 3rd par
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
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
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
24 matches
Mail list logo
