Welcome to jambox-pi-gen Discussions!

[kdoren]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[jp8]

Hi Kevin,
In the README, you mention the Pi has issues with USB hotplug. Do you have any details about it? For me it seems to work, but I am wondering if there is something I should watch for.
Kind regards,
JP

[kdoren]

Main issue is hardware, but software issues are also possible.

The hardware issue is that you can easily crash the Pi. Hot-plugging a USB device into a Raspberry Pi, especially something like a USB-powered audio interface, can cause a power glitch & crash (it's power supply and filtering don't seem to handle this very well).

The software issue is that, depending on what you plug in, a reboot might be required in order for the device to be properly recognized. In my opinion, software handling of hot-plugged USB devices in linux leaves something to be desired.

You can hot-plug a USB mouse or keyboard and be fine. But USB-powered audio interface? I advise against it.

[razze2006]

Hello,

I'm not an experienced linux user, but I wanted to try and use a Pi4b to run jamulus as a portable alternative to my laptop. At the moment i'm struggling to even get my Presonus Audiobox USB 96 to even get connected to the Pi!
I'm getting an endless cycle of the device being recognised and then found not to be an MTP device and subsequentluy disconnected.

Any library i need to install? libmtp perhaps? I'd love to hear any ideas :)

Cheers,
Marco

[kdoren]

@marco Carlos got this working with his A96.
Here's what did the trick:

# in /etc/jackdrc.conf
DEVICE=hw:A96

[razze2006]

Nice to wake up and somebody hands you the solution to the problem you had before you went to bed. I'll test today and report

[CAguayo]

I am seeing this same issue, but am an experienced Linux user, but not an audio expert. I would be happy to help diagnose, maybe discuss in the Slack channel? Thanks, Carlos

…

On Thu, Jan 7, 2021 at 10:08 AM razze2006 ***@***.***> wrote: Hello, I'm not an experienced linux user, but I wanted to try and use a Pi4b to run jamulus as a portable alternative to my laptop. At the moment i'm struggling to even get my Presonus Audiobox USB 96 to even get connected to the Pi! I'm getting an endless cycle of the device being recognised and then found not to be an MTP device and subsequentluy disconnected. Any library i need to install? libmtp perhaps? I'd love to hear any ideas :) Cheers, Marco — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKJTEZRHG5C3L4EF4W3SATSYX2AXANCNFSM4VH63KSA> .

[razze2006]

I'll set up slack and try. Should there be a slack workspace i should be able to join with the email I use to log into github? I'm in the uk, so I'll have to wait until tomorrow to do it

[CAguayo]

The slack team I mentioned can be joined by following this link: https://join.slack.com/t/jacktripcollaboration/shared_invite/zt-g3iz2nkh-d9tQeOZItS30SZUELaXf1A The #jambox channel is where relevant discussion would be found. Carlos

…

On Thu, Jan 7, 2021 at 2:24 PM razze2006 ***@***.***> wrote: I'll set up slack and try. Should there be a slack workspace i should be able to join with the email I use to log into github? I'm in the uk, so I'll have to wait until tomorrow to do it — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKJTE7OLJV732IXPW7P6JLSYYYBFANCNFSM4VH63KSA> .

[razze2006]

I joined, thanks. I'm going to use jambox for jamulus, but the setting up of the audio interface should be common to both jacktrip and jamulus

[Ghost6772]

Hello
i do not know anything about linux, but i am using the jambox image on a RasPi.
Now i wonder how i could start Jamulus as a server. I thing i just have to add the parameter -s. But where?
How/where can i find the right file an what do exactly do i have to do there?

[kdoren]

@Ghost6772
I have jamulus server configured as a systemd service, to start it:

sudo systemctl start jamulus-server

If you need to make any configuration changes, this should be done in /home/pi/.config/Jamulus/jamulus-server.conf

This is descibed in the desktop README.md file

• Running a Jamulus Server
  • Jamulus server can run on Raspberry Pi. It's best run on its own separate box. Running on the same Raspberry Pi that runs a Jamulus Client will increase jitter.
  • Your internet connection needs enough upstream bandwidth to send streams to multiple clients. DSL and Cable internet typically don't have very much.
  • You router will likely require port forwarding set up.
  • Customizable Settings are described in file /home/pi/.config/Jamulus/jamulus-server.conf
  • jamulus-server doesn't need the "jack" service, so stop it unless you're running a client: "sudo systemctl stop jack"
  • To start: "sudo systemctl start jamulus-server"

[Ghost6772]

Hey, many many thanks for the quick reply.
Yes, i will use a separate box. And Port forwarding is no problem I know how to configure this.
My internet bandwidth is 300 Mbps download and 30Mbps upload. Do you think this will work?
I tried the two sudo commands stop jack and start server. They both work fine. Thanks a lot.
But i cannot find the /home/pi/.config/Jamulus/jamulus-server.conf
What does the little dot before config meamn? I cannot find a config directory in /home/pi/
Sorry, but these are my first steps with raspberry and linux
Many thanks

[kdoren]

@Ghost6772 the little dot before config is what makes it a hidden directory (that's standard for a user's config directory in this distro). In the file manager, you won't see this directory unless you select View -> Show Hidden.

You should be able to copy and paste the following command into a terminal window to see/edit it.
To copy/paste in noVNC is 2 steps, first you need to paste into the clipboard that pulls out from the left, then you can edit -> paste in the terminal window. FYI "~" is short for /home/<user> ( in this case /home/pi )

leafpad ~/.config/Jamulus/jamulus-server.conf

[Ghost6772]

Thank you so much for your answer in the middle of the night :-)
It worked fine!

[Ghost6772]

Which is correct image version?
Is the Jambox release 1.2.0 only for RasPi with 8GB Ram, or will it work even fine on a Raspberry with only 4GB?
Or do I have to use an older image for RasPi 4GB?

[kdoren]

@Ghost6772 version 1.2.0 is the latest release, it should work on RPi4 of any memory size. RPi3 should also works. RPi400 works but currently requires a change in /boot/config.txt.

[Ghost6772]

Hi, we tested the jambox today with 4 raspberries to connect. But we had problems with Jamulus and with sonobus.

1. One of the raspberries said: ALSA Device card 2 not availiable: PLAY_RESULT: 1, RECORD_RESULT:1 (when trying to start Jamulus, but it worked with the same type of audio interface here when I tested it.)

2. Sonobus started without problems on each rasberry and everyone could connect. But then one of us lost connection an it said we should enable port forwarding on the router. But i cannot check the option in sonobus. I can check, but sonobus looses the check when leaving the option window.

Maybe anybody has an idea?

Many thanks :-)

[kdoren]

@Ghost6772

1. the Jamulus/sonobus start scripts are looking in /etc/jackdrc.conf for DEVICE to figure out what audio device is in use. Inside /etc/jackdrc.conf, If you haven't set value for DEVICE, by default it will choose the last capture device it sees (by running "arecord -l"). If that's not the device you want, you can hard-set a value for DEVICE, in the form DEVICE=hw:n,0, where n is the card number shown in "arecord -l".

So (1) what do you see when you run "arecord -l"? do you see the interface listed?, and (2) did you set "DEVICE" in /etc/jackdrc.conf, and if so, to what.

2. If your router requires you to set up port forwarding, that's done in the router itself. What option were you trying to set in SonoBus that lost the setting?

[Ghost6772]

Hello,
the "arecord -l" command can i test only in a couple of days because the raspberry is not here. I gave it to a friend. I will give you feedback then.

In SonoBus it's the option "use specific UDP port" i tried to check. Because otherwise i will not know which port i should configure for portforwarding in my router.

Many thanks :-)

[kdoren]

@Ghost6772 Settings changes should save. If they aren't saving, try a different micro SD card. Another test: write something to a file, and make sure you can read it after a reboot.

[Ghost6772]

In general setting changes do save. e.g the option "autoreconnect to last group" works fine. Only the option "use specific UDP port" does not save. But i will try what you said. New card , new flash, new luck :-) I will give you feedback then.....

[ve3meo]

I've had a Pi 4B kit for over a week and was struggling to get it to drive an old DVI monitor whose power supply I repaired just for this purpose and which worked up to a month ago with my laptop's HDMI port. No success there so I plugged it into the replacement monitor, installed Jamulus on Raspbian and tried to get it going. No luck sorting out Jack. So I finally read through the JamBox instructions and finally succeeded in flashing an image onto the 4GB card I pulled from my wife's defunct Kobo Reader. Fired it up and voila! JamBox sorted out the first audio interface I tried. More on that later. And noVNC/urlrelay works a charm on my pc but not my old iPad 2 nor the phones (screen too small). I imagine the iPad's browser does not support JavaScript.

Thanks, Kevin!

[kdoren]

@ve3meo I personally use an iPad in my setup, but not one that old, I think mine is a 2018 model. It works fine with noVNC, with several different browsers (I usually use Safari but Firefox/Chrome also work). Works in a phone too - the small screen is awkward, but is OK in a pinch if you need to get in, launch and connect.

[ve3meo]

@kdoren so no tablet but I dug out a 18-year old IBM ThinkPad T41 from a box in the basement. After trying my Jamulus-OS stick on it and being told it was i686 CPU and not 64-bit and so it wouldn't work, I let it boot up to Windows XP to see if its browser would work with noVNC. It finally did after some minutes probably doing an update of Chrome from 32 to 49, the last version offered for XP. To my delight, it succeeded and seems to work very well. I loved that old machine: quiet, comfortable, 1080X768 screen's still bright.

I tried 3 USB adapters, a Logitech H590 USB headset and Roland QUAD-CAPTURE USB audio interface. All but the Roland were found by your auto setup routine.

1. Trond AC2: seems stable, low latency but needs a high output TRRS headset or mic/earbuds which I don't have
2. Trond AC3: versatile in that it can take TRRS or a TRS mic and TRS headphones; also low latency but suffered from some drifting in and out of a buzzsaw distortion of the audio; maybe higher mic gain than AC2 but not enough for my earbuds mic.
3. plugable(TM) USB-AUDIO: stable, higher latency, stereo input and output, really more like line level sensitivity. That's what's pictured and I've settled on for now. Had to plug my 35-yr old Realistic dynamic mic into my 45-yr old Yamaha Hi-Fi stereo and run its headphone output across the room to the plugable input. The plugable is a hissy device; the RTLutility reported a noise floor of ~-65dBFS.
4. Logitech H590 USB headset: same issue as I experienced on other systems. It has active mic noise suppression that cannot be turned off and gates the microphone off or lowers its gain below a certain volume. Also has an overly active AGC for the headphones and can crank up the gain to the point of feedback howl (maybe defective in that it should then reduce gain but it can howl on)
5. QUAD-CAPTURE: wasn't surprised. I don't think it was produced to support Linux but I must admit I didn't even check to see if it started - maybe the Pi power supply through the USB port couldn't deliver the current needed.

The ThinkPad has a 1.6GHz Pentium with 1GB RAM, running Win XP Pro 2002 SP3. My Pi has 4X the cores, twice the arithmetic width and 4X RAM!

[kdoren]

@ve3meo @CAguayo Even the cheapest USB Audio Interfaces can have internal controls and switches that might be useful (sometimes a bewildering array of them) They're not necessarily exposed through any GUI, but you might be able to get to them via the "amixer" command.

For example, it might be possible to disable AGC. Here's a cheap one (Sabrent I think, card 1 in this case) that has AGC:

# look for a control with "Auto" in the name
pi@jambox:~ $ amixer -c 1 | grep Auto
Simple mixer control 'Auto Gain Control',0

# get the value of mixer control "Auto Gain Control
pi@jambox:~ $ amixer -c 1 cget iface=MIXER,name='Auto Gain Control'
numid=9,iface=MIXER,name='Auto Gain Control'
  ; type=BOOLEAN,access=rw------,values=1
  : values=on

# set "Auto Gain Control" off
pi@jambox:~ $ amixer -c 1 cset iface=MIXER,name='Auto Gain Control' 0
numid=9,iface=MIXER,name='Auto Gain Control'
  ; type=BOOLEAN,access=rw------,values=1
  : values=off

If you find the magic command that disables AGC, you could put it in /etc/jackdrc.conf (that file is sourced so any commands in it are executed). Then it will get executed whenever Jamulus starts or jack is restarted.

The cheap audio interfaces typically have poor power supply filtering, and the Pi has noisy power (Pi4 is better than Pi3). Trashy power + poor filtering + mic preamp = noise problems.

Glad you found a use for your T41; I still have a couple of T40's lying around, they were great laptops for their day.

[chrisclev]

My band mate has a Roland Quad Capture UA55 card. It is not USB class compliant so won't work with the Pi. The clue was that it needed a driver for Mac. I wouldn't expend any more effort on that one!

[CAguayo]

Thank you, Kevin, I hadn't come across this super-useful tidbit anywhere, and I have been studying up on amixer, because our group has a need to control mic gain and/or volume, and I can imagine putting into some handy scripts with a gui icon. I am going to work on this, so let me know if you beat me to it. ;-) Carlos

…

On Tue, Feb 2, 2021 at 6:28 PM Kevin Doren ***@***.***> wrote: @ve3meo <https://github.com/ve3meo> @CAguayo <https://github.com/CAguayo> Even the cheapest USB Audio Interfaces can have internal controls and switches that might be useful (sometimes a bewildering array of them) They're not necessarily exposed through any GUI, but you might be able to get to them via the "amixer" command. For example, it might be possible to disable AGC. Here's a cheap one (Sabrent I think, card 1 in this case) that has AGC: # look for a control with "Auto" in the name ***@***.***:~ $ amixer -c 1 | grep Auto Simple mixer control 'Auto Gain Control',0 # get the value of mixer control "Auto Gain Control ***@***.***:~ $ amixer -c 1 cget iface=MIXER,name='Auto Gain Control' numid=9,iface=MIXER,name='Auto Gain Control' ; type=BOOLEAN,access=rw------,values=1 : values=on # set "Auto Gain Control" off ***@***.***:~ $ amixer -c 1 cset iface=MIXER,name='Auto Gain Control' 0 numid=9,iface=MIXER,name='Auto Gain Control' ; type=BOOLEAN,access=rw------,values=1 : values=off If you find the magic command that disables AGC, you could put it in /etc/jackdrc.conf (that file is sourced so any commands in it are executed). Then it will get executed whenever Jamulus starts or jack is restarted. The cheap audio interfaces typically have poor power supply filtering, and the Pi has noisy power (Pi4 is better than Pi3). Trashy power + poor filtering + mic preamp = noise problems. Glad you found a use for your T41; I still have a couple of T40's lying around, they were great laptops for their day. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKJTE6BKYSMLALQQ5TUC5TS5CYGBANCNFSM4VH63KSA> .

[rtrial]

This discussion looks like it might be a bit old. We have been using Jamboxes for singings online a couple of times a week. We are looking to see if there might be a 64bit image available or information on how to load the necessary software on a 64bit Bookworm Pi. I am particularly interested at the moment in how to get the URLRelay feature working. P)lease advise if this is not the proper place to ask about this. Any assistance would be much appreciated.

[kdoren]

@rtrial Thanks for the question! (Although FYI it's best to start a new discussion or open a new issue, rather than resurrect a 4 year old discussion).

What is the reason that you want a 64-bit Bookworm version? Are you adding additional applications?

The existing (but old) release is still functional AFAIK. There are still quite a few users, although it's way down from the peak during the pandemic.

I was at one point building under Debian Bullseye (still using 32 bit because that was RPi default at the time). The main thing I was working on was using pipewire to route audio instead of jack. This worked but didn't add any new functionality for the jamming use case. So I never released it.

It would be quite a bit of work for me to build and test a Bookworm release. I'm not currently inclined to do that unless there is significant demand for it.

The urlrelay functionality is itself fairly simple on the RPi side (it registers its internal url with urlrelay.com at startup and again every 24 hours). See here for more detail: #69 However it does require noVNC to be running to make the RPi gui web-accessible on your local network.

The urlrelay.com service runs in AWS and is all serverless, so it costs me almost nothing to run. I intend to keep it running as long as anyone is using it.

• Kevin

[rtrial]

Many of us have been using Jamulus for shape note (Sacred Harp) singings since the beginning of the pandemic. We still me twice a week (and sometimes more). We have deployed several Jamboxes to the less computer capable singers in our community. (And, as you probably are aware, it is sometimes impossible to get Jamulus to run on some machines!) We are quite grateful for being able to do this! I recently thought I might try to build one without using the standard 1.5 image and immediately ran into issues. That has gotten me quite interested in the process of using the current 64bit version of the Pi OS. Mind you, I am very computer literate both from a hardware and software standpoint. I have gotten more and more familiar with Linux by downloading about a dozen different flavors and installing Jamulus on them. I now have a version of Wubuntu that will run quite well booted from a thumb drive. However, I am relatively a Linux newbie. I usually try to access the systems that I am running (even my multiple home, mostly Windows, machines on multiple floors of the house) with some flavor of VNC. (I usually use UltraVNC.) On the Linux machines, I have found KRFB to be the most consistent server. I have run my Jamboxes headless and really like the ability to access them from a browser! I am not sure how whatever VNC version on the 1.5 image communicates with noVNC but would love to try to understand that. (Does it have something to do with PiConnect?) I assume that the version of RealVNC that is on that image must be an older edition. I have tried installing the new RealVNC server version on my current Pi and it seems to require the viewer to also use RealVNC viewer. I would prefer not to have to install client viewer software. Are there any instructions that you can point me to on how to implement the noVNC connection to the urlrelay.com service, I would much appreciate it. Is AWS Amazon Web Service? Is that something for which you pay? Can you tell if it is still getting much use? From the work I have done on Linux, I also understand that installing Jamulus and Jack and whatever dependencies they have on the Pi probably is going to be challenging. Other than those and perhaps the volume control app, I am not sure what might lurk in the bowls to trip me up. But I have already had many challenges – how else do we learn? The Pi was introduced as a learning tool! Thank you so much for your reply and any further assistance you may be able to provide. RT From: Kevin Doren ***@***.***> Sent: Saturday, October 19, 2024 1:18 PM To: kdoren/jambox-pi-gen ***@***.***> Cc: rtrial ***@***.***>; Mention ***@***.***> Subject: Re: [kdoren/jambox-pi-gen] Welcome to jambox-pi-gen Discussions! (Discussion #1) @rtrial <https://github.com/rtrial> Thanks for the question! (Although FYI it's best to start a new discussion or open a new issue, rather than resurrect a 4 year old discussion). What is the reason that you want a 64-bit Bookworm version? Are you adding additional applications? The existing (but old) release is still functional AFAIK. There are still quite a few users, although it's way down from the peak during the pandemic. I was at one point building under Debian Bullseye (still using 32 bit because that was RPi default at the time). The main thing I was working on was using pipewire to route audio instead of jack. This worked but didn't add any new functionality for the jamming use case. So I never released it. It would be quite a bit of work for me to build and test a Bookworm release. I'm not currently inclined to do that unless there is significant demand for it. The urlrelay functionality is itself fairly simple on the RPi side (it registers its internal url with urlrelay.com at startup and again every 24 hours). However it does require noVNC to be running to make the RPi gui web-accessible on your local network. The urlrelay.com service runs in AWS and is all serverless, so it costs me almost nothing to run. I intend to keep it running as long as anyone is using it. * Kevin — Reply to this email directly, view it on GitHub <#1 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6CGDPK2GQFOTTMKT523TMDZ4KH6BAVCNFSM6AAAAABP7OMVACVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAOJZGI2DAOI> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/A6CGDPMLGMQSVPNESUTULHDZ4KH6BA5CNFSM6AAAAABP7OMVACWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAU65RS.gif> Message ID: ***@***.*** ***@***.***> >

[kdoren]

@rtrial The jambox-pi-gen repo is a fork of Raspberry Pi's pi-gen, its function is to create a pre-configured ISO file that can be flashed onto an SD card. In the jambox case, it installs and configures everything, including noVNC, the jamming apps, and setting all the configurations properly. Under Buster and Bullseye, it also installed a low-latency kernel (might not be necessary on Bookworm which uses a low-latency kernel by default).

You could accomplish similar by manually configuring a stock Raspberry Pi OS image and then cloning it, this is what most people do. The downside of this is that for a complex configuration, you'll have a lot of trouble replicating what you did unless you take really good notes and follow them precisely. With the pi-gen approach, I could change configurations, push a button, and easily generate a new image. Which made it very easy to experiment.

To see the steps I used, the jambox pieces are under the "stage3" directory of this repo. I suggest you look at the "jambox-pw" branch, which works but was never released. It's for Debian Bullseye but it uses pipewire for audio routing which is now the default used by Bookworm. Pipewire is better than jack but maintains a jack interface for compatibility.

The apps and kernel were installed from .deb packages from my apt repo (which serves Buster and Bullseye, but not yet Bookworm). If the only app is Jamulus, and you're using the stock kernel, you wouldn't need that, you could just use the default debian repos.

noVNC is the magic required to run the GUI in a web browser without installing a client. noVNC has a mini-HTTP server that loads a javascript VNC client into the user's browser, then connects to the Pi's VNC server over a websocket. This requires "websockify" to be installed and running on the RPi to bridge them together. Look at stage3/04-install-sw/02-run.sh for installation details.

The urlrelay systemd service is installed in stage3/07-install-boot-script/01-run.sh (with files in stage3/07-install-boot-script/files/ )

The urlrelay web service runs in AWS; I pay for this but it's all serverless so it costs very little money. It's essentially free except for the domain name and DNS zone, so maybe $25/yr for urlrelay.com and another $25/year for jambox-project.com which is for my apt repo (and maybe a website at some point).

At the peak there were over 1000 jamboxes out there, all over the world, around 2/3 in Europe. It's down to a bit over 100 and holding steady these days.

A lot of the work for Jambox was making it easy to use for non-technical end users and people like you who are helping them. This includes the urlrelay service and noVNC for web browser GUi access without installing anything or knowing the RPi's IP address (although in many cases you may also be able connect to the RPi via a .local DNS name without using urlrelay). Also things like the application start scripts that run by clicking an icon, which set up and tear down the jamming apps.

Much work for Jambox was also testing to get the configuration optimized for reliable operation for jamming while minimizing latency. Also testing with various RPi and audio hardware, and stability testing. For me to do a Bookworm release, it would be quite a bit of implementation and debug/testing work, which I'm not inclined to do right now, especially if the end result did pretty much the same thing, but under Debian Bookworm.

My general advice is that if the existing jambox image still does the job for you, save yourself some pain and keep using it. Unless of course you like a challenge and want to use it as a learning experience. If that's the case, have fun.

-Kevin

[rtrial]

Thank you so much for your kind reply. Since I received this, I have had some health issues (a cardio ablation to correct ventricular tachicardia). I am doing well now and hopefully, that is behind me. Consequently, I have not done much with my project. I have run stage3/07-install-boot-script/01-run.sh but there is obviously more needed. That seems to have installed some, or perhaps all, of URLRelay. The only thing that seems to have changed is that I am now having to provide a password when I reboot. I have found what appears to be the NoVNC portion, or at least some part of it, in stage03/ 04-install-sw/02-run.sh. I may try to run that next. My question to you now is, might I consider running all of stage3? might that install all of the apps and adjust configurations? how do I do that? Your reply is much appreciated. RT From: Kevin Doren ***@***.***> Sent: Tuesday, October 22, 2024 5:23 AM To: kdoren/jambox-pi-gen ***@***.***> Cc: rtrial ***@***.***>; Mention ***@***.***> Subject: Re: [kdoren/jambox-pi-gen] Welcome to jambox-pi-gen Discussions! (Discussion #1) @rtrial <https://github.com/rtrial> The jambox-pi-gen repo is a fork of Raspberry Pi's pi-gen, its function is to create a pre-configured ISO file that can be flashed onto an SD card. In the jambox case, it installs and configures everything, including noVNC, the jamming apps, and setting all the configurations properly. Under Buster and Bullseye, it also installed a low-latency kernel (might not be necessary on Bookworm which uses a low-latency kernel by default). You could accomplish similar by manually configuring a stock Raspberry Pi OS image and then cloning it, this is what most people do. The downside of this is that for a complex configuration, you'll have a lot of trouble replicating what you did unless you take really good notes and follow them precisely. With the pi-gen approach, I could change configurations, push a button, and easily generate a new image. Which made it very easy to experiment. To see the steps I used, the jambox pieces are under the "stage3" directory of this repo. I suggest you look at the "jambox-pw" branch, which works but was never released. It's for Debian Bullseye but it uses pipewire for audio routing which is now the default used by Bookworm. Pipewire is better than jack but maintains a jack interface for compatibility. The apps and kernel were installed from .deb packages from my apt repo (which serves Buster and Bullseye, but not yet Bookworm). If the only app is Jamulus, and you're using the stock kernel, you wouldn't need that, you could just use the default debian repos. noVNC is the magic required to run the GUI in a web browser without installing a client. noVNC has a mini-HTTP server that loads a javascript VNC client into the user's browser, then connects to the Pi's VNC server over a websocket. This requires "websockify" to be installed and running on the RPi to bridge them together. Look at stage3/04-install-sw/02-run.sh for installation details. The urlrelay systemd service is installed in stage3/07-install-boot-script/01-run.sh (with files in stage3/07-install-boot-script/files/ ) The urlrelay web service runs in AWS; I pay for this but it's all serverless so it costs very little money. It's essentially free except for the domain name and DNS zone, so maybe $25/yr for urlrelay.com and another $25/year for jambox-project.com which is for my apt repo (and maybe a website at some point). At the peak there were over 1000 jamboxes out there, all over the world, around 2/3 in Europe. It's down to a bit over 100 and holding steady these days. A lot of the work for Jambox was making it easy to use for non-technical end users and people like you who are helping them. This includes the urlrelay service and noVNC for web browser GUi access without installing anything or knowing the RPi's IP address (although in many cases you may also be able connect to the RPi via a .local DNS name without using urlrelay). Also things like the application start scripts that run by clicking an icon, which set up and tear down the jamming apps. Much work for Jambox was also testing to get the configuration optimized for reliable operation for jamming while minimizing latency. Also testing with various RPi and audio hardware, and stability testing. For me to do a Bookworm release, it would be quite a bit of implementation and debug/testing work, which I'm not inclined to do right now, especially if the end result did pretty much the same thing, but under Debian Bookworm. My general advice is that if the existing jambox image still does the job for you, save yourself some pain and keep using it. Unless of course you like a challenge and want to use it as a learning experience. If that's the case, have fun.

…

-Kevin — Reply to this email directly, view it on GitHub <#1 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6CGDPLBFULCGSLS7RRYBLDZ4YKO7AVCNFSM6AAAAABP7OMVACVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBRGQ4DAMI> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/A6CGDPOCMUBDAHXJZ3UEP63Z4YKO7A5CNFSM6AAAAABP7OMVACWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAVAJJC.gif> Message ID: ***@***.*** ***@***.***> >

[kdoren]

@rtrial the scripts in stage3 are meant to be run by the pi-gen process, which sets up and understands the context. Pi-gen is somewhat complex. The jambox-pw branch was working under Debian bullseye, but would need some work to get it running under bookworm.

I pointed you to them to use as a guide to manually modifying a bookworm installation. You only need the primarily the Jamulus app which should be available in the rpi bookworm repo.

The scripts and config files for installing noVNC and websockify should work but may need some modifications to be run outside of pi-gen.

I would suggest starting with a stock bookworm image, then try to get noVNC and websockify working. You can use my scripts as a guide but there is also info available online.

You don't need urlrelay to test noVNC, if it's working you should be able to connect to its IP address on port 6080 I think. And with many routers you could connect to .local:6080 without even knowing the IP.

There is code there to set a VNC password from an encrypted environment variable. But you could just set the password manually by command, I think it's vncpasswd.

Once you get noVNC working, you can try adding urlrelay if you want (but you may not need to if you can use hostname.local). That is relatively simple and requires installing the script, config, and systemd unit files, and enabling it to start on boot. It registers its local url with my urlrelay web service, then re-registers every 24 hours. You can also inspect these files on an existing jambox.

[rtrial]

I have struggled to make some progress with NoVNC. I have managed to get it and websockify installed and they appear to be running properly. I do get a Connect screen when I go to URLRelay.com/go however. When I click “Connect" it comes back saying “Connecting” and then an error screen with no indication of what the error might be: I am running RealVNC server on the Pi with wayland. I am able to connect remotely with both Pi Connect and also UltraVNC (although only one seems to work at a time). I must be getting close to having this work. Any suggestions/recommendations would sorely be appreciated. Also, if you could suggest how I can make the ./novnc_proxy start when I reboot, that would be appreciated. Please remember that I am a relative unix newbie. RT From: Kevin Doren ***@***.***> Sent: Friday, November 22, 2024 7:11 AM To: kdoren/jambox-pi-gen ***@***.***> Cc: rtrial ***@***.***>; Mention ***@***.***> Subject: Re: [kdoren/jambox-pi-gen] Welcome to jambox-pi-gen Discussions! (Discussion #1) @rtrial <https://github.com/rtrial> the scripts in stage3 are meant to be run by the pi-gen process, which sets up and understands the context. Pi-gen is somewhat complex. The jambox-pw branch was working under Debian bullseye, but would need some work to get it running under bookworm. I pointed you to them to use as a guide to manually modifying a bookworm installation. You only need the primarily the Jamulus app which should be available in the rpi bookworm repo. The scripts and config files for installing noVNC and websockify should work but may need some modifications to be run outside of pi-gen. I would suggest starting with a stock bookworm image, then try to get noVNC and websockify working. You can use my scripts as a guide but there is also info available online. You don't need urlrelay to test noVNC, if it's working you should be able to connect to its IP address on port 6080 I think. And with many routers you could connect to .local:6080 without even knowing the IP. There is code there to set a VNC password from an encrypted environment variable. But you could just set the password manually by command, I think it's vncpasswd. Once you get noVNC working, you can try adding urlrelay if you want (but you may not need to if you can use hostname.local). That is relatively simple and requires installing the script, config, and systemd unit files, and enabling it to start on boot. It registers its local url with my urlrelay web service, then re-registers every 24 hours. You can also inspect these files on an existing jambox. — Reply to this email directly, view it on GitHub <#1 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6CGDPMHILGVJA2IWMLXPHL2B4NN3AVCNFSM6AAAAABP7OMVACVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZUHA2DEOI> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/A6CGDPNYU3XJAXLDY7MUKTL2B4NN3A5CNFSM6AAAAABP7OMVACWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAVUU42.gif> Message ID: ***@***.***>

[kdoren]

Hi @rtrial ,

Sorry to go dark on you, I was traveling for a while.

If you get the "connect" button, but the button doesn't work, consider the following:

Working system requires VNC server, NoVNC, and websockify, all working together.

1. Check that a VNC server is running on your Pi. You should be able to test it using a standard VNC client to connect to your pi's IP address using the standard VNC port of 5900.

2. NoVNC runs an http server on port 6080, which loads a javascript VNC client into your web browser, but that is likely working if you get the NoVNC screen and the connect button.

3. It the above 2 things are both working, problem is likely with "websockify" (not installed, not running, or not configured correctly). A web browser is not allowed to directly open a VNC connection, that would be a security problem. Web browser is only allowed to open a websocket connection. Websockify runs on the pi, and functions as a bridge. It accepts a websocket connection on port 6080, and sends the data to/from the pi's VNC server on port 5900. If this isn't working, I expect you'd see the behavior you describe.

I hope this helps,

-Kevin

[rtrial]

Thank you for getting back to me. I went a little dark over the holidays also. Once I got back to it a week or so ago, I have had some moderate success. I have all three of the things you mention running. NoVNC and websocify were installed and set up per your instructions. The VNC server has been the issue. I have tried RealVNC with no luck. I have finally resorted to WayVNC server. (Apparently, the VNC protocol has been enhanced and functions a bit differently.) I struggled with it for a while but got a tip from someone on a Google group related to NoVNC pointing me to here: How to connect to Raspberry Pi Desktop using wayvnc VNC Server <https://www.claudiokuenzler.com/blog/1385/how-to-connect-raspberry-pi-bookworm-desktop-vnc-wayvnc> suggesting that there was an issue with certification. Once I removed the "enable_auth=true" line from the config file, NoVNC worked!!! However, unfortunately, it seems to be unsecured and I get the attached messages from RealVNC and UltraVNC viewers. I am not concerned about encryption, but none of the viewers prompt for credentials any longer. This is not acceptable for any device on my network. I am trying to find out if there is some way to require at least password verification without enable_auto=true? Probably not something you are familiar with but you may have some insight. Any thoughts or suggestions are welcome. RT From: Kevin Doren ***@***.***> Sent: Monday, January 20, 2025 5:23 AM To: kdoren/jambox-pi-gen ***@***.***> Cc: rtrial ***@***.***>; Mention ***@***.***> Subject: Re: [kdoren/jambox-pi-gen] Welcome to jambox-pi-gen Discussions! (Discussion #1) Hi @rtrial <https://github.com/rtrial> , Sorry to go dark on you, I was traveling for a while. If you get the "connect" button, but the button doesn't work, consider the following: Working system requires VNC server, NoVNC, and websockify, all working together. 1. Check that a VNC server is running on your Pi. You should be able to test it using a standard VNC client to connect to your pi's IP address using the standard VNC port of 5900. 2. NoVNC runs an http server on port 6080, which loads a javascript VNC client into your web browser, but that is likely working if you get the NoVNC screen and the connect button. 3. It the above 2 things are both working, problem is likely with "websockify" (not installed, not running, or not configured correctly). A web browser is not allowed to directly open a VNC connection, that would be a security problem. Web browser is only allowed to open a websocket connection. Websockify runs on the pi, and functions as a bridge. It accepts a websocket connection on port 6080, and sends the data to/from the pi's VNC server on port 5900. If this isn't working, I expect you'd see the behavior you describe. I hope this helps,

…

-Kevin — Reply to this email directly, view it on GitHub <#1 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6CGDPK4TO3I4CCO5CEVNNL2LTE7LAVCNFSM6AAAAABP7OMVACVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBYHA4DQMI> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/A6CGDPOJ7QIWDSCNI34YZSL2LTE7LA5CNFSM6AAAAABP7OMVACWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAWVUPC.gif> Message ID: ***@***.*** ***@***.***> >

[kdoren]

On jambox image I used realvnc-vnc-server.

Config file /root/.vnc/config.d/vncserver-x11 contains:

Authentication=VncAuth
Encryption=PreferOff
Password=70dc86dbbe2f1bc7

NoVNC will normally prompt for a password, unless you give it one in the URL (with ?password= at end of url). urlrelay supplies the URL to your browser, it's whatever url the pi registered with urlrelay. Jambox defaults to including the password, to simplify operation for users. But you can change that in file /etc/urlrelay/urlrelay.conf by commenting out URL_ARGS

Running VNC secured requires TLS connection with trusted certificate. This protects against a bad guy from sniffing the traffic and seeing the data or reading the password. This could be an issue for VNC traffic routed over the internet, but it's simply not a problem for VNC traffic confined to your local network (and jambox firewall will refuse traffic from outside your local network).

There are 3 connections involved. The browser connects to the pi on port 6080 (currently via HTTP, but could be secured with HTTPS). Then the browser opens a websocket to websockify on the pi using port 6080. Then websockify on the pi opens a VNC connection to VNC server on the pi using port 5900.

Securing connections requires a trusted certificate (otherwise you might be sending encrypted data to a bad guy). On the internet, certificates for domain names are signed by a trusted Certificate Authority (CA). But you can't do that when connecting to an IP address on your local network. TLS on local network requires creating a private CA and self-signed certificate, then adding your private CA to the trusted CA store (on the pi for the NoVNC/websockify, and on user's PC for the web browser-to-pi connection. While this can be done, there's no benefit to doing it. There's zero chance that there's a bad guy on your local network sniffing the VNC traffic so they can break into your pi via VNC.

-Kevin

[rtrial]

I have reinstated RealVNC server on the Pi and am able to access it remotely from RealVNC and UltraVNC remote clients. I am no longer able to get at it with Pi Connect and still unable to access it with NoVNC. I have been unable to locate the vncserver-x11 file to make your recommended config settings. Do I need to create a config file or a vncserver-x11 file as below? RT From: Kevin Doren ***@***.***> Sent: Monday, January 20, 2025 3:02 PM To: kdoren/jambox-pi-gen ***@***.***> Cc: rtrial ***@***.***>; Mention ***@***.***> Subject: Re: [kdoren/jambox-pi-gen] Welcome to jambox-pi-gen Discussions! (Discussion #1) On jambox image I used realvnc-vnc-server. Config file /root/.vnc/config.d/vncserver-x11 contains: Authentication=VncAuth Encryption=PreferOff Password=70dc86dbbe2f1bc7 NoVNC will normally prompt for a password, unless you give it one in the URL (with ?password= at end of url). urlrelay supplies the URL to your browser, it's whatever url the pi registered with urlrelay. Jambox defaults to including the password, to simplify operation for users. But you can change that in file /etc/urlrelay/urlrelay.conf by commenting out URL_ARGS Running VNC secured requires TLS connection with trusted certificate. This protects against a bad guy from sniffing the traffic and seeing the data or reading the password. This could be an issue for VNC traffic routed over the internet, but it's simply not a problem for VNC traffic confined to your local network (and jambox firewall will refuse traffic from outside your local network). There are 3 connections involved. The browser connects to the pi on port 6080 (currently via HTTP, but could be secured with HTTPS). Then the browser opens a websocket to websockify on the pi using port 6080. Then websockify on the pi opens a VNC connection to VNC server on the pi using port 5900. Securing connections requires a trusted certificate (otherwise you might be sending encrypted data to a bad guy). On the internet, certificates for domain names are signed by a trusted Certificate Authority (CA). But you can't do that when connecting to an IP address on your local network. TLS on local network requires creating a private CA and self-signed certificate, then adding your private CA to the trusted CA store (on the pi for the NoVNC/websockify, and on user's PC for the web browser-to-pi connection. While this can be done, there's no benefit to doing it. There's zero chance that there's a bad guy on your local network sniffing the VNC traffic so they can break into your pi via VNC.

…

-Kevin — Reply to this email directly, view it on GitHub <#1 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A6CGDPPIYCY2VVHGFGQRBMD2LVI3BAVCNFSM6AAAAABP7OMVACVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBZGQ3TQMY> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/A6CGDPMJT5RJCI4DZRYFAJL2LVI3BA5CNFSM6AAAAABP7OMVACWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAWV776.gif> Message ID: ***@***.*** ***@***.***> >