Update to R2026-07-13 [Linux-ARM32]

[simes_pep]

On a RPi2 can I check that the configuration library has changed from .dBpoweramp to .AssetUPnP
And takes a number of reboots for the change to become effective

Thanks,
Simon.

[cornishman]

Hi Simon,

Same for me too, so don't panic too much.
The installation script also fails to run properly - hard coded path of "$HOME/.dBpoweramp" in both the Linux and Raspberry Pi versions. Tried for ages to find out why the configuration kept changing to the old location. It wasn't until the update changed a Linux machine from $HOME/.dBpoweramp to $HOME/.AssetUPnP that I realised the cause. I was about to wipe and rebuild the Pi machine to get a clean install.

Cheers.

[simes_pep]

Hi, Just making sure.
I don't use the INSTALL scripts as I built the RPi2 before them, with a very early version of Asset for Linux.
I unpack the zip file and override the binary and any other elements that have changed in the directory within a SSH session using WinSCP - very manual.
But I did see the configuration location changed and thought, is that a mistake etc., particularly when I looked at the INSTALL script which still has $HOME/.dBpoweramp
Hence my ticket.

[PeterP]

The installer script was out of date. Revised packages (with same Asset program but corrected INSTALL.sh / UNINSTALL.sh) have just been uploaded to dbpoweramp.com.
Note that offending INSTALL.sh actually succeeds, just gets stuck waiting for Asset to start up because it's looking for a status file in wrong location; you can safely cancel it at that stage.

[cornishman]

Thanks Peter.