Live data from Hacker News

Hacking YouTube with a MP4

realkeyboardwarrior.github.io

71–80 of 94 posts

Re: Hacking YouTube with a MP4

#71
post #66
post #61

Earlier quoted context omitted.

The current state of the art is Opus, but HE-AAC is also superior, and then there’s always the appeal of lossless which is a lot more practical than it once was.

A format which cannot deliver quality is not state of the art. Opus is the Internet Explorer 6 of musical and video formats.

What on earh are you talking about? For lossy formats, there is currently nothing better than opus in actual use.

Re: Hacking YouTube with a MP4

#72
post #57

Earlier quoted context omitted.

> MP3 is obsolete What should we be using instead for lossy audio?

AAC is far superior, as is OGG, on a technical basis

On the basis of "can it play in my car", MP3 is the only winner. My car's player has one of those baseline decoding chips that can only do MP3.

Re: Hacking YouTube with a MP4

#73
post #67

Video timestamps are weird. Years ago I routinely pulled event VODs from an HLS source and re-uploaded to YouTube. To speed up downloading, I downloaded the MPEG-TS segments in parallel and assembled them with FFmpeg. Initially I used the basic and familiar concat demuxer during assembly. The results were fine locally. Months in a visitor told me that all my VODs had subtle yet frequent stutters. Turned out the video…

This is what I love about tech. I have 15 years experience as a software developer but I have no clue what any of these words mean. Amazing you can have such specialised knowledge about something.

Re: Hacking YouTube with a MP4

#75
post #61
post #57

Earlier quoted context omitted.

> MP3 is obsolete What should we be using instead for lossy audio?

The current state of the art is Opus, but HE-AAC is also superior, and then there’s always the appeal of lossless which is a lot more practical than it once was.

HE-AAC is only useful at low bitrates though (below 64 kb/s), and supposedly never reaches transparency. Above that, you should use AAC-LC (or, of course, Opus if you can).

Vorbis is also notable as a better format than MP3, although that too is made obsolete by Opus.

Re: Hacking YouTube with a MP4

#76
post #72

Earlier quoted context omitted.

AAC is far superior, as is OGG, on a technical basis

On the basis of "can it play in my car", MP3 is the only winner. My car's player has one of those baseline decoding chips that can only do MP3.

That's true, MP3 is by far the most widely supported lossy audio format (except presumably MP1/MP2, since MP3 decoders have to support them), so it will live on for a long time, although Opus is the best one nowadays. Just like with PNG and JPEG for images, which will live on for a long time even though we have WebP, AVIF and JPEG XL. And AVC will probably live on for a long time even though we have HEVC, VP9 and AV1.

Re: Hacking YouTube with a MP4

#77
post #67

Video timestamps are weird. Years ago I routinely pulled event VODs from an HLS source and re-uploaded to YouTube. To speed up downloading, I downloaded the MPEG-TS segments in parallel and assembled them with FFmpeg. Initially I used the basic and familiar concat demuxer during assembly. The results were fine locally. Months in a visitor told me that all my VODs had subtle yet frequent stutters. Turned out the video…

This is what I love about tech. I have 15 years experience as a software developer but I have no clue what any of these words mean. Amazing you can have such specialised knowledge about something.

Your comment gave me perspective on how far down the rabbit hole my media server has taken me, as I was nodding along to everything the parent poster said having encountered similar issues with FFmpeg in the past.

Niche knowledge really can creep up on you over the years as you gradually encounter problems and work to solve them a few hours at a time.

Re: Hacking YouTube with a MP4

#78
post #72

Earlier quoted context omitted.

AAC is far superior, as is OGG, on a technical basis

On the basis of "can it play in my car", MP3 is the only winner. My car's player has one of those baseline decoding chips that can only do MP3.

Same here. And it doesn't even do that very well. Imagine spending 15k or more on a brand new car in 2021 just to realize that the sound tech is borrowed from a $5 MP3 player from the early 2000s.

Re: Hacking YouTube with a MP4

#79
post #38

Folks, just because the author wasn't wearing a Guy Fawks mask with a black hoodie and made no mention of gaining access to the Central Meme Database, that doesn't mean they weren't hacking. They were hacking around with MP4 muxers and YouTube. This is definitely the hacker spirit. The word doesn't need to be re-appropriated by Hollywood caricatures.

Does anyone else really use "hack" in the way HN uses it, ie with its original meaning? For your average person a hacker is a person in Guy Fawks mask with a black hoodie that steals your facebook password. For people in the industry a "hack" is a code that works but might be a placeholder/potentially dangerous code. The author would want to write a better version of it but perhaps is not able to due to time or desig…

To be fair, thanks to lifehacks, growth hacks and whatever it seems hack slowly fades back into the original meaning. At least from my POV

Re: Hacking YouTube with a MP4

#80

Earlier quoted context omitted.

This is what I love about tech. I have 15 years experience as a software developer but I have no clue what any of these words mean. Amazing you can have such specialised knowledge about something.

Your comment gave me perspective on how far down the rabbit hole my media server has taken me, as I was nodding along to everything the parent poster said having encountered similar issues with FFmpeg in the past. Niche knowledge really can creep up on you over the years as you gradually encounter problems and work to solve them a few hours at a time.

While I have not been this deep into the inner workins, I personally have skimmed that rabbit hole when I started a side-project that was essentially grep but for (mainly) MKV files.

Idea was that you could "grep" by specific text in the subtitles and automatically create a clip of every occurrence of the text (by looking at the subtitle timing and padding that in both directions).

The biggest source of my frustration was that I was unable to get the clipping to work exactly as I wanted, where the start or end of the clip would seemingly drift back and forth. That was until I realized it boiled down to how the different seek modes in ffmpeg handled keyframes.

I still haven't gotten the clipping to work exactly as I want but I figured doing two passes might be the way to go: first pass would do a fuzzy match and ensure there is enough extra on both ends of the desired clip and the second pass could re-encode the fuzzy-matched clip to shuffle the keyframes around, allowing more accurate clipping.

Post reply on HN