i have some troubles with an usb-audio device (an imic) on linux ppc
(an ibook2), i think becouse of endianness related troubles..
my big trouble is that jack says:
[EMAIL PROTECTED]:~$ jackd -d alsa -d hw:1
jackd 0.80.0
[...]
JACK compiled with System V SHM support
loading driver ..
creating al
Hi All
I've been trying to configure an asound file for my Delta66 and Intel8x0
(SIS645DX chipset... yes it works with all functionality including MIDI)
cards.
I have built the file at the bottom based on examples. I would like to
convert it so that both cards are seen as one (purely for ease of
At Mon, 3 Feb 2003 14:40:26 +0100 (CET),
Oliver Schrempf wrote:
>
> > it's the expected behavior, because the hardware doesn't support this
> > format. it suppors only S32_LE.
>
> OK, I understand this, but when I use
> % arecord -Dhw:0,0 -fS32_LE -r48000 foo.wav
> I get
> arecord: set_params:79
On Tue, 4 Feb 2003, Takashi Iwai wrote:
>
> well, this might be because you specfied 8 channels instead of 10.
> the hardware supports only 10 channels natively.
>
> could you check whether 20 (10+10) channels work?
One interesting thing is, that it works with -Ddefault
There I can specify as man
> it's the expected behavior, because the hardware doesn't support this
> format. it suppors only S32_LE.
OK, I understand this, but when I use
% arecord -Dhw:0,0 -fS32_LE -r48000 foo.wav
I get
arecord: set_params:792: Channels count non available
Is this expected, too?
> but it seems that this
At Mon, 3 Feb 2003 12:06:22 +0100 (CET),
Oliver Schrempf wrote:
>
> > > /home/oliver>arecord -Dplug:multi -c 16 test.wav
> > > Recording WAVE 'test.wav' : Unsigned 8 bit, Rate 8000 Hz, Channels 16
> > > arecord: set_params:765: Broken configuration for this PCM: no
> > > configurations available
>
> > /home/oliver>arecord -Dplug:multi -c 16 test.wav
> > Recording WAVE 'test.wav' : Unsigned 8 bit, Rate 8000 Hz, Channels 16
> > arecord: set_params:765: Broken configuration for this PCM: no
> > configurations available
>
> hmm.. does it work when you specify the format and rate?
>
> % ar
At Thu, 30 Jan 2003 12:06:17 +0100 (CET),
Oliver Schrempf wrote:
>
> On Thu, 30 Jan 2003, Takashi Iwai wrote:
>
> > At Thu, 30 Jan 2003 09:34:13 +0100 (CET),
> > Oliver Schrempf wrote:
> > >
> > > Since my last mail where I sent my current settings I still have the
> > > problem, that I recieve t
On Thu, 30 Jan 2003, Takashi Iwai wrote:
> At Thu, 30 Jan 2003 09:34:13 +0100 (CET),
> Oliver Schrempf wrote:
> >
> > Since my last mail where I sent my current settings I still have the
> > problem, that I recieve the following error message
> >
> > arecord: main:462: audio open error: No such fi
At Thu, 30 Jan 2003 09:34:13 +0100 (CET),
Oliver Schrempf wrote:
>
> Since my last mail where I sent my current settings I still have the
> problem, that I recieve the following error message
>
> arecord: main:462: audio open error: No such file or directory
what shows if you run "aplay -L" and
Since my last mail where I sent my current settings I still have the
problem, that I recieve the following error message
arecord: main:462: audio open error: No such file or directory
when trying
arecord -Dplug:multi -c 16 -t wav test.wav
Oli
--
On Tue, 28 Jan 2003, Takashi Iwai wrote:
> > Umpf, sorry. I just realized, that I had a mistake in asoundrc from
> > playing around with plug:multi.
> >
> > The error I get now from
> > arecord -Dmplug -c16 test.wav
> > as well as from
> > arecord -Dplug:multi -c16 test.wav
> >
> > is
> >
> > arec
At Mon, 27 Jan 2003 19:14:07 +0100 (CET),
Oliver Schrempf wrote:
>
> > hmm, there is still a bug in the alsa-lib configuration parser..?
> >
> >
> > anyway, add the following and try -Dmplug instead as a workaround.
> >
> >
> > pcm.mplug {
> > type plug
> > slave.pcm "multi"
> > }
> >
>
>
> hmm, there is still a bug in the alsa-lib configuration parser..?
>
>
> anyway, add the following and try -Dmplug instead as a workaround.
>
>
> pcm.mplug {
> type plug
> slave.pcm "multi"
> }
>
Umpf, sorry. I just realized, that I had a mistake in asoundrc from
playing around with p
At Mon, 27 Jan 2003 18:03:21 +0100 (CET),
Oliver Schrempf wrote:
>
>
> > > > > Broken configuration: no configurations available: Invalid argument
> > > >
> > > > doesn't it work with the pcm "plug:multi" ?
> > >
> > > Sorry, but I can't find any documentation on "plug:multi"?
> > > How do I have
> > > > Broken configuration: no configurations available: Invalid argument
> > >
> > > doesn't it work with the pcm "plug:multi" ?
> >
> > Sorry, but I can't find any documentation on "plug:multi"?
> > How do I have to to use it?
>
> aplay -Dplug:multi
>
> It's device description/name for alsa-li
On Mon, 27 Jan 2003, Oliver Schrempf wrote:
> On Mon, 27 Jan 2003, Takashi Iwai wrote:
>
>
> > > Broken configuration: no configurations available: Invalid argument
> >
> > doesn't it work with the pcm "plug:multi" ?
>
> Sorry, but I can't find any documentation on "plug:multi"?
> How do I have
On Mon, 27 Jan 2003, Takashi Iwai wrote:
> > Broken configuration: no configurations available: Invalid argument
>
> doesn't it work with the pcm "plug:multi" ?
Sorry, but I can't find any documentation on "plug:multi"?
How do I have to to use it?
Oli
At Mon, 27 Jan 2003 14:09:03 +0100 (CET),
Oliver Schrempf wrote:
>
> Hi All,
> I get this errormessage for the multi configuration below:
>
> Broken configuration: no configurations available: Invalid argument
doesn't it work with the pcm "plug:multi" ?
Takashi
--
Hi All,
I get this errormessage for the multi configuration below:
Broken configuration: no configurations available: Invalid argument
pcm.multi {
type multi;
slaves.a.pcm "hw:0,0,0";
slaves.a.channels 8;
slaves.b.pcm "hw:1,0,0";
slaves.b.channels 8;
Paul Davis wrote:
>>>What is the purpose of the ctl.rme9652 declaration? My plugin devices
>>>seem to work without it.
>>>
>>
>>It is a configuration for the onboard mixer. Very little is known about
>>why we use it. Some programs (JACK) won't work without it.
>
>
> not really.
>
> the control
>> What is the purpose of the ctl.rme9652 declaration? My plugin devices
>> seem to work without it.
>>
>
>It is a configuration for the onboard mixer. Very little is known about
>why we use it. Some programs (JACK) won't work without it.
not really.
the control device for a card is the way th
Patrick Shirkey wrote:
>
> Kris Modrak wrote:
> > The start of my .asoundrc file is as follows:
> >
> > pcm.rme9652 {
> > type hw
> > card 0
> > device 0
> > }
> >
> > ctl.rme9652 {
> > type hw
> > card 0
> > }
> >
> > What is the purpose of the ctl.rme9652 declaration? My plugin devices
> > seem
Kris Modrak wrote:
> The start of my .asoundrc file is as follows:
>
> pcm.rme9652 {
> type hw
> card 0
> device 0
> }
>
> ctl.rme9652 {
> type hw
> card 0
> }
>
> What is the purpose of the ctl.rme9652 declaration? My plugin devices
> seem to work without it.
>
It is a configuration for the
The start of my .asoundrc file is as follows:
pcm.rme9652 {
type hw
card 0
device 0
}
ctl.rme9652 {
type hw
card 0
}
What is the purpose of the ctl.rme9652 declaration? My plugin devices
seem to work without it.
Regards
Kris Modrak
---
This
hi,
cause i didnt found any sufficent documentation again i started to wrote a
kind of asoundrc-minihowto. my plan is to put it on the alsa-wiki-page,
but i dont know where the (un)offical alsa-wiki-page is, its not linked
on alsa-project.org. otherwise i will put it 'statically' somwhere on the
>Another currently available option is to use the pcm_shm plugin which
>outputs audio to a separate aserver process (see alsa-lib/aserver). This
>plugin does work, but like pcm_share, hasn't been widely used yet. But
>it's the only working ALSA alternative for concurrent pcm access at the
>moment.
On Thu, 28 Feb 2002, Kai Vehmanen wrote:
> On Thu, 28 Feb 2002, Patrick Shirkey wrote:
>
> > I attempted to get the share device working a little while ago but had
> > no luck. I can try again though. Actually, at the time Abramo said that
> > it was possible but that it had not been coded compl
On Thu, 28 Feb 2002, Patrick Shirkey wrote:
> I attempted to get the share device working a little while ago but had
> no luck. I can try again though. Actually, at the time Abramo said that
> it was possible but that it had not been coded completely yet due to
> funding constraints. Is that righ
--- "Ivica Bukvic" <[EMAIL PROTECTED]> wrote:
>
>Is there anyone else with some kind of experience in this field? Maybe
>it is time to start documenting this potentially awesome feature... I
>could easily provide webspace and/or maintain the docs webpage if
>needed, as long as I can get a pool of
agreed i have not been able to find documentation about how to construct
this file.
On Wed, 2002-01-16 at 09:13, Bob Ham wrote:
> Hi there
>
> It's been a while since I installed alsa and it appears I now have to
> make a configuration file in ~/.asoundrc (at least if I want ardour to
> stop
Hi there
It's been a while since I installed alsa and it appears I now have to
make a configuration file in ~/.asoundrc (at least if I want ardour to
stop moaning at me.) Unfortunately, I've not been able to find any docs
on what needs to go in it apart from format descriptions. I've searched
t
On Wed, 19 Dec 2001, Alexander Ehlert wrote:
>Hi,
>
>is there any documentation yet for the format of an asoundrc file?
alsa-lib-0.9.0beta10a.tar.bz2:
alsa-lib-0.9.0beta10a/doc/asoundrc.txt
Hopefully even reasonably up-to-date...
--
Erik I. Bolsø | email:
The UNIX philosophy basically involve
Hi,
is there any documentation yet for the format of an asoundrc file?
Cheers, Alex
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
34 matches
Mail list logo
