On 29/01/2014 23:52, Chuck Forsberg WA7KGX wrote:
Hi Chuck,
I now have r3669 running on Fedora 20, the released version.
As with Rawhide, I had to load a 32 bit libgfortran so the 32 bit
kvasd would run.
Glad you are getting the required dependencies sorted out. Clearly a
x86_64 build of kvasd for Linux would be beneficial at some point for
64-bit packages of wsjtx.
I have tried two versions of Ubuntu and wsjtx could not select
the ASUS Xonar DX sound card I use for wsjt/wspr et al.
So in this case Fedora beats Ubuntu.
I am no expert in Linux/Pulseadio audio configuration but I doubt this
is an unsolvable problem on Ubuntu. Have you checked 'dmesg' for any
pertinent error messages about the sound subsystems?
Some users have reported recently that upgrading Ubuntu has allowed some
soundcards to be used that weren't visible before. Have you tried 13.10?
If not, give the liveCD a try and see if the pavucontrol application can
see all the input and output devices on your system.
It would be nice if the configuration for audio would list something
more understandable than "alsa_input.pci.0000_00_1b.0.analog stereo"
which (I think) refers to the motherboard sound chip which is not
on a PCI card at all.
PCI and PCIe are bus technologies which are implemented within the
motherboard chipset as well as the physical card slots. The onboard
sound chip is almost certainly a PCIe device connected directly to the
chipset (SouthBridge if it is Intel).
The name of the device is presented to us by the Qt audio device
enumeration class which in turn uses Pulseaudio to hide the Unix
implementation details, we don't choose it or parse it, we just list the
names we are given in the hope that you the user can match them to
physical connections. Any attempt to parse the name and convert it to
names like "Motherboard" or "Manufacturer name card in slot X" would be
a major project with many platform dependent implementation details.
Since we use Qt to hide all these platform dependencies allowing us to
focus our programming efforts to the communications and GUI core
application it would be counter productive to start reverse engineering
the internals.
73
Bill
G4WJS.
On 01/29/2014 01:11 PM, Joe Taylor wrote:
On 1/29/2014 2:44 PM, Chuck Forsberg WA7KGX wrote:
If the 64 bit kvasd Joe compiled at omen.com is present, there are
no decodes after the first minute's batch.
CPU utilization goes to 100 per cent and stays there. Kvasd continues
at 100 per cent CPU utilization even if wsjtx is terminated. Rather
than
improving sensitivity by 2 db it makes wsjtx deaf.
The downloadable kvasd is a 32 bit version. Hardly anyone runs 32 bit
Linux anymore.
I finally got the 32 bit KVASD running. I had to poke, prod and cajole
Rawhide (very unstable cutting edge developmental Linux) to install
the required 32 bit libs.
Thanks for putting in such heroic efforts to make the pre-compiled
32-bit kvasd run on your very unstable cutting edge developmental Linux.
We're not necessarily set up to support such systems with
click-to-install packages. Please feel free to volunteer your help,
if you think there is a need.
The KVASD decoder is necessarily an extra nuisance because of its
patented algorithm and non-open source code. However, since 99% of
our users run Windows, the nuisance is well contained in practice.
Moreover, the improved sensitivity of soft-decision decoding makes
KVASD well worth the extra effort -- especially for EME, the original
target purpose for JT65.
-- 73, Joe, K1JT
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
