studio-controls autoconnects the wrong ports
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
studio-controls (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I happen to have three USB devices that are (also) audio input devices which studio-controls bridges as C920,0,0-in, MICROPHONE,0,0-in and MS2109,0,0-in, only one of which is actually a microphone (guess which one). If I try to set up an input bridge for MICROPHONE,0,0-in, studio-controls will always connect it to MS2109,0,0-in. A bridge for C920,0,0-in is connected correctly.
If I try to configure a bridge for MS2109,0,0-in, it is displayed as a bridge for MICROPHONE0,0-in in auto connect port dropdown on the Pulse Bridging tab, but still connected to MS2019,0,0-in. I do not know as how many bugs I should count this.
It is wrong in autojackrc:
pulse-in = pulse_in MIC C920 HDMI
pulse-out = pulse_out
pj-in-con = system:capture_1 MS2109,
If I edit it manully in autojackrc, studio-controls will set up the correct connections, but will display an empty text in the auto connect port dropdown.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: studio-controls 2.0.8-0ubuntu1
ProcVersionSign
Uname: Linux 5.8.0-20-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 3 15:32:17 2020
InstallationDate: Installed on 2020-05-28 (127 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitec
SourcePackage: studio-controls
UpgradeStatus: Upgraded to groovy on 2020-10-03 (0 days ago)
Changed in studio-controls (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Len Ovens (len-ovenwerks) |
Changed in studio-controls (Ubuntu): | |
status: | Incomplete → In Progress |
Changed in studio-controls (Ubuntu): | |
status: | In Progress → Fix Committed |
assignee: | Len Ovens (len-ovenwerks) → nobody |
@Florian Hars (hars) Can I get you to try out a fix for me? Attached to this comment is a file that you can download and run from a terminal and see if it works better. Just cd to whatever place this is downloaded to and run ./studio-controls (the ./ means run this one and not the system copy)