From: Hamish Moffatt <hamish@cloud.net.au>
To: linux-hams@vger.kernel.org
Subject: Re: gmfsk
Date: Mon, 30 Oct 2006 08:31:57 +1100 [thread overview]
Message-ID: <20061029213157.GA25286@cloud.net.au> (raw)
In-Reply-To: <4544D1A7.3010103@blueyonder.co.uk>
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?
> There never seems to be any input directed from /dev/dsp, bur /dev/dsp1
> has an input even when everything has been muted.
> I've had problems trying to get the sound from the TV card which is hard
> wired to AUX i/p on the mobo to route through the digital mixer
> to get routed out of the delta 66 breakout box to a diddy little hifi
> system in the shack. So I'm aware that the two cards don't talk to each
> other very well.
There's no way that sound can get from one card to the other via the
mixer alone. Either you need a cable from a line-out to a line-in, or
you need a program to copy samples from one card to the other. I think
this is irrelevant to your use of gMFSK though.
> Is this behaviour I'm seeing on GMFSK normal , ie displaying garbage on
> /dev/dsp1 ??
Not sure what you mean by garbage?
> Yet I can run winrad using wine to use the delta66 card as the input and
> the VIA 8253 as the output device
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?).
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2006-10-29 21:31 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 ` Hamish Moffatt [this message]
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 ` 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=20061029213157.GA25286@cloud.net.au \
--to=hamish@cloud.net.au \
--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.