I feel like I’m blogging too much lately, but I also feel like I have a lot of stuff rattling around in my head, and I need to get it out.
I’ve mentioned in a recent post that we’re in the middle of a company-wide Windows 11 upgrade at work. They finally got around to pushing it out to my desktop on Wednesday and my laptop on Thursday. The desktop upgrade broke networking, which was a bit of an issue. I won’t get into the details, but I had to unplug the PC and walk it over to our help desk so they could get it working again. That cost me a couple of hours, between the upgrade and all the troubleshooting and back and forth.
The laptop upgrade was easier. I had a similar networking issue, but I knew how to fix it now, and could do that myself, in that instance. Also, I could continue working on the desktop while the laptop was updating itself. (With the desktop, I hadn’t brought in the laptop that day, so I was stuck fooling around on my phone while the upgrade was running, and while I was waiting on the help desk…)
Windows 11 hasn’t broken any of the tools I rely on for work. It’s made one or two things slightly harder to do. I don’t think it’s made anything easier. (I’ve probably said this before, but my criteria for OS upgrade success these days isn’t “does it make things better?” but rather “does it break anything important?” and “how much more of a pain is it vs. the old version?”)
I’ve been toying with the idea of upgrading my home desktop PC to Windows 11, despite the fact that it’s not really supported. (The CPU is too old.) I set a registry value that is supposed to bypass the CPU check. But that still wouldn’t allow me to run the installation assistant. So, then, I made a bootable installer on a USB stick, but that won’t let me upgrade, just do a clean install. So, anyway, that was all a waste of time.
Back on the audio stuff: There were three football games airing exclusively on the NFL Network yesterday, and I wanted to watch them. (Maybe not all of them, but I wanted to kill a little time with football playing in the background.) My NFL+ subscription lets me do that, but I couldn’t get the audio working in the NFL app on my Apple TV. This is one of those things that should just be a minor irritation, but I was in enough of a mood when this happened that I got really frustrated with it. I actually could get sound, weirdly, if I switched from my TV speakers to AirPlay output to my Sonos speakers. (I’m using a Sonos soundbar as my TV speaker anyway, but I have it directly hooked up to the TV, so the Apple TV isn’t normally aware that it’s even using the Sonos.) I’m definitely not the only person to have this issue with the NFL app. I’ve found references to it on Reddit and the Apple forums. And the NFL+ site has an article about troubleshooting audio problems, but it’s typically generic and useless.
The frustration was mostly around how complex something as simple as watching TV has gotten… It used to be that you could just turn on your TV, and, you know, watch a football game. Now I have to turn on the TV, switch the HDMI input to the Apple TV, turn on the Apple TV, launch the app, watch it lock up, force quit the app, relaunch the app, wait for it to load, find the right button to press to get into the right feed… Yeah, I know I’m an old man. I should be happy I have so many options for quality entertainment.
And a little more on my new Beats Studio Pro headphones: I found a good video review of them from MKBHD. And I used them last night to watch 65 on Netflix. “Loud dinosaur movie” was a good choice for checking them out. They worked well for that, and successfully drowned out the Christmas music outside.
I’ve been awake today since 5:30 AM. It’s almost noon now. I haven’t done much useful, but I made myself a nice breakfast, went for two walks, listened to some music, read some comics, and had a croissant for a snack, so life is good, I guess.