[mythtv-users] Simultaneous analogue (analog) and S/PDIF output

[Alex Butcher]

On Wed, 12 Jan 2011, Alex Butcher wrote:

> On Wed, 12 Jan 2011, Jean-Yves Avenard wrote:
>> Then you set the passthrough override to ALSA:iec958:AES0=6, and check
>> the StereoPCM flag, and do not enable the 5.1 stereo upmixer..

[...]

> A further complication is that I don't think the audio settings page is
> displaying properly on my system. I don't know whether that's an issue with
> the build from rpmfusion that I'm using, or whether it's because there are
> too many settings to squeeze onto my display (1024x576, with mythfrontend
> using 944x557 to avoid parts of the GUI being in the overscan area). For a
> start, the 'Device Capabilities' box is squashed to nothing.

I meant 'Audio Capabilities', of course.

> It looks just like <http://www.gregandeva.net/mythfrontend.png> reported
> in <http://www.gossamer-threads.com/lists/mythtv/users/443270#443270>. 
> I'm running a more recent 0.24-fixes though:
>
> $ rpm -q --changelog mythtv
> [...]
> * Mon Nov 22 2010 Jarod Wilson <jarod at wilsonet.com> 0.24-2
> - Update to release-0-24-fixes, svn revision 27317
> - Add preview image fixup patch from ticket #9256
> - Add alsa passthru device patches from trunk r27306 and r27307
> [...]

I've just increased GuiHeight to 1000 and run mythfrontend over X, and sure
enough, the Audio Capabilities box is filled with three checkboxes;
Analogue/LPCM (presumably what you mean by 'StereoPCM'), Dolby Digital and
DTS.  I've now reported this as <http://code.mythtv.org/trac/ticket/9472>

> There's no StereoPCM flag in my GUI. Is the StereoPCM flag you describe the
> MultiChannelPCM row?

Answering my own question, it is. the Analogue/LPCM checkbox is checked if
the MultiChannelPCM row is 1, and unchecked if it's 0.

> I'm trying to make this thread something of a canonical explanation of how
> MythTV handles analogue, S/PDIF, and so on so that people with problems
> can refer to it to debug their problems too (regardless of what the GUI
> reports; we've all seen incidents where the settings GUIs report differ
> from the settings that are actually being /used/).

Oh, look, here's one of those bugs! :-)

Best Regards,
Alex