All installed and I love it so far… gone are the effects when adding a module in the patch, much smoother experience overall… thanks to the team at SSP for continuing the development… The SSP is now my preferred module by far… the module I would choose if I could only choose one… by far…
2 Likes
Having problem to exctract the file in mac os. I used Keka as suggested, btw after few minutes it crash and has error code 70 using “zstd”. Have any idea what is the problem?
Thanks
specific this…
OS: Version 11.6.4 (Build 20G417) (x86_64)
Keka: v1.2.54-r4983 (WEB) (Sandboxed) (en)
Format detected: Undefined
Binary used: kekazstd
Arguments: (
“-d”,
“-T4”,
“-o”,
“/Users/embryonaler/Audio/Percussa/ssp-sandisk-extremepro-32gb-290520221129.img.kextraction/Operation/ssp-sandisk-extremepro-32gb-290520221129.img”,
“/Users/embryonaler/Audio/Percussa/ssp-sandisk-extremepro-32gb-290520221129.img.zstd”
)
90520221129.img.zstd : 0 B…
90520221129.img.zstd : 18.8 MiB…
90520221129.img.zstd : 40.0 MiB…
90520221129.img.zstd : 56.1 MiB…
90520221129.img.zstd : 75.5 MiB…
Ive just downloaded (from url provided by Bert) and extracted with Keka on my Mac, and all worked ok.
unfortunately, the above doesn’t really give any idea of what the issue might be…
did you enable debug info on the above? as well as open debug session?
if you did, interesting, when I run in debug I get a message about ‘READER’ which your logs seems to not have.
Id say one of the following will likely be the issue: (in kind of order of likelihood?!)
a) keka doesn’t have permission to access folder to READ the zstd file.
b) keka doesn’t have permission to access folder to WRITE the resulting file.
c) the zstd has been corrupted during download.
d) you have a compatibility issue with keka and your Mac.
(a) and (b) , unfortunately this is becoming an increasing common issue on Macs, as Apple try to protect users by sandboxing apps.
it wasn’t an issue on my Mac, but then again… as mine is a ‘dev’ machine, Ive changed the default setup a lot … so hard to tell … anyway see this article , and add permissions for Keka to just access downloads folder. (Id not recommend full disk access 
)
(c) , see info below…
you can check md5 on image file on the command line with
md5 ssp-sandisk-extremepro-32gb-290520221129.img.zstd
note: file corruptions on ‘completed downloads’ is much less common than many are led to believe, even on large downloads. but, of course, always a possibility… esp, if network connection was interrupted at some point.
(d) this seems unlikely, and its not something I can check…
all I can say is im running on an apple silicon mac, running on macOS 12.3.1 … and all is ok, and I think would be the most likely to have issues. so seems unlikely.
as above you could use homebrew to do the extraction, but really I doubt this is necessary, as its working fine here… I think the other ‘issues’ I presented above are more likely the issue.
some general info… which may be useful for those checking if there download is corrupted or not.
file: ssp-sandisk-extremepro-32gb-290520221129.img.zstd
size : 16994017692 bytes
md5 : 9cca3179e3d6d2ae7ea089db170c93ad
1 Like
Thanks for your help. I ended up asking a windows friend to format the card for me and all is installed now. I’ll hopefully have some time to play about with it over the weekend
1 Like
Thanks Mark,
I ll try my best but no sure can solve it.
I work on analogue. all these code and terms not really familiar. md5/change permissions???
Probably Percussa is too much for me, ahahahha.
Anyway thanks again
its not a percussa thing… its just macOS, and the way apple are moving to protect users when using 3rd party applications (like Keka)
the article I linked to above, is for Apple Support, so walks through how to change privacy settings.
you could also try doing the extraction in the downloads folder, rather than moving it somewhere else.
md5… sure I get that, then just check the file size
Id assume zstd will have some kind of integrity checking within its file format, so Id expect if it was corrupted, that keka would very likely display some kind of error message in this case.
of course, you can ignore all that, and just try downloading again 
anyway, I try to give as much info as possible - users can use what they can, or ignore things they find to complicated.
Yeah just refered about my poor skills with code.
Anyway I have followed your tips and finally extract the file.
Thanks for your support
1 Like
cool what was the issue? file/disk permissions?
unfortunately, I suspect this might catch others out too!
Yeah disk permissions. And of course as you said the extraction should be in the downloads folder.
Thanks again
1 Like
Some info setting up the new disk on windows PC
I put the downloaded zstd file into newly created directory on the desktop
Run winrar - I used 64 bit version - and open the directory above (file/open archive)
You won’t see any files - change the ‘All archives’ option bottom right to ‘All files’
Now you should see the zstd file - so select it - then OPEN
Now select the .img file and use ‘extract to’ - select ok - it’ll take a minute or so
the default location will be within the newly created directory
the .img file will be within an image folder
this is the ‘new’ image file you want to write to an sd disk
. . . . . . . . . . . . .
Heed the warnings about overwriting (the sd didk) as once done all is lost - back up what you need/want.
Two ways for me to save older stuff
i) I took a copy of the 'boot' on my current isd disk as that's got presets and other bits and bobs that I can get back to if ever I need to.
ii) I kept the 'old' sd disk so it's obviously easy to return to the previous state and get access to presets etc. and overwrote an even earlier disk with this new image
. . . . . . . . . . . . .
When accessing the sd via PC you may well get a zillion messages and message boxes - ignore by cancelling them (do NOT take the format option offered) - you should end up when looking at the disk with something like the picture shown - here drive letters J: thru to P:
Run the win32diskimager - select the above new disk image
Select the ‘write’ option and point to the ‘boot’ part of the sd disk - here O:
Took 16:09 minutes to write
Eject (the boot)
And try on the Percussa - ran fine!! 
FWIW, I had no issues on Mac with the extracting (make sure you change settings from compress to extract). Flashing was slow but also worked fine.
&e
1 Like
The new software is indeed a huge advancement. Overall VERY EXCITED!!! But I have a couple issues.
The system frequently hangs when changing algorithms in Clouds (latest), but recovers after 1 to 10 seconds which is much better than the hard crashes before. iCloud
The encoders are still super slow, trying to zoom a waveform takes ages. iCloud
The encoder round/limit option is not “sticky” and is saved per preset?
Stereo waveforms look the same as mono ones, I preferred the blue/red glitchy ones from before
Could not zoom all the way out on some waveforms in sampler and granular some weird waveform glitches. iCloud
can you change the title of your links… I kept reading this as 3 bugs on clouds
I had a look at the (one) clds issue its not super clear, thought I don’t see it hanging… in fact, it looks like clds is still producing audio (given the waveforms).
what I believe is happing is when algos are switched, clds is creating some kind of ‘invalid audio buffer’ causing the audio to halt… we saw something similar happen with SAM just before superbooth…so im not 100% sure if its not always been there, and synthor is not quite as ‘robust’ to bad data as it was previously.
anyway, i need to find a way to reproduce it and get some more info.
Oh sorry about the link names. I don’t see how to change the link name in this forum.
In other news, here is a video of the PLY module hard crashing when course pitch is changed. I am however impressed with how quickly it recovers.
There is now an update to the above mentioned software release, which fixes USB audio issues. See Update 13072022 [Superbooth 2022 SD Card image - Fixes for USB Audio, Sample rate switching, ASIO Support]
2 Likes
great, does that mean above software is out of BETA ?
I don’t know for sure (as not talked to Bert), but I’d assume it’s NOT beta.
reasoning :
a) not marked as beta,
the previous release, clearly stated BETA in title, this one does not… looks like a ‘normal’ update.
b) the original beta thread has the following statement.
I also don’t believe more betas were planned, basically the idea was one beta to give a taste, get some feedback, then a release.
important note: putting out new images is more work for everyone (e.g. Percussa and users alike) that a new SYNTHOR - so, Id assume that is where the focus was. also alot of users use the USB side, so great to see thats fixed 
anyway… now off to install this now … remembering, to save all my plugins/presets/samples beforehand !
1 Like
ok, all installed, and glad to say, everything works!
I like that @bert has moved back to a plain zip file
in celebration… as I had to re-setup all my networking again, I thought I’d document the process on the community wiki , particularly, as things have changed a bit …
go checkout things here
anyway, there are two highlights…
(some benefits from all of @bert hard work on this release that he has not previously mentioned!)
as Bert moved to a much ‘fresher’ version of Linux the networking is much improved, and from this we get.
a) Ethernet working out of the box
more usb ethernet dongles are recognised out of the box
b) wifi support
with a bit of config you can use wifi, using a cheap ($10?) usb wifi dongle
details on community wiki, on the how to do…
2 Likes
