A Pretty Good Jacktrip Toolkit — FAQ — A collection of hints and tips

Navigation:

Toolkit – home page
Installation — Getting started — the short version
Installation — Getting started — the long version with screenshots
FAQ — A collection of hints and tips

This is a pretty disorganized collection right now.  It’s on the ToDo list to tidy things up a bit.

The screen is blank in GLISH.   Toggle back and forth between the Lish and Glish tabs a few times.  If that doesn’t work, close and reopen the Glish window.  The server is fine and the jacktrip session will continue without trouble, the GLISH-window-gizmo is a little flaky.  That flakiness is the main reason I added the more-reliable VNC server to the script.

Search for files.   Use the Nautilus file-manager — Applications/Accessories –> Files

Graphical text-editor.   Use the Kate text-editor — Applications/Accessories -> Kate

Change the size of the desktop.  
If using GLISH web interface:
—–  Applications/Settings/Settings Manager –> Display
If using the VNC server:
—–  Save your work and disconnect the VNC session
—–  Kill the VNC server from your local desktop ( type ” vncserver -kill :1 ” at the command line)
—–  Restart the VNC server with new geometry settings (” vncserver -geometry nnnnXnnnn “)
—–  Restart the VNC session

Where can I get a VNC client app?   A good option is RealVNC

Help!  How do I escape full-screen mode in RealVNC!  Been there.  I feel your pain.  Look **very** closely at the top center of the screen and you will see a hint of the drop down menu that appears when you hover your mouse over that spot.  It’ll look like this.  Et voila.  Note the other handy items hidden in there.

Apps are cluttered.  Spread them out between Workspaces (the four boxes in the upper right)

Format of jacktrip and Jmess commands.  Normal — “jacktrip” and “jmess” in a terminal window

Where does Jmess store it’s settings files?  In the Root home directory by default.

Where are QjackCtl and Ardour?  Applications/Multimedia

QjackCtl error!  “Could not open ALSA seqencer as a client”  What now?  This is something I’m working on.  It’s harmless, and happens because we’re using the Dummy driver, not the ALSA driver.  I’m trying to figure out how to avoid it.  For now, close the warnings and carry on.

Where is Audacity?  Audacity does not play well with Jack and is excluded for that reason.  The big issue for me is that it can only see one of the incoming performers at a time — so it can’t be used for multi-performer recording.  Use Ardour for recording.  If you still want to install Audacity, type ” sudo apt install audacity ” in a terminal window.

How do I share/download recordings and other files.  Anything stored in Root’s “Recordings” folder will be visible world wide via web browser.  I make that the Recordings folder the default file location for Ardour.  View those files with a web browser pointed at  http://[server’s IP address]/Recordings

Ardour track recordings.  The files are located several layers down the project folder.  Here’s the path: Recordings/[Project Name]/interchange/[Project Name]/audiofiles.  They’re stored as individual files, which makes them tedious to download.  Consider using the Nautilus file-manager to zip them into an archive: select them all, right-click and select “Compress…”

I want to read the script without logging into Linode.  Here’s a link to the current version of the script.