Remodel mess update

Comments

Insurance inspector came out today to look at the damage. He said the situation is a bit complicated because part of the damage was due to an ongoing maintenance issue and part of it was due to an emergent issue, and insurance only covers the emergent issue. He thinks that he can at least get me coverage for replacing the sink cabinet and all of the water mitigation, at least, and also since my house is without running water, the insurance company is putting me in a fancy hotel for a week. I’ll still probably be driving back to my house to work, though (as well as making sure my cats are okay), and fortunately I have a port-a-potty and a portable foot-pumped sink for that stuff.

Also, post-leak-dryup it became pretty obvious that the fiberglass in the ceiling wasn’t put there by a previous owner to mark/plug the leak, but was actually pulled down over time by the ongoing leak. So that must have been going for much longer than I realized.

The housing person said I could also take my cats to the hotel with me if I want but that seems like it’d cause more problems than it’d solve.

Read more…

Got the disaster out of the way

Comments

So, my bathroom renovation got delayed a few days (due to supply issues), and then started today.

You know how every home renovation project always has some major disaster, usually towards the end? This time we at least got it out of the way right away: while they were removing the sink cabinet, a pipe burst.

Fortunately nothing got badly soaked, and what got wet has dried off pretty quickly. I don’t think there’s any specific water damage to anything (although that was an extremely close call for my entire recording studio), although only time will tell. The main issue of concern is that my guitars and some of my acoustic treatments were directly below the water blast. The guitars have dried out easily, and the acoustic treatment is easy to replace if it gets moldy (it’s just cheap acoustic foam which I have plenty of).

Read more…

Attention all coffee friends!

Comments

Do you have a coffee grinder? One which could actually be identified by name? Do you have the ability to record video? Want to be featured in an upcoming Sockpuppet video?

For this year’s Novembeat album I’m doing songs inspired by different coffee grinders and their respective techniques, and as part of this I’m also making silly videos of each grinder. But I only have a handful of grinders myself, and good process-forward footage is difficult to come by. So that’s where you possibly come in.

Updates: I’ve been making edits to this post as various questions come in. I should really be tracking them specifically.

Read more…

Studio hardware stuff, part 2349872984

Comments

My ongoing anxiety regarding recording studio computer stuff has continued. Yesterday while doing day 1 of Novembeat I found that my 2016 MacBook pro is still just like… way too slow to make music on (especially if I stream at the same time). And then I saw that there’s a bunch of deals on 2020 MacBooks happening right now.

I was about to buy a 2020 MacBook Air with 16GB RAM and 512GB SSD, but then found out that Apple had a deal on refurbished 2020 MacBook Pro with 16GB RAM and 1TB SSD for only a little bit more, and the refurb price is less than the equivalently-equipped MacBook Air’s price. So that’s what I ended up ordering.

Read more…

More thoughts on recording studio hardware

Comments

Now that the new M1 Pro/Max MacBooks are out and are getting real-world reviews, I have a bit more information about what I should consider in terms of computer upgrades.

This particular video is pretty helpful:

In pretty much all of the side-by-side tests, the M1 Pro is only negligibly faster, aside from encoding H.265 video from RED or ProRes sources — none of which I ever do.

Read more…

macOS 12 SSD issue update

Comments

Going through a few rounds of troubleshooting with folks on the macOS community forum as well as Apple tech support regarding the SSD overheat issue has helped me determine the following things:

  • Whatever this problem is, it’s uncommon; nobody else seems to have experienced it
  • The enclosure itself isn’t to blame; it happens on both my Plugable USB 3.1gen2 and on my Sabrent dual-slot Thunderbolt enclosure
  • The overheating is only happening on the Crucial 2TB NVMe stick (that normally lives in the USB enclosure); having just the PNY stick (which lives in the Thunderbolt enclosure) doesn’t overheat, moving the PNY stick to the USB enclosure doesn’t overheat, and the Thunderbolt enclosure only overheats if I have both the PNY and the Crucial stick in it
  • The overheating stops if I unmount the drive but leave it electrically-connected
  • Mounting the drive even under macOS Recovery causes the overheat to occur just as quickly

For now I’ve moved my most critical files from the Crucial stick to my older SATA drive (which isn’t having trouble) so I can continue to work on the things that I normally do on my desktop, and my studio laptop seems to be okay with the PNY+Thunderbolt combination so I don’t think Novembeat is at risk because of that, at least.

This does mean I won’t be able to work on music from my desktop computer in the meantime, and video editing will have to be direct to NAS, which is doable, just not ideal.

Hopefully this all gets sorted out in a macOS update.

Warning about macOS 12.0 Monterey

Comments

I’m running into a pretty severe problem with my external USB 3.1-connected NVMe drive on macOS 12.0 on my M1 mac; something in the system is causing the drive to get extremely hot (to the point of disconnecting within a few minutes) when there’s no recorded activity going to it, and also while it is connected, Blackmagic Disk Speed Test reports that it’s only capable of around 150MB/sec, which is significantly less than what it usually gets. Which tells me that something in the OS is causing the drive to go under significant load.

I tried disabling Spotlight, both from the GUI and using sudo mdutil -i off /Volumes/storage, which made no difference.

Read more…

Some thoughts on comments and interaction

Comments

Recently I’ve been thinking a lot about some of the differences between self-hosted vs. silo spaces. One thing that really stood out to me is that in self-hosted spaces, the tendency is to allow complete control over which comments are visible, and silos almost never allow that, or if they do it’s at best an in-retrospect thing.

For example, most self-hosted blogging systems give you the ability to moderate all comments (as I do), or give easy access to deleting comments which got posted, or any number of mechanisms for curating the community.

But most silo systems don’t give you that access; you might be able to block recurring trolls, or flag a comment for third-party review (usually to no effect), but all posts are set to allow anyone (with access to the post) the ability to post anything at any time, and by default everything gets floated to everyone else.

This came especially to mind today because of this unfortunate video:

I’ve seen so many creators get burned out on what they like doing, because even if 99% of the comments are positive, that 1% really gets under their skin, and they stop creating.

I’ve seen so many creators get burned out on their communities, because even if 99% of it is positive, that 1% really gets under their skin, and they stop interacting with the community, turning it into a toxic cesspool.

I’ve seen so many creators decide to capitulate to the communities and set up a personal SubReddit that they designate other people to moderate, just to keep it contained somewhere else.

I know so many creators who are on the verge of burnout and getting really tired of the dark side of having an audience.

I’m not sure if giving people the ability to require commentary to be opt-in rather than opt-out would solve these problems, but I do know anecdotally that the random snipe-type responses I get from Twitter or Mastodon are way more annoying to me than the comments I opt not to post when submitted to my site. They’re out there and visible and I have to take extra steps to get rid of them, and it’s taken out of my hands as to whether I even can get rid of them.

I don’t think I like how webmention works.

Read more…

Studio stasis

Comments

For now I’m just going to stick with my 2016 MacBook Pro, and I bought a 27" 4K monitor for it to alleviate the display-size issue.

It’s a little slow and a little janky but a lot of my music stuff still doesn’t work right on M1 anyway, and in particular Native Instruments is taking their sweet time to update everything to be M1-compatible. Also, I could theoretically use my PreSonus FireStudio with the hacked driver, although it looks like that’ll probably stop working in macOS 12 and I can’t use it with my ADAT preamp anyway, so the only advantage to it is I could put my Scarlett 18i8 back in my office, which is a pretty low priority now.

(I suppose I could also make an aggregate interface of the FireStudio with the 18i8+ADAT, but I already have 14 functional inputs as it is and I barely ever use more than 5 of them at a time. 22 is definitely overkill.)

If I get desperate for an upgrade I suppose I could get a current 27" iMac but that doesn’t feel particularly necessary right now (and it also feels like a waste since Apple will stop supporting it sooner rather than later; I went through the exact same thing with the PowerMac G5 that I bought literally two weeks before they announced the Intel transition).

I also need to give both Reaper and Bitwig another shot because both of them seem like they’d be able to mostly replace Logic for me at this point, and I’m sick of being wedded to macOS. (But right now is not the time for me to learn a new DAW. Or maybe it’s the perfect time. I dunno.)

Or maybe I should see what the pre-trashcan Mac Pros are going for. The 12-core model would still be a pretty decent upgrade from the 2016 MacBook pro, and also has the advantage of having upgradeable SATA storage, plus PCIe slots that could theoretically take an NVMe adapter. On the minus side, no Thunderbolt 3 (not that I’d need it) and I’d also be stuck on macOS 10.14 without some sketchy patching. But it looks like they’re going for under $400 (shipping included), all the same.

Or there’s always Hackintosh.

But nah I’ll wait, the old MacBook Pro is fine for now.

The unfortunate reality of Apple’s product focus

Comments

Today’s Apple announcement brought forth the usual advancements that I was looking forward to: faster processors, better GPUs, and so on.

But Apple has this hyperfocus on making The Best Laptops Possible, which is a little puzzling when the entire focus of today’s update was on creative studio uses, especially on music.

Read more…