You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the problems I have had with using the official Raspberry Pi OS desktop image, is that for some reason the Raspberry Pi Foundation does not put out a 64bit version. While this means that the image can run on either 32 or 64 bit hardware, a lot of projects just are no longer bothering to support x86_32 systems. I ran into this problem with Mozilla DeepSpeech and Coqui, and now the Phonetisaurus PyPi package also does not support x86_32.
For this reason, I think it would be better to drop the Raspberry Pi OS Desktop operating system and move to Debian Bookworm x86_64, probably running an LXDE desktop.
I have seen some interest in using a Docker container instead of a full virtual machine. My issue with Docker has always been that it makes interacting with the filesystem more difficult, and I also don't know how stable the Docker audio system is. Rhasspy has been recommending users use Docker environments for years, so I should think getting the audio working would be fairly straightforward, but if the user wants to be able to edit the environment, they would probably have to mount the image filesystem using sshfs.
The text was updated successfully, but these errors were encountered:
Selecting this link downloads https://naobian.projectnaomi.com/NaobianX86-1.0.ova, but this version is very old and appears to date back to 2020.
One of the problems I have had with using the official Raspberry Pi OS desktop image, is that for some reason the Raspberry Pi Foundation does not put out a 64bit version. While this means that the image can run on either 32 or 64 bit hardware, a lot of projects just are no longer bothering to support x86_32 systems. I ran into this problem with Mozilla DeepSpeech and Coqui, and now the Phonetisaurus PyPi package also does not support x86_32.
For this reason, I think it would be better to drop the Raspberry Pi OS Desktop operating system and move to Debian Bookworm x86_64, probably running an LXDE desktop.
I have seen some interest in using a Docker container instead of a full virtual machine. My issue with Docker has always been that it makes interacting with the filesystem more difficult, and I also don't know how stable the Docker audio system is. Rhasspy has been recommending users use Docker environments for years, so I should think getting the audio working would be fairly straightforward, but if the user wants to be able to edit the environment, they would probably have to mount the image filesystem using sshfs.
The text was updated successfully, but these errors were encountered: