Victoria of Many Faces, Vol. 1 (light novel)

I read Victoria of Many Faces largely because I enjoyed one of the author’s other books, Soup Forest, and decided to pre-order the moment that Amazon notified me about the coming title. It turned out to be an excellent choice, and I almost binge read the book in about two or three sittings. In fact, the only reason it took three days is because I decided on the second, that I really did need to sleep πŸ˜….

Victoria is perhaps one of the more interesting light novel characters that I’ve encountered. Fleeing the organization, she ends up settling in another country and becomes embroiled in various antics–which eventually lead to her efforts to lie low becoming more complicated as time goes on. But we see a character who’s done some not-so-great things choosing to deviate from what they were trained to do because they choose to follow their heart. Even from the very beginning, Victoria recognizes that her course of action would be ill-advised and if she were still an operative would have to avoid the risks that it incurs. Faced with that, Victoria makes her own choice about what is right and that moral compass sets her on a beautiful course.

I love that the actions Victoria takes are her choice, and often bring about the major shifts in the plot. As a light novel, Victoria of Many Faces is often amusing and intriguing, and honestly I laughed so hard during the pub scene with the cat….I love so much that it’s even captured by one of the illustrations. The follow up in the bakery was superb, with there “Don’t you want to ask me something? / Do you want me to ask? / No” moment ending with the two laughing like loons. It’s very much like a shared story over cake, and plays off the incident with such comedic beauty.

Throughout the story, Victoria’s interactions with other people define what becomes the new “Normal” for her. By making it a slice of life tale, I think the story captures well why such shifts in Victoria’s life lead her towards finding happiness in such unlikely actions.

The ending in particular was rather beautiful, and after having seen several of the character’s aliases and efforts at concealing her true identity, Victoria’s exchange with the captain is especially poignant at the end. I’m glad that when all is said and done, she is able to reveal both her true self and the name hidden behind it all.

Overall, I would say that the protagonist is more realistic than most LN characters tend to be while remaining a vehicle for the story, and that makes her a wonderful counter-point to the various antics she gets wrapped up in. Victoria of Many Faces becomes a fairly warm slice of life / action comedy with a bit of romance here and there as the volume progresses, and it works really well IMHO.

I’m rather looking forward to the second volume, and hope that it proves as entertaining as the first was.

Ramblings of an insane nerd

The conceptℒ️ 

Mp3Tag (Mac rather than Win in my case) for managing metadata. Cover art is a weak point for something like Quod Libet that I would otherwise choose, and the Mac version is broken on modern systems, meaning I would have to break out my 17 year old ThinkPad to run the FlatPak, or suffer X Forwarding or similar grumbles with restoring my 12 year old Latitude to its Debian glory days. Thus indie software wins this scenario because MacBook Air.

Good ol’ ffmpeg for audio conversions. I’m really not a fan of hand-wrangling ffmpeg, and don’t want to mess with it for cover art purposes. It’s like a grizzly bear wielding a Swiss army knife when it comes to esoteric video muxing and complex encodes, which are a pain. But I’m content to use it for transcoding audio. The open question is whether I want to load ffmpeg on one of my Linux server’s virtual machines, or just brew install ffmpeg while drinking a root beer.

These both solve the problems that exist between my existing music collection, and what Apple Music can offer in the ways of managing a personal music library like it’s still two thousand ‘ought something.

Apple Music is still combat effective for ripping CDs, since I actually like the iTunes+ format of MP4 + AAC 256K and it does a passable job of fetching metadata. It’s just after the disc is ripped, we’re done.

The file server for warehousing data. I’ve mostly followed the pattern of collecting content in its various forms under Music, while backups exist imaginatively under Backups. Things will probably become divided either by format or purpose, such as FLAC, M4A or Library, Player directories in place of the existing “Artist – Album” structure. I might debate between the old media depot under Backups getting reorganized or moving to a dedicated “Originals” structure organized by source (CD, Steam, iTunes, Amazon, Google, yada, yada) on my Music share. One of the advancements over the past decade is its no longer just “Backups” and individual hosts that gets backed up regularly, but the entire file server’s shares where LAN data lives.

This path of insanity makes a good excuse to start normalizing my approach to dealing with cover art, lyrics, and readme files pertaining to music–but are a smaller problem than ensuring sane song metadata and library structure. Enforcing a tag editor centric data flow is also a good reason to make for easily saving/loading metadata from disk.

I’m also thinking that for a general approach to normalization, making MP4/AAC the standard lossy format with FLAC as the lossless where applicable. One of those things that has changed over the past decade and a half, is I’ve no real reason to prefer MP3/320K over AAC/256 or WAV over FLAC. Software compatibility for decoders (unless perhaps, you’re a damn iPod or the like) just isn’t a problem like it was in the early days of AAC, and there’s no real reason to treat the hax that ID3 evolved from and WAV is basically the software equal of a 3.5mm analog jack this side of FLAC.

Yup, let’s just say the iPod experiment finally drove me over the hill ^(o_o)^

Continuing iPod Experiments

Augmenting the iPod, I’ve ended up with a trio of different players. Okay, so yeah, I finally went crazy πŸ€ͺ.

Digital Media Players

There’s the iPod in the middle that I’ve posted about a few times, which is effectively a 5th generation late 2006 model with a new front plate, battery, and a 64G SD card replacing the 30G hard drive. Not to mention some blood, sweat, and tears invested. Well, thankfully not blood since I used an iFixIt toolkit instead of an Elite Old Electronics opening tool, but I can now understand while opening the metal models that followed is such a pain πŸ˜‚.

Flanking this is to the right is HIFI WALKER’s H2, which has turned up so often in YouTube and Amazon suggestions, that we may as well call this a crosspoint between being advertised to death and being pissed at the iPod that much.

On the Left is Innioasis’s Y1, which is a device that I had came across researching the cost between old iPods and the question, “Surely someone makes a modern thing with a clickwheel,” and it is also the cheapest of the group. The wallpaper set is one I used to use on my Xbox One, not the standard one.

iPod 5th Gen

The iPod actually works pretty good when it works. Issues stemming from the memory card size and the cable aside, the primary beef I have with it is the PC/Mac software. It’s pretty cool that Apple Music and Finder/Apple Devices supports recovering and syncing to iPods in this day in age, but frankly the software sucks.

Syncing services on Mac are pretty crappy but do remain effective. It’s been so many years since the Apple sold iPods, a product that originally began in the PowerPC era, that I can forgive the CPU load and occasional bottlenecking, because it does in fact work. Enough so, that I kind of suspect at least one or two quality assurance engineers at Apple must still have an actual iPod. But I suspect that hooking it up to something on my Linux machine using libgpod would be far, far more resource efficient.

The only thing that was hacky was recovering on Mac, since its kind of a pull plug and restart trick; it’s better to just use Apple Devices on Windows unless you specifically want a Mac APM/HFS+ formatted iPod instead of a PC MBR/FAT32 formatted iPod. Otherwise, the software is just like grossly inefficient and twitchy. Like, the sync services may be one of the more CPU intensive things I’ve ever run on my MacBook Air–a machine that can find itself doing x265 video encodes in 1080p, lol.

Hardware wise, I think the iPod is pretty great. Discounting the cable hoopla and surgical procedures, the worst I can really say there is that it uses the old 30-pin connector and that I don’t want to desolder that for a USB-C mod.

Something that remains questionable is the decoder. Certain audio tracks lead to artifacts in playback, which do not seem to affect other devices.

Attempts at running Rockbox have been spotty enough that I returned to booting into the iPod’s native OS. Stability seems to be better in recent development versions than 3.15 stable, but the combo of an iFlash Solo and Rockbox on the iPod means having to boot into the iPod’s disk mode to sync. Using Rockbox’s USB mass storage mode leads to corruption and slow I/O, the kind where the memory card in the iFlash Solo seems to both get files jumbled up (parts of another song running together) and shitting data across the disk in a way that makes fsck wonder just what the fuck was done to it, lol.

In a nutshell, running the iPod firmware gives crap syncing and running Rockbox firmware is a bit twitchy in my hardware configuration. I think if Rockbox was stable or I had less grief with the iTunes front, I would spring for a 30-pin Bluetooth connector like one from Kokkia; it’s less effort than modding but too expensive to splurge on during the experimental phase.

HIFI Walker H2

The H2 is perhaps the real winner in the experiment, or at least the lead horse. Hardware wise, I can’t say that the style really does it for me, but it is very well made. It feels like a brilliant hardware engineer went craftsmen on the ODM front, and then let his cousin Bob write the firmware as a college project so that they could sell it as an white label product.

The H2’s hardware reminds me a lot of the old school Walkmans. So much so that it makes me wish for a belt clip, lol. The zinc alloy frame seems to be pretty durable, and I wouldn’t be surprised if it would hit the pavement like a Chuck Norris joke and come out unscratched next to a broken side walk. Looking online for tear downs, suggest that it likely has a pretty hefty battery filling most of its thickness. While our tastes may differ, I have a lot of respect for whoever designed the H2 hardware, they did an awesome job. Coincidentally, the earbuds that come bundled are pretty darn nice!

Software works as advertised, but is the worst user experience of these three players. I think that the vendor would have been better off hiring some Rockbox developers to improve the port, and someone else to graft on Bluetooth support. The awesome thing is the Rockbox build is even more stable than the original firmware, and sounds like it will be promoted to stable whenever Rockbox 4.0 happens. The main negative to hosted Rockbox, is it places the firmware on the memory card at .rockbox, where the native firmware is on the player’s tiny, tiny internal flash; which makes it easier to go oopsie with an rsync. The Rockbox wiki page has plenty of info on the hardware which is quite helpful.

For the most part, I find myself using the H2 most often in the past few weeks–but booted to Rockbox rather than the OEM firmware. The worst thing that I can say about RB on the H2 is that it doesn’t support Bluetooth, which is pretty much true of everything that runs Rockbox. The native firmware seems to be better about handling cover art, but the only real reason to use the HiBy Player firmware that’s on the H2’s flash is to use Bluetooth.

My preference for BT, and the support for aptX being one of my reasons for coughing up the dough aside. I think that one would be better off using Rockbox and tag editing software on a PC to handle their music collection. From the sounds of the manual, future software updates are likely to include a version of HiBy player that doesn’t support as many features, so Rockbox is probably a net win.

While I’ve experienced no problems with the USB mass storage mode in the H2’s native HiBy Player or the development builds of Rockbox, it’s just more convenient to eject the memory card and use it directly IMHO.

Innioassis Y1

I kind of have the most mixed feelings about the Y1, but would recommend it if someone wants an “iPod Like” device but not an iPod.

Hardware wise, just imagine what an iPod classic would look like today. Looking online for tear downs suggests that it’s a hardware design that is reminiscent but with a MicroSD card in place of where I would have expected eMMC soldered. Opening the iPod was enough of a pain, I don’t really want to find out, so I will just be thankful for the 128G capacity.

Software wise is interesting but also kind of “Meh” IMHO. Connecting the device to USB, it is obviously running some form of Android because of the folder structure. That it identifies itself with an HTC vendor id and 1 as the device id make some wonder if it was simply a device SDK with a few custom APKs baked in. Looking online, it sounds like the vendor is willing to support customers on the hardware front, but has zero access to the firmware, so it’s basically orphan ware.

The upside however is the software doesn’t suck, it’s just pretty bare. The trick of holding the back/menu key to control sorting based on file name or song name is perhaps the make or break between “Good enough” and “Missed it by that much,” and I think it would be neat if there was a way to jailbreak and replace it–I kind of want to see what happens on a machine with adb available. As it is, I would say that the firmware is just a little worse than an actual iPod. In that, I think it could be called a success, but like the H2–don’t ask a lot of it. Being able to load custom APKs and replace the launcher would be a major win, but I’m not likely to pursue that beyond the most obvious experiments to try.

I’ve only encountered one real problem and a few minor quibbles. Some of my music causes the album view to crash due to the album art, but that was easily rectified by bisecting a lot of music to find which albums caused woe. It’s amazing how many times you can forget to press the button to enable USB storage mode πŸ˜†. Aside from that, I would say it handles album art pretty swell–better than my iPod’s stock firmware, more reliably than Rockbox has so far, and less ‘ahh, my eyes’ the H2’s translucency approach.

On the minor quibbles front, the 3.5mm analog jack puts out a bit of hiss whenever headphones are connected. I’m not sure if this comes from interference or whatever state the DAC’s line in pins might be left in, or if it is just the quality of the amplifier circuit. It’s not too noticeable while playing music, and for $45 I’m fine with that. Not really an analog audio guy anymore, and the Bluetooth output to my Echo Dot was fine. In the near future, I need to try BT earbuds or headphones.

Interesting to me, my experiment with the higher sample rate FLAC plays out as a middle ground on the Y1. It cannot play the original FLAC the way the H2 can, but unlike the iPod it can play my AAC resampling just fine. And pretty much everything except for the iPod does play that AAC version just fine, lol.

Where to from here

Given the issues with the iPod, I’m tempted to relegate this to a secondary machine or shelf it as a vintage project. The H2, it remains to be scene whether or not my preference for BT will win out over RB, and the Y1 is a device that would fill the gap if only the software was more featured.

I think in the long run however, that neither syncing my “Originals” from the file server nor my Apple Music library will be a viable solution. Rather, some library where the metadata is more aggressively managed will be necessary. Because when using the former there is too much variation for the iPod/Y1 to take it as is, and in the latter too many issues between the iPod/H2/Y1 to call it good enough.

The question of course is what form that will take.

With a little help from my kitchen tools

An idea occurred to me last night that I decided to try this morning: omelet in muffins.

I’m reminded of my mother telling me as a kid that her father managed to destroy several toasters trying to make homemade McMuffins when they came out in the early 1970s. Never really understood how you would do that, short of putting runny egg in the toaster. In my case, I simply put two whipped eggs in a greased tamagoyaki pan and only folded it over in half to finish before cutting that in half. Perhaps this is ironic considering that my grandfather was in the pacific theater during WWII, lol.

One muffin was made with a thick slice of snack-cheddar so that it would melt just enough to get soft and spongy enough to fill the crevices of the muffin and omelette, and the other with the available sandwich cheese at hand (a thin slice of Swiss). Kinda made me wish that I had bothered to grab some ham or pastrami while I was at it, but alas I did not.

Since I’ve been watching the sodium and cholesterol intake with my blood pressure, I’ve tried to avoid the temptation to take a Drive-Thru breakfast on the way to work over this past year. So I found this a rather nice breakfast, if rather large for me. Between the lack of ham and my disinclination to salt the shit out of my food, each probably represents half the sodium content of one McMuffin.

Batteries and Old Computers

One of the downsides of breaking out an old laptop to test something that involves a bunch of file I/O, is watching the battery life deplete. To be fair, my old X61T was old when I bought it. That it’s still got about 44% of its original battery capacity left is kind of impressive, and it’s enough for it’s purposes.

One of the upsides of modern software is the oh crap your battery is at 2% warning πŸ˜†. This is a great contrast to my very first laptop, where there was a certain tendency as it aged for the power connector to get loose enough to stop charging, and the key way you could tell was the BIOS changing the screen brightness…or the screen suddenly going blank.

The part that I find kind of sad, is given the popularity of ThinkPads I could probably dig up an aftermarket replacement battery for this old machine, but Hill was mostly an experiment that didn’t work out due to hardware issues. On the flip side, somewhere between updated Alpine Linux and replacing my wireless network, the Lenovo PCI-E ID locked BIOS and its P.O.S. Intel card no longer seems to experience routine firmware crashes and connectivity problems. Which has made it rather handy for those times where a spare Linux computer to one side is useful. I think my fiddling with vintage Macs has also in a round about way, provided the hardware that I would need to flash hacked BIOS for removing the hardware check and bumping up the SATA link speed.

But let’s not go booting into DOS while we’re at it πŸ˜›

Old tunes

One miscellaneous upside of the recent putzing with portable media players, I ended up cleaning off one of my older USB sticks where I had stashed some files that never quite made it into the Plex-ification of my music library back in the day, which in turn helped me find the associated backups of those on my file server.

In most cases, these are files that I either have on my server’s Music folder already, or have the original CDs and plan to make a modern rip. In some cases, old downloads and freebies where I’d just go back and buy the rest of the album at this point. But in a few cases there are files that aren’t so replicable: party mixes and compositions that musically inclined friends did back in the day, that I assumed had been lost in the years since my first laptop was decommissioned.

Yeah, well, it turns out I’m an even better backup-horder than I remember, since I’ve found copies exported from my first laptop, and archives of old backups from the same laptop, lol.

The iWar Continues

Largely wrapping up the cluster-fuckery that is File Server -> Apple Music -> iPod, I find myself only mildly perturbed with some of the files that were filed (pun intended) for later review before import.

Cases where the album’s original source is a FLAC or WAV with an unusual sample rate when having Audacity convert it to an M4A/AAC file for import. Apple Music will happily import files with the crazy high 96 kHz sample rates, and Audacity happily uses 44.1 kHz for the project. Apple Music, whatever Finder uses for its previews, and VLC (the known good) all play them audibly fine but these can’t be synced to the iPod because of being unplayable due to the sample rates. In one specific case, Apple Music had audible muffling artifacts but otherwise sounds fine through multiple local audio outputs.

Adjusting the conversion options in Audacity to encode these at 44.1 kHz, works in that all points of software reference sound fine off the laptop, but generate chirp artifacts on the iPod as the source goes outside the sample range. Reconfirmed that it’s not just my ears by way of jacking into my speakers with a 3.5 male to male cable, and comparing the output of the iPod to Apple Music on my laptop.

Which makes me even more tempted to just say to fuck with it and load Rockbox. I’ve mostly tried to use the provided tools, even if I’m pretty sure that the iTunes side must have been the worst aspect of iPod software. But my temptation for replacement firmware has been more driven by the aspect that I’d prefer to treat the device as a generic storage device for media and playlists. Whether or not the FLAC encoder is up to snuffs or can support some of the more esoteric files in my collection would really just be a benefit IMHO.

In other weirdness, of course the first 3.5 M to M analog cable doesn’t work, because it’s probably the one weirdo in the box of analog computer stuffs, forcing me to go get the known good cable from my car just to do that AUX IN test, lol.