<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
Michael T. Dean wrote:<br>
<blockquote type="cite" cite="mid40857947.4000703@thirdcontact.com">KianTeck
wrote: <br>
<br>
<blockquote type="cite">No joy again. <br>
<br>
I changed the "Audio Output device" in mythtv to "ALSA:mixed-digital"
and tried to watch live TV again. This is what the mythfrontend says: <br>
------------------ <snip>---------------------- <br>
Opening ALSA audio device 'mixed-digital'. <br>
Unable to set hw params for playback: Invalid argument <br>
Error setting audio params: Invalid argument <br>
------------------ <snip>---------------------- <br>
<br>
I get the same deal too, as above, if I change the "Audio output
device" in mythtv to "ALSA:default". Anyway, I do not get the "Device
or Resource busy" message in both the above settings now. <br>
</blockquote>
<br>
Are you certain your MythTV was compiled with native ALSA support?
There's a section in mythtv's settings.pro: <br>
<br>
# Native ALSA support <br>
#CONFIG += using_alsa <br>
#ALSA_LIBS = -lasound <br>
<br>
Uncomment the CONFIG and ALSA_LIBS lines when building mythtv and see
if that helps (unless you're positive it's been compiled that way).
May not help, but... <br>
</blockquote>
<br>
I installed my MythTV using "apt-get install mythtv-suite" as detailed
in Jarod's guide. So, I cannot be certain if it was compiled with
native ALSA support. How can I confirm it?<br>
<br>
<blockquote type="cite" cite="mid40857947.4000703@thirdcontact.com"><br>
<blockquote type="cite">Setting .asoundrc in mixed digital, while
live TV is running, and issuing "aplay
/usr/share/sounds/KDE_Startup.wav" (via ssh) run immediately without
any queuing. <br>
<br>
I also noticed TWO other settings in mythtv audio setting (Setup |
General | Audio) "Mixer Device = /dev/mixer" and "Mixer Controls =
PCM". Do I need to change any of one of these 2 values? <br>
</blockquote>
<br>
Shouldn't be necessary. AFAIK, S/PDIF output is line-level output that
requires a decoder and an amplifier, so you can only adjust volume
externally (on the receiver you're using as a decoder). However, the
.asoundrc has defined control devices even for the digital and
mixed-digital devices, so if your software tries to use it, it's
available (just probably doesn't do anything). <br>
<br>
Since you previously said aplay outputs through S/PDIF, your ALSA setup
is correct. (At the time, you were using unmixed digital output as the
default, but the only change we've made since then makes mixed digital
the default. You might want to verify that aplay still works with
S/PDIF, though. Use "aplay" and "aplay -D mixed-digital" to test.)
Therefore, it's probably either the way your MythTV was compiled or an
error (i.e. typo or something) in your Myth database. <br>
</blockquote>
------------------ <snip>---------------------- <br>
pcm.!default {<br>
type plug<br>
## Uncomment the following to use mixed analog by default<br>
# slave.pcm "dmix-analog"<br>
## Uncomment the following to use unmixed digital by default<br>
# slave.pcm "digital-hw"<br>
## Uncomment the following to use mixed digital by default<br>
slave.pcm "dmix-digital"<br>
}<br>
------------------ <snip>---------------------- <br>
<br>
ok, so with mixed-digital still at my default in .asoundrc, I tried
both the "aplay -D mixed-digital" and "aplay", I can get sound through
the SPDIF. But still not able to get sound through SPDIF in MythTV.<br>
<br>
However, reviewing through this thread (way back to the Apr 10), I did
noticed a reply by Chris. After following his instructions in adding
the "options snd-pcm-oss adsp_map=2" to /etc/modules.conf and changing
MythTV to use /dev/adsp, I can get sound through SPDIF. I am I right
in saying this is using the oss emulation?<br>
<br>
KianTeck<br>
</body>
</html>