Update formatting of requirements in README
Formatted requirements section for better readability.
This commit is contained in:
1 parent
4ba509ab41
commit
b339f76b7d
1 file changed
+5
-5
@@ -26,11 +26,11 @@ Because it runs on a full Linux system and offers access significantly more loca
|
|||||||
|
|
||||||
## Requirements
|
## Requirements
|
||||||
|
|
||||||
- Microphone: Device must support 16kHz mono audio
|
- **Microphone:** Device must support 16kHz mono audio
|
||||||
- CPU: 1Ghz
|
- **CPU:** 1Ghz
|
||||||
- Memory: min. 512MB
|
- **Memory:** min. 512MB
|
||||||
- Storage: The OS and software is around 4GB
|
- **Storage:** The OS and software is around 4GB
|
||||||
- OS: linux/amd64 or linux/aarch64
|
- **OS:** linux/amd64 or linux/aarch64
|
||||||
|
|
||||||
A more extensive list for possible compatible hardware can be found in the [PiCompose documentation](https://github.com/florian-asche/PiCompose) but basically any microphone that works with [PipeWire (multimedia framework for Linux)](https://pipewire.org/) can in theory be used for voice input with the prebuild image from there, you should however preferably use a far-field microphone-array solution if want better result.
|
A more extensive list for possible compatible hardware can be found in the [PiCompose documentation](https://github.com/florian-asche/PiCompose) but basically any microphone that works with [PipeWire (multimedia framework for Linux)](https://pipewire.org/) can in theory be used for voice input with the prebuild image from there, you should however preferably use a far-field microphone-array solution if want better result.
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user