hardware doesn't even need to be that recent! i'm using an i7 8700K for my plex server and it can transcode h.264 into h.265 on the fly.
kieron115
joined 2 years ago
I've noticed that things recorded on film hold up much better to low resolution compared to digitally filmed content.
The biggest issue with downloading x265 stuff from the high seas is that so many of them are just x264 that's been re-encoded in x265, resulting in smaller file sizes but reduced quality as well. x265 is superior in almost every way technically speaking but it needs a good source material, not an x264 reencode. Their "golden rule" is more like a rule of thumb and I absolutely wouldn't use some blanket criteria like resolution or dynamic range.
Gonna turn an old vacuum tube into an extruder nozzle to keep that nice, warm analog sound.
Can't wait til 3d printers get good enough to make records so i can stock up on audiophile filament!
I would also put a good bit of the blame on executives and marketing people being way out of touch with the average person.
to get something as flexible as my android tv i'd need an nvidia shield and those are going on ten years old at this point. maybe if/when they do a hardware refresh, assuming sideloading isn't completely impossible by then.
Yeah. To be honest on the DNS side it would probably be far easier to just do a whitelist instead, block everything except your specific service. and yeah, its a stupid amount of work. i hate smart tvs but i'll be damned if im gonna pay extra for a streaming box =|
just saying its possible
Not sure if you mean hardcoded DNS IPs or hardcoded "phone home" IPs. Hardcoded DNS addresses in devices are annoying, the only way i've found to get around that is using destination nat rules (DNAT) which requires more than a consumer router typically. hardcoded phone home IPs would get blocked by your firewall. you're right that most firewalls are set up by default to implicitly allow outbound traffic. you set up a rule that explicitly denies all outbound traffic from the TV, then only allow port 443 (or whatever port your streaming service uses) on the specific IP/IPs that your service uses. Here's Netflix's published IP info for example.
edit also i'm fully aware it's fucking ridiculous that we as consumers have to go through this much rigamarole. you shouldnt have to be a literal network engineer to do something as simple as have an internet-connected tv that doesnt spy on you.
no it helps to block everything that isnt just netflix or whatever streaming service you use. you combine a DNS adblock along with blocking all the unused ports and it severely limits the communications. you could also add a vpn to add another layer of security. idk about jellyfin but most streaming services i know use https/443 to stream to your tv. so youre only allowing the specific service you want and only on a specific port. buncha great dns blocklists here https://github.com/hagezi/dns-blocklists, and a smart tv specific one for pihole here https://github.com/Perflyst/PiHoleBlocklist/blob/master/SmartTV.txt
view more: next ›
Yup, coffee lake is when intel quick sync gained HEVC 10-bit. I had a 6th gen in my server for a while and that one needed h.264 content.