My custom housing is a repurposed fancy/slylish mini settop box from my cable provider that became obsolete. I will post a couple off pics tonight. Although the current status is not to my standards yet… i messed up a bit milling the opening for the display. Due to the lack of a device blowing away the plastic waste, the plastic melted a bit and ended up on the cutter… and i have to rotate the display because of the orientation of the viewing angle, currently its hard to read when flat on the desk (need to make a V2). Once i have finalized which connections to add on the back,I still need to 3d print a back plate.
The housing is black but see through… im still debating what additional fancy lights (or lcd dot/text display) i can add to make it look even cooler if you guys have any ideas for something “usefull” to indicate…
With regards to performance, I have not done any comparison. I’m awaiting a usb3 m.2 case and m.2 120GB SSD to come in. I can perform a boot up time with that setup.
I can check how quickly a synth loads … any specific wishes what to test where we could really notice a difference ?
So my m.2 SSD came in
I tried to measure boot time.
sd card takes about 31 seconds… but because i have set boot order to usb - sd, the system waits for an usb device first before starting from sd… my guesstimation is that this takes about 6 seconds… so it leaves about 25 seconds of real start up time.
ssd starts right through and takes 21 seconds.
Adding a new synth layer (ZynAddSubFx) loading time is comparable.
I my setup i have wifi active, ssh, vnc. Audio set to [HifiBerry DAC+ light], Display: [WaveShare 5 HDMI+USB],Wiring: [MCP23017_EXTRA]
Both configurations run the same SW
I can confirm that you can “repair” your internal sd card while starting from usb by mounting it (accidently made the cmdline.txt changes on the sd card) …
I used the one in the KXStudio thread. I still copied all the elf and bin files, I might give it a go without as I’d like to know if it worked. I didn’t need the blank sd card boot in the linked thread.
To temporarily solve the cmdline.txt device name it’s simply copied from $ZYNTHIAN_SYS_DIR/boot/cmdline.txt so you can probably edit that and it will update and reboot fine.
Not just updates, but also any changes to config can revert it too. That said, if you do get it working and don’t change stuff often, it feels pretty good.
I’m looking carefully on these announcement because I’ve got some “spare parts” liké 2.5 inch SSD and M2 SATA SSD in my definitively dead computers (PC and notebook).
Thanks. I tried this, and made the changes.
However, as soon as I make any changes in the webconf and try to save them, I permanently lose the ability to use webconf over browser. Any ideas?
I found that webconf changes reverts the settings.
In a connected issue, I talked about an SD card extension ribbon I bought recently on the zynth club meetings. It turns out that pi 4s use a low power mode for SD cards and as such, they don’t work very well unless you update the cmdline.txt on the boot partition, which has similar results if you webconf.
I will raise a request tonight to add “special cmdline.txt and config” parameters to webconf to rectify.
