• Mark with a Z@suppo.fi
    link
    fedilink
    arrow-up
    6
    ·
    30 days ago

    Choices when trying to get reaper or ardour to work:

    • Massive latency, unusable
    • All other audio stops working
    • No audio at all
    • Have audio but now midi devices don’t work
    • ExtremeUnicorn@feddit.org
      link
      fedilink
      arrow-up
      5
      ·
      30 days ago

      At least for Linux-Reaper:

      Use Jack. Install the “Pulse Jack Module”, route Pulseaudio through Jack to simultaneously connect Reaper and everything else to the Jack System out. Always autostart Jack and use the Pulse Module “autoconnect” parameter as a startup script (QJackCtl helps here).

      Should fix 1-3, 4 I’m not sure.

      • Mark with a Z@suppo.fi
        link
        fedilink
        arrow-up
        2
        ·
        30 days ago

        I eventually gave up and just chose ALSA, which “just works” with the downside of being exclusive. I’ll give jack another try once I distrohop again.

    • murtaza64@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      29 days ago

      I feel like I got pretty lucky with my bitwig setup (on arch)? I selected PipeWire as the output driver and everything just works (no latency, midi is fine, other apps can still be heard). the only caveat is I have to fiddle a bit if I want the audio to be sent over screen sharing apps, which I think introduces a decent amount of latency. Maybe bitwig has invested in some tech the other DAWs don’t have since it’s commercial software and Linux support is one of their competitive advantages…