I like all discussions about Qtel to be on the mailing list
(svxlink-devel@...). That way other people can learn about
solutions to problems. I sent this answer to the mailing list. I hope you
On Thursday 11 September 2003 02.31, Aleksandar Ilic wrote:
> I was glad to find your Qtel as new, modern EchoLink client, since EchoGUI
> is just a demonstration program for interfacing with echolinux.
Nice to hear from you and that you have tried to get Qtel running under
Slackware. I have actually never seen EchoGUI but what I heard, as you said,
was that it was a demo GUI. I have never seen the original windows EchoLink
application running either (only screen shots) so if you find some stange
behaviour, that's why :-) I thought that I maybe could find other (better?)
solutions to the design if I was not coloured by the original application.
> As traditional Slackware user, I downloaded source tarball of Qtel and
> libsigc library. With new version, 1.2.5, Qtel couldn't compile, but I
> manage to do it with libsigc-1.0.4.
Yes, it will not compile with newer versions of SigC. That should be on the
home page, but as you probably have seen I have not had time to finish it.
> Program compiled, without errors, and it is (allmost) works. I can connect
> to echolink server, have a list of stations, connect to other stations,
> write and read notices to them, even talk to them - but I can heard them at
> all. The receiving indicator is showing incoming voice, but audio from
> soundcard is dead.
Well, nice to hear that it is mostly working. Not so fun that you have no
audio though. There have been some trouble with sound cards that only support
stereo operation. My thoughts:
* Since the reception indicator is lighting up, you get audio packets into
* Does audio work for other things ?
* Do you have both master volume and pcm volume turned up and not muted ?
* Maybe there is some trouble with full duplex operation on your sound card.
Full duplex is not needed but the application checks if the sound card is
capable of full duplex and if so open the device in full duplex. Have a look
in ComDialog.cpp in the constructor (ComDialog::ComDialog). The test is done
there (audio_io->isFullDuplexCapable()). Add a printout to see if full duplex
operation is tried. If so, force it to use half duplex operation by for
example changing "if (audio_io->isFullDuplexCapable())" into "if (0)".
* Is it possible for you to try it out on another computer ?
* Is it possible for you to try it with another sound card ?
Tobias / SM0SVX