My system has been handicapped after the Music Assistant Dev’s had a big update on their release after v2.3.6. The update had CPU benchmarks due to transcoding audio requirements that would make it so Music Assistant would not even start if the CPU didn’t meet or exceed their programming. This effectively rendered a lot of older CPU’s incompatible with Music Assistant and made it so older hardware was stuck on v2.3.6… until now! Thank you, Devs! I can finally take advantage of all of these awesome new features, providers, and players. Excellent work! According to the release notes, older CPU’s from ~2009 can work now. Fair warning, Music Assistant v2.7.10 is still more resource intensive than v2.3.6 and just because Music Assistant will start on your system doesn’t mean your system can handle some of the transcoding depending on your audio formats. Users beware.
1 Like
Note this edit is the reason some may have issues with MA and Piper on Proxmox.
The default Proxmox HA scripts set a very vanilla processor type (doesn’t support SSE2) therefore your awesome Proxmox box suddenly can’t run the container and crashes out.
If you’re running ha on Proxmox and see MA or Piper crashing inthe app logs set the processor type for the HA VM to ‘HOST’ to allow the VM access to the additional instructions to let MA and Piper etc. Access the media accelerator instructions to make it work… (also resolves Piper and MA crashes on recent versions on Prox)
2 Likes