[mythtv-users] Digital audio Capability grayed out

Klaas de Waal klaas.de.waal at gmail.com
Fri Aug 12 19:15:58 UTC 2022


On Fri, 12 Aug 2022 at 19:42, James Abernathy <jfabernathy at gmail.com> wrote:

>
>
> On Mon, Aug 8, 2022 at 6:46 AM James Abernathy <jfabernathy at gmail.com>
> wrote:
>
>>
>>
>> On Mon, Aug 8, 2022 at 6:38 AM Justin Smith <justin at smithpolglase.com>
>> wrote:
>>
>>> Hi James,
>>>
>>> > > This sounds like an issue similar to one I had recently:
>>> > >
>>> > > http://lists.mythtv.org/pipermail/mythtv-users/2022-June/409756.html
>>> > >
>>> > > I managed to get it working (not because I have any particular
>>> insight
>>> > > into this - more by luck - see the email), but I came to the
>>> > > conclusion that there is a bug either in MythTV or the kernel/alsa
>>> > > functionality that reports audio functionality.
>>>
>>> > Thank you for replying. I did a lot of searching on the mailing list
>>> for
>>> > Digital Audio Capabilities without finding your issue.
>>> >
>>> > I know back with Raspbian OS on the RPI4 I had to create a Mythtv audio
>>> > device in a file called: $HOME/.asoundrc. This must be what you did
>>> with
>>> > the right parameters.
>>> >
>>> > I'll test and report back. In my case Kodi and VLC both worked with
>>> Dolby
>>> > Digital.  Sometimes I see "Multi Channel In" on the display instead of
>>> > Dolby.  I think this must be content related.
>>>
>>> To be clear, I didn't edit $HOME/.asoundrc (or any file for that matter).
>>> I simply typed in
>>> "hdmi:CARD=PCH,DEV=0,AES0=0x06,AES1=0x82,AES2=0x00,AES3=0x09"
>>> in the audio output device field under Settings->Audio in the FrontEnd.
>>> I got this string from the Kodi log.
>>>
>>> After doing this, the "Digital Audio Capabilities" menu item became
>>> "ungreyed" (i.e. selectable) so I could enable all digital audio formats
>>> and 7.1 or 5.1. Digital passthrough now worked.
>>>
>>> Afterwards, I removed all those AES codes from the audio output device,
>>> and digital passthrough still worked.
>>>
>>> Obviously this AES string is setup dependent but my point is that since
>>> you
>>> use Kodi, you might be able to do the same thing.
>>>
>>> Cheers,
>>> Justin.
>>
>>
>>  I've looked all over Kodi logs for that string you used.  I could not
>> find it. Any help locating it would be great.  I'm using Kodi 19.4
>>
>> Jim A
>>
>
> I had the 5.1 working on mythtfrontned v32.0-6 on my FireTV, but today I
> rebuild the android mythfrontend to v32.0-59 and now I have the grayed out
> Digital Audio Capability the same as on my x86_64 versions of
> mythfrontend.  So something changed since March because my hardware and
> setup has not changed.
>
> JIm A
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org


It is really a lot of work but if you would do bisecting (see "git bisect"
https://git-scm.com/docs/git-bisect) you can pinpoint it down to a single
commit.

Klaas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20220812/8305dcc9/attachment.htm>


More information about the mythtv-users mailing list