From c4a17b83cd07f18cb72e22150468efe27cb9e859 Mon Sep 17 00:00:00 2001 From: "F. Duncanh" Date: Tue, 14 May 2024 21:33:14 -0400 Subject: [PATCH] README fix video memory units (GB->MB) in RPi discussion --- README.html | 8 ++++---- README.md | 6 +++--- README.txt | 8 ++++---- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/README.html b/README.html index aa61121..cd745df 100644 --- a/README.html +++ b/README.html @@ -628,10 +628,10 @@ lower-power models to keep audio and video synchronized using timestamps. In Legacy Raspberry Pi OS (Bullseye), raspi-config “Performance Options” allows specifying how much memory to allocate to the GPU, but this setting appears to be absent in Bookworm (but it can -still be set to e.g. 128GB by adding a line “gpu_mem=128” in -/boot/config.txt). A Pi Zero 2 W (which has 512GB memory) worked well -when tested in 32 bit Bullseye or Bookworm Lite with 128GB allocated to -the GPU (default seems to be 64GB).

+still be set to e.g. 128MB by adding a line “gpu_mem=128” in +/boot/config.txt). A Pi Zero 2 W (which has 512MB memory) worked well +when tested in 32 bit Bullseye or Bookworm Lite with 128MB allocated to +the GPU (default seems to be 64MB).

The basic uxplay options for R Pi are uxplay [-vs <videosink>]. The choice <videosink> = glimagesink is sometimes diff --git a/README.md b/README.md index 3377cbc..f913862 100644 --- a/README.md +++ b/README.md @@ -502,9 +502,9 @@ See [Usage](#usage) for more run-time options. Even with GPU video decoding, some frames may be dropped by the lower-power models to keep audio and video synchronized using timestamps. In Legacy Raspberry Pi OS (Bullseye), raspi-config "Performance Options" allows specifying how much memory -to allocate to the GPU, but this setting appears to be absent in Bookworm (but it can still be set to e.g. 128GB by adding a line "gpu_mem=128" in /boot/config.txt). -A Pi Zero 2 W (which has 512GB memory) worked well when tested in 32 bit Bullseye or Bookworm Lite -with 128GB allocated to the GPU (default seems to be 64GB). +to allocate to the GPU, but this setting appears to be absent in Bookworm (but it can still be set to e.g. 128MB by adding a line "gpu_mem=128" in /boot/config.txt). +A Pi Zero 2 W (which has 512MB memory) worked well when tested in 32 bit Bullseye or Bookworm Lite +with 128MB allocated to the GPU (default seems to be 64MB). The basic uxplay options for R Pi are ```uxplay [-vs ]```. The choice `` = ``glimagesink`` is sometimes useful. diff --git a/README.txt b/README.txt index 6532296..d464317 100644 --- a/README.txt +++ b/README.txt @@ -626,10 +626,10 @@ lower-power models to keep audio and video synchronized using timestamps. In Legacy Raspberry Pi OS (Bullseye), raspi-config "Performance Options" allows specifying how much memory to allocate to the GPU, but this setting appears to be absent in Bookworm (but it can -still be set to e.g. 128GB by adding a line "gpu_mem=128" in -/boot/config.txt). A Pi Zero 2 W (which has 512GB memory) worked well -when tested in 32 bit Bullseye or Bookworm Lite with 128GB allocated to -the GPU (default seems to be 64GB). +still be set to e.g. 128MB by adding a line "gpu_mem=128" in +/boot/config.txt). A Pi Zero 2 W (which has 512MB memory) worked well +when tested in 32 bit Bullseye or Bookworm Lite with 128MB allocated to +the GPU (default seems to be 64MB). The basic uxplay options for R Pi are `uxplay [-vs ]`. The choice `` = `glimagesink` is sometimes useful. With the