Thanks for the reply. I miss typed. The Getting started documentation is filled with info but as a new user (even though I have 10+ years in the IT field) I failed to comprehend on how to first get started.
I was going purely by the onscreen promts and not the documentation.
I didn’t find the “getting started” documentation until later.
- I failed to understand what exactly an “application” is
- I failed to understand that I was supposed to image the device and boot it up before I could add plugins.
- Had trouble differentiating between “Development” and “Production” images.
- I failed to understand how “adding releases” works.
4.1 The firsttime instructions just say that you should add them via BalenaCLI .
4.2 No instuctions on what to exactly do with it or commands. I spent quite a while just experimenting and google-ing.
4.3 Also had trouble finding BalenaSound. Ended up following this manual >>LINK<< which is already a bit outdated.
It also expects that people are familiar with GitHub and downloading and pushing packages from there (which I was not)
4.4 Would be much easier for new users to redirect them to a website that has these buttons for different usecases.
and then hinting to “advanced users” that they can also visit balenaLabs · GitHub if they’re feeling lucky and want to experiment with diferent branches.
- BalenaCLI also doesn’t show up in the Start menu.
Took some time for me to figure out that the installer just added a whole new set of commands to use.
Slight side note: As I mentioned my previous IT background I also tried to ease my life a bit with adding BalenaCLI as a “profile” to >>Windows Terminal<< but BalenaCLI installation doesn’t generate a GUID. Typing “balena” everytime to every command seemed a bit tedious.
Coming back to my tweaks that I tried. I’ve tried several going off of various GitHub pull requests, balena forum posts etc. Some even “bricked” my OS so I had to remove them or reimage it but I don’t even remember what they were
Anyway this is my current set of added commands:
SOUND_SPOTIFY_PASSWORD not gonna share
SOUND_SPOTIFY_USERNAME not gonna share
Disabling VPN Connectivity check
Disabling Rainow splash screen
Default DT parameters
DT overlay as hifiberry-dac
Local mode is not enabled atm. and the SD card I’m using is the 16GB SanDisk Edge that came with the Pi Zero.
Just an idea but is it possible to create a boot order for the plugins?
Start supervisor and audio first… wait a couple of seconds and then the rest of the plugins?
Also why isn’t
SOUND_DISABLE_AIRPLAY removing the plugin from the bootsequence entirely? Going by the log AIRPLAY currently spends about 46 seconds trying to boot up before it realizes that it should be disabled and exits.
If we’re talking about possible resource constraints then these last two points should probably be a priority…