On Wed, 16 Sep 2009 13:51:41 +0100 Stelios Bounanos <m0gld at enotty.net> wrote:
> >>>>> On Wed, 16 Sep 2009 07:06:37 -0400, Ed <autek2 at gmail.com> said: > > > I notice when using the drop down that the waterfall and the qso > > frequency window do not always update. I have to select the new band > > change twice. Might be a reaction to the speed of the double click. > > This does not happen with hamlib. > > > I'm no longer getting the hex-out error. I corrected it before by > > raising the write delay. But now the setting is even lower than the > > original. > > If you go back to the settings for 3.13AF and see the same problems > with 3.13AG, then you will have found a regression that should be > fixed before release. This sort of thing tends to drive users > away :-O I'm now testing AH. I find the timing to be very critical and one setting interacts with the other. Retries have not changed. The interval and write delay are really touchy. If you don't get them right, then the drop down does't respond. The qso frequency box,waterfall, and rig stay at the previous setting. My final settings are no where close to the original. This will really drive new users away.... > > I'm getting no other errors. The sound server and so forth have all > > cleared themselves. Still not sure what was the real cause from > > yesterday. > > There have been complaints about PortAudio which leads me to suspect > problems with the move to PulseAudio and related patch for PortAudio > to work better with the former. The patch is for PortAudio's ALSA > backend, but there may also be issues with the OSS emulation. I normally use port audio as I need pulse to be able to select the correct audio out stream when using headphones with Firefox. If upstream ever fixes the bug in Firefox this wouldn't be a problem. Ed W3NR
