Music Production on Guix System

Re:Music Production on Guix System by PaulDavisThe1st on Thursday November 26, 2020 @01:29PM (#25222408)

JACK2's benefits over JACK1 are:

   * dbus integration
   * multi-core parallelism
   * click-free port connect/disconnect

But: the first only matters on systems with PulseAudio installed (or where you insist on being able to use dbus to control JACK). The second only matters if you have actual parallel signal flows, which many people do not. The third is only possible if you run JACK2 in non-sync mode, which adds an extra cycle of latency.

JACK1's continuing benefits over JACK2:

   * integration of a2jmidid so no need to use separate tools to make MIDI devices visible
   * integration of zita-a2j making it easy to use multiple audio devices from a single JACK instance

I believe that Filipe, the current maintainer of both JACK versions, plans to unify these features.

[ Parent | on HN ]

Re:Music Production on Guix System by justaj on Friday November 27, 2020 @09:33AM (#25228963)

> I believe that Filipe, the current maintainer of both JACK versions, plans to unify these features.

If you don't mind me asking: With PipeWire on the horizon, do you think this will still be a useful thing to spend time on?

[ Parent | on HN ]

Re:Music Production on Guix System by PaulDavisThe1st on Friday November 27, 2020 @11:10AM (#25229801)

I don't have much of an opinion. Precisely how PipeWire might affect (or not affect) the direct use of the existing implementations of the JACK API (JACK1 and JACK2) isn't of a lot of interest to me. But I trust Filipe to know what to do.

[ Parent | on HN ]