5 ms·
Agreed, my neighbors probably hate me right now from the audio. On a serious note, though, I hope a write up with more details pops up.
by nikmobi 11y ago
Agreed, my neighbors probably hate me right now from the audio.
On a serious note, though, I hope a write up with more details pops up.
- cellularmitosis 11y agoThis was bad enough that I bothered to figure out how to fix it. VLC -> Media -> Open Network Stream, paste in the youtube URL. VLC -> Tools -> Effects and Filters -> Audio Effects -> Compressor. Enable the compressor. Here's where I moved the sliders: http://i.imgur.com/fGlPM5R.png http://i.imgur.com/fGlPM5R.png I basically followed the advice given here: http://lifehacker.com/5920290/how-to-fix-movies-that-are-really-quiet-then-really-loud http://lifehacker.com/5920290/how-to-fix-movies-that-are-rea... The last 10 seconds of the video is the best way to verify it is working. Without compression, the clapping is ear-drum-splitting-loud compared to the speakers voice.
- karlshea 11y agoThank you, that made this super-interesting video actually watchable. Also, I learned VLC will just happily play a YouTube video right from the page's URL.
- cellularmitosis 11y agoYeah, that trick is also useful for older machines which are otherwise too slow to play stutter-free youtube video in a web browser. The VLC implementation appears to be significantly more CPU efficient.
- jsprogrammer 11y agoProbably pulls the h264 version instead of VP8/9.
- noobie 11y agoI was gonna say there's a Chrome extension (H264ify) that allows that, but then again I doubt the machine would even be capable of running chrome.
- ploxiln 11y agoThat's probably not why. h264 would indeed use less cpu time than vp8 if there was hardware acceleration from the graphics driver available and being used for h264 but not vp8 (which is plausible). But software decoding can be pretty efficient in dedicated video players, and browsers and flash can be pretty damn slow at just getting decoded frames to display. Back in 2010 I was using a computer I built in 2004, which had a single-core athlon64 3200. Watching standard definition video in Hulu was a blocky slideshow, totally unusable. But I could watch 720p h264 video at a decent bitrate, with mplayer, with no hardware acceleration. One of the bigger differences is that browsers/flash have to put the video output as a surface that they composite with the controls on top and the rest of the page behind. Old-style video players actually render to a different hardware "overlay" plane and don't mix anything with it in software, and it makes a huge difference. (My mplayer example is from linux, but I've also used MPC on windows a lot. You can change the renderer in the settings, and "overlay" doesn't support showing subtitles, but has noticeably faster/smoother performance. Well, back on windows XP.)
- jsprogrammer 11y agoYou think VLC pulls the VP8/9 version instead of the h264 version? I seriously doubt it. Why would it? It would make no sense. Most devices have h264 hardware decoders. Most don't have VP8/9 decoders (though they exist). I also have no doubts that an Athlon64 could decode 720p h264 completely in software. You'd be pegging that single core pretty high, but it could do it.
- ploxiln 11y agoMy point was that the hardware acceleration, and vp8 vs h264, doesn't really matter. The computation power of processors sold in 2010, even those in not-very-thick laptops, was probably double my Athlon64. The difference is everything else, the UI stuff (and maybe also flash and browsers being less efficient at decoding than ffmpeg).
- good-citizen 11y agowow, that's amazing. thank you.
- voltagex_ 11y agoLooks like VLC uses http://ffmpeg.org/ffmpeg-filters.html#compand http://ffmpeg.org/ffmpeg-filters.html#compand. If someone wanted to have a permanent fixed version.
- adam12 11y agoNice to know that VLC takes youtube urls. The compressor didn't improve the sound for me though.