Will subtitle depth be supported in 3D m2ts files at some point, @tanio99?
Oh, and how does this interact with Kodi’s central subtitle depth setting? E.g. is that simply ignored for 3D PGS subtitles but still used for .srt subs?
Hmmm, good question. The problem is that the 3d-plane isn’t stored in the subtitle track itself. For instance, for ISOs it seems to be stored in the playlist files (mpls). For mkv files it’s stored in that “3d-plane” tag and AFAIK there’s no such place defined for m2ts files.
Currently, I’m adding the subtitle depth to Kodi’s central one. Do you think that should be changed?
Ok, I installed the latest test version on my vero4k+ and it‘s working good so far. The only bad thing I noticed is a cosmetic bug. If I spress fast forward within a movie, a pink field is shown for a second on the lower half of the screen. Did not have this behavior with the old kernel. Any idea what is causing this?
This build is now live – same updating method as always.
I wouldn’t want to be too prescriptive about that, but off the top of my head… if the subtitles have depth information, the disc author has presumably set it in such a way that there are no clashes, i.e. the subtitles don’t appear “inside” or “behind” an on-screen object. But if there’s no per-subtitle depth info available then you might need to pull all of the subtitles towards you to avoid clashes, and the central setting allows you to do that. So maybe the central setting should control depth when there is no per-subtitle depth information available, but it should be ignored when there is?
OSMC Linux Kernel 4.9 Config breaks UFW (Uncomplicated Firewall) / iptables:
Reproduce:
apt install ufw
ufw allow SSH (better ufw limit SSH)
ufw enable
Easy compatibility check:
/usr/share/ufw/check-requirements
Has python: pass (binary: python2.7, version: 2.7.13, py2)
Has iptables: pass
Has ip6tables: passHas /proc/net/dev: pass
Has /proc/net/if_inet6: passThis script will now attempt to create various rules using the iptables
and ip6tables commands. This may result in module autoloading (eg, for
IPv6).
Proceed with checks (Y/n)? y
== IPv4 ==
Creating ‘ufw-check-requirements’… done
Inserting RETURN at top of ‘ufw-check-requirements’… done
TCP: pass
UDP: pass
destination port: pass
source port: pass
ACCEPT: pass
DROP: pass
REJECT: pass
LOG: FAIL
error was: iptables: No chain/target/match by that name.
hashlimit: pass
limit: pass
ctstate (NEW): pass
ctstate (RELATED): pass
ctstate (ESTABLISHED): pass
ctstate (INVALID): pass
ctstate (new, recent set): FAIL (no runtime support)
error was: iptables: No chain/target/match by that name.
ctstate (new, recent update): FAIL (no runtime support)
error was: iptables: No chain/target/match by that name.
ctstate (new, limit): pass
interface (input): pass
interface (output): pass
multiport: FAIL
error was: iptables: No chain/target/match by that name.
comment: pass
addrtype (LOCAL): FAIL
error was: iptables: No chain/target/match by that name.
addrtype (MULTICAST): FAIL
error was: iptables: No chain/target/match by that name.
addrtype (BROADCAST): FAIL
error was: iptables: No chain/target/match by that name.
icmp (destination-unreachable): pass
icmp (source-quench): pass
icmp (time-exceeded): pass
icmp (parameter-problem): pass
icmp (echo-request): pass== IPv6 ==
Creating ‘ufw-check-requirements6’… done
Inserting RETURN at top of ‘ufw-check-requirements6’… done
TCP: pass
UDP: pass
destination port: pass
source port: pass
ACCEPT: pass
DROP: pass
REJECT: pass
LOG: FAIL
error was: ip6tables: No chain/target/match by that name.
hashlimit: pass
limit: pass
ctstate (NEW): pass
ctstate (RELATED): pass
ctstate (ESTABLISHED): pass
ctstate (INVALID): pass
ctstate (new, recent set): FAIL (no runtime support)
error was: ip6tables: No chain/target/match by that name.
ctstate (new, recent update): FAIL (no runtime support)
error was: ip6tables: No chain/target/match by that name.
ctstate (new, limit): pass
interface (input): pass
interface (output): pass
multiport: FAIL
error was: ip6tables: No chain/target/match by that name.
comment: pass
icmpv6 (destination-unreachable): pass
icmpv6 (packet-too-big): pass
icmpv6 (time-exceeded): pass
icmpv6 (parameter-problem): pass
icmpv6 (echo-request): pass
icmpv6 with hl (neighbor-solicitation): pass
icmpv6 with hl (neighbor-advertisement): pass
icmpv6 with hl (router-solicitation): pass
icmpv6 with hl (router-advertisement): pass
ipv6 rt: FAIL
error was: ip6tables: No chain/target/match by that name.FAIL: check your kernel and that you have iptables >= 1.4.0
FAIL: check your kernel and iptables for additional runtime support
//edit: This means upgrading an working OSMC with UFW breaks network connectivity until disabling UFW.
Do you know what CONFIG_ options are needed to enable support?
You could use iptables for now.
Do you know what CONFIG_ options are needed to enable support?
Not really, these are definitely missing:
CONFIG_NETFILTER_XT_TARGET_HL
CONFIG_NETFILTER_XT_TARGET_LOG
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE
CONFIG_NETFILTER_XT_MATCH_RECENT
CONFIG_NETFILTER_XT_MATCH_MULTIPORT
Do you want to build a minimal kernel? Otherwise it might be a good idea to just migrate the netfilter part from the old kernel config.
cat /boot/config-3.14.29-157-osmc | grep "_NETFILTER_\|_NF_" | grep -v "#"
You could use iptables for now.
Yeah, but just with limited functionality.
I will sync the differences for the next kernel build.
It would be good if you can report back after this and let me know if this fixes things.
Not sure if the last update was meant to fix the issue with the hobbit movie (3d) being squished, but just want to let you know that it wasn’t fixed. Also, i found another movie with the same issue (predator 3d).
one more thing - i’m new to 4k and watching on my epson 5030 (1080p) projector. i just added frozen 4k (mkv) and compared it to the blu ray (1080p), and the 4k version was dark and the colors were washed out. i’ve seen some posts here about tone-mapping but i’m not sure if this is automatic or if there are settings that need to be added/changed. i was assuming that 4k with a 1080p projector was going to have problems, but thought i’d ask to make sure that there’s nothing i can do about it. thanks.
Is it actually in the latest release, or not yet?
@sam_nazarko (or possibly @tanio99), is there any word from Amlogic about a microcode fix for the 3D macro-blocking problem?
Not yet. I think it will be part of the next test build.
I already included it.
I have the 5030 also. Most 4K movies only begin to look decent when the brightness is increased from 50 to 52 and the contrast is increased anywhere to around 56 - 60. Some 4K titles, like Solo A Star Wars Story, need the contrast increased to 70 (and it still looks bland). Other titles, like The Meg, are mastered at 4000 nits and will have highlights completely blown out if contrast is increased at all.
It would be great if some good tone mapping could be added/enabled for HDR to SDR conversion and where we could identify which titles are 4000 nits and not the more common 1000 nits.
Thanks MidnightWatcher for the reply. I love the 5030 and it will be some time before i switch projectors. based on the first post here, i thought that tone-mapping had already been added. is it not enabled?
i’m new to 4k as this was my first experiment with it. do i need to do anything to enable tone-mapping?
i’d prefer not to have to change settings on the 5030 to get a bland or just ok image, but without hdr etc on the 5030 perhaps that’s the best i can hope for even with tone-mapping.
thanks
It doesn’t look like any significant tone mapping has been implemented yet. What I’m looking for is tone mapping that will allow me to leave Brightness and Contrast at their default values and still get a picture from an HDR 4K source that looks as good as, or better than, their SDR 1080p counterparts.
By the way, the Brightness and Contrast settings I mentioned in my previous post are the settings on the Vero 4K itself (and are saved on a per title basis), not the Brightness and Contrast settings on the 5030, which I leave untouched.
that’s great to know! thanks for replying and correcting me. i was wondering why you were recommending certain brightness settings, etc for the 5030 when it is so dependent on other factors such as size of screen, etc.
funny, i never adjust the brightness etc in the vero 4k. i’ll have to see how to do that!
When you play a 4K title, enter the video settings on the Vero 4K while it’s playing and adjust the values from there. You can do this for each title. Start with a brightness of 52 and then try raising the contrast 56 - 60. Watch for highlights. If you begin to lose too much detail, leave the contrast to where you have a good balance of brightness and detail.