You are not logged in.

#76 2021-06-20 18:53:04

bernd_b
Member
Registered: 2013-07-30
Posts: 140

Re: A52 plugin with alsa-plugins >1.1.6

Yes, I think you are right. But a52-plugin would be of use if you redirect the hdmi sound output to a decoder which only has a toslink/ S-PDIF interface. It is easier and much cheaper to buy an adapter from hdmi to toslink than to find a new amplifier supporting virtual souround for headphones.

The question is, if you can use the a52 plugin like the dcaenc plugin, meaning output the encoded stream via hdmi.

So thanks for the additional infos, it does not seem to work (at least out of the box).

Offline

#77 2021-06-20 22:57:51

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 13,805

Re: A52 plugin with alsa-plugins >1.1.6

My alsa-plugins (which is from the repos and I'm not in need of what you are trying to do here, so YMMV) contains a /usr/share/doc/alsa-plugins/a52.txt with how an example config should look like. To my knowledge there's nothing that would be set up by default automatically. If there was any default config it would be under a snippet in /usr/share/alsa/alsa.conf.d/

Offline

#78 2021-06-21 07:17:21

bernd_b
Member
Registered: 2013-07-30
Posts: 140

Re: A52 plugin with alsa-plugins >1.1.6

I think that is different with the future packages of alsa-plugins

pacman -Ql alsa-plugins-git | grep /usr/share/alsa/alsa.conf.d/

alsa-plugins-git /usr/share/alsa/alsa.conf.d/
alsa-plugins-git /usr/share/alsa/alsa.conf.d/10-rate-lav.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/10-samplerate.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/10-speexrate.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/50-arcam-av-ctl.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/50-jack.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/50-oss.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/50-pulseaudio.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/60-a52-encoder.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/60-speex.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/60-upmix.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/60-vdownmix.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/98-maemo.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/98-usb-stream.conf
alsa-plugins-git /usr/share/alsa/alsa.conf.d/99-pulseaudio-default.conf

and

cat /usr/share/alsa/alsa.conf.d/60-a52-encoder.conf 
pcm.a52 {
	@args [ CARD SLAVE RATE BITRATE CHANNELS ]
	@args.CARD {
		type integer
		default {
			@func refer
			name defaults.pcm.card
		}
	}
	@args.SLAVE {
		type string
	}
	@args.RATE {
		type integer
		default 48000
	}
	@args.BITRATE {
		type integer
		default 448
	}
	@args.CHANNELS {
		type string
		default 6
	}
	type a52
	card $CARD
	slavepcm $SLAVE
	rate $RATE
	bitrate $BITRATE
	channels $CHANNELS
	hint {
		show {
			@func refer
			name defaults.namehint.basic
		}
                description "Plugin to convert multichannel stream to A52 (AC3) bitstream"
	}
}

Up to now, I never succeeded in really understanding this code with all its @func and $CARD/SLAVE etc.. So far, I see no hint on how the plugin finds its output device.

Offline

#79 2021-06-21 08:09:53

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 13,805

Re: A52 plugin with alsa-plugins >1.1.6

@args.CARD {
		type integer
		default {
			@func refer
			name defaults.pcm.card
		}
	}

If the CARD= environment variable isn't set the default card is whatever is defined as the defaults.pcm.card (which is hw:0 by default, check /usr/share/alsa/alsa.conf  for the defaults for the references here) so if you don't see this currently it's likely that the default card is not the one you actively want to manipulate in this case. You mentioned you don't have an explicit SPDIF device, how exactly is the adapter connected then? If I'm reading the aforementioned helptext correctly, if the card does not have a traditional spdif pcm you will want to define the slave so e.g. 

pcm.a52 {
     slavepcm "hdmi"
}

Last edited by V1del (2021-06-21 09:02:03)

Offline

#80 2021-06-21 09:01:19

bernd_b
Member
Registered: 2013-07-30
Posts: 140

Re: A52 plugin with alsa-plugins >1.1.6

V1del wrote:

You mentioned you don't have an explicit SPDIF device, how exactly is the adapter connected then?

PC  (--->via HDMI)   TV   (--->via HDMI)   Hardware Adapter   (---> via coaxial cable-S/PDIF)   Headphone amplifier with virtual surround decoder for dts/ac3

Offline

#81 2021-06-21 09:06:42

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 13,805

Re: A52 plugin with alsa-plugins >1.1.6

Ah my edit and your response coincided. You should check what happens if you set the slavepcm explicitly to the HDMI PCM you want to have used.

Offline

#82 2021-06-21 14:04:02

quequotion
Member
From: Oita, Japan
Registered: 2013-07-29
Posts: 797
Website

Re: A52 plugin with alsa-plugins >1.1.6

Videl wrote:

If there was any default config it would be under a snippet in /usr/share/alsa/alsa.conf.d/

There is a config file there if alsa-plugins gets built against ffmpeg, triggering the a52 plugin to be built and the config to be generated.

The current alsa-plugins in [extra] doesn't include ffmpeg in makedepends() because of (one of) the issues, now resolved, that also initiated this thread: namely, that when libavresample was deprecated from ffmpeg (and thus dropped from Archlinux's package in [extra]), alsa-plugin's upstream did not update their lavrate plugin to use libswresample. Given that the plugins would not build anyway, ffmpeg was then dropped from alsa-plugins' makedepends().

That should change with the next upstream release (alsa-plugins finally got patched to use libswresample, and so can once again have ffmpeg in makedepends() to build and package the a52 plugin).

V1del wrote:

usr/share/doc/alsa-plugins/a52.txt...

I believe this file is being neglected by alsa-plugins' upstream (edit: last updated May 24, 2006). See this discussion in which I was at last informed of these two things:

First, that there is a default configuration supplied, which enables a "plug:a52" device (at least, for S/PDIF cards) without any need for user intervention (although this device is not listed by aplay -L).

Second, that unless one prepends their manual configuration with an exclamation point (pcm.!a52), alsa will attempt to merge their manual configuration with the supplied one, resulting in a dysfunctional mess ("unknown field card", etc).

Getting back to bernd_b's HDMI question, I think you may be correct that it can be resolved with a manual configuration--but that needs to be done either in a way that is safe to merge with the supplied one, or written from scratch and prepended with an exclamation mark as noted above.

Last edited by quequotion (2021-06-22 01:41:25)

Offline

#83 2021-06-21 16:09:57

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 13,805

Re: A52 plugin with alsa-plugins >1.1.6

I'm aware of all of that. The snippet I posted should be "safe" to merge (the slavepcm key is present and of type string and will get the relevant assignment) though I don't know what it's going to do with the card field as the two are mutually exclusive so if there's indeed a conflict, copy that entire config, drop the card key and just set the slavepcm relevantly

pcm.!a52 {
	@args [ CARD SLAVE RATE BITRATE CHANNELS ]
	@args.CARD {
		type integer
		default {
			@func refer
			name defaults.pcm.card
		}
	}
	@args.SLAVE {
		type string
	}
	@args.RATE {
		type integer
		default 48000
	}
	@args.BITRATE {
		type integer
		default 448
	}
	@args.CHANNELS {
		type string
		default 6
	}
	type a52
	slavepcm "hdmi" #Adjust this so it picks the correct PCM as listed in aplay -L
	rate $RATE
	bitrate $BITRATE
	channels $CHANNELS
	hint {
		show {
			@func refer
			name defaults.namehint.basic
		}
                description "Plugin to convert multichannel stream to A52 (AC3) bitstream"
	}
}

Last edited by V1del (2021-06-21 16:10:47)

Offline

#84 2021-06-23 10:45:59

asm0dey
Member
From: Moscow
Registered: 2021-06-23
Posts: 2
Website

Re: A52 plugin with alsa-plugins >1.1.6

I'm sorry folks, but from all these messages I didn't understand how to obtain 5.1 surround sound from my optical S/PDIF without the `alsa-lib-a52pcm` package and that famous asound.conf?

Offline

#85 2021-06-23 12:14:24

quequotion
Member
From: Oita, Japan
Registered: 2013-07-29
Posts: 797
Website

Re: A52 plugin with alsa-plugins >1.1.6

asm0dey wrote:

I'm sorry folks, but from all these messages I didn't understand how to obtain 5.1 surround sound from my optical S/PDIF without the `alsa-lib-a52pcm` package and that famous asound.conf?

1. Throw out the old config (remove the whole "pcm.a52 {}" node).  If you previously added alsa-lib, alsa-plugins, or ffmepg to "IgnorePkg" in pacman.conf, remove them from this list and upgrade.

pacman -Syu

2. Replace alsa-lib-a52pcm with alsa-lib from [extra]:

pacman -S --asdeps alsa-lib

3. Build and install alsa-plugins-git from AUR*:

$ git clone https://aur.archlinux.org/alsa-plugins-git
$ cd alsa-plugins-git/
$ makechrootpkg -c -r $CHROOT
# pacman -U alsa-plugins-git-*-x86_64.pkg.tar.zst

*Note that this will only be necessary until the next upstream release of alsa-plugins and subsequent repackaging for [extra], after which it will be as simple as having alsa-lib and alsa-plugins installed by pacman (no more configuration, no more building packages).

For ALSA applications, use "plug:a52" as the device (note that it isn't listed by "aplay - L").

For pulseaudio, you can set a "Digital Surround" profile in pavucontrol, or load the card with the profile manually in default.pa (get the parameters from "pactl list cards")

Last edited by quequotion (2021-06-23 12:25:39)

Offline

#86 2021-06-24 07:37:58

asm0dey
Member
From: Moscow
Registered: 2021-06-23
Posts: 2
Website

Re: A52 plugin with alsa-plugins >1.1.6

quequotion wrote:
asm0dey wrote:

I'm sorry folks, but from all these messages I didn't understand how to obtain 5.1 surround sound from my optical S/PDIF without the `alsa-lib-a52pcm` package and that famous asound.conf?

1. Throw out the old config (remove the whole "pcm.a52 {}" node).  If you previously added alsa-lib, alsa-plugins, or ffmepg to "IgnorePkg" in pacman.conf, remove them from this list and upgrade.

pacman -Syu

2. Replace alsa-lib-a52pcm with alsa-lib from [extra]:

pacman -S --asdeps alsa-lib

3. Build and install alsa-plugins-git from AUR*:

$ git clone https://aur.archlinux.org/alsa-plugins-git
$ cd alsa-plugins-git/
$ makechrootpkg -c -r $CHROOT
# pacman -U alsa-plugins-git-*-x86_64.pkg.tar.zst

*Note that this will only be necessary until the next upstream release of alsa-plugins and subsequent repackaging for [extra], after which it will be as simple as having alsa-lib and alsa-plugins installed by pacman (no more configuration, no more building packages).

For ALSA applications, use "plug:a52" as the device (note that it isn't listed by "aplay - L").

For pulseaudio, you can set a "Digital Surround" profile in pavucontrol, or load the card with the profile manually in default.pa (get the parameters from "pactl list cards")

Thank you very much for this answer!

If there is a way to do it I would pin this message and, possibly, post its excerpt to the wiki.

Last edited by asm0dey (2021-06-24 10:00:52)

Offline

#87 2021-06-26 22:22:13

bernd_b
Member
Registered: 2013-07-30
Posts: 140

Re: A52 plugin with alsa-plugins >1.1.6

V1del wrote:

I'm aware of all of that. The snippet I posted should be "safe" to merge (the slavepcm key is present and of type string and will get the relevant assignment) though I don't know what it's going to do with the card field as the two are mutually exclusive so if there's indeed a conflict, copy that entire config, drop the card key and just set the slavepcm relevantly

pcm.!a52 {
	@args [ CARD SLAVE RATE BITRATE CHANNELS ]
	@args.CARD {
		type integer
		default {
			@func refer
			name defaults.pcm.card
		}
	}
	@args.SLAVE {
		type string
	}
	@args.RATE {
		type integer
		default 48000
	}
	@args.BITRATE {
		type integer
		default 448
	}
	@args.CHANNELS {
		type string
		default 6
	}
	type a52
	slavepcm "hdmi" #Adjust this so it picks the correct PCM as listed in aplay -L
	rate $RATE
	bitrate $BITRATE
	channels $CHANNELS
	hint {
		show {
			@func refer
			name defaults.namehint.basic
		}
                description "Plugin to convert multichannel stream to A52 (AC3) bitstream"
	}
}

Since I can identify the term "hdmi" in my aplay -L output and I don't understand "drop the card key" I copied and pasted this configuration into my /etc/asound.conf. But the output of aplay -L remains the same.

As a quick shot, I used the dca.conf file and put this as a replacement into my /etc/asound.conf while replacing the term "dca" with "a52". This leads to:

[bernd_b@P4560-dev ~]$ cat /etc/asound.conf

#!!!!!!! dca-plugin !!!!

<confdir:pcm/dca.conf>

#!!!!!!! dca-plugin !!!!


#needed by some devices
#defaults.pcm.dca.aes0 0x04
#defaults.pcm.dca.iec61937 1

# vim:set ft=alsaconf:



#dca.conf where dca is replaced with a52

defaults.pcm.a52.aes0 0x06
defaults.pcm.a52.aes1 0x82
defaults.pcm.a52.aes2 0x00
defaults.pcm.a52.aes3 0x00
defaults.pcm.a52.iec61937 0

pcm.!a52 {
    @args [ CARD DEV AES0 AES1 AES2 AES3 IEC61937 ]

    @args.CARD {
        type string
        default {
            @func getenv
            vars [
                ALSA_IEC958_CARD
                ALSA_PCM_CARD
                ALSA_CARD
            ]
            default {
                @func refer
                name defaults.pcm.iec958.card
            }
        }
    }

    @args.DEV {
        type integer
        default {
            @func igetenv
            vars [
                ALSA_IEC958_DEVICE
            ]
            default {
                @func refer
                name defaults.pcm.iec958.device
            }
        }
    }

    @args.AES0 {
        type integer
        default {
            @func refer
            name defaults.pcm.a52.aes0
        }
    }

    @args.AES1 {
        type integer
        default {
            @func refer
            name defaults.pcm.a52.aes1
        }
    }

    @args.AES2 {
        type integer
        default {
            @func refer
            name defaults.pcm.a52.aes2
        }
    }

    @args.AES3 {
        type integer
        default {
            @func refer
            name defaults.pcm.a52.aes3
        }
    }

    @args.IEC61937 {
        type integer;
	default {
	    @func refer
	    name defaults.pcm.a52.iec61937
	}
    }

    type a52
    slave.pcm {
        @func refer
        name {
            @func concat
            strings [
                "cards."
                {
                    @func card_driver
                    card $CARD
                }
                ".pcm.iec958." $DEV ":"
                "CARD=" $CARD ","
                "AES0=" $AES0 ","
                "AES1=" $AES1 ","
                "AES2=" $AES2 ","
                "AES3=" $AES3
            ]
        }
    }

    iec61937 $IEC61937

    hint {
        show {
            @func refer
            name defaults.namehint.basic
        }
        description "DTS Encoding through IEC958 (S/PDIF)"
        device $DEV
    }
}

pcm.!a52hdmi {
    @args [ CARD DEV AES0 AES1 AES2 AES3 ]

    @args.CARD {
        type string
        default {
            @func getenv
            vars [
                ALSA_IEC958_CARD
                ALSA_PCM_CARD
                ALSA_CARD
            ]
            default {
                @func refer
                name defaults.pcm.iec958.card
            }
        }
    }

    @args.DEV {
        type integer
        default {
            @func igetenv
            vars [
                ALSA_IEC958_DEVICE
            ]
            default {
                @func refer
                name defaults.pcm.iec958.device
            }
        }
    }

    @args.AES0 {
        type integer
        default {
            @func refer
            name defaults.pcm.a52.aes0
        }
    }

    @args.AES1 {
        type integer
        default {
            @func refer
            name defaults.pcm.a52.aes1
        }
    }

    @args.AES2 {
        type integer
        default {
            @func refer
            name defaults.pcm.a52.aes2
        }
    }

    @args.AES3 {
        type integer
        default {
            @func refer
            name defaults.pcm.a52.aes3
        }
    }

    @args.IEC61937 {
        type integer;
	default {
	    @func refer
	    name defaults.pcm.a52.iec61937
	}
    }

    type a52
    slave.pcm {
        @func refer
        name {
            @func concat
            strings [
                "cards."
                {
                    @func card_driver
                    card $CARD
                }
                ".pcm.hdmi." $DEV ":"
                "CARD=" $CARD ","
                "AES0=" $AES0 ","
                "AES1=" $AES1 ","
                "AES2=" $AES2 ","
                "AES3=" $AES3
            ]
        }
    }

    iec61937 $IEC61937

    hint {
        show {
            @func refer
            name defaults.namehint.basic
        }
        description "AC3 Encoding through HDMI"
        device $DEV
    }
}

This gives me new devices:

[bernd_b@P4560-dev ~]$ aplay -L | grep CARD
sysdefault:CARD=PCH
front:CARD=PCH,DEV=0
surround21:CARD=PCH,DEV=0
surround40:CARD=PCH,DEV=0
surround41:CARD=PCH,DEV=0
surround50:CARD=PCH,DEV=0
surround51:CARD=PCH,DEV=0
surround71:CARD=PCH,DEV=0
hdmi:CARD=PCH,DEV=0
hdmi:CARD=PCH,DEV=1
hdmi:CARD=PCH,DEV=2
hdmi:CARD=PCH,DEV=3
usbstream:CARD=PCH
dcahdmi:CARD=PCH,DEV=0
dcahdmi:CARD=PCH,DEV=1
dcahdmi:CARD=PCH,DEV=2
dcahdmi:CARD=PCH,DEV=3
a52hdmi:CARD=PCH,DEV=0
a52hdmi:CARD=PCH,DEV=1
a52hdmi:CARD=PCH,DEV=2
a52hdmi:CARD=PCH,DEV=3
usbstream:CARD=U0x46d0x819

But whereas

mpv --audio-channels=7 --audio-device=alsa/dcahdmi:DEV=1 /home/bernd_b/makepkg/surroundTest.ac3

works and the dca-devices are available in pavucontrol too, this won't work and the a52-devices aren't shown in pavucontrol either:

bernd_b@P4560-dev ~]$ mpv --audio-channels=7 --audio-device=alsa/a52hdmi:DEV=1 /home/bernd_b/makepkg/surroundTest.ac3
[ffmpeg/demuxer] ac3: Estimating duration from bitrate, this may be inaccurate
 (+) Audio --aid=1 (ac3 6ch 44100Hz)
ALSA lib pcm_a52.c:1100:(_snd_pcm_a52_open) Unknown field slave
[ao/alsa] Playback open error: Invalid argument
[ao] Failed to initialize audio driver 'alsa'
[ao] This audio driver/device was forced with the --audio-device option.
[ao] Try unsetting it.
Could not open/initialize audio device -> no sound.
Audio: no audio

Exiting... (Errors when loading file)

Offline

#88 2021-06-27 09:55:24

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 13,805

Re: A52 plugin with alsa-plugins >1.1.6

In my configuration example, the slavepcm you'd want to use is "hdmi:CARD=PCH,DEV=1".

Last edited by V1del (2021-06-27 10:06:53)

Offline

#89 2021-06-27 19:48:52

bernd_b
Member
Registered: 2013-07-30
Posts: 140

Re: A52 plugin with alsa-plugins >1.1.6

This alsa-conf stuff is really beyond my mental capabilities.
So the editable line in your config now looks like this:

slavepcm "hdmi:CARD=PCH,DEV=1"

aplay -L shows no new device, at least here are some new results, but I fear there is still some magic missing:

mpv --audio-device=alsa/a52 /home/bernd_b/makepkg/surroundTest.ac3
[ffmpeg/demuxer] ac3: Estimating duration from bitrate, this may be inaccurate
 (+) Audio --aid=1 (ac3 6ch 44100Hz)
Segmentation fault (core dumped)
bernd_b@P4560-dev ~]$ speaker-test -D a52

speaker-test 1.2.5.1

Playback device is a52
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Access type not available for playback: Invalid argument
Setting of hwparams failed: Invalid argument

Last edited by bernd_b (2021-06-27 19:49:15)

Offline

#90 2021-06-27 20:11:19

bernd_b
Member
Registered: 2013-07-30
Posts: 140

Re: A52 plugin with alsa-plugins >1.1.6

Wait, there is more:
After reboot, pavucontrol shows me a new device: "Digital Surround 5.1 (IEC958/AC3) Output"

The decoder signals receiving a ac3-stream, but unfortunately the sound last half a second, vanishes half a second, appears again half a second and so on.
But: there is at least output of the plugin through hdmi!

When I close pavucontrol, playback seems to work flawlessly with the plugin through the chosen hdmi port:

mpv --audio-channels=auto --audio-device=pulse /home/bernd_b/makepkg/surroundTest.ac3
[ffmpeg/demuxer] ac3: Estimating duration from bitrate, this may be inaccurate
 (+) Audio --aid=1 (ac3 6ch 44100Hz)
AO: [pulse] 44100Hz 5.1(side) 6ch float
(Paused) A: 00:00:08 / 00:00:08 (100%)

Exiting... (Quit)

And this works without any problems:

speaker-test -D plug:a52 -c6 -t waw

Last edited by bernd_b (2021-06-27 22:03:42)

Offline

#91 2021-06-27 23:26:04

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 13,805

Re: A52 plugin with alsa-plugins >1.1.6

Yes your first speaker-test failed because you didn't specify a correct/proper channel count. So does this work properly now? Due to the nature of how this works you're unlikely to get around the weirdness with pavucontrol open as the device isn't exactly "normally" usable by the monitors pulse tries to allocate for estimating output levels.

Offline

#92 2021-06-28 21:21:08

bernd_b
Member
Registered: 2013-07-30
Posts: 140

Re: A52 plugin with alsa-plugins >1.1.6

V1del wrote:

Yes your first speaker-test failed because you didn't specify a correct/proper channel count.

Yes, maybe since

speaker-test -D plug:a52 -t wav

works as well
while, e.g.,

[bernd_b@P4560-dev ~]$ speaker-test -D a52 -t wav -c6

speaker-test 1.2.5.1

Playback device is a52
Stream parameters are 48000Hz, S16_LE, 6 channels
WAV file(s)
Access type not available for playback: Invalid argument
Setting of hwparams failed: Invalid argument

So using "-D plug:a52" instead of "-D a52" seems to make the difference.

As you expected, the following lines are sufficient for me to be added in /etc/asound.conf

pcm.a52 {
     slavepcm "hdmi:CARD=PCH,DEV=1"
}

And last observation:
As told,

mpv --audio-channels=6 --audio-device=pulse /home/bernd_b/makepkg/surroundTest.ac3

works fine with a52 plugin selected when pavucontrol ist not running the same time.

Strangely enough, playing the same file with vlc, the output behaves like mpv does when pavucontrol isn't closed before starting playback (so sound drop outs per every second).

Offline

#93 2021-06-29 01:02:32

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 13,805

Re: A52 plugin with alsa-plugins >1.1.6

VLC does a lot of internal processing, not sure whether it will properly pass the signal through.

Yes using a "plug" is the ALSA way of enabling automatic format conversion, so it will turn your single channel request into a 6 channel to fulfill the needs of the a52 PCM (not sure whether it just mutes the remaining 6 channels or copies the single signal automatically across all of them), but using a plug will do these kind of conversions for "incorrect" inputs

Offline

#94 2021-06-30 05:41:56

quequotion
Member
From: Oita, Japan
Registered: 2013-07-29
Posts: 797
Website

Re: A52 plugin with alsa-plugins >1.1.6

@bernd_b

This seems worth investigating.

I wonder if your HDMI port does not have its non-audio bit set.

This might explain why the autoconfiguration does not set it up and why it seems to be rejecting the a52 data stream.

Edit: I missed some posts; looks like you've got this worked around. Still, worth looking in to.

Last edited by quequotion (2021-07-02 04:38:09)

Offline

Board footer

Powered by FluxBB