Opened 7 years ago
Closed 6 years ago
#54870 closed defect (fixed)
Update JACK 0.124.1 and add jack2
| Reported by: | sletz (Stéphane Letz) | Owned by: | neverpanic (Clemens Lang) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | raimue (Rainer Müller), kurthindenburg (Kurt Hindenburg) | |
| Port: | jack |
Description
JACK exists in two versions : JACK1 and JACK2 (see http://jackaudio.org/downloads/) The macport distributed package uses the old and unmaintained JACK1 0.124.1 version.
Please remove it since it confuses users.
Change History (11)
comment:1 Changed 7 years ago by raimue (Rainer Müller)
| Cc: | raimue added |
|---|---|
| Port: | jack added |
comment:2 Changed 7 years ago by mf2k (Frank Schima)
Why not just update it to the latest version 1.9.11-RC1?
comment:3 Changed 7 years ago by sletz (Stéphane Letz)
Yes if you can compile 1.9.11-RC1 (which is JACK2), this would be correct.
comment:5 Changed 7 years ago by sletz (Stéphane Letz)
I should add that 0.125 (= JACK1) is not uptodate on OS X (this is not the case on Linux....). On OS X 1.9.11 (= JACK2) is the official version.
comment:6 Changed 7 years ago by kurthindenburg (Kurt Hindenburg)
| Cc: | kurthindenburg added |
|---|---|
| Summary: | Please remove JACK 0.124.1 from macports → Update JACK 0.124.1 and add jack2 |
There's currently 22 ports that depend on jack - I don't think we can just remove it. I'd say update to latest jack1 version and add jack2 port. Then we can see if all the other ports can use jack2.
comment:7 Changed 7 years ago by sletz (Stéphane Letz)
jack2 has been the "official" version on OS X for years... (macports people never asked anything on jack dev list bit on that which is sad....) Why no simply trying to recompile all this 22 ports using jack2 ?
comment:8 follow-up: 9 Changed 7 years ago by kurthindenburg (Kurt Hindenburg)
From https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2
The short answer: Jack 1 and Jack 2 are equivalent implementations of the same protocol. Jack 2 was originally written to add multi-processor support and to rewrite the internals using C++. Programs compiled against Jack 1 will work with Jack 2 without recompile (and vice versa). Jack 2 was originally planned to replace Jack 1, but this is no longer so and they are considered equivalent implementations. JACK is a C API, and so the C++ rewrite in Jack 2 only matters to the people who program/maintain jack.
I'll update the port to 0.125 - Homebrew mentions they can't get jack2 to compile and i don't see a reason to try unless someone provides a patch.
comment:9 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to kurthindenburg:
Homebrew mentions they can't get jack2 to compile and i don't see a reason to try unless someone provides a patch.
Well the PR where that's mentioned is from 2013. Worth checking if things have improved since then.
comment:10 Changed 7 years ago by kurthindenburg (Kurt Hindenburg)
I can't get the current version or new 0.125 to actually work. When I get it to not crash, it hangs up when used. Also trying to get jack2 to compile isn't going well.
comment:11 Changed 6 years ago by neverpanic (Clemens Lang)
| Owner: | set to neverpanic |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Should JACK1 in general be considered unmaintained or would updating the jack port to 0.125 resolve this issue?