Hacker Newsnew | past | comments | ask | show | jobs | submit | dither8's commentslogin


Original author isn't involved with this fork AFAIK, but fixes from SoX are backported which is why the author may appear in the commit history.


> Opus is also now supported in WebM, but you still can't just decode Ogg Opus

Apparently Ogg Opus and Ogg Vorbis has been supported since 18.4 (Mar 2025)[1]

I think it would be great to see more adoption of Opus in podcasting personally.

[1]: https://developer.apple.com/documentation/safari-release-not...


It's really hard to keep up with Apple's support for open codecs: it's always bad, and it always improves one minor step per year at best. Evidently, I'm behind on it, because I've mostly given up on trying to make software I work on work well with Apple devices by this point. (I can't tell you exactly what's wrong, but I've noticed I still can't get most WebMs to load in Safari on my M1-based iPad... some of them do, some of them do not.)

Apple is hopefully noticing that while major publishers can be swayed by this sort of behavior, lack of support for open codecs and open formats is going to make the iPhone and iPad web experience much worse for people who veer outside of the mainstream for a bit.


Google would retain copyright to all of it's employees contributions to Chromium. Which I recall being 90%+ of contributions. The propsal PDF from justice.gov doesn't mention Chromium anywhere, so maybe Google will retain copyrights, but the sale would seem pointless if they do.

The real question is to what level Google continue investment in Chrome after the sale. Remember both Mozilla and Apple will also loose out on the search engine deal.


Copyrights do not mean much here except that Google could license that code differently at some point, though the previous licenses are irrevocable so the "sold" Chrome would be the new main line, and Google's 90% of a browser fork under a new license could do something else. They'd certainly have to do some work to get it to be a browser again though because the 10% they cannot arbitrarily re-license is scattered around the codebase and some of it in critical parts of the system.


Thank you. For some reason HN search wasn't showing me anything for CookLang

See also: FOSDEM 2025 lightning talk

https://fosdem.org/2025/schedule/event/fosdem-2025-6651-cook...


This post was inspired by recent discussion here:

RCE Vulnerability in QBittorrent - https://news.ycombinator.com/item?id=42004219

See also:

https://news.ycombinator.com/item?id=38506835, 11 months ago, 14 comments


> This post was inspired by recent discussion here:

> RCE Vulnerability in QBittorrent - https://news.ycombinator.com/item?id=42004219

Worth noting that Rust will not prevent that kind of security hole:

> To be fair, this function ignoreSslErrors is not from the authors of qBittorrent, it comes from QT framework. The idea behind the function is that you provide it a small whitelist of errors you wish to ignore, for example in a Dev build you may well want to ignore self-signed errors for your Dev environment. The trouble is, you can call it with no arguments and this means you will ignore every error. This may have been misunderstood by the qBittorrent maintainers, maybe not.


In my input.conf file I've created filter keyboard shortcuts:

  F1 af toggle "acompressor=ratio=4,loudnorm"
  F2 vf toggle "bwdif"
First one is an alright dynamic range compressor (makes the loud parts quieter and quieter parts loud). Second is a deinterlace at default settings. These are standard ffmpeg filters and mpv let's you turn these on in real time.


I amalgamated some audio filters to cycle through on a F1 press

- Loudness Normalization: "lavfi=[loudnorm=i=-14.0:lra=13.0:tp=-1.0]"

- Loudness Normalization + Mild Tinnitus Filter: "lavfi=[loudnorm=i=-14.0:lra=13.0:tp=-1.0,equalizer=f=6000:width_type=o:w=2:g=-20]"

- Mild Tinnitus Filter: "equalizer=f=6000:width_type=o:w=2:g=-20"

- Aggressive Tinnitus Filter: "equalizer=f=4000:width_type=q:w=1:g=-30,equalizer=f=6000:width_type=q:w=1:g=-30,equalizer=f=8000:width_type=q:w=1:g=-30"

- Bass Reduction: "bass=f=210:g=-17.7"

- Alternative Loudness Normalization: "loudnorm=linear=no"

- Dynamic Audio Normalization: "dynaudnorm=s=0"

- None: ""

F1 cycle-values af "lavfi=[loudnorm=i=-14.0:lra=13.0:tp=-1.0]" "lavfi=[loudnorm=i=-14.0:lra=13.0:tp=-1.0,equalizer=f=6000:width_type=o:w=2:g=-20]" "equalizer=f=6000:width_type=o:w=2:g=-20" "equalizer=f=4000:width_type=q:w=1:g=-30,equalizer=f=6000:width_type=q:w=1:g=-30,equalizer=f=8000:width_type=q:w=1:g=-30" "bass=f=210:g=-17.7" "loudnorm=linear=no" "dynaudnorm=s=0" ""

https://reddit.com/r/mpv/comments/xf8p9t/movie_volume_compre...

https://pastebin.pl/view/2f48e64c


Instead of using 2 compressors in tandem, it might be better to set the very good one to your preference:

  F1 af toggle "loudnorm=I=-14:LRA=1:tp=-1:linear=false:dual_mono=true"
The I=-14 is the target 'volume', which makes it as loud as YouTube and Spotify, setting it to -23 will be much quieter, but gives you more dynamic range. LRA=1 goes from 1-50, with 1 being the most compressing which is probably what you want in this case. TP=-1 sets the limiter to -1dB, which is plenty of clipping threshold because loudnorm calls the resampler for 192kHz before working in dynamic mode. Linear=false because we use dynamic mode here and cannot even use linear mode. Dual_mono=true makes -14 as loud for mono as stereo sources.

Since loudnorm adjusts volumes and sets limits for you, you can forego mpv's audio downmixing if your target is stereo and simply put all your channels together before bringing them to loudnorm:

  F1 af toggle "pan=stereo|c0=FC+LFE+FL+BL+SL|c1=FC+LFE+FR+BR+SR,loudnorm=I=-14:LRA=1:tp=-1:linear=false:dual_mono=true"


Yep I first noticed this a month ago with OpenSans https://www.google.com/search?q=opensans


You can actually do this with YouTube. By search for MOV001 etc.

Mental Outlaw did a video demonstrating this a while ago: https://www.youtube.com/watch?v=t_Ho_KDPi_U



I expected dumb gameplays and influencers. Somehow zero of those. Almost all the random samples have been immensely interesting.


Good luck “searching” for anything on YouTube in 2024..


It's 2024 and need a search engine that doesn't suck


https://kagi.com is by far the best out there IMO.


Also:

- http://startpage.com

(Quite the story, that ...)


It was a journey for sure. I never contributed code, but color schemes and emojis. But I always enjoy Andreas' Serenity videos, even some coding videos were good (I cannot code). These are special and will forever live in my heart.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: