> 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 chip) works great.
YES, this helps me when i set "ALC861 Analog" sound is ok > Some tools to help debugging if you need it: > > Run on the command line. Warnings & errors are enabled by default, you > should see some sound card related messages. > > strace will show you all system calls made by the application. > > Change the debug level: set the environment variable OWLOGGER_DEFAULT to > "debug" to get lots more messages when running from the command line. > > You can debug just the audio component by unsetting OWLOGGER_DEFAULT and > just setting OWLOGGER_SOUND to "debug" should debug sound more heavily > than the other components. (by the way - anyone know how to get a list > of valid components for the OWLOGGER_* env. variables?) GREAT! added to the wiki http://trac.qutecom.org/wiki/FAQ >> 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. what is pa_alsa? i have alsa-plugins-pulseaudio This plugin allows any program that uses the ALSA API to access a PulseAudio sound daemon. In other words, native ALSA applications can play and record sound across a network. There are two plugins in the suite, one for PCM and one for mixer control. this is not what i am want imho. i want direct pulseaudio access (because of simultaneous access by qutecom,vlc,psi etc.) --------------------------------------- Marek Cervenka ======================================= _______________________________________________ QuteCom-dev mailing list [email protected] http://lists.qutecom.org/mailman/listinfo/qutecom-dev
