Ubuntu Studio

Studio control hangs on adding bridges if main output ports are changed

Asked by Jean-Martin

Hello,

I'm on ubuntustudio 21.10, using studio control with FFADO Firewire Modules (sound device MOTU 828 MKII). If I change the main output ports (default are system:playback_1 <firewire_pcm>), studio control statrts jack but hangs on "adding bridges". This is annoying because port audio connects to the main output ports, and on the FFADO implementation of my sound device system playback is phone outputs, not main outputs. So, for instance, if I playback a sound with Audacity I can't hear anything on the loud speakers which are connected to the main outputs of my device (FFADO jack ports 13 and 14).
It's surprising that one cannot change the studio control main output ports on another port than 1, seems to be a bug.

Thanks for your help !

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Studio Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Erich Eickmeyer (eeickmeyer) said : 		#1
Revision history for this message
Erich Eickmeyer (eeickmeyer) said : 		#2

Probably best to raise this at https://github.com/ovenwerks/studio-controls/issues since it's an upstream project now and not necessarily something for Ubuntu Studio, but for lots of distributions.

Revision history for this message
Jean-Martin (jmb13) said : 		#3

OK I thought it was specific to UbuntuStudio. I'm a bit lost is this system of hierarchization of issue reports. Do you mean that I should report it on the link you mentioned ?

Revision history for this message
Len Ovens (len-ovenwerks) said : 		#4

If studio-controls jack status stops at adding bridges, that is a bug and should be reported as such. The url above ( https://github.com/ovenwerks/studio-controls/issues ) would indeed be the best place. please go to the system tweaks page and set logging level to "Extra" then restart jack so the problem shows up. (you get back to adding bridges) Then attach the file:
~/.log/autojack.log and ~/.log/autojack.log.1 (the second is just in case the log file rolled over part way through the startup)

Setting main output ports to the ports you want to listen to, should work.

Revision history for this message
Jean-Martin (jmb13) said : 		#5

Done

Revision history for this message
Erich Eickmeyer (eeickmeyer) said : 		#6

Marking as answered, to be handled upstream.

Can you help with this problem?

Provide an answer of your own, or ask Jean-Martin for more information if necessary.

To post a message you must log in.