From: richard <richard.bown@blueyonder.co.uk>
To: linux-hams@vger.kernel.org
Subject: Re: gmfsk
Date: Mon, 30 Oct 2006 23:44:22 +0000 [thread overview]
Message-ID: <45468E56.1090903@blueyonder.co.uk> (raw)
In-Reply-To: <1162246448.5345.5.camel@oh2bns.ampr.org>
Tomi Manninen wrote:
> On Tue, 2006-10-31 at 08:38 +1100, Hamish Moffatt wrote:
>
>
>> I don't think there is a CW decoder anyway.
>>
>
> 0.7pre1 has one.
>
Now I know about the permissions problem, I've noticed it decodes well
at 38wpm.
Not that many can read at that speed, definitely not me :)
>
>> I had more success when I set the sampling rate to 48000. My sound card
>> doesn't really have the lower rates and the sample rate converter inside
>> gMFSK seems to do a better job than the ALSA one which is providing
>> /dev/dsp.
>>
>
> This is a good suggestion. I've heard lots of complaints about the
> sample rate conversion stuff in ALSA.
>
>
>>> What is giving me a real problem is that if I go to TX I get the box up
>>> with:-
>>> "sound_open_for_write:opensnd: /dev/dsp: Deviceor resource busy"
>>>
>> Could be that gMFSK requires (inadvertently?) a full duplex sound card
>> which yours is not? Unlikely though.
>>
Is'nt the delta 66 capable of full duplex ?
>
> It shouldn't. I've tried to make gMFSK as simple as possible here:
>
> - open card for reading
> - listen and decode
> - close card
> - open card for writing
> - send
> - close card
>
> ... and so on.
>
> That should be pretty fool proof, but I guess anything is possible.
>
>
It might be foolproof, but not quite proof against me.
Another thing I've found, after loading FFTW Wisdom it now allows two
failure in TX mode to write to /dev/dsp
before the waterfall goes extra fast and no input signal is seen or
decoded..
That could be a bug as Hamish suggested
If I can get the permissions sorted, its working, but at the moment only
if run by root..
Richard
next prev parent reply other threads:[~2006-10-30 23:44 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 ` gmfsk richard
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 ` richard [this message]
-- 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=45468E56.1090903@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).