I am trying to run JamulusOS 1.03 on an Intel compute stick, m3-6y30 processor, 4G RAM, built-in Intel sound card, which 'aplay -l' lists as card0. I try to start the jamulus client, but it dies with a jackd message.
pulseaudio was at first running, and got in the way. I could ask that future versions of JamulusOS come with a pulseaudio.service file so pulseaudio can be stopped with 'systemctl'.
I found out how to turn off pulsaudio with the conf files in /etc/default and rebooting. jackd still won't start, whether I start it from 'qjackctl' or from the command line.
I have run Jamulus under Windows 10 on the very same compute stick. I was able to connect to a server that a friend of my has running. I have since ordered an ethernet-to-usb adapter, because I can see the latency through wi-fi is killing me. BUT: the jamulus client runs on my hardware with Windows 10, even though it doesn't run well.
So why won't jackd start under ubuntu/JamulusOS?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Check that your jack settings are ok for Jamulus (it only supports 48000Hz).
In the case you set the good sample rate then please try the 1.05 version. It has support for updating Jamulus and do various check on jack settings before starting Jamulus.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you, Laurent. Unfortunately, your suggestions don't help.
I don't know what the Jack settings are supposed to be, so I can't check them. The sample rate is set to 48000, and the audio interface is set to the card I have. I don't know what other settings should be.
I downloaded JamulusOS 1.05. It does not fix any problems
This version has a hardware check that didn't work under 1.03. It says my interface is slow (I knew that), and it says that jack won't work with Intel audio hardware I have. But Jamulus runs just fine with Windows on the same hardware!
When I try to start Jamulus from the desktop icon, or from the command line, the GUI never starts. See below when I try to update....
The error message is the same whether I try to start Jamulus or qjackctl:
ALSA: Cannot open PCM device alsa_pcm for playback.
So, OK 1.05 has a Jamulus upgrader -- but when I start the upgrader, it says to check the version I'm running by using the ABOUT menu option. I can't do that because the gui won't start. I tried versions 3_5_3, 3_5_2, and 3_5_1. None of them will run.
I'm trying so hard because there is a huge need for Jamulus-on-a-stick. I want this to work so badly. I know a bunch of musicians who need it, and the choir at church could use it, too.
Last edit: Kathleen Caywood 2020-05-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Many thanks, Laurent, for creating and distributing Jamulus OS v1.06. Unfortunately for me, it does not correct the problems I have with it.
The Jamulus client runs just fine under Windows 10 on the same hardware. I just looked, and I cannot find a version number for the Jamulus program. I downloaded and installed it on 12 May; it would be whatever was current on sourceforge that day.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Jamulus hardware check give you three parameters for each proposed setup:
the Frames/period
the sample rate
the name of the sound card (ALSA short name)
Select one setup and report those three parameters in qjackctl app.
Go to whiskermenu and type qjackctl and press enter.
Once in the qjackctl application, click on the setup button. In parameters tab, set the frames/period, the sample rate and select your device (ALSA short name). The other parameters should work with defaults.
Once you are done, save your change.
Stop jack with the stop button in qjackctl app if jack is running and restart it with the start button (the new settngs will take effect).
Now your jack setting should work and you should be able to start Jamulus.
I tried versions 3.5.2, 3.5.3, and 3.5.4. The same error message appears with all 3 versions.
I could not find out how to get the version of jamulus that runs successfully on Windows. I think it is 3.5.2. Whatever it is, it continues to connect to jamulus servers. ASIO4ALL reports 128 frames and 48000 samples/second.
Last edit: Kathleen Caywood 2020-05-24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Annoying, it's possible that your sound card model is not well supported by ALSA driver. The fact that it works on windows does not imply that it works on Linux.
The Jamulus version installed does not have influence on jack sound server.
So first, try to have jack sound server running and then you will upgrade your Jamulus installation if needed.
If at least one of these setup works, please open a ticket in the bug tracker. https://sourceforge.net/p/jamulus-os/tickets/. You can add to the ticket the output of the following command (press CTRL+ALT+t, copy/past the command, press ENTER):
jamulus-audio-check -d
Last edit: Laurent Schwartz 2020-05-24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, so none of the jack setups worked with the sound card on the Intel compute stick.
However, my main linux machine is Ryzen 5 1400 with 16M RAM, running ubuntu 18.04. I didn't want to use this machine because I have 3 virtual servers running on it, plus my unbuntu apps -- it takes a while to shut it all down.
I took the time the other day to shut everything down and boot from Jamulus OS 1.06 usb stick. I selected one of the sound cards, based on the hardware check program. Both jack and jamulus started right away and I was able to connect to a couple of servers.
I am still waiting for better sound hardware to use with the compute stick, so I can be ready to jam any time. I appreciate the work you have done on Jamulus OS. I will recommend it to my friends.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am trying to run JamulusOS 1.03 on an Intel compute stick, m3-6y30 processor, 4G RAM, built-in Intel sound card, which 'aplay -l' lists as card0. I try to start the jamulus client, but it dies with a jackd message.
pulseaudio was at first running, and got in the way. I could ask that future versions of JamulusOS come with a pulseaudio.service file so pulseaudio can be stopped with 'systemctl'.
I found out how to turn off pulsaudio with the conf files in /etc/default and rebooting. jackd still won't start, whether I start it from 'qjackctl' or from the command line.
I have run Jamulus under Windows 10 on the very same compute stick. I was able to connect to a server that a friend of my has running. I have since ordered an ethernet-to-usb adapter, because I can see the latency through wi-fi is killing me. BUT: the jamulus client runs on my hardware with Windows 10, even though it doesn't run well.
So why won't jackd start under ubuntu/JamulusOS?
Check that your jack settings are ok for Jamulus (it only supports 48000Hz).
In the case you set the good sample rate then please try the 1.05 version. It has support for updating Jamulus and do various check on jack settings before starting Jamulus.
Thank you, Laurent. Unfortunately, your suggestions don't help.
ALSA: Cannot open PCM device alsa_pcm for playback.
So, OK 1.05 has a Jamulus upgrader -- but when I start the upgrader, it says to check the version I'm running by using the ABOUT menu option. I can't do that because the gui won't start. I tried versions 3_5_3, 3_5_2, and 3_5_1. None of them will run.
I'm trying so hard because there is a huge need for Jamulus-on-a-stick. I want this to work so badly. I know a bunch of musicians who need it, and the choir at church could use it, too.
Last edit: Kathleen Caywood 2020-05-17
Many thanks, Laurent, for creating and distributing Jamulus OS v1.06. Unfortunately for me, it does not correct the problems I have with it.
The Jamulus client runs just fine under Windows 10 on the same hardware. I just looked, and I cannot find a version number for the Jamulus program. I downloaded and installed it on 12 May; it would be whatever was current on sourceforge that day.
The Jamulus hardware check give you three parameters for each proposed setup:
Select one setup and report those three parameters in qjackctl app.
Go to whiskermenu and type qjackctl and press enter.
Once in the qjackctl application, click on the setup button. In parameters tab, set the frames/period, the sample rate and select your device (ALSA short name). The other parameters should work with defaults.
Once you are done, save your change.
Stop jack with the stop button in qjackctl app if jack is running and restart it with the start button (the new settngs will take effect).
Now your jack setting should work and you should be able to start Jamulus.
https://www.youtube.com/watch?v=DBUoEmRz24E
Hope this helps
I regret to say that the hardware check does not work. Here is the output from the sound card check:
I tried versions 3.5.2, 3.5.3, and 3.5.4. The same error message appears with all 3 versions.
I could not find out how to get the version of jamulus that runs successfully on Windows. I think it is 3.5.2. Whatever it is, it continues to connect to jamulus servers. ASIO4ALL reports 128 frames and 48000 samples/second.
Last edit: Kathleen Caywood 2020-05-24
Annoying, it's possible that your sound card model is not well supported by ALSA driver. The fact that it works on windows does not imply that it works on Linux.
Please try the following jack setups in qjackctl:
Interface=PCH / 512 Frames / 48000 hz
Interface=PCH / 256 Frames / 48000Hz
Interface=PCH / 128 Frames / 48000Hz
The Jamulus version installed does not have influence on jack sound server.
So first, try to have jack sound server running and then you will upgrade your Jamulus installation if needed.
If at least one of these setup works, please open a ticket in the bug tracker. https://sourceforge.net/p/jamulus-os/tickets/. You can add to the ticket the output of the following command (press CTRL+ALT+t, copy/past the command, press ENTER):
jamulus-audio-check -dLast edit: Laurent Schwartz 2020-05-24
Ok, so none of the jack setups worked with the sound card on the Intel compute stick.
However, my main linux machine is Ryzen 5 1400 with 16M RAM, running ubuntu 18.04. I didn't want to use this machine because I have 3 virtual servers running on it, plus my unbuntu apps -- it takes a while to shut it all down.
I took the time the other day to shut everything down and boot from Jamulus OS 1.06 usb stick. I selected one of the sound cards, based on the hardware check program. Both jack and jamulus started right away and I was able to connect to a couple of servers.
I am still waiting for better sound hardware to use with the compute stick, so I can be ready to jam any time. I appreciate the work you have done on Jamulus OS. I will recommend it to my friends.