Due to the never ending plandemic lockdowns it's now been well over a year since I've done any sorta substantial coding effort at work. It's been mostly just endless talk about maybe getting into the lab and doing something when things finally open up. But now I don't even do that because I got myself "resigned" for resisting the jab.
So I thought maybe I should try and code something in my now copious free time to see if I still got what it takes. And this is where it took me. Ziptuner on Windows 10. Why not?
Update Feb 11, 2022
Problems, problems, problems. The Windows 10 PC is really throwing up some roadblocks. Apparently the Windows Terminal app has quite not come along as far as I'd hoped. The internet and linux have rallied around the versatile variable length utf-8 Unicode encoding, but MS support is spotty, even in the spiffy new tabbed terminal app. I can't seem to stabilize it on one set of glyphs that works well in the ziptuner. I'm sure this is partly due to ignorance on my part, but the OS still gets some of the blame in my mind.
To test it I saved the dialog command from a sample ziptuner query to a simple batch file called dlg.bat and ran it through several paths to the display to try and sort out what's going on. First I just typed it out in the command prompt.
D:> Type dlg.bat
D:> Type dlg.bat | more
Unfortunately, the alternate "Engrish" name on the purple Music Faily disk proved more apt, and it performed as promised. It failed. Or more precisely, it failed for me on Windows 10. I suspect the ancient drivers delivered on the purple mini CD made extensive proprietary use of the CPU for extra signal processing horsepower to assist the stick. Sadly, those drivers only work on expired Windows from the distant past, and while Windows 10 has some generic drivers that claim to support the sound stick, the audio output is a cacophonous discordant disaster. Very discouraging.