From: richard <richard.bown@blueyonder.co.uk>
To: linux-hams@vger.kernel.org
Subject: gmfsk
Date: Sun, 29 Oct 2006 16:07:03 +0000 [thread overview]
Message-ID: <4544D1A7.3010103@blueyonder.co.uk> (raw)
Hi all
System here
Mandriva 2007 Gnome 2.16
GMFSK 0.7 pre1
sound cards M-audio delta 66
on board VIA 8253
Problem:-
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.
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.
Is this behaviour I'm seeing on GMFSK normal , ie displaying garbage on
/dev/dsp1 ??
Yet I can run winrad using wine to use the delta66 card as the input and
the VIA 8253 as the output device
the output from lspci -v below
00:0d.0 Multimedia audio controller: VIA Technologies Inc. ICE1712
[Envy24] PCI Multi-Channel I/O Controller (rev 02)
Subsystem: VIA Technologies Inc. M-Audio Delta 66
Flags: bus master, medium devsel, latency 32, IRQ 17
I/O ports at d800 [size=32]
I/O ports at d400 [size=16]
I/O ports at d000 [size=16]
I/O ports at b800 [size=64]
Capabilities: [80] Power Management version 1
00:11.5 Multimedia audio controller: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
Subsystem: ASUSTeK Computer Inc. A7V8X-X Motherboard
Flags: medium devsel, IRQ 18
I/O ports at e000 [size=256]
Capabilities: [c0] Power Management version 2
I'm using the envy24 patch bay as well as the alsa control thing.
It used to be easy to determine which dsp was in use by selecting them
with other software like skype, which now lists devices not by which dsp
they are connected to, but by a list of device types.
Any help appreciated
73
Richard g8jvm
next reply other threads:[~2006-10-29 16:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 16:07 richard [this message]
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 ` 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=4544D1A7.3010103@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.