Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pipewire pipewire
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 636
    • Issues 636
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 17
    • Merge requests 17
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PipeWirePipeWire
  • pipewirepipewire
  • Issues
  • #289
Closed
Open
Issue created Sep 12, 2020 by Swiftb0y@Swiftb0y

Constant XRuns / Stutter with external USB DAC

So far I've been using pipewire successfully on my laptop with an integrated Intel DAC. I have a Numark NS6II DJ Controller which features a 4.0 Soundcard (1 Stereo pair for the main out and one pair for the pfl headphone out). Unfortunately, no matter what API is used, PW produces lots of underruns. Though I'm not sure whether those are really underruns, because it doesn't seem like the missed buffers are rejected but rather the player is given the chance to take longer than expected to fill the buffer fully. I've tried using Jack, PA, or the alsa bridge and all produce the same results. The soundsource being used also doesn't seem to make a difference. I've tried firefox, totem and Mixxx. Though when inspecting the log from Mixxx, I was able to spot the following error:

[W][000204713.517280][remote-node.c:650 client_node_port_use_buffers()] Failed to mlock memory 0x7fb6e11a5000 32832: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK

I don't know how to increase that or even what I should increase it too. I'm running the binaries from the fedora package repositories so currently PW version 0.3.10

Assignee
Assign to
Time tracking