This seems to be the normal speed for that hardware. The NIC specs don't mean you really get it in real life.
No. The linked chewitt post reported:
I see transfers around ~112MB/s from an RPi5 with nvme storage.
112MB/s is 896Mbit/s, so very close to gigabit.
Yes - you can get close to gigabit real world speed from a Pi5 ethernet port.
This assumes the rest of the network devices and cables can handle gigabit.
this maybe ?
That gives you an irda receiver so you can control kodi.
It has no ability to power the pi off and on.
What a pity. But thanks for confirming this. Can you reference/link one of those boards?
I've never used one of these boards. So can't really advise. Maybe someone else uses something similar.
This is the sort of thing, but that one looks to be discontinued.
The Pi5 can't wakeup over CEC. You can configure to shut down when TV shuts down, but you'd have to use the power button on the Pi5 to switch back one. There do exist some addon boards (HATs) that can power cycle the pi.
But most users leave the Pi on continuously - it uses little power.
Not for 4K. There's no dedicated hardware that can handle it, and it's too much processing for the 3d hardware or arm CPUs.
popcornmix what's the latest on that front? - I can see pelwell and @6by9 commenting so it's presumably on their radar.
Sorry I have no knowledge of this issue beyond this.
I believe officially WPA3 is not supported on any Pi boards, although with combinations of custom versions of wifi firmware, kernel patches and userland libraries some users have had success, but I don't believe it's mature enough to say "this will work".
popcornmix is there any way to force 1080p composite output using kernel DRM?
No, composite cannot handle HD. From here:
Composite video is an baseband analog video format that typically carries a 405, 525 or 625 line interlaced black and white or color signal, on a single channel,
I don't know if there was a way to force an older version of LE using the firmware driver to generate a 1080p gui, and rescale it down to SD, then output it. If there was it wasn't a deliberately supported use case and kernel driver has no mechanism for that.
No. The projector just turns off. Shuts down exactly as if I were to hit the standby/power button on the projector's remote. I need to hit the power button on the remote to turn the projector back on to re-display the picture. The Pi 5 and receiver continue playback through the process. However, I do notice a brief blip in the audio when this happens.
Hmm. If you asked me to create some code that ran on the Pi and powered off the projector without using CEC (which you say is disabled) or DDC (which the pi will never send without running an external program like ddcutil), I'd say that was impossible.
Your projector is choosing to power off for some reason. It could be an intermittent hardware fault of the projector.
It could dislike something about the signal coming from the pi over hdmi (although switching to standby is very surprising for this - normally you would expect a loss of sync, resulting in a temporary black screen, and recovery shortly after).
The likely causes for it not liking the signal (after it being happy for ~25mins) is something marginal - possibly caused by a poor hdmi cable/adaptor, or an inadequate power supply (the 5V from the power supply does go over the the hdmi cable and powers the display/projector's hotplug/edid logic).
Might be worth timing how long playback lasts before failure. If it is always 25min then that would be interesting (but I suspect it is more likely random).
Recommendation for the dev team: If someone enables passthrough then enable it for all formats by default...it makes no sense I have to go into Expert mode and enable them manually despite the main passthrough being enabled already.
Not really.
A TV supporting AC3 passthrough is quite common.
A TV supporting DTS passthrough is quite rare.
A TV supporting DTS-HD/TrueHD passthrough is almost unheard of.
Enabling passthrough on a device that doesn't support it, will at best produce silence and possibly loud white noise.
25ish minutes into a longer movie, projector will shut off but my receiver and Pi 5 will continue to play. The playback may stutter a second or two after this happens as well but resumes.
Just to be clear, the projector shuts off for just a couple of seconds then resumes normally?
hdmi cable would be my first guess. What's the hdmi resolution/refresh rate?
For 4kp60 you do need a high quality cable (and mico hdmi -> full size adaptor if you are using a separate one).
Does it still occur if you force hdmi mode to 1080p?
Other tests would be does the issue occur if you connect straight to projector (no AVR)?
Does the issue occur with a normal TV instead of projector?
I can also confirm this error. There was no problem unber 12.0.0, but after update to 12.0.1, SMB shared folders load time became almost 1 minute on a 1GB LAN network, with Synology NAS.
Your report doesn't match Stooovie's
Downgrading to 12.0.0 did not fix the issue, nor did adjusting SMB chunk size.
Is entering an empty folder as slow, or does it scale with number of files?
Does it depend on the file type of files?
Note that archives (e.g. zip/rar) can cause a massive slowdown, as kodi will open and decompress to file if they contain video/subs etc.
Opening the same folder on LE 12.0.0 or 12.0.1: almost a minute
Can you check for any messages in the debug log during that minute?
Might be useful to install LE 11.0.6 and absolutely confirm that does not have the issue.
Just in case the issue is due to some change in the network or SMB server.
Hi, LibreElec 12.0.1 on a Rpi4, Synology NAS connected via SMB using 1Gbps ethernet. Fine for years, but somewhere around the 12.0.1 update (I can't say with certainty it was caused by it though)
You can always revert back to 12.0.0 and report if that works fine or has the issue.
If it really is due to 12.0.1 then the number is changes to consider is very much smaller than if it is 11->12.
It looks like from the log, the video that was playing when it crashes was using ffmpegdirect addon.
Do you get crashes when playing local content, or is it only videos using ffmpegdirect?
I'm not sure if ffmpegdirect causes significantly more memory usage.
A simple way to reduce some memory is to disable caching. In settings/services/Caching, set buffer mode to no buffer.
A lighter skin may be helpful.
So, it seems manageable for now, so thanks again. Hopefully the root issue will be resolved in further updates, just wanted to raise awareness of it.
Unfortunately this is just feature creep in kodi. Each version released tends to demand more memory.
A few releases back it was feasible to run kodi on a 512M pi, but that hasn't been possible for some time.
More recently, I'd say 2GB is needed for 4K kodi, and 1GB is okay for 1080p (*).
But it depends on the exact configuration. Using certain skins or add-ons may make even 1080p usage on 1GB unreliable.
(*) Note the workaround of "dtoverlay=cma,cma-384" will stop some 4k hevc content from being played, so isn't something that is going to be fixed. You make find "dtoverlay=cma,cma-320" is better for your situation.
Everything was unplugged during the RasPi switch, at least 30 Minutes.
Removing power from the TV (unplug from mains) is the important step here.
I'd power off avr too (although I think that is less likely to help).
From wiki:
LibreELEC 10.x also dropped support for Raspberry Pi Zero and other 512MB RAM devices as 1GB is now considered as the minimum RAM needed for a good Kodi experience.
.
Pi3A has 512M and is not supported. Pi3B has 1GB and is supported.
You could try LE 9.2.8 which may be somewhat usable (as long as you don't want the latest add-ons to work).
