From: Apostolos Kefalas <sv1ljj@raag.org>
To: Haines Brown <haines@histomat.net>
Cc: linux-hams@vger.kernel.org
Subject: Re: fldigi setup question
Date: Thu, 23 Jun 2016 12:28:24 +0300 [thread overview]
Message-ID: <1466674104.1592.6.camel@raag.org> (raw)
In-Reply-To: <20160623011533.GB12415@engels.historicalmaterialism.info>
[-- Attachment #1: Type: text/plain, Size: 2822 bytes --]
On Τετ, 2016-06-22 at 21:15 -0400, Haines Brown wrote:
> There was no response to the question of my original post. I assume that
> this was because it was too open ended. So I'll be more specific.
>
> I'm running debian Wheezy with a SignaLink USB sound card and fldigi
> software. The transmitter is a K3 tuned to 14.070, TX DATA mode USB. My
> computer uses PulseAudio as default. Alsamixer also sees the presence of
> SignaLink's USB Audio CODEC, which is un-muted and at 84%.
>
> The SignaLink USB instructions tell me to make sure the software's
> transmit and receive audio card is set to USB Audio CODEC. I go to
> fldigi, Configure, Soundcard. Although PulseAudio is present on the
> computer, not wishing to use PulseAudio for fldigi, I have selected
> PortAudio. I assume I can do this. Am I wrong?
No you are not wrong... though I can not understand why you want to do
that. Portaudio will use ALSA which will redirect you through
Pulseaudio!!!
>
> PortAudio does not offer an option to choose the Transmit and Receive
> audio card, but instead the Capture and Playback card. I set PortAudio
> Capture to the SignaLink's USB Audio CODEC card. But the fldigi
> PortAudio Playback does have that option. Its options are Xonar DX (my
> computer's sound card) HDA NNvidia (motherboard audio chip), iec958,
> spdif (a cable?), pulse (PulseAudio?) and default (my computer's Xonar
> sound card?). USB Audio CODEC is not a choice. Should it be? Should I
> instead use iec958?
Make sure you have installed libportaudio packages.
>
> Pavucontrol sees "ALSA Plugin [fldigi]" for ALSA Capture under Recording
> and sees PCM2904 Audio Codec Analog Stereo among Output
> Devices. Question: shouldn't what pavucontol sees and the values it sets
> be irrelevant?
See above!!!
>
> And the fldigi waterfall is strange. Fldigi is set to PSK31 at
> 14070.000. The waterfall sees noise only in a band at its center
> (14071.240 to 14071.716) and at its extreme left edge (14070.041). While
> the middle region has nothing that looks like signals (unless it itself
> is a broadband signal), the left edge looks as though it is close to the
> IM distortion of a signal just out of range. Although the central region
> has no visible PSK31 signals and I hear no PSK31 warble, it and the
> extreme left produce garbage text ("e S tite ate oee o e too="), whether
> I set the demodulation for frequency or phase shift. The only effect
> changing the demodulation is that with RTTY, the garbage is upper case.
>
> Please help.
>
> Haines Brown KB1GRM
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-23 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 13:54 fldigi setup question Haines Brown
2016-06-23 1:15 ` Haines Brown
2016-06-23 9:28 ` Apostolos Kefalas [this message]
2016-06-23 11:48 ` Haines Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1466674104.1592.6.camel@raag.org \
--to=sv1ljj@raag.org \
--cc=haines@histomat.net \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox