studio-controls autoconnects the wrong ports

Bug #1898369 reported by Florian Hars on 2020-10-03
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
studio-controls (Ubuntu)
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,0,0-in:capture_1 C920,0,0-in:capture_1 MS2109,0,0-in:capture_1

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
ProcVersionSignature: Ubuntu 5.8.0-20.21-lowlatency 5.8.10
Uname: Linux 5.8.0-20-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
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)
PackageArchitecture: all
SourcePackage: studio-controls
UpgradeStatus: Upgraded to groovy on 2020-10-03 (0 days ago)

Florian Hars (hars) wrote :
Changed in studio-controls (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Len Ovens (len-ovenwerks)
Len Ovens (len-ovenwerks) wrote :

@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)

Marked as incomplete, info has been requested from reporter.

Changed in studio-controls (Ubuntu):
status: Triaged → Incomplete
Florian Hars (hars) wrote :

Yes, that seems to fix it.

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
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package studio-controls - 2.0.9-0ubuntu1

---------------
studio-controls (2.0.9-0ubuntu1) groovy; urgency=medium

  [ Len Ovens ]
  * Fixed: Wrong variable used causing incorrect port to be chosen (LP: #1898369)

 -- Erich Eickmeyer <email address hidden> Tue, 06 Oct 2020 14:43:43 -0700

Changed in studio-controls (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers