On Sun, Feb 14, 2010 at 12:11:27PM +0000, Peter Hamilton wrote: > > > The Solution: > > This was with both fldigi instances having "manage mixer" ticked. The > above problem goes away completely if neither fldigi instance touches > the mixer. The problem is linked to fldigi's state on startup: If > "manage mixer" is enabled in the preferences file the CPU load hits the > roof *and stays there* for the session even if "manage mixer" is then > disabled. If it's disabled on startup, fldigi behaves itself for that > session even if "manage mixer" is enabled during the session. This is > 100% repeatable. > > So the fix is to disable mixer control: since doing that I have had no > problems whatsoever. > > > My workaround, which I actually prefer to fiddling with a continuous > mixer control, is to create a few macros to select different power > levels. They look like: > > <EXEC>alsactl -f ~/fldigi/icom706-10W.alsa restore</EXEC> > > Where the files *.alsa are generated by adjusting the mixer values with > alsamixer for the right levels and then saving with > > alsactl -f <filename> store > > (Is it worth adding similar functionality within fldigi? A row of macro > buttons which instantly select previously calibrated power levels is > quite useful.) > > _______________________________________________
I can duplicate the same problem here on Jaunty. Disable the mixer management, end and restart fldigi and down to about 5-15% -- Larry Levesque KA1VGM _______________________________________________ fldigi-alpha mailing list [email protected] https://lists.berlios.de/mailman/listinfo/fldigi-alpha
