Sorry for writing in this discussion because i need some clarifications from you. I have always erperience some "jitter" sound even i have added a hardware purifier/ compression . I realised that the "jitter" sound from jamulus on occurs when there is high level of signal shown on my mixer board. May i know whetther this software did set a limiter or anything to control our input signal level? It would be great if you could share some information with me. Thank you! =)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I will read up more about that! =) So I was just wondering, whether there’s still any information I should take note of that was not shared as the “First Rule of Jamulus” if I wanna get rid of the “jitter” sound when I am using Jamulus. 😅
For the best tone quality you want to set the signal level in the analog portion of your system before it sees any software. If your signal is distorted because it is overdriven you can not repair it digitally. If, on the other hand, the signal is too weak you will have more noise than is necessary.
It sounds like you need to turn down the input volume on your mixer.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The client of this new version says it is version 3.5.9
The server of this new version says it is version 3.5.10
What is correct?
odroid@focal-server:/usr/src/jamulus/jamulus$ sudo service jamulus status
● jamulus.service - Jamulus-Server
Loaded: loaded (/etc/systemd/system/jamulus.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-07-19 11:29:58 UTC; 20s ago
Main PID: 4469 (Jamulus)
Tasks: 2 (limit: 1169)
Memory: 15.9M
CGroup: /system.slice/jamulus.service
└─4469 /usr/local/bin/Jamulus -s -n -F -e jamulusclassical.fischvolk.de:22524 -a StringsServer -u 10 -w Welcome to the Str>
Jul 19 11:29:58 focal-server jamulus[4469]: - server name for HTML status file: StringsServer
Jul 19 11:29:58 focal-server jamulus[4469]: - maximum number of channels: 10
Jul 19 11:29:58 focal-server jamulus[4469]: - welcome message: Welcome to the Strings Server St-Blaise running Jamulus 3.5.6
Jul 19 11:29:58 focal-server jamulus[4469]: - server info: Strings Server;St-Blaise;206;
Jul 19 11:29:58 focal-server jamulus[4469]: Recording state not initialised
Jul 19 11:29:58 focal-server jamulus[4469]: *** Jamulus, Version 3.5.10git
Jul 19 11:29:58 focal-server jamulus[4469]: *** Internet Jam Session Software
Jul 19 11:29:58 focal-server jamulus[4469]: *** Released under the GNU General Public License (GPL)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After you run git to get the latest sources, you can use git checkout to install the latest official release, instead of installing the latest version on github, which is why your versions shows as 3.5.10git, that's not the latest official release, that's the latest version on Github. The offical release is 3.5.9 as you've noted.
This is the command I use is something like this:
cd jamulus
git pull
git checkout r3_5_9
qmake "CONFIG+=nosound headless" Jamulus.pro`
make clean
sudo make install
Last edit: Rob Durkin 2020-07-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So you are saying that is the development version?
But why does it then show 3.5.9 when run as a client ?
It sure is strange that the same code shows different version numbers when run as client or server.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, I see now that under Win10 both client and server are V 3.5.9, it is just the linux server I am seeing 3.5.10git. If the git versions are all development versions it is time to get the word out, I see many many 3.X.Xgit versions in the server lists. I bet all those people would, like me, prefer to be using a released version.
I have been updating with simply:
sudo git pull
sudo make
I will try your version.
Don
Last edit: DonC 2020-07-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The reason why we don't describe how to get the latest released version from git in the way Rob describes is that it will complicate the installation instructions (and we don't want to keep updating the wiki manually with version numbers on each release).
However, now that Volker is identifying the latest release as such on git we can instruct people to use this link to get the latest official released sources using the Github alias for this:
I'll update the wiki. BTW it's quite important that we don't have various different ways of downloading and compiling Jamulus described on the wiki as that's going to make the docs much harder to maintain over time.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A new Jamulus software version is available: 3.5.9. Here are the changes:
new app icon for Jamulus, created by geheimerEichkater (#410)
support up to four different groups for the channels (#202)
support sorting faders by channel group
add support to change the GUI language (#297)
add special server list filter for filtering occupied servers by using "#" (#397)
update server UI to allow setting the jam recorder directory (like -R) (#228, #405)
redesign of the server dialog (e.g. added welcome message setting)
save and restore mixer state (like fader, mute, etc.) (#377)
note that saving/loading of settings only works if not connected
scale channel instrument picture in Compact skin mode
show maximum number of clients for servers in the serverlist, coded by dingodoppelt (#451)
log the number of connected clients on each new connection (#277)
move the Mute Myself button up to prevent accidentally disconnecting
bug fix: grouping faders in the client should be proportional (see discussion in #202, #419)
Hi Volker,
Sorry for writing in this discussion because i need some clarifications from you. I have always erperience some "jitter" sound even i have added a hardware purifier/ compression . I realised that the "jitter" sound from jamulus on occurs when there is high level of signal shown on my mixer board. May i know whetther this software did set a limiter or anything to control our input signal level? It would be great if you could share some information with me. Thank you! =)
There is no limiter implemented. But maybe inside the OPUS audio codec you will have some audio processing like this.
Ok!
I will read up more about that! =) So I was just wondering, whether there’s still any information I should take note of that was not shared as the “First Rule of Jamulus” if I wanna get rid of the “jitter” sound when I am using Jamulus. 😅
With Warmest Regards,
Irwin (阿 Win)
For the best tone quality you want to set the signal level in the analog portion of your system before it sees any software. If your signal is distorted because it is overdriven you can not repair it digitally. If, on the other hand, the signal is too weak you will have more noise than is necessary.
It sounds like you need to turn down the input volume on your mixer.
the issue i have is actually non consistent "jitter" sounds
Could it be that you are connected using wifi and not a wired connection to the Internet?
I get non-consistent noise if I try to use wifi.
I use lan cable cat 6 for the connection Of jamming though.
The client of this new version says it is version 3.5.9
The server of this new version says it is version 3.5.10
What is correct?
Hey Don,
After you run git to get the latest sources, you can use git checkout to install the latest official release, instead of installing the latest version on github, which is why your versions shows as 3.5.10git, that's not the latest official release, that's the latest version on Github. The offical release is 3.5.9 as you've noted.
This is the command I use is something like this:
Last edit: Rob Durkin 2020-07-21
So you are saying that is the development version?
But why does it then show 3.5.9 when run as a client ?
It sure is strange that the same code shows different version numbers when run as client or server.
Are you running the client and server on a Linux box? If so, I don't know why they'd show different versions. I only run the server on my Pi.
OK, I see now that under Win10 both client and server are V 3.5.9, it is just the linux server I am seeing 3.5.10git. If the git versions are all development versions it is time to get the word out, I see many many 3.X.Xgit versions in the server lists. I bet all those people would, like me, prefer to be using a released version.
I have been updating with simply:
I will try your version.
Don
Last edit: DonC 2020-07-21
Just a footnote on this.
The reason why we don't describe how to get the latest released version from git in the way Rob describes is that it will complicate the installation instructions (and we don't want to keep updating the wiki manually with version numbers on each release).
However, now that Volker is identifying the latest release as such on git we can instruct people to use this link to get the latest official released sources using the Github alias for this:
https://github.com/corrados/jamulus/releases/latest
I'll update the wiki. BTW it's quite important that we don't have various different ways of downloading and compiling Jamulus described on the wiki as that's going to make the docs much harder to maintain over time.
Just to check: may I connect to a 3.5.9 server from older clients? Thanks.
Yes, although some features like mute notifications and genre servers may
not be there depending on how old the client is. But they can still jam :-)