I've been transcoding my media collection leaving my PC on overnight over months, it's great. My biggest issue is client support for native playback of AV1, naturally.
For what it's worth, AB-AV1 [1] is a pretty awesome tool written in rust which compares random samples from a file at different parameters based on their VMAF score [2] (algorithm from Netflix for human-perceived visual likeness), choosing optimal parameters to save as much space as possible with the loss you're willing to stomach, on a file-by-file basis.
Small plug: I made a nice little python GUI wrapper for ab-av1 [3].
IIUC, it's more about the client hardware that determines ability to play without transcoding. You'd have to check the mix of devices you have connecting to it and make a judgement call.
First in-the-wild reference I've seen to some of my favourite books. I feel your watch as Goblin makes more sense if it's stuck around with you for a long time and generally works but is a bit of a pain to use. Thanks for the share.
On the normal food blogger pages it is fluff to make room for ads or to get people to misclick on the ads while trying to get to (or back to; the scroll changes feel intentional too) the actual recipe bit. Super effective, especially with people using mobile and trying to scroll with one finger while cooking.
A ton of these sites were bought up and they all look the same now and run the multiple floating ads, especially a wide banner at the -bottom- which is a perfect misclick monetizer.
I thought it's because there's no copyright possible on recipes, but there is on the fluff writing...
I don't know if it's to prevent mass theft of content (oh no, the thieves would have to go through the text and cut off the stories. Although nowadays the biggest IP thieves have built systems to automate this..)
I just bought an AirGradient sensor and set up home assistant. What an absolute joy, both experiences (though I had issues building AirGradient's firmware due to some issues on their end, to their credit their dev team told me they're going to adopt my recommendations) are streamlined and professional and super easy to set up for a techie. I've already got in the habit of opening the window to the office as the sensor detects elevated CO2 (happens faster and more often than expected, very glad I invested).
However, I also bought a 3 SCD41 sensors and ESP32 C3 Superminis from the most reputable sellers on AliExpress, that's been an abject failure. I wanted additional sensors in other rooms less at risk, and wanted to try using ESPHome and putting together my own soldered little devices. Got counterfeit sensors (no laser engraving on the side as Sensiron indicates is without reception the case in genuine parts) and either counterfeit or defective microcontrollers (cannot connect to wifi, even 2.4GHz WPA2, a common enough problem from my research with ). The spread from reputable sellers in NA was absolutely ridiculous and worse then buying premade pieces by a large margin.
All to say, as fun as DIY is, I'm grateful to have trustworthy products available affordably. I'll still block internet access and leave them on a dedicated IoT VLAN, but I can at least not worry it's going to incorrectly label the air quality for a child's bedroom. I'll probably pick up 3 of the CO2 sensors from IKEA, if reviews look good.
I suggest the SenseAir sensors. They don't seem as susceptible to fakes, and auto calibrate when exposed to fresh air. Supported by ESP home so build is simple.
Any evidence the Ikea sensor are actual CO2 censors and not just cheap "eCO2" sensors? Lots of the "CO2" censors our there are just cheap VOC censors with an calculation to estimate CO2.
Seriously. I still find it ridiculous that even after they upped Opus' limit from 60% to 80% they don't show usage % below that. It's sapping my ability to use it quickly on the 5x plan.
Switching to Opus is an eye-opening experience. You hit limits often, and need to get creative to avoid burning through limits, but the difference is seriously impressive. You'll waste a lot less time with dead ends and bad code.
The issue (with Sonnet, I'm not using Opus), is not always that the code is bad per se, but merely that it doesn't solve the problem in the way I expected.
I have two problems with that. Firstly, I want my code to be written a particular way, so if it's doing something out of left field then I have to reject it on stylistic grounds. Secondly, if its solution is too far from my expectation, I have to put more work into review to check that its solution is actually correct.
So I give it a "where, what, how" prompt. For example, "In file X add feature Y by writing a function with signature f(x: t), and changing Z to do W..."
It's very good at following directions, if you give it the how hints to narrow the solution space.
maybe he is not far-right and the framing of how you get your info about Elon is skewing your perception?
His politics have been fairly stable the last 20 years. The Overton window has not been.
For what it's worth, AB-AV1 [1] is a pretty awesome tool written in rust which compares random samples from a file at different parameters based on their VMAF score [2] (algorithm from Netflix for human-perceived visual likeness), choosing optimal parameters to save as much space as possible with the loss you're willing to stomach, on a file-by-file basis.
Small plug: I made a nice little python GUI wrapper for ab-av1 [3].
[1] - https://github.com/alexheretic/ab-av1 [2] - https://github.com/Netflix/vmaf [3] - https://github.com/Loufe/AB-AV1-GUI
reply