I just said that if you take a screenshot of this video and you zoom in you can see the bad downscale.
I’m sorry but I’m not understanding what you are saying. You have the video of the recording so you can do with it what you want. So can’t you take a screenshot of the video if that’s what you want.
Sorry if I’ve got this all wrong.
I did that (screenshot + zoom). This video is SD, bad quality and the text size is small so it is normal that you can’t read the text.
Basically, he’s saying that because it’s from an SD source, you’re never going to get a very crisp picture on an HD screen, and that your TV will likely able to upscale it better than CoreELEC (due to the fact that CE has to do it in software).
To go about using your TV’s up scaling, you’d need to “whitelist” the resolution, so that CE knows that it doesn’t have to try and upscale it. The whitelist is in Settings->System->Display.
Feature request (if possibe):
Due to Amlogic’s very bad quality SD upscaling, I would like to see an option for enabling the SuperScaler in CoreELEC’s menu.
An option fo enabling SuperScaler globally and an option for SD contents only.
Many thanks!
It introduces the cartoon effect and the HEVC double contour effect. So if you want it there is a sysfs module param. Just enable it in autostart.sh.
Re: @gregeeh’s posts…
Maybe someone with display experience can answer this?
What does this mean?
screen_real_width: 1210
screen_real_height: 680
I know some older TVs were marketed and sold as “1080p” when the panel resolution is in actuality much smaller (1080p input-capable, downscaled). If the panel in this display is 1210x680, that would explain the terrible “small text” issue — the display would be downscaling the 1080p signal of an already-upscaled SD stream.
EDIT: Nevermind, that appears to be display measurement (in mm). Interesting that a display can report that info back, but also confusing in that the terms “height” and “width” are used for both physical size and panel resolution.
So, the new 0619 build.
I cannot really do anything without the system hanging, browsing around menus = hang, trying to add media = hang etc …
These hangs are different each time though as sometimes the blue light is off, sometimes it’s solid and the time it takes to reboot itself varies wildly.
Also the network seems to have taken a speed hit, yesterday on 0613 I was getting around 100MB/s for file transfer and today with 0619 it’s only 40-55MB/s under the same conditions with gigabit connection via cable.
Check your SD card… and try another one… if all is hanging than it looks like something broken.
For me all is working. And network speed is normal too. 70-80 MB/sec for my connected HDD
I will try it on the SD card, I was on eMMC before
Can I give you the crash log to look at? I have no idea what I’m looking at with it.
Yep, Upload it to check. May be we will find something.
Just updated to nightbuild0620, can’t wakeup from suspend,down to the build 0619, wakeup from suspend works again.
hi, is it normal for the ethernet light/port on the n2 to be still on after i powered down core elec? or does it mean core elec is still on and using some energy?
Can you try to diable the Wake-On-Lan?
What wakeup method?
Thanks for that bit of info, wanted my ethernet port to be off with the box powered down, but didn’t realize it’s because the default for wake on lan is “on”. Set wol=0 in config.ini and now it powers down with the box off, nice.
BTW, any options for the heartbeat light? Would like steady on.
The heartbeat light should be off in suspend or poweroff.
Right now I’m using heartbeat=0 in config.ini. Would like that to be on steady instead of flash. I know someone answered that before saying there are no options, but just checking to see if that’s still the case.
In that case you don’t use config.ini at all.
You can use sysfs to change the mode.
cat /sys/class/leds/blue:heartbeat/trigger
Will give you all available modes.
Then echo one in autostart.sh