hi Jane,
how about having both at the same time? that's what i'd doing with the PGJTT these days. that way i can run one or the other. i put them on the system with two different file names. so i can run jacktrip1.4 when i'm trying the new stuff and jacktrip when i don't want any surprises (like yesterday). this 2-line collection of commands will put the jacktrip1.4 binary on your machine and make it executable.
terminal command #1)
this downloads my PGJTT copy of Jacktrip 1.4 binary that is referred to in Chris's note, renames it "jacktrip1.4" and puts it in a safe spot on your linux machine. you don't have this file on your system already, and putting this one there won't disturb anything. here's the copy/paste version:
this string is saying... copy a file from a web-address (
curl) and overwrite the file if it's already on your system (
-o ). the location to write it to is... (
/usr/local/bin/jacktrip1.4) and the web-address to grab it from is... (
https://PGJTT.com/Binaries/jacktrip1.4 )
terminal command #2)
this makes that newly-loaded file executable
chmod +x /usr/local/bin/jacktrip1.4
you're doing everything from a terminal window on your Mac, logged into the Pi, right?
here's what it looks like for me, if i'm not running the X-windows system. this is normal if you're not using the desktop interface on your Pi. if you *are* using the desktop on the Pi to do all this, this command will open the cool new GUI.
root@localhost:~# jacktrip1.4
ERROR: Display not found. Make sure X or Wayland is running or try running jacktrip in command line mode.
(To display a list of command line options run "jacktrip -h")
try that suggested command to see the options:
root@localhost:~# jacktrip1.4 -h
JackTrip: A System for High-Quality Audio Network Performance
Copyright (c) 2008-2021 Juan-Pablo Caceres, Chris Chafe.
SoundWIRE group at CCRMA, Stanford University
This build of JackTrip is subject to LGPL license.
JackTrip source code is released under MIT and GPL licenses.
See LICENSE.md file for more information.
Usage: jacktrip [-s|-c|-S|-C hostIPAddressOrURL] [options]
REQUIRED ARGUMENTS: One of:
-s, --server Run in P2P Server Mode
-c, --client <peer_hostname_or_IP_num> Run in P2P Client Mode
-S, --jacktripserver Run in Hub Server Mode
-C, --pingtoserver <peer_name_or_IP> Run in Hub Client Mode
... and so forth. there's a bunch more stuff, but you get the idea... it's working and it's Jacktrip 1.4
here's the command to test a bare-bones hub server
root@localhost:~# jacktrip1.4 -S
mThreadPool default maxThreadCount = 2
mThreadPool maxThreadCount previously set to 32
JackTrip HUB SERVER: UDP Base Port set to 61002
JackTrip HUB SERVER: Waiting for client connections...
JackTrip HUB SERVER: Hub auto audio patch setting = 0 (server-to-clients)
=======================================================
meanwhile plain "jacktrip" starts a regular Jacktrip 1.3 session -- all your existing stuff is undisturbed
root@localhost:~# jacktrip -S
mThreadPool default maxThreadCount = 2
mThreadPool maxThreadCount set to 32
JackTrip HUB SERVER: UDP Base Port set to 61002
JackTrip HUB SERVER: Waiting for client connections...
JackTrip HUB SERVER: Hub auto audio patch setting = 0 (server-to-clients)
=======================================================
two commands... that's all it takes. :-)
mike