Faceman2K23

joined 1 year ago
[–] [email protected] 13 points 9 months ago (3 children)

All the more reason to fire up adb and replace that launcher before they take that ability away.

[–] [email protected] 1 points 9 months ago (1 children)

lower res, low bitrate AV1 can be decoded in software pretty well (<1080p animation etc) but with high bitrate 4k AV1 it cant get anywhere near 24fps.

[–] [email protected] 3 points 9 months ago

I hate it on high, but low looks excellent for everything I throw at it, but I had to set my TVs sharpness to zero to get it to play nice, otherwise its an artifacty mess.

[–] [email protected] 2 points 9 months ago

I find it severely overdoes it on anime when set to medium and high but on Low it looks excellent.

I leave it on low 100% of the time and it works great.

[–] [email protected] 5 points 9 months ago

The AI upscaling isn't magic, it's just a decent algorithm to get the best out of lower res content. tuned properly and combined with a TV properly configured to not oversharpen everything it looks excellent but is best left at the lowest setting.

My findings after using a 2019 shield pro since launch (also decrapified via ADB, and running projectivy) is that it is way too aggressive most of the time on the medium and high settings, leading to heavy artifacting and unnatural looking edges. for live action 720p and 1080p it looks fantastic on low and sometimes medium, but often over-sharpened on high depending on the content of the footage on high, for animation it looks down right deepfried meme sharpened sometimes unless you set it to low.

It cant make new detail where there was none before (it's not anywhere near the same tech used in high end GPUs like DLSS), its just a smarter, more content aware smoothing and sharpening filter, you can turn it on and off and bring up a side-by-side to see how it is processing the content to help you tune it and also to dial in your TVs settings to suit. if you use resolution switching in plex it will not be active by the way, that will force the shield to output 1080p and the TV handles the upscale at that point, so turn that off if you want to use the shields scaler.

on 1080p high bitrate content (bluray rips) it looks great, again usually on low or medium, high is too much most of the time, it gets very close to a native 4k rip of the same source if the source is a bit softer to start with, like many films with 2k intermediate masters where the advantages of 4k aren't fully utilised. Native 4k (some higher end films, many high budget tv shows, high value youtube channels etc) still look significantly better at true 4k than AI upscaled 1080.

So set the shield to Ai Low and set your TVs sharpness to zero or very low (mine is on 5 out of 100 for example in its movie preset, every one is different of course), there are calibration and test patterns built into projectivy (great feature!) you can use to tune motion smoothing, colours and contrast in SDR, HDR10 and DV as well as detail test patterns for upscaler and sharpness tuning so use them for the best experience.

One thing to note about the instructions on the website you linked for decrapifying via ADB, on the latest firmwares 9.1.1 and newer some of those commands will crash the shield, so go through them one by one rather than running the one line all in one, go through each line and if it forces a reboot, wait for it to come back and just go onto the next command. it wont do any damage but you have to skip a couple of lines to get it to work.

[–] [email protected] 2 points 9 months ago (1 children)

The UI is definitely better than it used to be, but nodered can do some more powerful stuff like pulling the html of a devices web ui and parsing data straight from the page when there's no API to use for example. I used to do that for a solar inverter at my last house.

Now I use it to control my AV switcher that distributes video through the house, it has no native homeassistant integration and only supports things like control4 and RTI so I implemented my own control using their REST API and hooked it all up to buttons and selectors in homeassistant. works great.

Also my home theatre receiver has a homeassistant integration but its terrible, so again, I've manually implemented the tcp controls in nodered.

[–] [email protected] 2 points 9 months ago (3 children)

I run nodered within Homeassistant in a vm on one of my nucs, I do all of my actual automation in there and homeassistant is just an IO layer for zigbee and bluetooth stuff.

[–] [email protected] 2 points 9 months ago

With Google domains transferring to Squarespace I'll be transferring my one remaining domain with them to something else soon enough.

I already moved all of my other domains over to a local provider I use for work that has treated me well, but this one last google domain address has my self hosted services on it and I was using some features that I didn't want to have to transfer so I kept it with google. I was using their ddns service too but my IP is now sticky (effectively static but can change in some rare circumstances) and it has only changed once in the last 3 years so I think I'll just manually manage the A records if needed until I either go fully static or use a third party ddns provider. I also use email aliasing to use me@mydomain with gmail.

[–] [email protected] 5 points 9 months ago

I have several media libraries so I set up file flows to only perform compression based on a few specific rules. I never used to compress, but 2 years ago I ran out of space and had no money to upgrade disks, so I started compressing, intending for it to be temporary until I could add space. but it became part of my servers automatic setup and it works great.

TV show episodes between 3 and 5gb that aren't already H265 get compressed with RF21 H265, but files over 5gb get RF22. only files older than 6 weeks get compressed to give people a chance to watch them in original quality. the compression flow also includes making a stereo aac downmix audio track for added compatibility. so anything that is already H265 or low bitrate is left untouched to avoid unnecessary compression.

Movies get a similar treatment and H264 files under 5gb are ignored, 5-20gb gets RF21 and 20gb plus gets RF22. All of this is done with 10bit H265 as it tends to look a little better. the amount of compression I;m doing is pretty small, a 3gb TV show for example might end up being 2gb or so, and a 30gb movie will usually end up around 12-15gb at most. I could push harder, particularly for movies but I don't see a need as i've saved 13TB so far with this setup.

If sonarr/radarr download new versions of something (a TV show gets released on bluray for example) it will go back into the loop and get compressed again, but now it will be a higher quality.

4K shows and movies are always left untouched, they are in a separate library and are only accessible to certain clients.

[–] [email protected] 9 points 10 months ago (1 children)

A certain Steve miller band song comes to mind.

[–] [email protected] 3 points 10 months ago

Blame profiteering businessmen and a weak as piss government of the time not stepping in to block the sale of the distribution of essential public information to a chinese entity for profit.

[–] [email protected] 7 points 10 months ago (1 children)

your local library should have them or if you ask they can get them for you or tell you where you can access them.

They are starting to make them more accessible, for example, see here for actually free, official access to the standards but with a few caveats.

view more: ‹ prev next ›