I had a brilliant idea this morning. Given the relative sizes and usefulness of cellular phones and GPS units, it won't be long until the mass market is full of devices that integrate both. (I'm sure I'm not the first to think of that, but wait, it gets better...) Here's my idea - for states/regions that wish to ban cell phone use in moving vehicles, or for parents who don't want their kids talking on cell phones as they drive, how about designing the phone/GPS in such a way that if the GPS measures your velocity at, say, above 5 mph it won't allow use of the phone? Could I possibly be the first to think of this? If you think I am and you like the idea, contact me and I'll tell you where to send the check.
"Fantastic!" Every once in a great while, I dive deep down the rabbit hole of media formats and the codecs 1 that encode and decode them. Sometimes it's photos, sometimes it's audio, and this time it's video. I'm no expert in these things, but rather an enthusiast who (a) likes to create and organize digital media and (b) likes knowing that the formats I'm choosing are going to meet my present and future needs. In the past few months I've been adding Blu-ray movies to my media server. I've relied on H.264/AVC as my video format for a long time (more than a decade, maybe?), but with H.265/HEVC now pretty mainstream and AV1 emerging, I figured it was time to refresh my knowledge and get to know how these different tools might serve me. This is going to be a long post, so I'm going to take a moment here to establish the four considerations I make whenever I'm encoding media, whether it's video, audio, or photos. The four consider