Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
pipewire
pipewire
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 175
    • Issues 175
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 6
    • Merge Requests 6
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWire
  • pipewirepipewire
  • Issues
  • #591

Closed
Open
Opened Jan 18, 2021 by Georges Basile Stavracas Neto@feaneronContributor

Scarlett 4i4 (3rd gen) not listed as input device by libgnome-volume-control

Distro: Arch Version: master (d46c58e9) Dump: pw-dump

I have a Scarlett 4i4 USB DAC that has its quirks, but generally works well enough. As of lately, however, the Sound panel of GNOME Settings stopped listing it as an input device - only as output.

Captura_de_tela_de_2021-01-18_20-39-17

pavucontrol, however, properly lists it:

Captura_de_tela_de_2021-01-18_20-39-54

I see the following couple of lines in the journal:

jan 18 20:32:53 feareniar-x1 gnome-control-c[95325]: Couldn't match the portless stream (with card) - 'Scarlett 4i4 USB Multichannel' is it an input ? -> 1, streams card id -> 46
jan 18 20:32:53 feareniar-x1 gnome-control-c[95325]: gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE (device)' failed

I bisected as far as 0.3.18, and all commits seem to be bad, but this was working okay until yesterday. Coincidentally, yesterday was the day I tried to reproduce old friend HDMI problem (#377 (closed), #390 (closed)) so I suspect it must be related.

Edited Jan 19, 2021 by Georges Basile Stavracas Neto
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: pipewire/pipewire#591