WSJT v 1.1 and Rigblaster compability issue

Bug #1315769 reported by Hveem
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alsa-driver (Ubuntu)
Undecided
Unassigned
wsjt (Ubuntu)
Undecided
Unassigned

Bug Description

Hello, i am running Linux ubuntu with the latest updates, and wsjtx
installed from ppa:jnogatch/wsjtx

Running the program results in:
Portaudio says the requested soundcard format is not supported
Failed to start audio input stream.
Wsjt is set to use the correct soundcard in its configuration menu.

Output form command prompt:
wsjtx
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
bt_audio_service_open: connect() failed: Oppkobling nektes (111)
bt_audio_service_open: connect() failed: Oppkobling nektes (111)
bt_audio_service_open: connect() failed: Oppkobling nektes (111)
bt_audio_service_open: connect() failed: Oppkobling nektes (111)
ALSA lib pcm_dmix.c:961:(snd_pcm_dmix_open) The dmix plugin supports
only playback stream
ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = Ingen slik fil eller filkatalog
Cannot connect to server request channel
jack server is not running or cannot be started

Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 1968
Expression 'PaAlsaStreamComponent_InitialConfigure( &self->capture,
inParams, self->primeBuffers, hwParamsCapture, &realSr )' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 2643
Expression 'PaAlsaStream_Configure( stream, inputParameters,
outputParameters, sampleRate, framesPerBuffer, &inputLatency,
&outputLatency, &hostBufferSizeMode )' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 2767

Relevant information from dmesg output:
[11428.050146] usb 3-1: New USB device found, idVendor=0451, idProduct=2036
[11428.050151] usb 3-1: New USB device strings: Mfr=0, Product=1,
SerialNumber=0
[11428.050154] usb 3-1: Product: General Purpose USB Hub
[11428.050320] usb 3-1: ep 0x81 - rounding interval to 1024 microframes,
ep desc says 2040 microframes
[11428.050797] hub 3-1:1.0: USB hub found
[11428.050865] hub 3-1:1.0: 2 ports detected
[11428.321277] usb 3-1.1: new full-speed USB device number 13 using xhci_hcd
[11428.338983] usb 3-1.1: New USB device found, idVendor=2405,
idProduct=0003
[11428.338988] usb 3-1.1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[11428.338991] usb 3-1.1: Product: West Mountain Radio RIGblaster Advantage
[11428.338994] usb 3-1.1: Manufacturer: Silicon Labs
[11428.338996] usb 3-1.1: SerialNumber: 54ddaac5
[11428.339800] cp210x 3-1.1:1.0: cp210x converter detected
[11428.409286] usb 3-1.1: reset full-speed USB device number 13 using
xhci_hcd
[11428.425923] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called
with disabled ep ea835c2c
[11428.425928] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called
with disabled ep ea835c00
[11428.426287] usb 3-1.1: cp210x converter now attached to ttyUSB0
[11428.497116] usb 3-1.2: new full-speed USB device number 14 using xhci_hcd
[11428.518056] usb 3-1.2: New USB device found, idVendor=2405,
idProduct=0002
[11428.518062] usb 3-1.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[11428.518065] usb 3-1.2: Product: RIGblaster Advantage Audio
[11428.518067] usb 3-1.2: Manufacturer: West Mountain Radio
[11428.526215] input: West Mountain Radio RIGblaster Advantage Audio as
/devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1.2/3-1.2:1.3/input/input22
[11428.526410] hid-generic 0003:2405:0002.0007: input,hidraw3: USB HID
v1.00 Device [West Mountain Radio RIGblaster Advantage Audio] on
usb-0000:00:14.0-1.2/input3

It works with Fldigi, it uses portaudio.

---
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: haaken 2044 F.... pulseaudio
 /dev/snd/controlC2: haaken 2044 F.... pulseaudio
 /dev/snd/controlC0: haaken 2044 F.... pulseaudio
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-04-27 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
NonfreeKernelModules: nvidia
Package: alsa-driver (not installed)
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=nb_NO.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
Tags: trusty
Uname: Linux 3.13.0-24-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 12/19/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1805
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH Z77
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1805:bd12/19/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

Hi,

do you know http://ubuntuforums.org/showthread.php?t=2214335 ?

Also we need some more information. From a terminal window please run:

sudo apport-collect 1315769

and then change the status of the bug to 'Confirmed'.

Jörg

Changed in wsjt (Ubuntu):
status: New → Incomplete
affects: wsjt (Ubuntu) → alsa-driver (Ubuntu)
Revision history for this message
Hveem (krbjhvee) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
Hveem (krbjhvee) wrote : BootDmesg.txt

apport information

Revision history for this message
Hveem (krbjhvee) wrote : CurrentDmesg.txt

apport information

Changed in alsa-driver (Ubuntu):
status: Incomplete → Confirmed
Hveem (krbjhvee)
description: updated
Revision history for this message
John Nogatch (jnogatch) wrote :

> > Error in Soundin
> > Failed to start audio stream
> >
> > Error in Soundin
> > PortAudio says requested soundcard format not supported

Are you starting wsjtx from a terminal window? Are you observing the
"...SetApproximateSampleRate..." message?

 wsjtx tries to open the sound input device with sampleRate=48000. If
the device does not support that rate, then error messages are
produced. For example, if I try to use device hw:1,0 directly, then I
see these messages in the terminal window:

 Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in
'src/hostapi/alsa/pa_linux_alsa.c', line: 1968
 Expression 'PaAlsaStreamComponent_InitialConfigure( &self->capture,
inParams, self->primeBuffers, hwParamsCapture, &realSr )' failed in
'src/h
 ostapi/alsa/pa_linux_alsa.c', line: 2643
 Expression 'PaAlsaStream_Configure( stream, inputParameters,
outputParameters, sampleRate, framesPerBuffer, &inputLatency,
&outputLatency, &ho
 stBufferSizeMode )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2767

  I was able to make this device work by creating ~/.asoundrc with
this entry in it, and then telling wsjtx to use device "p148k":
  pcm.p148k {
      type plug
      slave {
           pcm "hw:1,0"
           format S16_LE
           channels 1
           rate 48000
       }
  }

Note that the entry is specific for audio device "hw:1,0". It creates
a new virtual audio device, based on hw:1,0 but supporting the desired
sample rate. You can see the id number of all audio devices by running
alsamixer and hitting function key F6. Use the hw number for your
particular device.

I hope that this helps you.

-John AC6SL

Revision history for this message
Hveem (krbjhvee) wrote :

creating ~/.asoundrc helped, it works now. Thanks.

Revision history for this message
Hveem (krbjhvee) wrote :
Revision history for this message
Greg Beam (ki7mt) wrote :

Just FYI:

There is ( 0 ) upstream effort being expended on WSJT-X v1.1 thru 1.4, and major bug fixes only on v1.5.0, none of which are formally available to Debian/Ubuntu.

Due to a pending release of Hamlib(3), which is required for v1.5.0 and above, a new version of WSJT-X is not formally available for the repository yet, however, I do have packages available on Launchpad which should overt most of these issues. When Hamlib(3) is released and updated in the Debian/Ubunbtu repo's, we'll be able to update WSJT-X to a much improved version over what is available to the repo now.

In the interim, I would recommend using either v1.5.0 for production and / or v1.6.0 for testing. You can use / test the following PPA's as you see fit:

WSJT-X v1.5.0 - ( latest upstream GA release )
https://launchpad.net/~ki7mt/+archive/ubuntu/wsjtx

WSJT-X v1.6.0 - ( current development focus, but fairly stable )
https://launchpad.net/~ki7mt/+archive/ubuntu/wsjtx-next

WSJT-X v1.6.1 - ( experimental testing )
https://launchpad.net/~ki7mt/+archive/ubuntu/wsjtx-exp

73's
Greg, KI7MT

Revision history for this message
Hveem (krbjhvee) wrote :

WSJT-X v1.5.0 works fine here,no problems at all.
I suggest that WSJT-X v1.5.0 is included in the official repos.

Revision history for this message
Greg Beam (ki7mt) wrote :

Hveen,

An updated version of WSJT-X will be provided in due time. There are a few thing that need to happen, in order, before formal upgrading of the repository version can be accomplished. When the upgraded version is available, an announcement will be made to the appropriate Debian and Ubuntu Ham Radio mailing lists.

73's
Greg, KI7MT

Hveem (krbjhvee)
affects: wsjtx (Ubuntu) → wsjt (Ubuntu)
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in alsa-driver (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.

Changed in alsa-driver (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers