I have a zoom H4 connected to it, acting as a USB Cardwith microphone & headphone (Works without any driver on Mac or Windows, so working immediately on RPI).
Hi,
I've tested Jamulus on my Raspberry Pi 3 B. It compiled and worked fine as a client (with my Focusrite Scarlett) and a server too.
M. Volker, you did a great soft !
Thank you very very much.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I built Jamulus on my RPi3B, and the build went smoothly and it works great, as does the server. I am using it with a Behringer UMC202HD USB interface (through ALSA/Jack), which is showing too much latency. The USB interface does not show the latency on my W10 PC.
Any thoughts about improving the latency would be appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Exactly the same issue as chuck above. RP3b. Tested on both a UMC22 and UMC404 audio interface. Latest Buster RP OS. Jamulus giving overall delay circa 100ms. Played in jack settings no improvement noticed. Any ideaa?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My experience installing Jamulus (version ~3.5.12) on a stock Raspberry Pi 3B Plus h/w rev 1.3 running Raspbian 9.13 was that the lowest I can set the buffer size using qjackctl is 512 frames. If I select 256 frames or lower, qjackctl returns error:
"ALSA: Cannot open PCM device alsa_pcm for capture".
Jamulus works OK with frame size 512, but I'd like to get the latency lower, if possible. Would an add-on hardware sound module help with that?
Would an out-of-the-box Raspberry Pi 4B do any better?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After running ./raspijamulus.sh (on a raspberry pi4 with debian)
I got
The Jack server is not running. This software requires a Jack server to run. Normally if the Jack server is not running this software will automatically start the Jack server. It seems that this auto start has not worked. Try to start the Jack server manually.
I tried
qjackctl
but got
JackServer::Open failed with -1
Failed to open server
23:19:35.194 JACK was stopped
23:19:36.878 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I believe you have no USB sound card or device attached (see at the top of your log, where is says "using USB device: "), which may be why Jackd did not start.
Last edit: SIVA Frédéric 2020-03-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have realised that my build only worked thanks to a package I had installed earlier: libjack-jackd2-dev.
I have proposed a script correction on github and pull request.
BTW: I have also tested the RPI4 with a UM2 card (33 EUR!), it works like a charm.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried to run the raspijamulus.sh on my Rapsberry Pi4
The script ended up with an error message (attached).
I am not really a linux guru. Does anybody have an idea on how I can get Jamulus working on my RPI4?
Thanks for help
Just amazing! It worked out perfectly.
Now I have my Jamulus client running on the Rapsberry Pi4. I stil have too high overall delay (128ms) but I am working on that. Rob Durkin, I don't know who and where you are, but I know that you have immense skills. Thanks a lot to you and everybody else who is contributing to this fantastic project.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks DA, that's probably the nicest thing anyone has ever said about me! Most of the credit should go to SIVA Frédéric for writing the original Raspberry Pi server wiki instructions, and Volker for making great software that "just works". Also the Jamulus community is pretty good at helping each other out.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The server is the 8GB version, rev. 1.4. It was installed at the weekend and it seems to work OK, with responses very similar to my shared 'cloud' server.
The original client is the 4GB version, rev. 1.2. It has worked really well for over a month, with slightly better performance than the others in our group (ping 8 ms, O.D. 28 ms, so performance = ping + 20 ms).
The new client is the 2GB version, rev 1.2 (costs less!), which has been set up to be identical in all other respects. Disappointing! Performance is ping + 110 ms, which is unusable.
Has anybody done better than this with a Raspberry Pi4, 2GB? Has anyone had similar results? Is there a known solution?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, @DA, did you get the O.D. down from 128ms?Yes, qjack was not properly configured (buffer 1024!). Now with a buffer of 128 I have a performance of 21 ms. My RPi is a 4 GB version.DA
The server is the 8GB version, rev. 1.4. It was installed at the weekend and it seems to work OK, with responses very similar to my shared 'cloud' server.
The original client is the 4GB version, rev. 1.2. It has worked really well for over a month, with slightly better performance than the others in our group (ping 8 ms, O.D. 28 ms, so performance = ping + 20 ms).
The new client is the 2GB version, rev 1.2 (costs less!), which has been set up to be identical in all other respects. Disappointing! Performance is ping + 110 ms, which is unusable.
Has anybody done better than this with a Raspberry Pi4, 2GB? Has anyone had similar results? Is there a known solution?
On the Advanced tab in QJackCtl Settings (the one that says ‘Please do not touch these settings unless you know what you are doing.’!), I changed Output Device and Input Device from (default) to hw:CODEC (i.e. Behringer UCA-202).
Much better now.
It was a solution to another problem (QJackCtl cannot connect to client as server) but it has fixed this one too.
Last edit: Robin Rigby 2020-07-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
On the Advanced tab in QJackCtl Settings (the one that says ‘Please do not touch these settings unless you know what you are doing.’!), I changed Output Device and Input Device from (default) to hw:CODEC (i.e. Behringer UCA-202).
Much better now.
From: DA gikke@users.sourceforge.net
Sent: 28 July 2020 17:24
To: [llcon:discussion] 533517@discussion.llcon.p.re.sourceforge.net
Subject: [llcon:discussion] Re: Working Jamulus Client on Rapsberry 4
Sent from Yahoo Mail for iPad
Hi, @DA, did you get the O.D. down from 128ms?Yes, qjack was not properly configured (buffer 1024!). Now with a buffer of 128 I have a performance of 21 ms. My RPi is a 4 GB version.DA
On Tuesday, July 28, 2020, 11:13 AM, Robin Rigby robinr@users.sourceforge.net robinr@users.sourceforge.net wrote:
Hi, @DA, did you get the O.D. down from 128ms?
We now have three Raspberry Pi4s:
The server is the 8GB version, rev. 1.4. It was installed at the weekend and it seems to work OK, with responses very similar to my shared 'cloud' server.
The original client is the 4GB version, rev. 1.2. It has worked really well for over a month, with slightly better performance than the others in our group (ping 8 ms, O.D. 28 ms, so performance = ping + 20 ms).
The new client is the 2GB version, rev 1.2 (costs less!), which has been set up to be identical in all other respects. Disappointing! Performance is ping + 110 ms, which is unusable.
Has anybody done better than this with a Raspberry Pi4, 2GB? Has anyone had similar results? Is there a known solution?
Yepee - I managed to get Jamulus run on a regular Raspberry4 (4Gb) running latest Raspian with Desktop.
https://www.raspberrypi.org/downloads/raspberry-pi-desktop/
I have a zoom H4 connected to it, acting as a USB Cardwith microphone & headphone (Works without any driver on Mac or Windows, so working immediately on RPI).
I just followed instructions I found on the video: https://www.youtube.com/watch?v=n7WaU_QiYkc
Even with the GUI, CPU is always under 20%, so quality and latency are pretty good.
I love Jamulus.
Great to hear that it works fine on a Raspberry Pi 4. Thanks for the info.
Hi,
I've tested Jamulus on my Raspberry Pi 3 B. It compiled and worked fine as a client (with my Focusrite Scarlett) and a server too.
M. Volker, you did a great soft !
Thank you very very much.
I built Jamulus on my RPi3B, and the build went smoothly and it works great, as does the server. I am using it with a Behringer UMC202HD USB interface (through ALSA/Jack), which is showing too much latency. The USB interface does not show the latency on my W10 PC.
Any thoughts about improving the latency would be appreciated.
Exactly the same issue as chuck above. RP3b. Tested on both a UMC22 and UMC404 audio interface. Latest Buster RP OS. Jamulus giving overall delay circa 100ms. Played in jack settings no improvement noticed. Any ideaa?
What buffer size do you have in the Jack settings?
My experience installing Jamulus (version ~3.5.12) on a stock Raspberry Pi 3B Plus h/w rev 1.3 running Raspbian 9.13 was that the lowest I can set the buffer size using qjackctl is 512 frames. If I select 256 frames or lower, qjackctl returns error:
"ALSA: Cannot open PCM device alsa_pcm for capture".
Jamulus works OK with frame size 512, but I'd like to get the latency lower, if possible. Would an add-on hardware sound module help with that?
Would an out-of-the-box Raspberry Pi 4B do any better?
After running ./raspijamulus.sh (on a raspberry pi4 with debian)
I got
I tried
qjackctl
but got
Earlier messages include (as in screenshot)
exec of JACK server (command = "/usr/local/bin/jackd") failed: No such file or directory
I believe you have no USB sound card or device attached (see at the top of your log, where is says "using USB device: "), which may be why Jackd did not start.
Last edit: SIVA Frédéric 2020-03-26
Thank you
I have realised that my build only worked thanks to a package I had installed earlier: libjack-jackd2-dev.
I have proposed a script correction on github and pull request.
BTW: I have also tested the RPI4 with a UM2 card (33 EUR!), it works like a charm.
I tried to run the raspijamulus.sh on my Rapsberry Pi4
The script ended up with an error message (attached).
I am not really a linux guru. Does anybody have an idea on how I can get Jamulus working on my RPI4?
Thanks for help
is qmake available on your pi? The log seems to indicate it did not find it.
Thanks for your comment Frédéric. I am trying to figure out. As I said I am not an expert of Linux.
Perhaps run this command to update your dependencies, including Qt5
sudo apt-get install build-essential qtdeclarative5-dev qttools5-dev-tools libjack-jackd2-dev
Just amazing! It worked out perfectly.
Now I have my Jamulus client running on the Rapsberry Pi4. I stil have too high overall delay (128ms) but I am working on that. Rob Durkin, I don't know who and where you are, but I know that you have immense skills. Thanks a lot to you and everybody else who is contributing to this fantastic project.
Thanks DA, that's probably the nicest thing anyone has ever said about me! Most of the credit should go to SIVA Frédéric for writing the original Raspberry Pi server wiki instructions, and Volker for making great software that "just works". Also the Jamulus community is pretty good at helping each other out.
Hi, @DA, did you get the O.D. down from 128ms?
We now have three Raspberry Pi4s:
Has anybody done better than this with a Raspberry Pi4, 2GB? Has anyone had similar results? Is there a known solution?
Sent from Yahoo Mail for iPad
On Tuesday, July 28, 2020, 11:13 AM, Robin Rigby robinr@users.sourceforge.net wrote:
Hi, @DA, did you get the O.D. down from 128ms?
We now have three Raspberry Pi4s:
Has anybody done better than this with a Raspberry Pi4, 2GB? Has anyone had similar results? Is there a known solution?
Working Jamulus Client on Rapsberry 4
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/llcon/discussion/533517/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Thanks, but I changed the buffers from 1,024 to 128 this morning, That’s not my problem.
RPi version remains a possibility.
Last edit: Robin Rigby 2020-07-28
… but this fixed it.
On the Advanced tab in QJackCtl Settings (the one that says ‘Please do not touch these settings unless you know what you are doing.’!), I changed Output Device and Input Device from (default) to hw:CODEC (i.e. Behringer UCA-202).
Much better now.
It was a solution to another problem (QJackCtl cannot connect to client as server) but it has fixed this one too.
Last edit: Robin Rigby 2020-07-28
Well done Robin!Can you tell us how much latency you have now?DA
Sent from Yahoo Mail for iPad
On Tuesday, July 28, 2020, 7:36 PM, Robin Rigby robinr@users.sourceforge.net wrote:
… but this fixed it.
On the Advanced tab in QJackCtl Settings (the one that says ‘Please do not touch these settings unless you know what you are doing.’!), I changed Output Device and Input Device from (default) to hw:CODEC (i.e. Behringer UCA-202).
Much better now.
From: DA gikke@users.sourceforge.net
Sent: 28 July 2020 17:24
To: [llcon:discussion] 533517@discussion.llcon.p.re.sourceforge.net
Subject: [llcon:discussion] Re: Working Jamulus Client on Rapsberry 4
Sent from Yahoo Mail for iPad
Hi, @DA, did you get the O.D. down from 128ms?Yes, qjack was not properly configured (buffer 1024!). Now with a buffer of 128 I have a performance of 21 ms. My RPi is a 4 GB version.DA
On Tuesday, July 28, 2020, 11:13 AM, Robin Rigby robinr@users.sourceforge.net robinr@users.sourceforge.net wrote:
Hi, @DA, did you get the O.D. down from 128ms?
We now have three Raspberry Pi4s:
Has anybody done better than this with a Raspberry Pi4, 2GB? Has anyone had similar results? Is there a known solution?
Working Jamulus Client on Rapsberry 4
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/llcon/discussion/533517/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Working Jamulus Client on Rapsberry 4 https://sourceforge.net/p/llcon/discussion/533517/thread/1402605ef9/?limit=25#9f8f/61d3
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/llcon/discussion/533517/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Working Jamulus Client on Rapsberry 4
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/llcon/discussion/533517/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Just the same as the first one: ping + 20 ms
Hi all, documentation of Jamulus Server deployment on Raspberry 4 here: https://bernhard.hensler.net/jamulus-server-with-raspberry-pi-4/