>I guess this means that I will have to start reading JACK documentation
>in earnest. I trust that there is such a thing.. ;)
there is reference documentation generated by docbook using jack.h.
there is also a directory full of working example clients that you can
copy and modify to do whatever y
At Mon, 2 Jun 2003 14:18:26 -0600,
Ross Miller wrote:
>
> Also, the following lines are printed in the syslog:
> May 24 23:28:17 snoopy kernel: usb-uhci.c: interrupt, status 2, frame# 985
> May 24 23:28:18 snoopy kernel: usb_control/bulk_msg: timeout
> May 24 23:28:18 snoopy kernel: ALSA ../alsa-k
On Wed, 4 Jun 2003, Giuliano Pochini wrote:
>
> In v0.9.4 Rules.make changed. I used to put the files of my driver
> in the alsa-driver-xxx/pci directory, but they don't compile anymore:
>
> bash-2.05$ make
> Coping file alsa-kernel/core/pci/echoaudio.c
> cp: cannot stat `/home/pochini/soft/alsa
In v0.9.4 Rules.make changed. I used to put the files of my driver
in the alsa-driver-xxx/pci directory, but they don't compile anymore:
bash-2.05$ make
Coping file alsa-kernel/core/pci/echoaudio.c
cp: cannot stat `/home/pochini/soft/alsa-driver-0.9.4/alsa-kernel/pci/echoaudio.c': No
such file o
[EMAIL PROTECTED] wrote:
> Is there some way I can load snd-virmidi into the kernel multiple times?
Yes. This would be something like this in the modules.conf:
options snd cards_limit=3
alias snd-card-0 snd-whatever
alias snd-slot-0 snd-card-0
options snd-whatever
[EMAIL PROTECTED] wrote:
Jack is so great, many developers on this list have named their children
after it. Do the right thing.
LOL! That's a good one! David, meet Jack. David, Jack. David, Jack. ...
"Is your name not Jack?" .. "no" ..."that's going to cause a little
confusion, mind if we call
Is there some way I can load snd-virmidi into the kernel multiple times?
This would help me get around a deficiency in Pd. Pd uses OSS to open the
MIDI devices, and only opens each one once. So it only talks to port 1 on
my mtpav, for example. It treats a virmidi device the same way. But I
figure
> and no, you don't need to modify anything about your stock RH system to
> use JACK. the modifications are only needed if you want low
> latency, and such modifications would be needed to get this with just
> ALSA anyway. a jack client will run just as well as a native ALSA
> (better in some sens
David,
I don't know that much about the internals of JACK but I do know this -
all serious Linux sound apps either use or are preparing to use JACK.
I've gotten to the point where I look for that in an application. If
it's not JACK enabled I just move on to something else.
Jan
On Tue,
>Ah, I think you misunderstand me a little bit.. it's not that I am
>trying to do anything different than usual, it's that I'm having trouble
>with the basics. Specifically, the HOW-TOs that I have found all seem to
>have a different way of writing and reading to/from the hardware buffer.
thats be
On Tue, 2003-06-03 at 16:30, Florian Schmidt wrote:
> hi.. maybe i can add something.. here's a snippet from my .asoundrc
>
> pcm.!default {
> type hw
> card 0
> }
>
> ctl.!default {
> type hw
> card 0
> }
>
>
> this creates a "default" pcm device which can poi
On 03 Jun 2003 12:06:18 -0700
Mark Knecht <[EMAIL PROTECTED]> wrote:
> Jaroslav,
>This did not work for me. I made the edits to the .asoundrc file,
> tried aplay with and without the -D, then tried restarting alsa and
> tried aplay again. It didn't work.
hi.. maybe i can add something.. here
Takashi Iwai wrote:
At Mon, 02 Jun 2003 17:01:42 +0100,
James Courtier-Dutton wrote:
Is the SPDIF output of the SIS7012 (i810 with ac97) supported in alsa.
If so, how does one enable the SPDIF out.
The current kernel OSS module supports it.
which OSS (kernel) version supports spdif out on this c
On Tue, 2003-06-03 at 11:58, Jaroslav Kysela wrote:
> >
> > Will this make device 1 default for all applications that require sound but
> > do not ask for anything specific in terms of interfaces?
>
> The applications should use 'default' device name in that case. You can
> override it, of cour
On Tue, 2003-06-03 at 11:36, Mark Knecht wrote:
> >
> > Add 'device 1' to {} section.
> >
> > Jaroslav
>
> Thanks Jaroslav!
>
> Will this make device 1 default for all applications that require sound but
> do not ask for anything specific in terms of i
On Tue, 3 Jun 2003, Mark Knecht wrote:
> > > .asoundrc from Alsa site:
> > >
> > > pcm.via82xx {
> > >type hw
> > >card 0
> > > }
> > >
> > > ctl.via82xx {
> > >type hw
> > >card 0
> > > }
> > >
> > > Maybe I need to i
> > .asoundrc from Alsa site:
> >
> > pcm.via82xx {
> >type hw
> >card 0
> > }
> >
> > ctl.via82xx {
> >type hw
> >card 0
> > }
> >
> > Maybe I need to include the ',1' interface somehow? How would I do that?
>
> Add 'd
> .asoundrc from Alsa site:
>
> pcm.via82xx {
>type hw
>card 0
> }
>
> ctl.via82xx {
>type hw
>card 0
> }
>
> Maybe I need to include the ',1' interface somehow? How would I do that?
>
> Thanks,
> Mark
Would this be co
On Tue, 3 Jun 2003, Mark Knecht wrote:
> Hi,
>Yesterday evening I found that I could use aplay -D hw:0,1 and get sound
> out of Alsa. This was cool, but I don't normally do anything with aplay.
> Other apps that use sound are still locking up hard.
>
>I thought the .asoundrc file was supp
On Tue, 2003-06-03 at 09:18, Paul Davis wrote:
> its also very unclear what you want help with. there is nothing
> particularly different about capture and playback on 2 devices
> compared to doing it on just 1.
Ah, I think you misunderstand me a little bit.. it's not that I am
trying to do anyth
This patch fixes the kernel side of snd_pcm_pause() to actually pause
instead of always returning -EBADFD. The patch is against
alsa-driver-0.9.4, same as CVS HEAD for this file.
--- acore/pcm_native.c~ Tue Jun 3 13:48:09 2003
+++ acore/pcm_native.c Tue Jun 3 19:27:06 2003
@@ -863,7 +863,7 @@
>
> Xilinx Corporation RME Hammerfall DSP (rev 0b)
> 0b hexadecimal == 11 decimal
> so, you have revision 11 firmware...
>
> This looks like the problem I'm having that didn't go away by
> downgrading the firmware. Then again, I'm using the cardbus interface.
> Anyway, rev 10 firmware gets loade
Hi,
Yesterday evening I found that I could use aplay -D hw:0,1 and get sound
out of Alsa. This was cool, but I don't normally do anything with aplay.
Other apps that use sound are still locking up hard.
I thought the .asoundrc file was supposed to make this happen
automatically, but apparent
At Tue, 03 Jun 2003 11:54:58 -0400,
David van Hoose wrote:
>
> Takashi Iwai wrote:
> >>I never muted any of them. Also 0.9.2 works. Using it now in fact. My
> >>motherboard does not exchange jacks.
> >
> >
> > please try the cvs version. perhaps the pcm playback is muted but no
> > control was
Takashi Iwai wrote:
I never muted any of them. Also 0.9.2 works. Using it now in fact. My
motherboard does not exchange jacks.
please try the cvs version. perhaps the pcm playback is muted but no
control was available for c-media chips (it was removed mistakenly).
right now i added it back.
Thi
On Tuesday 03 June 2003 01:03, Clemmens Ladisch wrote:
> > CHANNELS: 1
> > ...
>
> Are you sure that the Optoplay supports _one_-channel output?
>
That's a good question - I'll try a stereo WAV later this evening after I get
off work.
> Please post the contents of /proc/asound/cardX/stream0 and t
At Fri, 30 May 2003 18:17:03 -0200,
Tal Eisenberg wrote:
>
> Hi, I own a Waveterminal 192M soundcard and recently moved to linux. I did
> this partly because the sound apps and programming that I found for it seemed
> really exciting and partly for the obvious microsoft-rules-the-world stuff.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of David Stuart
> Sent: Tuesday, June 03, 2003 6:53 AM
> To: David E. Storey
> Cc: alsa
> Subject: Re: [Alsa-devel] Quick question
>
>
> Ah! I do exist! :)
>
>
> 1) It's relatively easy to install (from rpm
28 matches
Mail list logo
