mdlbear | Back in the groove? (Reply)

Spent some time last night finally re-arranging the recording directory: it now looks like yyyy/mm-event/ where "event" is either a convention, a day or day range, or something like that. If I'm going to be recording practice sessions I should get in the habit of using day ranges -- and perhaps make each month a subdirectory -- for conventions just so things will be chronological.

I did the renames using a script that not only moved the existing concert directories, but left symlinks around for legacy code (for example, in some of the album directories). I'll have to write another script that goes through the tree and fixes up the existing symlinks, and yet another to fix web side of things, later on.

The big advantage of using a script is that I could use it to make corresponding changes on all my backup disks and offsite mirrors. Since the recording directory contains just short of 42GB of data, that saves several days worth of uploading. If I had it all under git control it would be a different matter, and that's something I need to do for collaboration anyway.

The other thing I have to do is fix my makefile template to make it easier to package up concerts.

Naturally, having done this, I had to test it, so when I came out to the living room to do some practicing I set the H2 on the music stand and recorded it. Very rough, and I haven't even listened to it let alone tried to do a normalize-and-split. But I will, because I want to have it done by Thursday. It was all stuff that I need for the album. Added a little more this morning.

I also need to get this onto the web, as the start of the collaboration area. In particular, this session has "The Toolmakers" and "The Stuff that Dreams are Made Of" in their correct keys.

The entire set of working directories will have to be password-protected at a rather fine-grained level, since the convention recordings contain a lot that isn't mine. Also, I'm going to be selling access to the working directories as the pre-order bonus for the next couple of albums, in addition to using it for collaboration. I'm going to start with basic authentication for collaborators because it's trivial to set up, gives the best performance, and makes it easy to access in a script. Then I'll add cookie-based authentication (which requires access through a CGI) for everyone else.

I'm going to be a busy bear this week.