Does your Internet Service Provider happen to be COMCAST? We’ve had reports that users under this ISP seem to have issues accessing our server…
What you could do is contact your ISPs support and ask them why are you getting network issues accessing this particular file, they ought to investigate and make any configuration changes necessary.
Does your Internet Service Provider happen to be COMCAST?
Gee, how did you guess? I went through this sisyphean struggle once before. I don’t remember how many rounds of “Just because you don’t get an error, using your office computer, on your office network, does not mean that there isn’t a problem out at the customers’ sites.” We went through.
We’ve already asked our service provider to look into the bandwidth issues with Comcast networks a little while ago, but reporting the problem from user’s end might help as well.
I put in a ticket the same day I made my last post. I’d been over a week and it’s still crickets.
I have just added an alt. download link via mega.nz - 1.63 GB file on MEGA
I got the same, found a workaround.
It looks like a bug – the service handler for the new admidiminder service expects there to be an explicit config parameter in the module’s patchbox-module.json. It looks like this was done properly for the orac module, but missing in the puredata module.
Edit /usr/local/patchbox-modules/puredata/patchbox-module.json and replace the line with
"amidiminder.service",
with
{
"service": "amidiminder.service",
"config": "blah"
}
My full file now looks like this:
{
"name": "puredata",
"version": "1.0.1",
"description": "PureData module",
"author": "blokas-community",
"launch_mode": "list",
"depends_on": [
"jack.service",
"pisound-ctl.service",
"touchosc2midi.service",
{
"service": "amidiminder.service",
"config": "blah"
}
],
"scripts": {
"install": "install.sh",
"launch": "launch.sh",
"list": "list.sh",
"stop": "stop.sh"
}
}
Hi folks! Has there been any update to the Patchbox OS ARM64 beta since 2024-04-04 release please? I don’t note any in this thread but I may have missed it (or another thread).
Thanks!
Yes, this is the current latest release. Some further OS package updates can be installed by running sudo apt update && sudo apt upgrade.
I’m interested in upgrading to this new version of Patchbox OS, but my project uses Super Collider and based on the initial post on this thread, that seems to not be working correctly with the new Patchbox OS.
Does anyone have updates on that? My assumption is that I should stick with the older release if I need to use Super Collider…
Ok, well I went ahead and just tried it out. So far, my Super Collider based project seems to work perfectly.
Great work with this update! It is so much faster. I’m never looking back. 
Good to hear your project is running just fine! Are you using the SuperCollider IDE or are you running it headless?
I’m running headless - though to be more specific I have a front end app that makes system calls to sclang to configure effects, and receives audio analysis data back via osc.
I left it running for several hours to test, because the initial post mentions super collider sometimes dies unexpectedly. I worry a bit that I’m just getting lucky and that will eventually happen, but so far all good.
Because I’m doing a lot of graphics work in addition to audio processing in super collider, the switch to Wayland is massively more performant.
Edit: I just realized I’m not using the real time kernel, now that it’s off by default. I’ll test that today.
confirmed, everything seems great with the real time kernel as well.
The problems were in running the Super Collider IDE - it was crashing soon after startup, something to do with its help documentation. Perhaps that was fixed in some update since last time I checked. Any chance you could see if the IDE loads up and doesn’t crash soon after startup?
just trying out the new patchbox with a new pi5 connected to a Scarlet 18i20 while waiting for my pisound to arrive for testing purposes and the default install does not want to play chromium youtube videos through the usb sound card. This is a killer feature for me as I need it to be able to play chromium streams from pykaraoke while applying effects using modep plugins for karaoke. Is there ba way to make it ignore the hdmi audio? IF I unplug the usb audio and plug it back in again then I get the chromium browser audio through the sound card but then I have lost modep 
Hello, is this true for the previous releases as well, or only this one? The main reason I wanted to use Patchbox was to have a realtime kernel out of the box since I’m inexperienced with kernels, if I install an older release on my 3B+ will that be good?
Older ones were fine as far as I recall.
Thanks for confirming, I installed an older release yesterday and so far everything works fine.
So my pisound arrived for my pi5 and I have done a clean flash of Patchbox OS and gone through the wizard. First thing to note is that it never manages to connect to wifi on first install using the wizard. I then have to select the wifi country when I get to the desktop. Then after a reboot I’m able to disconnect from the built in wifi hotspot and connect to my local wifi.
Then I ran sudo apt update and sudo apt upgrade to make sure I’m all up to date. I noticed that after running Chromium and loading a youtube video audio came out over hdmi and I was not able to select the pisound
So I re-ran patchbox and selected the pisound as the default device and the pisound then became available as an audio device.
Youtube videos will not play though when pisound is selected, but they will play when hdmi is selected as the audio device.
When I reboot the pi the pisound is not available again until I run patchbox and also still, youtube videos will not play when pisound is selected. So there’s a couple of issues here:
Booting the pi will not have pisound available until patchbox has been run and
Youtube videos in Chromium will not play when pisound is then selected
Anybody know how I can resolve these teething issues?
