← Back to team overview

ubuntustudio-bugs team mailing list archive

[Bug 1898369] [NEW] studio-controls autoconnects the wrong ports

 

Public bug reported:

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)

** Affects: studio-controls (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug groovy third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to studio-controls in Ubuntu.
https://bugs.launchpad.net/bugs/1898369

Title:
  studio-controls autoconnects the wrong ports

Status in studio-controls package in Ubuntu:
  New

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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/studio-controls/+bug/1898369/+subscriptions


Follow ups