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
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
There is no need to talk about an imaginary version of IPFS. GNUnet already exists. You can add that to the list of actually superior technologies that long predates IPFS.
As I mentioned, IPFS is nothing but very basic tech that got overhyped to junior/uninformed developers, and crypto scam victims.
Besides being overhyped basic tech where way more useful and practical solutions existed for decades (Freenet existed since year 2000 btw, and Tahoe-LAFS since 2007), there is nothing private about IPFS. This is a dangerous message to purport.
IPFS is as practically useful as NFTs. No wonder the two crowds connected well!
iroh is an attempt to create a useful and practical IPFS. But none of the bigger practical features is implemented yet. And the design itself doesn’t appear to be finalized. I’m willing to give iroh
a chance, although the close proximity to the IPFS crowd doesn’t fill one with confidence.
Sort by “best” is coming to Lemmy, in case you didn’t know.
Your aggressive tone is predictably inappropriate considering your failure at applying simple logic. You would only have a partial excuse if you’re 11y/o or something.
There is f-droid the app store, and f-droid.org
’s main repo. See, it’s not that hard.
just because they have an app that allows you to add other repos doesn’t mean those other repos are a part of f-droid
And that app is called… get it?
Because those other repos are not f-droid repos
Repos made to work in the f-droid app are not f-droid repos… wow
Is the f-droid.org
’s archive repo not an f-droid repo, too. lol.
Please tell me you’re not an adult!
The thing is, you started on the right track:
Sync is not open source and Fdroid only allows open source.
Here, you are on the right. And you could have followed up later by simply pointing out that “Will it be released to F-Droid” usually means “Will it be on f-droid.org
’s FOSS-only main repo”, but you decided to rant some weird incoherent shit, and insisted on dying on a hell of straws instead!
The codec is basic, uses decades-old tech, and was trivially REed.
Lemmy instance choice does not check out ;)
and for testing you get a wackload of SBCs and Bluetooth chips and test that
I asked because I wasn’t aware of any consumer buds supporting Opus. I wasn’t aware of PineBuds, thank you for mentioning them.
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.
After testing LC3Plus, Opus, and AAC personally for bluetooth, LDAC claims are BS
How did you test Opus for bluetooth?
latency is significantly better then AAC (tested against libfdk) and marginally better then opus
In case you didn’t know, you can use 10ms (or even 5ms) frames with Opus instead of the default (20ms). 10ms should roughly match LC3plus’s default latency while still retaining high quality.
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.
Because the audiophile is broke, and will have to listen to some music on a lowly device, but the craving for some placebo is still there.
EDIT: btw, the bitrate is missing a
k
in your command 😉