New Jamulus Release 3.5.4

[Volker Fischer]

A new Jamulus software version is available: 3.5.4. Here are the changes:

• introduce genre-based server lists (#139)

• implement panning for channels, coded by tarmoj (#52, #145)

• added an indicator that another client has muted me (#257)

• move central server type dropdown to connection setup (#157)

• added vocal bass/tenor/alto/soprano instrument icons created by Alberstein8 (#131)

• support intermediate Reaper RPP file while recording, coded by pljones (#170)

• save client settings on Linux cmdline termination signal, coded by pljones (#70)

• added translation: Italian by dzpex (#249)

• bug fix: fixed misaligned tracks in recordings, coded by snayler, improved by pljones (#234)

[Nick Veit]

How do you set the Genre on Ubuntu?

[Volker Fischer]

The same way as under Windows. Are you questioning the server operation or the client operation? For the client you choose the genre when opening the connect dialog on the top left drop down box.

[Nick Veit]

Thanks Volker. I found how to set the server Genre in the updated documentation at https://github.com/corrados/jamulus/wiki/Command-Line-Options. I understand you are operating separate Cerntral Servers for each genre determined by port number.

[Volker Fischer]

No, not only the port number. The server lists are now stored on different physical servers. Two are hosted at my server. Two are hosted at pljones's server and one is hosted at another server.

[Nick Veit]

I note both the host name and port are different for each genre?

Also, I am seeing a pan control above the fader on the central server but not on my own server. To upgrade my server in Ubuntu I simply did a Git again and followed Simon's instructions in the hope of compiling the new version.

I used "git clone https://github.com/corrados/jamulus.git llcon-jamulus". However, using "sudo systemctl status jamulus" it said I was using 3.4.5 a while back. Given my ignorance of Ubuntu I am concerned the git command is picking up the latest version not the latest released version and I do not understand how to simply upgrade and check the actual version running. Or is the lack of pan control caused by something else?

[Volker Fischer]

It should be:
git clone https://github.com/corrados/jamulus.git
without the "llcon-jamulus". Can you please try if this works for you?

[Nick Veit]

I am frustrated at my lack of Ubuntu knowledge and the apparent conflict between Simon's instructions at https://www.facebook.com/notes/jamulus-online-musicianssingers-jamming/howto-idiots-guide-to-installing-jamulus-server-on-amazon-aws-lightsail-ubuntu-i/507719749802976/ and the official instructions I later found at https://github.com/corrados/jamulus/wiki/Running-a-Server (<not taking me to the right page !!!)

I suspect I will not be the last to ask for one official guide that provides all the steps, concisely and includes an upgrade method. On every recent upgrade I have set up a server from scratch using Simon's method (no way for me to upgrade). I have then added tweaks such as No-IP.

I would rather follow your advice as the author. I would rather not look up what every Ubuntu command does to fix issues. I am asking myself the following questions instead of playing music:

Should I continue to set up a new server every time there is an update
Should I continue to follow Simon's instructions or are they wrong (e.g. delivering me beta versions not officially released).
How do I move from Simon's approach to leaving off the "llcon-jamulus" which I guess states the compile folder. He then moves this under bin - I cannot as it errors with files already there...

I am now fighting my way thru two sets of instructions and using google instead of simply upgrading....should I start from scratch with Simon's instructions or what?

[Volker Fischer]

I just tried it out, "git clone https://github.com/corrados/jamulus.git llcon-jamulus" works also. So Simon's instructions are ok.

e.g. delivering me beta verions not officially released

If you use the command as given in Simon's instructions you check out the most recent code which is not an official release. To use an official release version, you have to specify this, e.g.,

cd llcon-jamulus
git pull
git checkout r3_5_4

You can find the tag names here: https://github.com/corrados/jamulus/releases

Sound I continue to set up a new server every time there is an update

To get the latest features (e.g. the new panning) then, yes, it is a good idea to update to the newest Jamulus version. But it should not be necessary to setup a complete new server. It should be possible to upgrade your existing server.

To upgrade your existing server to the newest Jamulus release, you can try the following:

First, open a terminal to your server.
Then type:

cd llcon-jamulus
git pull
git checkout r3_5_4
qmake "CONFIG+=nosound" Jamulus.pro
make
sudo cp Jamulus /usr/local/bin/llcon-jamulus/
sudo systemctl restart jamulus

Can you please try that out and report back if it worked?

[Rob Durkin]

Hey Volker,

Working on upgrading a Raspberry Pi.
This command
git checkout r3_5_4
returns the error "error: pathspec 'r3_5_4' did not match any file(s) known to git"

inside the llcon-jamulus folder I simply ran
git checkout
and got this result "Your branch is up to date with 'origin/master'."

Note: I'm using the Raspberry Pi instructions, which say to use git clone https://git.code.sf.net/p/llcon/jamulus llcon-jamulus to pull the source code, which is probably why the r3_5_4 folder doesn't exist on my system.****

Edit:
Here is what I did to upgrade my Raspberry Pi server, I installed the binary into the usr/local/bin folder:

cd llcon-jamulus/
git pull
git checkout
qmake "CONFIG+=nosound" Jamulus.pro
make
sudo systemctl stop jamulus
sudo cp Jamulus /usr/local/bin/Jamulus
sudo systemctl start jamulus

And that worked great. Now I need to learn how to use the new central server settings.

[Rob Durkin]

Question: When I'm compiling, should I use make or qmake? The headless server guide says to use qmake.

Edit: nevermind, I used qmake and then make as your instructions said. I'm still unclear on what the difference is though so I'll have to read-up on that.

[Volker Fischer]

This command
git checkout r3_5_4
returns the error "error: pathspec 'r3_5_4' did not match any file(s) known to git"

You need to make a

git pull

first. Then it should work.

[Rob Durkin]

I installed initially from here,
git clone https://git.code.sf.net/p/llcon/jamulus

That's the location in the Raspberry Pi wiki instructions, which is why the git checkout r3_5_4 command failed, I don't have that folder. I did use git pull and that worked to get 3.5.4 and compile, so it's all good.

[hk1020]

Same here. There are no tags on the sourceforge git. Should we switch to github? And what's the relation between sourceforge git and github anyway?

[Volker Fischer]

Yes, definitely. Only use the github repo. Can you please edit the Wiki and correct that? Thanks.

[Rob Durkin]

Volker-

I changed the Raspberry Pi wiki from this:
1. Use the link to Download Snapshot to get the latest sources, or clone with git: git clone https://git.code.sf.net/p/llcon/jamulus llcon-jamulus

To this:

1. Find the latest official tagged release on this list: https://github.com/corrados/jamulus/releases
2. Use git to clone the source files to your system: 'git clone https://github.com/corrados/jamulus.git llcon-jamulus', this will create a local folder named llcon-jamulus with the files to compile
3. If necessary, unpack sources with tar xvf Jam*.gz
4. Checkout the latest official release, for example: 'git checkout r3_5_4'

Let me know if that looks OK. Also the Linux install wiki notes reference the Download Snaphot on Sourceforge, should that be removed as well?

[Volker Fischer]

Thanks. You actually do not need the llcon-jamulus. If you do not use that, simply a directory called "jamulus" is created.
Also, if you clone from git, you do not need to untar the sources. They are not compressed.

[Rob Durkin]

I flogged the Raspberry Pi instructions, take a look and see if I missed anything, Raspberry Pi Wiki

[Volker Fischer]

Looks good, thank you.

[hk1020]

Step 7 should be

sudo make install

which will move the executable to /usr/local/bin/Jamulus

[Rob Durkin]

I've added that, thanks for the tip.

[Robin Rigby]

Can you please update the dox?

https://github.com/corrados/jamulus/wiki/Installation-for-Linux
Compile this bad boy

R

[Gilgongo]

The Download Snaphot link is for people who don't have git installed (it's not in by default on some distros like Ubutu Desktop).

The git checkout step is something I wondered about including in the client and server install docs. I didn't in the end becuase the Jamulus "git release" has been very stable and I didn't want to add more complications with looking up the latest release and whatnot (the Jamulus Linux install looks complicated enough as it is).

BTW if Volker remembers to hit the "publish" button then this URL will always have the latest release ;-)

https://github.com/corrados/jamulus/releases/latest

Also BTW I'm a little wary of repeating info in more than one place on the wiki. If Jamulus changes something (which in fact it's about to with the "headless" build type - coincdentally helping RPi builds), then we have to change things in multiple places. There's always a balance between readability and maintainability of the docs, but it may be "safer" to simply refer people to a single set of instructions for getting Jamulus.

That is:

https://github.com/corrados/jamulus/wiki/Installation-for-Linux#get-jamulus

then

https://github.com/corrados/jamulus/wiki/Installation-for-Linux#install-the-dependent-packages

EDIT: You also need the make clean step, apparently, since it "is essential to remove the automatically generated Qt files which are present in the .tar.gz file and may not match the Qt version you are using."

**Hmm. If I may, can I make some tweaks to the RPi page to aid maintainability? **

[Nick Veit]

Volker...your help is much appreciated. I'm going for a long walk and will use your info with a refreshed mind then report back. :)

[Nick Veit]

Thanks...up and running now. Pan and new server registrations working and I learnt a little more.