2 Months since updating and I can confirm this issue has been resolved since 12.0.1.
Posts by tomstephens89
-
-
There was a recent kernel fix that could be helpful here.
I think the fix is included in LE 12.0.1. Might be worth a test.
I have now been running 12.0.1 for a week and have switched my Denon AVR-X 3600H on and off about 10 times, switched sources as well numerous times.
I am pleased to report the issue appears to be fixed. I am running 60FPS 3840x2160 output in settings and it has reliably always displayed since updating. I have not had to reboot the Pi or switch sources to force output.
-
There was a recent kernel fix that could be helpful here.
I think the fix is included in LE 12.0.1. Might be worth a test.
I have just updated and will test.
-
I upgraded to LE12 as soon as it was available on my Pi5. I use the Jellyfin add on to stream content from my Jellyfin Server.
If I’m watching a movie, playback might stop occasionally and if I’m watching a TV Show, playback might skip to the next episode suddenly.
This appears to happen at random.
Anyone else have this? -
Ok, it responds to on and standby commands from the console cec-client. But nothing when I issue volup or voldown.
Im not concerned with controlling the Pi with the TV remote, I just want to be able to control the volume from the USB remote I use with the Pi like I usually do.
-
Code
Display MoreLibreELEC:~ # echo 'scan' | cec-client -s -d 1 opening a connection to the CEC adapter... requesting CEC bus information ... CEC bus information =================== device #0: TV address: 0.0.0.0 active source: yes vendor: Samsung osd string: TV CEC version: 1.4 power status: on language: eng device #1: Recorder 1 address: 1.0.0.0 active source: no vendor: Pulse Eight osd string: CECTester CEC version: 1.4 power status: on language: eng currently active source: TV (0)Ive also just run getedid delete and getedid create.
Currently leaving everything powered off and unplugged for 10 minutes.
-
Hi tomstephens89 ,
some questions…
- Are you using a case for your RPi4?
- Do you have tried also another micro HDMI to HDMI adapter, if you use one?
- This could be ambiguous: HDMI 1 of „HDMI 0 + HDMI 1“ or „HDMI 1 + HDMI 2“ ?
- Perhaps you can provide a debug log?
Yes I use a case. FLIRC.
Yes I’ve tried other cables and adapters.
Yes I’ve tried different ports.
I can provide a debug if needed.
As I said, this was working, but since either 11.0.5 or maybe 6 it has stopped. -
Hi all,
Now I wish I could be more accurate in when this occurred exactly and what version I was running at the time, but it seems I can no longer get HDMI CEC to work between my Pi4 and Samsung K5500 in the bedroom. I know this used to work and im fairly sure it was on 11.0.5, but Ive had so much going on with buying house and decorating etc... I just can't remember... So theres every chance this wasn't working in 11.0.5 either.
I am using HDMI 1, closest to power. Have tried 2 different cables and all the ports on the TV. Anynet HDMI CEC is enabled, I have power cycled everything, reset TV to factory etc...
Just updated the Pi to LE12 and still no HDMI-CEC.
Short of me flashing a new card and trying LE from default, is this a known issue or is there anyone out there that is experiencing the same?
-
I should have gone with passive cooling for sure!
Now i do more than just play media on my raspberry pi 5, i also host a couple of docker containers such as qbittorrent, autobrr, swag, jellyfin, gluetun and duckdns.
Temp right now is 52.7c without playing any media and the RPi5 has been online but idle over the night
Cool, youre not running LibreELEC on this Pi then?
My backup plan for additional cooling if needed, is simply to use a 'cooling fan pad' like this.
https://www.amazon.co.uk/gp/product/B0CDL2HW6C/ref=ox_sc_act_title_1?smid=A3C69Z8RHG3G6K&psc=1
Just put the pi in the FLIRC case on top of it and youve got all that surface area of the case, combined with active airflow.
-
I use a Pi5 in a FLIRC case and no matter what type of content I am playing, temps are under 55c. Completely passive cooling. The CPU will run to over 85c before thermal throttling occurs.
-
I have been testing caching to disk to deal with a flakey connection, however experience some video stuttering and skips when the MicroSD is getting abused.
The 1GB RAM cache option works great but only results in a forward readahead of 383MB when full.
The max setting now in the GUI is 1GB. Does anyone know if this can be increased via a different file anymore to say 2GB? -
In my Rasperry Pi3 I have used the same MicroSD card for 8 years, it runs 24/7.
Transcend 600x 8GB MLC card, it cost £3.89 at the time
I don't mean to imply that I have 8 years uptime, I have re-imaged the card a few times during major version updates etc. But same card for 8 years with no failure/corruption.
That's good, but if you're not copying content or caching to the card you've barely got a couple of gigs written to it over that time I'd think.
-
So, after some thought, I think im just going to stick to a fast MicroSD. Running an external SSD means my nice tidy FLIRC case set up won't look so tidy.
I also enabled unlimited caching to disk last night for a test and it worked fantastically. The write life of modern SD cards is actually quite high so I don't think this is unsafe as it used to be. I currently have a 64GB Sandisk Extreme Pro V30 card installed, but have ordered a 256GB model instead. I think at £25 for a 256GB card, even if it died every year (which it won't), then who cares?
-
So this thread has got my attention since I use a remotely hosted Jellyfin Server at a datacenter I look after, and have a Starlink connection at home.
If I ran my Pi5 LE install on an SSD instead of a MicroSD, this means I could set the cache/buffer type to store the entire file on disk as quickly as my internet connection could download it, which would be better for me than the 1GB max size currently configurable in RAM.
So how do I go about installing the LE image to an SSD and booting from it, rather than MicroSD? -
Howdy all, an important change that I certainly overlooked is that the settings for readahead/cache which we previously implemented via the advancedsettings.xml file within the userdata folder have now been replaced by a GUI option under Settings > Services > Cache.
I wondered why I was having playback buffering issues since updating to LE12 on my Starlink connection until I noticed the system was not reading ahead.
These new GUI options override whatever you have in the advancedsettings.xml file.
This is documented on the Kodi site and I am sure its in the release notes somewhere!
Hopefully this saves some of you some pain!
-
The workaround is to use AUX1/AUX2 and then you can put the UI at 60hz. I haven't had any issues with this configuration and you can rename the inputs so although it's odd to be forced to use those ports, it has been smooth sailing as long as you plug into one of those.
I am fairly sure I tried this, as have others and it made no difference. Perhaps it’s unique to the 3800H. I have a 3600H and pretty sure using AUX made no difference but I am going to try again.
The workaround is to use AUX1/AUX2 and then you can put the UI at 60hz. I haven't had any issues with this configuration and you can rename the inputs so although it's odd to be forced to use those ports, it has been smooth sailing as long as you plug into one of those.
Can confirm this makes NO difference on my AVR-X 3600H. Using AUX2 still resulted in no signal from a cold start of all equipment until reboot of Pi whilst keeping the AVR on.
I’ve noticed that when I initially reported this problem, switch sources could eventually get display at 60Hz… However in the most recent 2 builds or so including 12, switching sources does not recover the display.
Only a reboot of the Pi does. And once everything has been off for a bit, it will not give me a display. -
The pi devs are currently looking into an issue related to loss of HDMI sync. It's not specifically about 4K60, but you never know, it might be related
This is interesting. But how do we go about reporting this thread as a bug for investigation as we have no idea currently if it’s on anyone’s radar for investigation? -
Bumping to keep this current. Has anyone made any progress on identifying the cause of this issue?
