evan314159
evan314159
A tangible advantage to ID3 2.4 is that it standardises storage of multiple values in a tag in an unambiguous way, albeit one that can have sharp edges for other...
It might be worth using a standard ID3 processing library so you don't need to implement all the wonders of ID3 yourself. I noted when I tried to convert my...
I spoke with the MP3Tag author and use of null in ID3 2.3 tags is intentional to avoid the AC/DC problem, and apparently well-supported by applications generally, which just reinforces...
Problem occurs on: UTM Version: 4.1.5 Platform: Apple Silicon (M2) Guest: Ubuntu 22.04 Virtualisation: Apple Network: shared Symptom: tcpdump shows that VM1 attempts to ARP for VM2 and receives no...
In the current code and this PR the LUFS progress is only saved to database after all albums or all tracks have been completed. If the normalisation is interrupted nothing...
It should work if the app encodes the DSD stream as DSD over PCM (DoP). Maybe other open source projects that Fintunes can borrow from? I do not often play...
Key reasons for Tailscale to support wildcards are privacy and complexity. These are the same reasons why enterprises use wildcard certificates. Supporting wildcard certificates *.node.tailnet.ts.net (or *.app.node if Tailscale wants...
There is also Caddy-tailscale https://github.com/tailscale/caddy-tailscale. It seems to be a staff project and could do with formal support from Tailscale but works really well with the community-contributed PRs.
> Seems like many of the usecases here would be covered by the new Tailscale Services concept, including support for autogenerated certs for the MagicDNS domains: https://tailscale.com/blog/services-beta Services don't support:...
Created PR #1013 to implement this functionality