Trouble getting Jack to work with "extra Device"

[Keith Smith]

I'm having trouble getting audio output to my internal ACS1220A
motherboard audio (connected to external speakers) when Jack is using
an external USB audio interface for input.

!. with Jack not running, pulseaudio works fine and sound (music file)
comes out of the ACS1220A

2. with Jack configured to use the USB audio interface as source and
sink, and pulseaudio bridge, it works fine. Sounds is heard from the
USB audio interface headphone.

However, If I add the AC1220A PCH 1,0 digital output device to JACK
(via studio controls "Extra Devices")  it shows up in Carla, and I can
connect it up so that all output (pulse_out) goes to it, but there's no
sound.

I check the ALSA mixer and pulse mixer controls and don't see any
problems.

I tried setting up Studio controls a few different ways, but nothing
seem to work.

Does anyone have any experience with this type of problem?  seems like
it should work.

Thanks,
Keith

[Keith Smith]

On Wed, 2020-12-23 at 20:01 -0800, Keith Smith wrote:
> I'm having trouble getting audio output to my internal ACS1220A
> motherboard audio (connected to external speakers) when Jack is using
> an external USB audio interface for input.
>
> !. with Jack not running, pulseaudio works fine and sound (music
> file)
> comes out of the ACS1220A
> with Jack configured to use the USB audio interface as source and
>
> sink, and pulseaudio bridge, it works fine. Sounds is heard from the
> USB audio interface headphone.
>
> However, If I add the AC1220A PCH 1,0 digital output device to JACK
> (via studio controls "Extra Devices")  it shows up in Carla, and I
> can
> connect it up so that all output (pulse_out) goes to it, but there's
> no
> sound.
>
> I check the ALSA mixer and pulse mixer controls and don't see any
> problems.
>
> I tried setting up Studio controls a few different ways, but nothing
> seem to work.
>
> Does anyone have any experience with this type of problem?  seems
> like
> it should work.
>
> Thanks,
> Keith
>
> music mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

Found the problem.  It appears that Studio controls is not passing the
correct hardware information to zita-j2a for my internal soundcard.

In studio Controls under Extra Devices - Add (available) the internal
Audio device is listed as: "PCH,1,0 playback (ALC1220 digital)".  When
I add this device I see it in the Carla patchbay and can route audio to
it, but no sound is produced.

From a kconsole if I run:

zita-j2a -j MYTRY -d hw:1,0

I then see a new sink device "MYTRY" in the Carla patchbay. When I
route audio to it I successfully get sound output.   I also get sound
output over my external USB audio interface which is the desired
behavior.

I would report this to github.com/ovenwerks/studio-controls, but the
version described there seems to be newer than what is provided in
Fedora Jam.  I'm not sure how to figure out what version Fedora uses vs
the released version?

-Keith

Hi Keth,
> Found the problem.  It appears that Studio controls is not passing the
> correct hardware information to zita-j2a for my internal soundcard.
>
> In studio Controls under Extra Devices - Add (available) the internal
> Audio device is listed as: "PCH,1,0 playback (ALC1220 digital)".  When
> I add this device I see it in the Carla patchbay and can route audio to
> it, but no sound is produced.
>
> From a kconsole if I run:
>
> zita-j2a -j MYTRY -d hw:1,0
>
> I then see a new sink device "MYTRY" in the Carla patchbay. When I
> route audio to it I successfully get sound output.   I also get sound
> output over my external USB audio interface which is the desired
> behavior.
>
> I would report this to github.com/ovenwerks/studio-controls, but the
> version described there seems to be newer than what is provided in
> Fedora Jam.  I'm not sure how to figure out what version Fedora uses vs
> the released version?
>
> -Keith

The version on Github is newer than Fedora and has not been released for 
Fedora because it's merely a prerelease (hence the -pre tag). We don't 
want unstable software hitting distributions.

I'd still report this issue because it's possible that the upcoming 
version (2.1) won't have that fix. He's most definitely going to want to 
see your logs (~/.log/autojack.log and ~/.log/jack/jackdbus.log) and may 
even have you set logging to debug in the Studio Controls interface.

--
Erich Eickmeyer
Maintainer
Fedora Jam