Hello everyone,
This one has been a head scratcher for me for a while. I'll explain the background of what I'm trying to accomplish.
I currently have a Pi 3 running various video files via VLC, all randomized. I am then using that Pi 3 via HDMI out into a HD RF modulator to convert the signal to coax and then that runs throughout my home, so I can tune any of the TVs to the channel and watch whatever is playing (kind of like my own linear TV channel that plays content I want to see).
As we all know, the Pi 3 is getting a little long in the tooth. Only having 10/100 Ethernet makes transferring new content to the Pi a little slow, the content is being housed on an external hard drive and the Pi 3 only has USB 2.0, so there are a few reasons to want to upgrade to a Pi 4 (I was considering a Pi 5 but the lack of hardware H264 non-4K decoding turns me off a little, but I honestly think a Pi 4 will serve my needs well).
On the Pi 3 running Buster (I know I know), I run entirely in CLI mode. VLC is called via a cron job and it displays perfectly in 1080p with no problems. No specific video settings in /boot/cmdline.txt but in /boot/config.txt, these are the settings I call:
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16
config_hdmi_boost=4
hdmi_force_edid_audio=1
force_hdmi_open=1
hdmi_pixel_encoding=2
dtoverlay=vc4-fkms-v3d
On the Pi 4...I can't keep it set at 1080p, at all. It's very odd. I don't have it plugged into the modulator just yet as I'm just playing on and off with getting it setup, testing performance, all of that stuff. But running Bookworm (also running the "Lite" version as this is all console/CLI), I can see the Pi starts up in 1080p, then goes black for a second, then comes back up in 1080i...on a 1080p TV. Additionally then it creates an issue for when VLC is playing a playlist because VLC appears to play video 1 in 1080i, then it temporarily goes back to 1080p, then sets itself back to 1080i, then plays the next video which is not the behavior I want as the Pi 3 Buster solution starts up in 1080p, lives in 1080p, and there is no pause between content.
On the Pi 3, everything just flows as expected: video 1 plays, video 2 plays, video 3 plays, video 4 plays, etc. with no issues. On the Pi 4, I get video 1 plays, resolution change, video 2 plays, resolution change, video 3 plays, and so on. Not the same smooth experience.
From a /boot/firmware/cmdline.txt perspective on the Pi 4, I did add "video=HDMI-A-1:1920x1080M@60" which didn't seem to make a difference. Looking at kmsprint, here is my output:
Connector 0 (32) HDMI-A-1 (connected)
Encoder 0 (31) TMDS
Crtc 3 (94) 1920x1080i@60.00 74.250 1920/88/44/148/+ 1080/4/10/31/+ 60 (60.00) U|D
Plane 3 (84) fb-id: 338 (crtcs: 3) 0,0 1920x1080 -> 0,0 1920x1080 (XR24 AR24 AB24 XB24 RG16 BG16 AR15 XR15 RG24 BG24 YU16 YV16 YU24 YV24 YU12 YV12 NV12 NV21 NV16 NV61 P030 XR30 AR30 AB30 XB30 RGB8 BGR8 XR12 AR12 XB12 AB12 BX12 BA12 RX12 RA12)
FB 338 1920x1080 RG16
Connector 1 (41) HDMI-A-2 (disconnected)
Encoder 1 (40) TMDS
I know it shouldn't matter, but I did add the same settings that I had on the Pi 3 Buster setup to /boot/firmware/config.txt on the Pi 4 Bookworm with the addition of the framebuffer settings and changing the dtoverlay to vc4-kms-v3d-pi4 (I wasn't sure if that would make a difference or not):
dtoverlay=vc4-kms-v3d-pi4
max_framebuffers=2
framebuffer_width=1920
framebuffer_height=1080
hdmi_group=1
hdmi_mode=16
config_hdmi_boost=4
hdmi_force_edid_audio=1
force_hdmi_open=1
hdmi_pixel_encoding=2
This one has me scratching my head. I want to upgrade the hardware, but the current issue of not being able to force 1080p from bootup to in the console is stopping me from doing so.
I know this is digging deep in the weeds since I'm not sure how many people are running their Pi hardware in console mode and having to force 1080p for video playback, but this is the only blocker stopping me from upgrading this hardware and making my life a little better. I'm a Linux pro through and through so I know there is probably a config file somewhere that I need to just put one line in to solve my problem but I can't for the life of me find where to make that change.
Thanks!
This one has been a head scratcher for me for a while. I'll explain the background of what I'm trying to accomplish.
I currently have a Pi 3 running various video files via VLC, all randomized. I am then using that Pi 3 via HDMI out into a HD RF modulator to convert the signal to coax and then that runs throughout my home, so I can tune any of the TVs to the channel and watch whatever is playing (kind of like my own linear TV channel that plays content I want to see).
As we all know, the Pi 3 is getting a little long in the tooth. Only having 10/100 Ethernet makes transferring new content to the Pi a little slow, the content is being housed on an external hard drive and the Pi 3 only has USB 2.0, so there are a few reasons to want to upgrade to a Pi 4 (I was considering a Pi 5 but the lack of hardware H264 non-4K decoding turns me off a little, but I honestly think a Pi 4 will serve my needs well).
On the Pi 3 running Buster (I know I know), I run entirely in CLI mode. VLC is called via a cron job and it displays perfectly in 1080p with no problems. No specific video settings in /boot/cmdline.txt but in /boot/config.txt, these are the settings I call:
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16
config_hdmi_boost=4
hdmi_force_edid_audio=1
force_hdmi_open=1
hdmi_pixel_encoding=2
dtoverlay=vc4-fkms-v3d
On the Pi 4...I can't keep it set at 1080p, at all. It's very odd. I don't have it plugged into the modulator just yet as I'm just playing on and off with getting it setup, testing performance, all of that stuff. But running Bookworm (also running the "Lite" version as this is all console/CLI), I can see the Pi starts up in 1080p, then goes black for a second, then comes back up in 1080i...on a 1080p TV. Additionally then it creates an issue for when VLC is playing a playlist because VLC appears to play video 1 in 1080i, then it temporarily goes back to 1080p, then sets itself back to 1080i, then plays the next video which is not the behavior I want as the Pi 3 Buster solution starts up in 1080p, lives in 1080p, and there is no pause between content.
On the Pi 3, everything just flows as expected: video 1 plays, video 2 plays, video 3 plays, video 4 plays, etc. with no issues. On the Pi 4, I get video 1 plays, resolution change, video 2 plays, resolution change, video 3 plays, and so on. Not the same smooth experience.
From a /boot/firmware/cmdline.txt perspective on the Pi 4, I did add "video=HDMI-A-1:1920x1080M@60" which didn't seem to make a difference. Looking at kmsprint, here is my output:
Connector 0 (32) HDMI-A-1 (connected)
Encoder 0 (31) TMDS
Crtc 3 (94) 1920x1080i@60.00 74.250 1920/88/44/148/+ 1080/4/10/31/+ 60 (60.00) U|D
Plane 3 (84) fb-id: 338 (crtcs: 3) 0,0 1920x1080 -> 0,0 1920x1080 (XR24 AR24 AB24 XB24 RG16 BG16 AR15 XR15 RG24 BG24 YU16 YV16 YU24 YV24 YU12 YV12 NV12 NV21 NV16 NV61 P030 XR30 AR30 AB30 XB30 RGB8 BGR8 XR12 AR12 XB12 AB12 BX12 BA12 RX12 RA12)
FB 338 1920x1080 RG16
Connector 1 (41) HDMI-A-2 (disconnected)
Encoder 1 (40) TMDS
I know it shouldn't matter, but I did add the same settings that I had on the Pi 3 Buster setup to /boot/firmware/config.txt on the Pi 4 Bookworm with the addition of the framebuffer settings and changing the dtoverlay to vc4-kms-v3d-pi4 (I wasn't sure if that would make a difference or not):
dtoverlay=vc4-kms-v3d-pi4
max_framebuffers=2
framebuffer_width=1920
framebuffer_height=1080
hdmi_group=1
hdmi_mode=16
config_hdmi_boost=4
hdmi_force_edid_audio=1
force_hdmi_open=1
hdmi_pixel_encoding=2
This one has me scratching my head. I want to upgrade the hardware, but the current issue of not being able to force 1080p from bootup to in the console is stopping me from doing so.
I know this is digging deep in the weeds since I'm not sure how many people are running their Pi hardware in console mode and having to force 1080p for video playback, but this is the only blocker stopping me from upgrading this hardware and making my life a little better. I'm a Linux pro through and through so I know there is probably a config file somewhere that I need to just put one line in to solve my problem but I can't for the life of me find where to make that change.
Thanks!
Statistics: Posted by charleszimm — Fri Sep 13, 2024 9:00 pm — Replies 0 — Views 20