All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard <richard.bown@blueyonder.co.uk>
To: linux-hams@vger.kernel.org
Subject: Re: gmfsk
Date: Sun, 29 Oct 2006 22:42:48 +0000	[thread overview]
Message-ID: <45452E68.9060601@blueyonder.co.uk> (raw)
In-Reply-To: <20061029213157.GA25286@cloud.net.au>

Hamish Moffatt wrote:
> On Sun, Oct 29, 2006 at 04:07:03PM +0000, richard wrote:
>   
>> Cant seem to get audio routed to GMFSK , it compiled OK as far as I 
>> know, no errors .
>> In settings , selecting device /dev/dsp  /dev/dsp1 /dev/dsp2 doesn't 
>> route audio to the program.
>> I've determined that /dev/dsp2 is the mic input off the webcam, so that 
>> can be ignored.
>>     
>
> Is /dev/dsp actually the ALSA emulation, ie you are using ALSA natively?
> Can you send the results of "aplay -l" so we can see how ALSA has
> detected your devices?
>   
I've got the internal card disabled in the bios now.
[ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: M66 [M Audio Delta 66], device 0: ICE1712 multi [ICE1712 multi]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
<snip>
>> Is this behaviour I'm seeing on GMFSK normal , ie displaying garbage on 
>> /dev/dsp1  ??
>>     
>
> Not sure what you mean by garbage?
>   
If I leave the mode in MSK16 or CW there is always a waveform shown,
even when there is no input.
With all the connections to the inputs on the break out box
disconnected, the waterfall is plain grey, yet there
is a noisy waveform and the percentage indicator is showing 10% .
I've had a look at the noise floor in winrad and I cant see anything
which would cause this.

I've noted /dev/dsp is  busy if put in transmit mode.
ps ax showed artsd running, but killing it makes no difference to the
device busy message..

Connecting an audio source with a 1KHz tone ,shows a line in the right
place on the waterfall display

<another snip>
> Is that the configuration you want? I don't think there is any support
> in gMFSK for input and output on different devices. Your setup sounds
> unusual (perhaps unusually complicated?).
>   
No I don't need input and out on different cards, just something that
decodes

It could also be I'm at the bottom of the learning curve with this package.

TIA
73  Richard




  reply	other threads:[~2006-10-29 22:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29 16:07 gmfsk richard
2006-10-29 21:31 ` gmfsk Hamish Moffatt
2006-10-29 22:42   ` richard [this message]
2006-10-30 17:31     ` gmfsk richard
2006-10-30 21:38       ` gmfsk Hamish Moffatt
2006-10-30 22:14         ` gmfsk Tomi Manninen
2006-10-30 22:47           ` gmfsk Al Bolduc
2006-10-30 23:34           ` gmfsk Hamish Moffatt
2006-10-30 23:39             ` gmfsk Dave Platt
2006-10-31  1:26               ` gmfsk Hamish Moffatt
2006-10-30 23:44           ` gmfsk richard
  -- strict thread matches above, loose matches on Subject: below --
2006-10-29 16:40 gmfsk richard
2004-01-20 21:14 gMFSK Erik Jakobsen
2004-01-20 21:35 ` gMFSK Tomi Manninen
2004-01-21  0:06   ` gMFSK Wilbert Knol
2004-01-21  6:07     ` gMFSK Erik Jakobsen
2004-01-21  8:27       ` gMFSK Wilbert Knol
2004-01-21  7:59     ` gMFSK Joni Bäcklund
2004-01-21  8:13       ` gMFSK Erik Jakobsen

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=45452E68.9060601@blueyonder.co.uk \
    --to=richard.bown@blueyonder.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.