On Thu, Jan 8, 2009 at 7:37 AM, marek cervenka wrote:
> ok. what is the schema(output)?
> qutecom - pulseaudio - alsa - soundcard
I guess: qutecom - alsa - pulsaudio - alsa -soundcard :)
> or some magic with pa_alsa plugin?
that pa stands for portaudio. AFAIK, qutecom is not able to speak
nativ
> On Wed, Jan 7, 2009 at 3:58 AM, marek cervenka wrote:
does qutecom support portaudio on linux?
>>>
>>> Yes, through pa_alsa. In fact, for applications, the use of portaudio is
>>> supposed to be transparent, as I understand it.
>
> I guess you meant pulseaudio and not portaudio...
oops, y
On Wed, Jan 7, 2009 at 3:58 AM, marek cervenka wrote:
>>> does qutecom support portaudio on linux?
>>
>> Yes, through pa_alsa. In fact, for applications, the use of portaudio is
>> supposed to be transparent, as I understand it.
I guess you meant pulseaudio and not portaudio...
portaudio is porta
> Hi Marek,
>
> marek cervenka wrote:
>> i have problem with qutecom 2.2 rc3 on fedora10
>> i have no sound
>>
>> can you point me how can i debug this?
>
> Check in your sound preferences. I don't know why, but on my laptop
> "ALSA default" doesn't work, whereas "STAC ..." (the explicit name of
>
Hi Marek,
marek cervenka wrote:
> i have problem with qutecom 2.2 rc3 on fedora10
> i have no sound
>
> can you point me how can i debug this?
Check in your sound preferences. I don't know why, but on my laptop
"ALSA default" doesn't work, whereas "STAC ..." (the explicit name of
the sound card
