Opened 11 years ago

Last modified 9 years ago

#40745 new request

jack2

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: eu@…, alexkowel@…, keybounce, kurthindenburg (Kurt Hindenburg)
Port:

Description (last modified by kurthindenburg (Kurt Hindenburg))

The jack homepage mentions jack2. If jack2 is significantly different from jack1 then we should probably create a new jack2 port for it. Or if it is backward compatible then we could update the jack port to this version.

Change History (5)

comment:1 Changed 11 years ago by alexkowel@…

Cc: alexkowel@… added

Cc Me!

comment:2 Changed 10 years ago by keybounce

Cc: keybounce@… added

Cc Me!

comment:3 Changed 9 years ago by kurthindenburg (Kurt Hindenburg)

Cc: khindenburg@… added

Cc Me!

comment:4 Changed 9 years ago by kurthindenburg (Kurt Hindenburg)

Description: modified (diff)

From https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2

Programs compiled against Jack 1 will work with Jack 2 without recompile (and vice versa)

....

Are we going to have two JACKs forever? No. However nobody forsees a sane way to choose between Jack 1 and Jack 2

comment:5 Changed 9 years ago by keybounce

I thought that Jack 2, aka multiprocessor / multithreaded Jack server, was the better choice except on single-core machines.

aha! From that linked page:

Many of the Jack 1 developers disagree with the implementation details and class hierarchy of Jack 2, to the point where they would prefer working on the Jack 1 code.

In other words, it's a case of "what code base do the different developers want to hack on".

Last edited 9 years ago by keybounce (previous) (diff)
Note: See TracTickets for help on using tickets.