Broken input sanitization probably.
Issue will thankfully no longer exist in the next lemmy release.
Not audiophilic enough.
ffmpeg -i in.flac -ar 48000 \
-af aresample=resampler=soxr:precision=28:cheby=1:dither_method=shibata \
-c:a libopus -b:a 224k out.opus
Funny you should mention that. I think iced
as of four days ago can do this!
If I'm reading the release notes and Cargo.toml
right, cargo add iced --no-default-features
and you should be good to go, as tiny-skia
will be used as a rendering backend instead of wgpu
.
Lemmy instance choice does not check out ;)
keep in mind that it’s hard to get real numbers on LDAC because decoding is proprietary
I used to think the same. But as it turns out, a decoder exists. Maybe some people don't want anyone to know about it to keep the myths alive ;)
EDIT: Also, as a golden rule, whenever anyone sees the words High-Res in an audio context, they should immediately realize that they are being bullshitted.
LDAC claims are completely bullshit.
LC3plus is worse than AAC quality wise (to be expected). Lower latency is the only thing going for it. And that's just because AAC is a very high-latency codec. Opus (as a format) would win on both fronts, although there could be issues with creating a high-quality encoder for it that is not too complex, and power-efficient.
I do think it is the future of filesharing
In internet years, Torrenting is old. I2P is old. Even torrenting in I2P is old. Nothing about this is "the future".
Ideally, the future of file sharing would involve a fully/natively integrated anonymous network with content-addressable distributed filesystem.
But this will probably not happen, as that architecture didn't see large scale success before, except in Japan where at least some elements of this architecture are used in their popular P2P networks.
The I2P crowd themselves tried with Tahoe-LAFS, but that was never really a network, even aMule over I2P had more traction, and by traction I mean tens or hundreds of users, not thousands or beyond.
Ironically, the one content-addressable distributed filesystem that gained some attraction (outside Japan) is IPFS, which doesn't offer anonymity, or replication, or anything special really. Yet for some reason, some hype-susceptible techies liked it, together with the NFT crowd, a great fit.
The future of file sharing will depend on where most content will land where it will be easily accessible and quickly grabbable. How those networks will look like? Nobody knows.
Your information is a few years outdated. lineageOS neither comes rooted, nor does it offer a native way to root anymore. Magisk became a thing with a whole community around it. It's an unlocked bootloader hider, root manager (and hider), and a system patcher, all wrapped up in one tool.
With Magisk, you give root access to the apps that need it, hide root ability from apps that require non-root devices (those apps do that by pretending to need root). Also, the Magisk app can rename itself, which is important as some apps check against the name itself.
The future challenge is with Google trying to force hardware identification (Apple style). I have not been following developments regarding that though, since as others mentioned, my X years old phone is still serving me perfectly, and I have no intention to upgrade any time soon.
Don't know if this will be relevant at all, but I'm almost hoping this will force Lemmy devs to abandon the obscure markdown crate they use for pulldown-cmark.
Using an obscure markdown implementation just because it supports spoiler tags always sounded like a silly decision to me!
"*"
dep version requirements.Cargo.lock
to version control.Vec<u8>
later anyway?