Pixel aspect ratio for 7'' display

[Romanz]

Greetings

I have a Pi4, 7'' 1024*600 display with HDMI, installed Moode Audio 9.0.6. The config.txt file says the following:

hdmi_force_edid_audio=1
max_usb_current=1
hdmi_force_hotplug=1
config_hdmi_boost=7
hdmi_group=2
hdmi_mode=87
hdmi_drive=2
display_rotate=0
hdmi_cvt 1024 600 60 6 0 0 0

Everything is fine until the UI, but the GUI itself is flattened. The circles look like ovals. How can this problem be fixed? Thanks

[Tim Curtis]

Try without any of the custom config.txt custom settings from the manufacturer.

The stock moode 906 config.txt is below.

Code:

#########################################
# This file is managed by moOde
#########################################

# Device filters
[cm4]
otg_mode=1
[pi4]
hdmi_force_hotplug:0=1
hdmi_force_hotplug:1=1
hdmi_enable_4kp60=0
[all]
dtoverlay=vc4-kms-v3d
max_framebuffers=2
display_auto_detect=1
disable_fw_kms_setup=1
arm_64bit=1

# General settings
arm_boost=0
disable_splash=1
disable_overscan=1
hdmi_drive=2
hdmi_blanking=1
hdmi_force_edid_audio=1
hdmi_force_hotplug=1
hdmi_group=0
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=audio=on

# Do not alter this section
# Integrated adapters
#dtoverlay=disable-bt
#dtoverlay=disable-wifi
# Audio overlays
#dtoverlay=none
#dtoverlay=force_eeprom_read=0
# PCI Express
#dtparam=pciex1
#dtparam=pciex1_gen=3
# Pi Touch
#dtoverlay=rpi-backlight
#dtoverlay=vc4-kms-dsi-7inch,invx,invy

[Romanz]

Try without any of the custom config.txt custom settings from the manufacturer.

Then the aspect ratio shows correctly, but everything is small, the image resolution is larger than the display resolution of 1024*600. Even the initial text output on loading is shown in very small font.

[Tim Curtis]

What version of moode are you using and what is "Integrated audio" set to in System Config.

[Romanz]

What version of moode are you using and what is "Integrated audio" set to in System Config.

Moode 9.0.6 and Integrated audio: Kernel mode (Default)

[Tim Curtis]

In that case you prolly have to use the manufacturer settings in config.txt and ask them if they have a solution for enabling square pixels.

When I tested on the Pi 7" Touch it also had non-square pixels and I wasn't able to find a solution for this with Bookworm and the KMS videocore driver.

[Romanz]

I now have another problem - I wrote in config.txt screen settings. When loading the resolution is normal, the text goes through, and then the screen clears and the text goes but the resolution is much higher, as if the screen goes to a higher resolution. And then appears UI with such a resolution, as on my computer monitor, and it has a resolution of 1920 * 1080. It turns out the monitor scales to FullHD. Though at the first installation everything was normal, only wrong proportions at UI.

[Romanz]

I installed moode audio 8.3.9, prescribed screen settings in config.txt - everything became normal, resolution is normal. And the shrivt at startup is normal, and the resolution does not change during the boot process.

[TheOldPresbyope]

I installed moode audio 8.3.9, prescribed screen settings in config.txt - everything became normal, resolution is normal. And the shrivt at startup is normal, and the resolution does not change during the boot process.

Trouble is, that experience with moOde built on Raspberry Pi OS Bullseye edition does not carry over to moOde 9.x built on Raspberry Pi OS Bookworm edition. Many of those config.txt settings are now considered legacy settings. Of such settings, the official Raspberry Pi documentation says

The config.txt options described here are considered legacy settings, are not used by Raspberry Pi OS Bookworm, and are no longer officially supported. They either relate to older software such as the firmware graphics driver, have been deprecated, or are very unlikely to be used by most people. However they remain documented here as they may still be of benefit to users of older OSes, or people doing bare-metal development.

A number of us are struggling with how to accomplish similar results in Bookworm. Unfortunately, the answers appear to depend on specifics of the display we're trying to use.

I'm hopeful but we're not there yet, wherever 'there' is. As one example, some of the things I recently said in a reply to another user's post concerning tests of my full-sized HDMI computer monitor have turned out not be equally true for a small Waveshare LCD display I just dug up which has a HDMI interface board that doesn't seem to conform to expectations.

Regards,
Kent

[Tim Curtis]

The challenge is that many display manufacturers in the DIY space don't keep up and test with new OS releases. I wouldn't count on much support from them for any given panel.