Skip to content
  • Hjem
  • Seneste
  • Etiketter
  • Populære
  • Verden
  • Bruger
  • Grupper
Temaer
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Kollaps
FARVEL BIG TECH
pauldavisthefirst@fosstodon.orgP

pauldavisthefirst@fosstodon.org

@pauldavisthefirst@fosstodon.org
About
Indlæg
1
Emner
0
Fremhævelser
0
Grupper
0
Følgere
0
Følger
0

Vis Original

Indlæg

Seneste Bedste Controversial

  • I'm slowly starting to understand the whole @pipewire issue.
    pauldavisthefirst@fosstodon.orgP pauldavisthefirst@fosstodon.org

    @mosgaard
    Applications doing audio (or MIDI) I/O should not, in general, be using any API provided by pipewire itself. So there's really nothing "to support" unless:

    * you're a distro provider
    * you're creating control and configuration apps for audio/MIDI on Linux
    * you're working on a very unique application that for some reason needs to use Pipewire APIs

    Unlike the Wayland/X11 situation, Pipewire intends to fully support existing APIs (ALSA, JACK, PulseAudio) and does (fairly well!)

    Ikke-kategoriseret linuxaudio
  • Log ind

  • Har du ikke en konto? Tilmeld

  • Login or register to search.
Powered by NodeBB Contributors
Graciously hosted by data.coop
  • First post
    Last post
0
  • Hjem
  • Seneste
  • Etiketter
  • Populære
  • Verden
  • Bruger
  • Grupper