Wherein your host is stirred (but barely shaken) by an earthquake and then goes on to ponder baseball, copyrights and other miscellaneous topics o' the day.
Addendum: It appears the earthquake did relatively little damage.
On this day in baseball history, Willie Mays made this spectacular over the shoulder catch at the wall to rob Vic Wertz in Game 1 of the 1954 World Series. The New York Giants would go on to upset the Cleveland Indians in four games: the last time the Giants franchise won the World Series. Damn, even in this grainy black and white, it's a sweet catch.
You can read the scorecard and the play-by-play on retrosheet.org. Wertz was four for five, with a double and a triple. Mays' catch preserved the 2-2 tie in the eighth, and the Giants would go on to win in the tenth.
SFGate ran a more complete article 50TH ANNIVERSARY / Mays' 'catch' might not rank among his greatest.
According to SFGate, Willie has been in the hospital for hip-replacement surgery, but is expected to return home today. Best wishes, Willie, and damn, that is one sweet catch.
Just a few minutes ago, I felt a couple of gentle rolls that usually indicate an earthquake. I mentioned it to my wife via IM, and she felt it too (in Pleasanton). I then did what I always do: I hit the USGS Realtime Earthquake site. Apparently a magnitude 6 event happend near Parkfield, right along the San Andreas. That's about 170 miles or so from here, so it must have been pretty bad.
Update: It now appears there have been two quakes, magnitude 5 and 5.9. Hope everybody is allright.
Update2: Apparently it's still shaking down there pretty good. I haven't felt any aftershocks, but the USGS maps are showing new sizeable quakes.
Update3: Here are a couple of realtime seismograph dumps of the event, as recorded by two seismic stations:
Here is the log of our IM conversation:
(10:17:12) ***myself wonders if that was just an earthquake.
(10:17:25) mywife: i thought i was tripping
(10:17:41) myself: you felt one too?
(10:18:04) mywife: yes
(10:18:25) myself: slow roller?
(10:18:31) mywife: slow
(10:18:33) mywife: rolling
(10:18:46) myself: nothing as yet on the realtime map.
(10:19:21) mywife: that was a weird one. 2 other people had the same reaction. "i thought it was me!"
(10:20:28) myself: still nothing on the earthquake map.
(10:21:16) mywife: 5.8 down south
(10:21:31) mywife: The magnitude 5.8 event occurred 14 km (9 miles) NNW of Shandon, CA.
(10:21:33) myself: ow! it just appeared!
(10:21:40) myself: That's a big one.
(10:22:32) mywife: yes
(10:22:49) mywife: oh, now it says 6
Yesterday I reached a minor milestone: the tenth of my audioblog entries, and I have a strong suspicion I may have had more than ten downloads. I also chose to wrote up a brief description about how I make these entries, and I hope that some people found it useful. After another minor glitch in yesterday's recordings, I thought it might be useful to also write up all the problems that I have. You can consider this a set of gotchas to watch out for, and also as a wishlist for creating tools that make recording these shows less error prone. Toward the end, I give some advice which I try to obey myself as I go into the future of audio weblogging.
Sound card configuration: I mentioned this a bit yesterday in the text blog, but I reiterate with a bit more detail. On the Mac, many people use WireTap, but on my PC I have found that many soundcards have the ability to record directly from their internal mixer. If your lucky, when you open it and look under the Options > Properties > Recording dialog for devices, you get something that looks like the image on the right. You generally want to record from the Stereo Mixer, not the microphone. Then anything you play back through PC should get recorded by your recording application.
This was actually pretty straightforward to setup on my laptop, but my new Media PC has 7.1 sound, which means that instead of a single sound card, it looks to WinXP as if there are four or five separate devices, and some of these devices reconfigure themselves automatically when speakers and headphones and microphones get plugged in. This results in a larger space of possible settings to search, and some of them inexplicably don't work. I'm still trying to figure out the rhyme and reason of the whole thing myself, so don't be discouraged if you can't seem to make it work right off the bat.
Levels: Of course what invariably happens is that even when you get the recording devices setup, the levels and loudness of things are completely inappropriate. The single thing you want to do is avoid clipping: I suspect that the artifacts in my closing music yesterday were due to the final clip being too hot, and clipping off. Sometimes minor clipping isn't bad, but it can introduce both popping and when you reencode at fairly low bitrates, all sorts of bizarre artifacts. I try to monitor the audio levels using Audacities record meter, and often jigger the recording levels on the fly. It's most convenient to do that using the mixer, which you will want to leave open anyway so that you can mute the microphone (yes, I didn't mute the microphone during one of my openings a couple of days ago, and you can hear me thumping around). I usually set the record levels at their midpoint setting, and then manipulate the playback levels during the "performance".
What is needed: Both of the above problems could be ameliorated by an audio recording wizard followed by a profile manager. You'd like the smarts of audio configuration to be encapsulated so that it would automatically configure the recording and playback settings and their levels, and then be able to save and restore these settings all at once. Then you wouldn't have to go through the error prone setup each time you changed your settings for some other purpose.
Try to have a plan: I don't script my audioblog entries (could you tell?) but I do find it useful to generate a short checklist of the major points I want to cover. When I don't have a plan, I panic as I try to fill dead air, and my speech becomes filled with all the classic irritations.
Resist the urge to over edit: I have pulled out short problems in my recordings as a courtesy to my listeners, but you learn more by mistakes than you do by trying to produce "the perfect recording". I find even the worst audioblogs to be better than 90% of commercial radio, if only because people are always talking about something they are passionate about. Don't bother trying to be too professional: it is the professional media that has bored us into trying broadcasting for ourselves.
That being said, try to improve: I listen to my audioblogs probably more than anyone else, and I try to do so critically to see if there are systematic things I can do to improve the quality of both the technology and the presentation. I also listen to other audioblogs to get ideas for things that are working for others, and try to adopt them into my own presentations.
Don't worry! The worst thing that can happen? Nobody listens to you. But nobody was listening to you before, so you haven't lost anything. 🙂
Wherein your host experiments with a remote on-the-street feed, thanks his patient and benevolent listeners for their comments, and reviews the British zombie comedy Shaun of the Dead. Download the MP3 for the complete review, but the summary is: it's a terrific zombie movie and a terrific comedy welded together to make a really great film.
I like Dave's new habit of posting URLs relevant to his audioblog, so I think I'll copy him.
- Dan Lyke's Flutterby!
- The Zvue mp3/mp4/jpeg viewer
- The Olympus VN-120 digital voice recorder
- The Misfits recording of The Monster Mash
Ob. mistake for the episode: odd mp3 artifacts of the Monster Mash at the end. Please visit the Misfits and download their version directly from their website.
Update: actually, the entire thing sounds a little hot and clippy. I will figure out a better way to set levels. I will...