RE: [Alsa-devel] more RME 9652 Hammerfall problems

2002-02-02 Thread Ivica Bukvic
Ico > -Original Message- > From: Jeremy Hall [mailto:[EMAIL PROTECTED]] > Sent: Saturday, February 02, 2002 7:46 PM > To: Ivica Bukvic > Cc: 'Jeremy Hall' > Subject: Re: [Alsa-devel] more RME 9652 Hammerfall problems > > the 14:0 means it is upset with line 1

Re: [Alsa-devel] more RME 9652 Hammerfall problems

2002-02-02 Thread Jeremy Hall
no, this is an alsa thing. I don't use the plughw construct, mainly because I don't grock it and it is not explained in the plentiful documentation and is difficult to understand the config files which also are not in the plentiful documentation from what I can tell. I understand the error but d

RE: [Alsa-devel] more RME 9652 Hammerfall problems

2002-02-02 Thread Ivica Bukvic
An update: I tried changing to what Paul recommended and here's what I got: My .asoundrc: pcm.rme9652 { type hw card 1 } ctl.rme9652 { type hw card 1 } pcm.dsp1 { type plughw card 1 } The error is now gone (the " _toplevel_:15:0:Unexpected char ALSA lib conf.c:2452:" one), but here's the output

Re: [Alsa-devel] more RME 9652 Hammerfall problems

2002-02-02 Thread Abramo Bagnara
Paul Davis wrote: > > >You want the ctl entry so that ardour will work properly. When you use > >aplay or any other application, use dsp1 as your alsa device, and when you > >use ardour, use rme9652, because ardour wants the raw access. > > 3 quick notes: > > 1) i prefer: > >pcm.dsp1 { >

Re: [Alsa-devel] more RME 9652 Hammerfall problems

2002-02-02 Thread Paul Davis
>Also, could someone please be so kind to send me their asoundrc file >that they are using for the hammerfall, so that I can learn from it as >to how to configure it since the one that comes with alsa-driver package >is rather esotheric for my understanding? Thank you very much! this is mine. pc

Re: [Alsa-devel] more RME 9652 Hammerfall problems

2002-02-02 Thread Paul Davis
>You want the ctl entry so that ardour will work properly. When you use >aplay or any other application, use dsp1 as your alsa device, and when you >use ardour, use rme9652, because ardour wants the raw access. 3 quick notes: 1) i prefer: pcm.dsp1 { type plughw card 1 } as

Re: [Alsa-devel] more RME 9652 Hammerfall problems

2002-02-02 Thread Jeremy Hall
WHat is line 15 of your .asoundrc? _J ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel

RE: [Alsa-devel] more RME 9652 Hammerfall problems

2002-02-02 Thread Ivica Bukvic
version of an .asoundrc file from someone who uses RME soundcard. Thank you! Sincerely, Ico > -Original Message- > From: Jeremy Hall [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 01, 2002 10:45 PM > To: Ivica Bukvic > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subjec

Re: [Alsa-devel] more RME 9652 Hammerfall problems

2002-02-01 Thread Jeremy Hall
When you use the hw:1 syntax, you are expecting alsa to try to talk to the card directly. Try this in your .asoundrc. pcm.rme9652 { type hw card 1 device 0 } ctl.rme9652 { type hw card 1 } pcm.dsp1 { type plug slave.pcm.rme9652 } then aplay -Ddsp1 filew.wav Alsa will perform the needed convers