The fact it works on my Acer monitor leaves me scratching my head and really bummed the Pi 4 is having these issues.
Very rare, but possible. If my last advice doesn't work, I would go for a replacement.
The fact it works on my Acer monitor leaves me scratching my head and really bummed the Pi 4 is having these issues.
Very rare, but possible. If my last advice doesn't work, I would go for a replacement.
One final thing, before I'm running out of ideas. Try different color spaces by editing hdmi_pixel_encoding at config.txt. Some monitors use YCbCr instead of RGB. Good luck!
Try this config.txt (enforces CEA mode 16):
gpu_mem=320
force_turbo=0
hdmi_ignore_edid=0xa5000080
disable_overscan=1
framebuffer_width=1920
framebuffer_height=1080
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16
dtparam=audio=on
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
Display More
Those settings work for many users with older monitors.
Do you use HDMI 0 as RPi's output? If you use a case with HDMI wiring, remove the case.
PS: Did you already tried hdmi_safe=1 at config.txt?
Nuke Windows, and use LE only, or dual-boot with a standard Linux.
yes, same buffer timeouts on sdcard. But shouldnt the problems occur at some point on every libreelec rp4 installation?
Yes, we already had other reports about AAC issues. Another theory is that the RPi4 data bus is too slow to handle AAC. Try this trick, which will set some data bus resources free, and hopefully solves your issue.
PS: I just found this buffering settings, which you can try, too. I'm optimistic that one of those two approaches will work.
The buffering options are active on A/V playback, WiFi or Ethernet doesn't matter. Try to play the same problematic file from USB stick to rule out slow WiFi.
Understand. I move this thread to the add-on sub-forum, because that's the place of those dev's. Most add-on dev's are at the Kodi forum, so it could be a good idea to ask there, too.
Looks line an AAC buffering issue:
2020-11-23 19:58:21.796 T:2256528240 NOTICE: Finding audio codec for: 86018
2020-11-23 19:58:21.799 T:2256528240 NOTICE: CDVDAudioCodecFFmpeg::Open() Successful opened audio decoder aac
2020-11-23 19:58:21.799 T:2256528240 NOTICE: Creating audio thread
2020-11-23 19:58:21.799 T:2148066160 NOTICE: running thread: CVideoPlayerAudio::Process()
2020-11-23 19:58:21.799 T:2256528240 NOTICE: Opening stream: 6 source: 256
2020-11-23 19:58:21.819 T:2148066160 NOTICE: Creating audio stream (codec id: 86018, channels: 2, sample rate: 44100, no pass-through)
2020-11-23 19:58:21.953 T:2117079920 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
2020-11-23 20:09:36.192 T:2117079920 WARNING: Previous line repeats 3 times.
Option a) Activate pass-through at the audio settings.
Option b) Use advancedsettings.xml (chapter 2.9.5: cache) to edit buffering.
Did you use our search function? We have many threads about Hyperion. Pro-tip: Go to the forums main page before clicking the magnifier icon. That way you'll get results from all sub-forums.
I've never seen this device before, so I just guess it's a color space issue. Provide a log file to see what happens under the hood.
No limits, we just check posts for spam before we activate them.
No problem. You marked this thread as solved. Is that true? If yes, what's the solution?
Fair question, but please stop using super size text - we hate that.
Try output_format=5 or output_format=6 for RGB666,
or output_format=2, output_format=3, output_format=4 for RGB565,
or output_format=7 for RGB888,
Read this GPIO pin table to find the right value. One of those values should be merged into the dpi_output_format value.
Have you already tried display mode 1 (RGB888)?
dpi_output_format=0x070027
The PDF says it should be dpi_output_format=0x070026 for display mode 2.