Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • pipewire pipewire
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 575
    • Issues 575
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • 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
  • #1473
Closed
Open
Issue created Jul 30, 2021 by Michele Perrone@michele-perrone🎶

Audio latency is too high with M-Audio FireWire 410 sound card

If you are filing this issue with a regular release please try master as it might already be fixed.

Version, Distribution, Desktop Environment: Pipewire 0.3.32, Manjaro GNOME

Description of Problem: Although having set an latency of 64/48000 and a period size of 128 samples, I perceive a much higher latency when playing virtual instruments plugins - I would say more 10ms, because it's noticeable. This happens only with my M-Audio FW410 firewire card. With my internal sound card and my USB sound card, the latency is fine. Looking at pw-top confirms that the quantum is indeed set to 64 samples.

How Reproducible: Play any virtual instrument as a standalone or inside a host (Carla or Ardour).

Steps to Reproduce:

  1. Set the property node.latency = 64/48000 in /etc/pipewire/jack.conf
  2. Set the property api.alsa.period-size = 128 in /etc/pipewire/alsa-monitor.conf
  3. Restart pipewire and play a virtual instrument ( or use jack_iodelay as suggested by @berthold.crysmann )

Actual Results: Latency is perceptibly higher than it should be (if I can hear it when playing the piano, then it's surely above about 10 ms)

Expected Results: Latency in the order of (period-size/quantum)*(quantum)/(sampling-rate) = (128/64)*64/48000 = 2.7 ms

Additional Info Eg. pw-dump -N > file (As Attachment Please): pw_top.txt pw_dump.txt

Edited Aug 01, 2021 by Michele Perrone
Assignee
Assign to
Time tracking