<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6">
</HEAD>
<BODY>
<BR>
Hi Stephen!<BR>
<BR>
Thanks for replying!<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
Yes, a look at alsamixer's output can reveal all sorts of interesting<BR>
things. When using SPDIF output, I always have to unmute it before it<BR>
will work. And then sometimes the automatic "alsactl save" does not<BR>
seem to happen, so I find it a good idea to do that after I have<BR>
everything working.<BR>
</BLOCKQUOTE>
<BR>
They may have changed it to 'alsactl store' else just typed the wrong word -- save, store, whatever to us humans! <g> This newbie did a Google search and found the storage goes to /etc/asound.conf -- which I don't have at all (!). Significant?? Or just empty because I haven't stored anything first? <BR>
<BR>
And as I reminded Nick, in System Settings I don't have a 'Sound' icon. LIS originally , not sure if that's significant. <BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
And then there is a new-ish bug that means that sometimes the "alsactl<BR>
restore" that is supposed to happen on boot does not work, or<BR>
something else turns off my SPDIF output. So if I start playing a<BR>
recording and there is no sound, the first thing I do is go to a<BR>
command prompt and do an "alsactl restore" and 99% of the time it<BR>
fixes it. Sometimes I have that problem several times in one day, and<BR>
sometimes not at all for a month or so.<BR>
</BLOCKQUOTE>
I wonder if that's what happened on my old Mythbuntu system (RIP -- late last week I think the storage drive died) Rarely had to reboot one of the Frontends to get sound. (That's the reason I'm using the old HDMI cards - trying to get them to connect to the new Backend.)<BR>
<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
Another little gotch I have is with my laptop. When it boots, it<BR>
assumes the audio is going to the headphone jack. I have to plug in<BR>
and unplug my headphones to get it to go to the speakers. I am sure<BR>
there is an option somewhere to fix this, but I have never had the<BR>
time to hunt it down.<BR>
</BLOCKQUOTE>
<BR>
Like this newbie knows much of anything ... ah heck: thought I remembered I had something in my notes but was "if HDMI audio pass through does not work". <BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
Note: The alsamixer and alsactl commands may need sudo - I run them<BR>
from a root command prompt.<BR>
</BLOCKQUOTE>
Right. I've found a lot of stuff when Googling trying to figure this last portion out and 'sudo' isn't written. I usually figure if it doesn't work as user 'barry' I just have to tell the computer who's boss with the 'sudo' nametag! <g><BR>
<BR>
Anyway, thanks for the help! We'll get this critter working yet!<BR>
<BR>
Barry <BR>
<BR>
</BODY>
</HTML>