Forgot your password?
typodupeerror

Comment YouTube Audio Quality - Bad Production (Score 1) 100

It's just that the entire YouTube is appallingly bad.

A lot of the audio production in individual videos is really bad. This isn't anything to do with YouTube per se, not their compression algorithms or other features. A lot of YouTubers have absolutely no concept of microphone placement, of using audio compression, of reducing background noise. All of which are things which will drastically affect audio quality and the ability of a speech-to-text model to create subtitles.

It would be nice if YouTube would normalize all the uploaded videos to one set standard. Note I'm not suggesting that they compress the videos as that might change the intended presentation of professional audio productions. I just mean peak-finding normalization which could be implemented losslessly and without breaking existing video links.

Having said that, when I look at my own channel - and I am not claiming to have great audio; I have a host which would destroy a lavalier microphone in mere seconds. YouTube's subtitling is really good. It automatically switches between English and French and Hebrew, and even with a fair bit of background noise (welding, grinding, cooking, crowd noise, music) it generally gets the text correct. So I don't know what the original complaint is, except that it's not perfect. Well, guess what, neither is human hearing. How about that famous Jimi Hendrix line, "Excuse me while I kiss this guy."

Comment Re:My home network is nearly pure IPv6 (Score 1) 73

To me the hoops that smoothbrains will jump through to avoid IPv6 and stay on legacy IPv4, especially when hosting, is pathetic. NAT, port forwarding, tunnels, blah blah blah blah.

I have something like ~1.2 trillion times the number of routable addresses that the entire IPv4 space has. Not all are reachable, of course, just the services that need incoming access and they're each on their own isolated DMZ.

Comment My home network is nearly pure IPv6 (Score 1) 73

Started the move about 18 months ago when I decided to get off my lazy ass. My ISP gives out a /56 prefix, so that lets me run 256 /64 subnets/VLANs in the house, currently there are ~10 in use. Everything get a GUA through SLAAC and I use RAs (Router Advertisements) to give ULAs to everything. Any external facing services get their own VLAN and /64 for the system(s) as needed. Firewall blocks all incoming as they usually do by default and I punch a hole for the external-facing systems. They can't reach back into the network, they only answer the phone. All the systems update DNS dynamically if the prefix or full address ever change.

I have an SSH bastion set up. In all this time there has not been a single SSH attempt from the internet. On IPv4 it was constant background noice.
For those legacy IPv4-only systems on the internet, I set up NAT64. I have an IoT VLAN and IoT 2.4 GHz wireless network that are only IPv4 because a lot of IoT network stacks are junk.

I'm still farting around with it, but man oh man, there's no way I'd go back to IPv4. It was one of the best moves I've done in ages.

Comment Re:How about? (Score 3) 95

I bought a used 2020 XC90 from CarMax last week. I did everything online from shipping it from Texas to Minnesota to financing the extended warranty. I walked in the door, gave them a cashier's check, and drove away within 10 minutes.

That's how it should be.

Slashdot Top Deals

The rule on staying alive as a program manager is to give 'em a number or give 'em a date, but never give 'em both at once.

Working...