[Beta] Patchbox OS image 2022-05-17

Giedrius · May 17, 2022, 1:46pm

Hey guys! Patchbox OS has been updated to be based on the Bullseye Debian release! It should work just fine with pretty much all the currently released Raspberry Pi’s out there. Also, most of the software that comes installed by default has been updated to latest versions available.

It also includes a real-time kernel installed by default, it’s been verified to run even with Pi 2 and Pi Zero W.

Downloads

Direct download
SHA-256: 8c806a94daba2298f96ede2a0f3e40f92ce26bf23a4ea357bbaf1919e2f09e4f

Default Passwords


User name	patch
Password	blokaslabs
WiFi SSID	Patchbox
WiFi password	blokaslabs

Please change your user password while going through the wizard, for security.

The WiFi hotspot is on by default.

steinber · May 17, 2022, 3:39pm

for those of us who are rusty at this sort of thing, is there a reasonable way to upgrade in place, or is it better to just back up everything and start with a clean image?

Paul_Routledge · May 17, 2022, 4:53pm

Pi 4 8GB

It’s a little buggy
CPU holds at 100% when using the button - which then fails.
Loading pedalboards is very slow when available
The web gui crashes when connecting with pisound app

I’ll send more details soon with logs

dormirj · May 17, 2022, 11:48pm

I would generally recommend to start from a clean slate and back up all your custom additions. Not sure it’s strictly necessary, but since it’s based on a completely new debian release version there might be a lot of issues involved.

I’m pretty happy with it so far, but I’m only using it to run my supercollider patches, seems more stable with the xruns, maybe I can even squeeze the latency a bit with the realtime kernel…

best,
dormir

Giedrius · May 18, 2022, 7:47am

It’s better to backup, flash the new build, and move over your stuff to the new build, that’s the recommended way for Raspberry Pi OS too.

In theory, it’s possible to edit your /etc/apt/sources.list.d/... to point to bullseye and do sudo apt-get dist-upgrade, but that also misses any changes that were done between the OS image releases outside of the deb packages, so in the end, you’d still end up with something different than the newly released image, it’s very complicated to debug and get everything right, as well as it’s not that well tested on Raspberry Pi OS and OSes derived from it, so this should only be attempted by Linux experts that can find their own way through it.

Please provides any steps to reproduce the issue. You can investigate the output of top to see which processes use the most resources.

MODEP didn’t change at all in this release. It used to do this before as well, when I looked into it, it seems the MOD UI isn’t able to handle changes that happen externally well, so you have to simply refresh the page after switching the pedalboard using external mechanisms.

Paul_Routledge · May 18, 2022, 8:14am

I put it on a spare SD to try it out… I’ll do another flash etc and see what happens, when I get a little more time.

BoxOfSnoo · May 18, 2022, 6:36pm

I am having issues installing updates and MODEP. I get the following errors:

1: update errors

E: Repsitory 'http://apt.blokas.io rpi InRelease' changed its 'Origin' value from 'main rpi' to '. rpi'
E: Repsitory 'http://apt.blokas.io rpi InRelease' changed its 'Label' value from 'main rpi' to '. rpi'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details

Installing MODEP
Apologies, but I have to transcribe this text manually due to my setup. I won’t do the full stack trace unless it’s really really necessary… but I will try my best

File "/usr/lib/python3/dist-packages/patchbox/module.py", line 621, in _install_module
  raise ModuleError(

patchbox.module.ModuleError: Failed to install modep.module via /usr/local/patchbox-modules/modep/install.sh script

During handling of the above exception, another exception occurred:

File "/usr/bin/patchbox", line 33 in <module>
   sys.exit(load_entry_point('patchbox-cli==1.0', 'console_scripts', 'patchbox')())

(etc)

Does this help debug?

Update: I was able to get past part 1 with sudo apt update which this time asked if I would accept the suggested changes. After that the MODEP module seemed to work.

Was that the solution?

mzero · May 19, 2022, 4:45am

The fix for this is to run the following from the command line:

sudo apt-get update --allow-releaseinfo-change

Now you can go back and run patchbox to install MODEP:

patchbox

Giedrius · May 19, 2022, 7:07am

Did this happen on the 2022-05-17 image, or are you updating and older install of Patchbox OS?

mzero · May 19, 2022, 3:54pm

It happens on the 2022-05-17 image.

Giedrius · May 20, 2022, 8:41am

Fixed it on our server.

Giedrius · May 23, 2022, 8:32am

7 posts were split to a new topic: Can’t add pedals to MODEP after starting a New Pedalboard

drandaji · May 27, 2022, 9:10pm

I’m not convinced that it’s fixed. I’ve tried 6 times from a fresh 2022-05-17 image (even a 2020-11-23) with or without an update first (tried --allow-releaseinfo-change and --fix-missing). modep module activation (via patchbox ui or commandline) always results in this error:

Get:51 http://apt.blokas.io rpi/main armhf modep-lv2-zam-plugins armhf 3.12.0-2 [6,399 kB]
Get:52 http://apt.blokas.io rpi/main armhf modep-touchosc2midi armhf 1.0.0-2 [9,360 B]
Fetched 172 MB in 50s (3,422 kB/s) E: Failed to fetch http://apt.blokas.io/pool/main/m/modep-ctl-scripts/modep-ctl-scripts_1.8.0.deb File has unexpected size (2408 != 2432). Mirror sync in progress? [IP: 79.98.29.34 80]
Hashes of expected file:
- SHA512:a02c18f8637356c4153f231ca15d980cf04d4fb6fbd72e77e07703af7ac5238a4bcbdd7766b5b7f01df0ba5588eab1153fc959731b9acec868d73ee69f1f10fd
- SHA256:f8e91f6684c6849f8a2a352632972a2781d9ab558527a54fa892051ce87f78af
- SHA1:3f43ca0d6c854ac4a119a93a1dad104a3f908890 [weak]
- MD5Sum:924c89707d841556aecb545c5b4d2ac8 [weak]
- Filesize:2432 [weak]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/patchbox/module.py”, line 621, in _install_module
raise ModuleError(
patchbox.module.ModuleError: Failed to install modep.module via /usr/local/patchbox-modules/modep/install.sh script

diy_nnick · May 28, 2022, 1:37pm

Hey guys,
thanks for the update!

File has unexpected size (2408 != 2432). Mirror sync in progress?

Happens to me as well when I try to install modep. I tried sudo apt-get clean and sudo apt-get update --allow-releaseinfo-change, no luck unfortunately. Is the apt mirror out of sync?

I’m on a fresh install of the Beta 2022-05-17.
Tried now to install the orac module. Worked without any issues.

diy_nnick · May 29, 2022, 10:00am

Seems like it’s really a mirror node which is out of sync.

@Giedrius, I saw that it’s possible to install modules from a file. Unfortunately I couldn’t find any information about how to build modep myself and install from a file. Do you know if there is some documentation about it?

Giedrius · May 30, 2022, 12:36pm

MODEP is built using https://github.com/BlokasLabs/modep-debs.

I’ve just fixed the issue with our APT server, the installs should now work again. (if installing manually, make sure to run sudo apt update)

diy_nnick · May 30, 2022, 7:17pm

thx mate
working perfectly now.

drandaji · May 31, 2022, 11:59pm

Works now for me too. Thanks for the fix @Giedrius!

drandaji · June 1, 2022, 4:42pm

Although all seems good with the newest Patchbox, it appears that the modep module is not backward compatible with the previous 2020-11-23 version of Patchbox. Maybe that’s expected?

Manager: modep.module install script found: /usr/local/patchbox-modules/modep/install.sh
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 http://apt.blokas.io rpi InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 modep : Depends: modep-mod-host (>= 1.8.0-2) but it is not going to be installed
         Depends: modep-mod-ui (>= 1.8.1-1) but it is not going to be installed
         Recommends: modep-fluidsynth (>= 2.1.0-1) but it is not going to be installed
         Recommends: modep-lv2-amsynth (>= 1.9.0-2) but it is not going to be installed
         Recommends: modep-lv2-artyfx (>= 1.3.0-1) but it is not going to be installed
         Recommends: modep-lv2-calf (>= 0.90.3-2) but it is not going to be installed
         Recommends: modep-lv2-caps (>= 0.9.26-1) but it is not going to be installed
         Recommends: modep-lv2-dpf-plugins (>= 1.3.0-1) but it is not going to be installed
         Recommends: modep-lv2-fat1 (>= 0.6.0-1) but it is not going to be installed
         Recommends: modep-lv2-fil4 (>= 0.7.1-1) but it is not going to be installed
         Recommends: modep-lv2-fluidplug (>= 1.0.0-1) but it is not going to be installed
         Recommends: modep-lv2-fomp (>= 1.1.0-1) but it is not going to be installed
         Recommends: modep-lv2-freaked (>= 0.0.1-1) but it is not going to be installed
         Recommends: modep-lv2-guitarix (>= 0.39.0-1) but it is not going to be installed
         Recommends: modep-lv2-gx-slowgear (>= 0.5.0-1) but it is not going to be installed
         Recommends: modep-lv2-gx-switchless-wah (>= 0.1.0-1) but it is not going to be installed
         Recommends: modep-lv2-infamousplugins (>= 0.3.0-1) but it is not going to be installed
         Recommends: modep-lv2-invada-studio (>= 0.0.1-1) but it is not going to be installed
         Recommends: modep-lv2-mda (>= 1.1.0-1) but it is not going to be installed
         Recommends: modep-lv2-midifilter (>= 0.6.2-1) but it is not going to be installed
         Recommends: modep-lv2-mod-distortion (>= 0.0.1-1) but it is not going to be installed
         Recommends: modep-lv2-mod-pitchshifter (>= 0.0.1-1) but it is not going to be installed
         Recommends: modep-lv2-mod-utilities (>= 0.0.1-1) but it is not going to be installed
         Recommends: modep-lv2-mtc (>= 0.2.1-1) but it is not going to be installed
         Recommends: modep-lv2-rkrlv2 (>= 0.3.0-1) but it is not going to be installed
         Recommends: modep-lv2-setbfree (>= 0.8.11-1) but it is not going to be installed
         Recommends: modep-lv2-shiroplugins (>= 0.0.1-1) but it is not going to be installed
         Recommends: modep-lv2-sooperlooper (>= 0.93.0-1) but it is not going to be installed
         Recommends: modep-lv2-tap (>= 1.2.7-1) but it is not going to be installed
         Recommends: modep-lv2-triceratops (>= 0.3.2-1) but it is not going to be installed
         Recommends: modep-lv2-tuna (>= 0.5.2-1) but it is not going to be installed
         Recommends: modep-lv2-zam-plugins (>= 3.12.0-1) but it is not going to be installed
         Recommends: modep-demo-content (>= 1.0.0-1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/patchbox/module.py", line 622, in _install_module
    'Failed to install {}.module via {} script'.format(module.name, os.path.join(module.path, module.has_install)))
patchbox.module.ModuleError: Failed to install modep.module via /usr/local/patchbox-modules/modep/install.sh script

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/patchbox", line 11, in <module>
    load_entry_point('patchbox-cli==1.0', 'console_scripts', 'patchbox')()
  File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/lib/python3/dist-packages/patchbox/modules/module/cli.py", line 136, in activate
    ctx.obj.activate(module, autolaunch=False, autoinstall=autoinstall)
  File "/usr/lib/python3/dist-packages/patchbox/module.py", line 636, in activate
    self._install_module(module)
  File "/usr/lib/python3/dist-packages/patchbox/module.py", line 625, in _install_module
    'Failed to install {}.module via {} script'.format(module.name, os.path.join(module.path, module.has_install)))
patchbox.module.ModuleError: Failed to install modep.module via /usr/local/patchbox-modules/modep/install.sh script

Giedrius · June 2, 2022, 2:57pm

If someone wants to stick to Buster, try editing /etc/apt/sources.list.d/blokas.list to have the following contents:

deb http://apt.blokas.io/buster/ rpi main

Then run sudo apt update and try installing again.