Re: [Ekiga-list] Ekiga 2.04 and ALSA
Thanks everyone for your help. All my ALSA stuff is upgraded to the
latest versions. I found that to get it to work right with Ekiga, I had
remove the asound.conf file. This doesn't make any sense because I never
had any problems with it before.
I agree with Rene, I just don't get it with ALSA. How did they become
the standard and be such a headache at the same time?
On Wed, 2007-01-31 at 21:13 +0100, Rene Bartsch wrote:
> > Hi,
> > sound on linux continues to be a problem.
> >
> > In some of my darker momements, I have mispronounced "ALSA" as
> > "ulcer".
> >
> > So where is real problem?
> > The alsa plugins in pwlib follow the alsa examples, and "should"
> > be correct. Then a bit of reading finds that between alsa
> > 1.0.10 and 1.0.11 (or was it 1.0.11 and 1.0.12?) that the alsa
> > internals were changed to add an extra dmix operator in the
> > system asound.conf and I just don't get it.
> >
> > Do we decide that the direction of alsa is not right for this project
> > and work on a openal based plugin. Will that be more reliable ?
>
>
> Since Ekiga 2.0.4 ALSA works fine for me.
>
> First, don't use ALSA driver 1.0.11*! (Upgrade your kernel or driver modules)
>
> I'm using the Gentoo versions of "Advanced Linux Sound Architecture
> Driver Version 1.0.12rc1" (Kernel 2.6.18), alsa-lib 1.0.14, alsa-headers
> 1.0.14 and alsa-utils 1.0.14, opal 2.2.4, pwlib 1.10.3 and Ekiga 2.0.4.
>
> With the following asound.conf I'm using just the "Default" devices for
> audio in Ekiga 2.0.4 (just rename your audio card):
>
> --- snip ---
>
>
> pcm.!default {
> type plug
> slave.pcm {
> type asym
> playback.pcm {
> typedmix
> ipc_key 1024
> ipc_perm0666
> slave.pcm {
> typehw
> card"Audio"
> }
> }
> capture.pcm {
> typedsnoop
> ipc_key 1025
> ipc_perm0666
> slave.pcm {
> typehw
> card"U0x46d0x8cb"
> }
> }
> }
> }
>
> ctl.!default {
> typehw
> card"Audio"
> }
>
>
> --- snap --
>
> Renne
>
>
> ___
> ekiga-list mailing list
> ekiga-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/ekiga-list
Fedora Core 6 Linux
Ekiga Rocks!! One program so many ways to connect!
sip: [EMAIL PROTECTED] (or [EMAIL PROTECTED])
H323: gk.voxgratia.net:1719 geboyd53
Voipbuster: geboyd53 (chat), 13606660349 (telephone)
e164: +13606660349 or +882 398265 (linked to ekiga)
Forward: 781549
Voxalot: 106153
Gizmo: 17476918163
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga 2.04 and ALSA
> Hi,
> sound on linux continues to be a problem.
>
> In some of my darker momements, I have mispronounced "ALSA" as
> "ulcer".
>
> So where is real problem?
> The alsa plugins in pwlib follow the alsa examples, and "should"
> be correct. Then a bit of reading finds that between alsa
> 1.0.10 and 1.0.11 (or was it 1.0.11 and 1.0.12?) that the alsa
> internals were changed to add an extra dmix operator in the
> system asound.conf and I just don't get it.
>
> Do we decide that the direction of alsa is not right for this project
> and work on a openal based plugin. Will that be more reliable ?
Since Ekiga 2.0.4 ALSA works fine for me.
First, don't use ALSA driver 1.0.11*! (Upgrade your kernel or driver modules)
I'm using the Gentoo versions of "Advanced Linux Sound Architecture
Driver Version 1.0.12rc1" (Kernel 2.6.18), alsa-lib 1.0.14, alsa-headers
1.0.14 and alsa-utils 1.0.14, opal 2.2.4, pwlib 1.10.3 and Ekiga 2.0.4.
With the following asound.conf I'm using just the "Default" devices for
audio in Ekiga 2.0.4 (just rename your audio card):
--- snip ---
pcm.!default {
type plug
slave.pcm {
type asym
playback.pcm {
typedmix
ipc_key 1024
ipc_perm0666
slave.pcm {
typehw
card"Audio"
}
}
capture.pcm {
typedsnoop
ipc_key 1025
ipc_perm0666
slave.pcm {
typehw
card"U0x46d0x8cb"
}
}
}
}
ctl.!default {
typehw
card"Audio"
}
--- snap --
Renne
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga 2.04 and ALSA
Hi, sound on linux continues to be a problem. In some of my darker momements, I have mispronounced "ALSA" as "ulcer". So where is real problem? The alsa plugins in pwlib follow the alsa examples, and "should" be correct. Then a bit of reading finds that between alsa 1.0.10 and 1.0.11 (or was it 1.0.11 and 1.0.12?) that the alsa internals were changed to add an extra dmix operator in the system asound.conf and I just don't get it. Do we decide that the direction of alsa is not right for this project and work on a openal based plugin. Will that be more reliable ? = On Wed, 31 Jan 2007, Rene Bartsch wrote: > Maybe you have to edit you asound.conf ... An activity which is technically challenging, and not for the faint hearted. Further, upgrades to your box will have an unknown outcome. Derek. -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: [EMAIL PROTECTED] ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga 2.04 and ALSA
> Since I have upgraded to Ekiga 2.04, I can no longer use the default > device for input or output. I have to use my sound card directly. I was > wondering if anyone else was experiencing this problem? > I had that problem with Ekiga-2.0.3. With 2.0.4 it's gone :-) Maybe you have to edit you asound.conf ... Renne ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Ekiga 2.04 and ALSA
Since I have upgraded to Ekiga 2.04, I can no longer use the default device for input or output. I have to use my sound card directly. I was wondering if anyone else was experiencing this problem? Tnx, George Fedora Core 6 Linux Ekiga Rocks!! One program so many ways to connect! sip: [EMAIL PROTECTED] (or [EMAIL PROTECTED]) H323: gk.voxgratia.net:1719 geboyd53 Voipbuster: geboyd53 (chat), 13606660349 (telephone) e164: +13606660349 or +882 398265 (linked to ekiga) Forward: 781549 Voxalot: 106153 Gizmo: 17476918163 ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
