God I wish megacorps would stop being morons with NDA nonsense and just open up the possibilities for open source devs to actually use the hardware that’s out there
- 0 Posts
- 10 Comments
stevestevesteve@lemmy.worldto Android@lemmy.world•How to Archive Apps on Android and Reclaim Your Precious StorageEnglish1·9 months agoIdk what it is with certain devices but I have had multiple cases where the device is telling me it’s running out of space for apps, but it has dozens of free GB sitting around.
Maybe there’s some partitioning where there’s limited app storage compared to media etc storage but yeah. It definitely happens and in ways that don’t make a lot of sense
stevestevesteve@lemmy.worldto Linux@lemmy.ml•[SOLVED] debian graphical installation, question about partition tables2·1 year agoLikely changing the “active” flag or boot stuff, but as the other commenter says, if you aren’t 100% confident, disconnect the scsi
stevestevesteve@lemmy.worldto Jellyfin: The Free Software Media System@lemmy.ml•Jellyfin Server/Web 10.9 ReleasedEnglish6·1 year agoThat’s my absolute #1 wish for jf. I’m sure it’s hard work and people are on it, it excites me to think about
stevestevesteve@lemmy.worldto Linux@lemmy.ml•Handbrake/ffmpeg: What free video codec to use for 720p videos?2·1 year agoVP9 has pretty wide support, probably due to the Google (and YouTube) backing. I sincerely doubt devices will phase out any codecs, especially not VP9.
AMD video cards have supported hardware decoding of VP9 since vcn1.0 - well before they had support for decoding AV1
stevestevesteve@lemmy.worldto Linux@lemmy.ml•Handbrake/ffmpeg: What free video codec to use for 720p videos?10·1 year agoAV1 and VP9 are likely going to be your highest efficiency “free” codecs. AV1 is the way to go if you mean free as in free open source. It’s not very likely to be implemented in many TVs or set-top-boxes, but VLC/ffmpeg will be able to decode any of these. Webm uses vp8 or VP9 which are “free”(made by Google) but it’s just more specific settings for sharing online/viewing in browser.
H264/H265 has license fees for non-free software and hardware, but they will be your most widely supported option. H265 is approximately twice as efficient as h264 (meaning you can get the same quality of encode from half the file size).
Regardless of preset I think you can get handbrake to encode something reasonable from any of these codecs. Especially with DVD video you’ll be able to crank through videos with modern high efficiency codecs
stevestevesteve@lemmy.worldto OpenStreetMap community@lemmy.ml•2024: announcing the year of the OpenStreetMap vector maps | OpenStreetMap BlogEnglish8·2 years agoMaybe it’s just harder to break vectors into tiles for partial downloads. You have to know not only the vector coords that are in the tile but also all those that connect to those within the tile
stevestevesteve@lemmy.worldto Linux@lemmy.ml•Optimising Ubuntu performance on amd64 architecture191·2 years agoReading this makes me want to try gentoo again…
stevestevesteve@lemmy.worldto homeassistant@lemmy.world•New IKEA motion, door, and water zigbee sensors under $10 - will these work with Home assistant?English41·2 years agoThere’s a lot of aqara “zigbee” stuff that just doesn’t work properly, even though it’s the same protocol. Also smart electric meters that have zigbee but not in a way that’s useful, just as another example
Not for normal playback but in particular ffv1 is used for archival stuff and is IMHO likely to be used with programmatic usage e.g. generating thumbnails for thousands of chapters of video and the like, where decoding speed does matter.