Wednesday, May 31
Future files - and eventually, past files as well - will appear here.
I uploaded a couple more videos, and Broadcast Machine lost the plot completely. So I've (a) switched it back to flat file mode, and (b) given up on it entirely.
I'll just do it as a Movable Type blog, I think.
Let's say you have a MySQL backup made using mysqldump -A, which dumps all the databases on the system into a single file. But you only want to restore one of the databases, which consists of about 300KB in the middle of a 1.7GB SQL dump. And you're not sure if you want today's file or yesterday's or the day before's. How do you find the right one? How do you restore it easily?
import sys bakfile=sys.argv outfile='header.dat' f=open(bakfile,'r') g=open(outfile,'w') while 1: t=f.readline() if t[0:20]=='-- Current Database:': db=t[22:-2] print db g=open(db+'.dat','w') g.write(t)Use: python dbsplit.py <filename>
Tuesday, May 30
Up now in the clips library: the opening and closing credits of Tweeny Witches (DVD version; edited down slightly from the original versions I posted), and the opening credits for Cutey Honey, Cutey Honey Flash, the Cutey Honey live action movie, and Re:Cutie Honey (spelling variable; since the creators aren't consistent I don't see why I have to be).
I'd like to add the credits for New Cutey Honey, but I only have it on VHS. If anyone out there has it on DVD, particularly if it comes with a textless version of the credits, please leave a comment.
Broadcast Machine seemed to be a bit slow doing updates of late, and even when displaying the galleries. It's supports MySQL, but you can use it without - after all, a simple text file should be fine if you're only going to have a few dozen items, right?
Well, evidently not, because when I reconfigured it to use MySQL just now it suddenly got much, much faster. How anyone could screw up the performance on such a small dataset so badly is beyond me, but they did. Well, that would all be of little import; just tell everyone to use MySQL. Except that if you switch to MySQL at a later date it randomises the sequence of all your files.
Fnord. Fnordling fnordy fnordness.
Update: Tried hacking the code. The database code in Broadcast Machine is mind-boggling bad. As bad as Movable Type. Possibly worse.
This is a common feature of open-source web apps. The people who write these apps don't have a clue how to cleanly interface with a SQL database. Of course, they're programming in PHP or Perl, so it's something of a case of "you can't get there from here", but the ways they find to make a bad situation worse can be entertaining. If you don't have to fix it, that is. And I do.
So far I've managed to break the channel display; none of my other changes have made the slightest difference. Why? Who knows. There are two different interfaces to MySQL, both of which replace the standard flat file storage system, which is in turn utterly broken.
Update: You know what the really great thing about Broadcast Machine is? When you try to upgrade or reconfigure it, and it infallibly goes wacko , you can downgrade it by reversing whatever you did - and get it back in a working state.
Update: Ye gods and little fishes! It takes THIRTY SECONDS for Broadcast Machine to pull 47 entries from a text file, sort them, and display the page. I originally thought it was my browser waiting for images to download or something, but no, it's taking THIRTY SECONDS OF CPU TIME. On a 2.8GHz Pentium D. It shouldn't be taking so much as thirty milliseconds.
Update: Back to MySQL. Enjoy your high-speed randomness. I'm going to bed.
Update: Apart from the fact that it doesn't work, it has this cute little trick: Every time you look at a listing of any of the channels, it sucks the entire database into an array. Oy.
Monday, May 29
Via The Commissar, Ambient Irony as a graph:
The Java applet that generates this is still chugging away, so I'll let it run overnight and see what it looks like in the morning.
Do not trust the lolis.
They cheat at cards.
Hale is Charlie Brown.
Guu is Lucy.
Sunday, May 28
The first dozen AMVs are available now.
I've linked back to the creators' pages at animemusicvideos.org so that if you like a particular video you can find what other work they've done.
Uploaded today: The high quality, un-subtitled (but not textless) versions of the Haruhi opening and closing, and all versions of the opening and closing credits for Galaxy Angel. (Some of these were available previously in the Clips and Clips2 collections.)
I'm going to make all the clips available for individual http download, but that will take a little while, as there are now 155 of them. I also have about twenty AMVs to upload. None of them are my work; they're just ones I've particularly enjoyed.
Friday, May 26
New goodies up in my anime clips collection: Opening credits for Sasami - Mahou Shoujo Club, opening and closing credits (and closing credits and closing credits) for Renkin San-kyuu Magical? Pokaan, and opening and closing credits for The Melancholy of Haruhi Suzumiya.
Most of the closing credits for MagiPoka are Matroska files, .mkv, rather than the usual avis I provide. There is a reason for this, but you will need a Matroska aware player to discover what it is. You should be able to get Windows Media Player to do the job; my current preferred alternative (since BSPlayer went crapware) is The Core Media Player. It's not pretty, but it works well enough.
Oh yes: BitTorrent trackering is currently rather messed up, so they're enabled for direct download. Try not to devour all my bandwidth.
I wound Broadcast Machine back to version 20. I also whined pathetically over on their forums.
Anyway, I'll put some more goodies up tonight.
Thursday, May 25
What's the lifespan of a notebook battery these days?
I got my notebook last September, and at the time I could watch 3 hours of anime on a battery charge. I was editing the subtitles for Dirty Pair episode 4 on my way home yesterday, and the battery was dead by the time I got to Waitara; that's about 40 minutes. And that's less intensive than just watching anime, because I keep pausing the video while I edit the script.
Also, the power meter went from 10% to 3% in two seconds, which seems to be just a tiny bit abrupt.
I'm doing a test right now: 100% CPU, screen on, no disk activity; so far it's gone from 98% (which is where it is once you've booted from standby on battery) to 57% in 14 minutes. The 3% per minute seems to be pretty steady. Also crappy. Particularly since the last 10% is basically gone anyway.
16 minutes: 51%
20 minutes: 40%
22 minutes: 33%
24 minutes: 27%
26 minutes: 22%
28 minutes: 16%
30 minutes: 9%
32 minutes: 3%
34 minutes: 0%
36 minutes: 0%
38 minutes: 0%
40 minutes: 0%
41 minutes: URK
10 minutes: 72%
22 minutes: 38%
30 minutes: 14%
32 minutes: 9%
34 minutes: 1%
36 minutes: 0%
38 minutes: 0%
40 minutes: 0%
41 minutes: URK
Well, the full discharge and recharge didn't help a whole lot.
Went to upload some new files to Broadcast Machine. It informed me that a new version was out and that I should upgrade immediately. I did so, and it utterly ceased to function.
Installed the new version to a clean directory... twice... and it's working again, or at least not giving any errors. Of course, there are no files there either, but that's a relatively minor detail.
It also comes with some new themes, which while being prettier, use a different size for the images, so all the old images get rescaled in the browser and end up looking like crap. It still has the old theme, only it has changed too, so it ends up looking like crap anyway.
I'll post the new videos, or some of them, since I've spent the hour I'd planned on using to upload the new files beating my head against a wall instead. Then I'll upload the old files. Then I'll upload some more new files. Or something.
Update: Or not. This new release looks like a major downgrade. Bah. And bah again.
Update: One of the things that is particularly broken about the new version of Broadcast Machine is that instead of showing my lovingly handcrafted images on the individual torrent pages, it embeds the file. Yes, it takes your avi file - or your mp3 or zip or whatever it might be, but it assumes it's an avi - and sticks it right there on the web page. Of course, that only works in Internet Explorer 6; other browsers have quite an entertaining variety of ways of not working when they encounter this particular... trick.
Unfortunately, but unsurprisingly, their web site seems to have crashed, so I can't visit their forums to ask what drugs they were on when they decided that this was a good idea.
I was disappointed with one of the episodes of Dirty Pair I subtitled last month because there were some lines of dialogue that weren't translated. There were just gaps; no subtitles at all. Only a few, but still not the sort of quality I want for a MuNu Fansub. I thought the problem lay with the original translations, which were produced back in the early nineties when the fansubbing community was much smaller.
Because I never considered the possibility that a popular subtitle editing program would have a major bug relating to one of the most common subtitle file formats that could lead to the deletion of words or entire lines of dialogue without any warning.
I am now editing the subtitles for episode 4 in Wordpad.
Bruce Bawer talks about his book:
I was also shocked to hear people refer to immigrantsâ€™ European-born children as â€œsecond-generation immigrants.â€ And their children were â€œthird-generation immigrants.â€ This summed up an incredibly dramatic difference in the ways Americans and Europeans thought about immigrants. My fatherâ€™s parents were Polish, but never in my life had it occurred to me to think of myself as a third-generation immigrant or of my father as a second-generation immigrant. The idea was ludicrous. We were Americans, period.My father's parents were Polish. My father was born in England, but lived most of his life in Australia. I'm Australian, period.
Read the whole thing, depressing though it may be.
(Via Roger L. Simon)
Tuesday, May 23
To expand on the theme still further:
Our office network is currently 100mbit, switched. There are two main 24-port switches, and a couple of 8-port switches for specific subnets, such as my desk. The exact topology doesn't matter, although a GbE uplink between the two main switches would be nice.
Anyway, the advantage of ATM over fast ethernet (as has been explained to us) is that it can guarantee the delivery of our critical voice traffic at the same time as it maintains a best-effort attempt at delivering data. Which is nice... But I have 100mbits available, unshared, to every desktop. If you are on two phone calls at once, at ISDN quality, that's a little more than one tenth of one percent of your bandwidth. You have to chew through most of the remaining 99.9% before you will start to affect the sound quality of those calls. And your PC (thanks to Microsoft's IP stack) isn't nearly powerful enough to do that. A full-size fast ethernet frame takes, what, 0.12ms to transmit, so the jitter will barely be measurable, much less noticeable.
Essentially, if you have the bandwidth, ATM isn't necessary, and if you don't have the bandwidth, you're going to lose something anyway. So where do we need it at all?
If you're a typical home user, you want to do stuff like downloading the latest episode of 24 over BitTorrent while making a VoIP call on your videophone. You've got what, a megabit upstream? Problem.
It guarantees the bandwidth for your videophone. Good.
To do so, it has to throw out some BitTorrent packets. Who cares? BitTorrent is completely self-healing at three different protocol levels. Anyway, it's your data it's throwing out, not anyone else's.
And the kicker: High-speed ATM is expensive, because you need high-speed processors to do all the fancy quality-of-service stuff. But we're talking about a megabit or so in an ADSL modem. We don't even need end-to-end QoS, since downstream bandwidth isn't in short supply, only upstream. So, finally, a win for ATM.
Unless you live in Japan, Korea, or Canberra, where ADSL has already been supplanted by something better.
As late as 1998, you could find papers extolling the virtues of ATM to the desktop. (Warning: Illegible in browsers other than IE6.) ATM could handle voice and video at the same time! Sure, fast ethernet looked sexy, but you only really achieved 40% of that 100mbits, and a single CSMA domain could only extend 200 metres at its furthest extremes. ATM could plug straight into the corporate backbone, and the 53-byte ATM cells meant a worst-case response time 7 times better than fast ethernet.
ATM to the desktop was the way of the future.
No-one rolled out ATM to the desktop. Everyone rolled out fast ethernet.
One: They already had ethernet. If you have ethernet, and it's slow, then the obvious solution is fast ethernet, right? Which is a large part of why 100BaseVG-AnyLAN died in the market. You can buy fast ethernet or... What was it again? 100BasicVB something? Let's just get some of that fast ethernet that everyone else is buying.
Two: Speed wins. Fast ethernet is 100mbits. ATM was being pushed for the desktop at 25mbits. 100 is more than 25. End of story.
Three: Price wins. Fast ethernet was cheaper.
Four: The price for ethernet switches fell through the floor. Suddenly, no-one in their right mind was using hubs. That 40% ceiling? Erased, utterly. Now you could not only safely hit 100%, you could safely exceed 100%, because different parts of your network were effectively on different circuits - all handled automatically.
That wiped out ATM's former big advantage - quality of service.
Let's say you had a network that was carrying both phone calls and data, such as terminal sessions to your accounting system. If your network gets full, you can't slow down the traffic on the phone calls, because then people won't be able to understand each other. But you can slow down the terminal sessions. It's annoying, but it still works. ATM looks after this for you.
On old-style ethernet, with a single network segment, once you started pushing too much traffic (and "too much" wasn't actually very much at all), everything would stop working. Both the phone calls and the terminal sessions would fail. (There was actually something called isochronous ethernet that ran 96 ISDN B-channels alongside standard 10mbit ethernet, so as to carry voice and data at the same time. It died.)
On new, switched, fast ethernet, it simply wasn't a problem. The phone calls and the terminal sessions weren't competing for scarce bandwidth anymore, because (a) they were put on different circuits, and (b) bandwidth wasn't scarce.
And ATM dropped dead, as far as computer networks go. The phone companies still haven't worked this out.
Right now, I can buy a 48-port gigabit stackable layer 3 managed network switch and 48 gigabit ethernet cards for the same price as one 155mbit ATM module from Cisco. Which way would you go?
And when you come to upgrade your gigabit ethernet, would you choose 10-gigabit ethernet, or... That other thing?
Last Friday, I wrote:
The next telco sales rep who tells me that we have to connect to them using ATM because they are selling a business grade product is going to get a punch in the snoot.Today we have a winner.
But he did it via email.
Sneaky weasels, these sales reps.
But for crying out loud, it's 2006! ATM is a 1970's solution to a 1960's problem. The increases in speed of computer networking mean that the QoS features built into ATM are now effectively redundant, and at the same time, enormously expensive.
Just. Go. Away.
This Wikipedia article provides a good overview of the issues. What it comes down to is that I can get at least three times as much bandwidth over ethernet for the same price, even though I am buying the ethernet from one of the most expensive players and the ATM from one of the cheapest.
Update: Here's a Wired article from ten years ago explaining the problems, only with more personal details. Of course, it's Wired, so half of it is crap, but it's still useful for perspective.
Basically, it's another example of Worse is Better.
Monday, May 22
Steven has a too many words post up about corny (anime) romantic comedies, including a point system for scoring them. But he doesn't calculate the scores for any Rumiko Takahashi shows, because he hasn't seen them. Let's see if we can fill in the gap.
2 or more people seriously contending for the affections of one (1 point for each serious contender)
Well, the two main characters have not just suitors but actual fiancees falling out of the woodwork. Let's start by counting themselves (ignoring their protests), and then adding, at a minimum, Ryoga and Kuno for Akane, and Shampoo, Ukyo, Kodachi, and Kuno (again) for Ranma. 8
...who trickle in 1
...who aren't human (1 for each) 0
...who have special powers (1 for each) 3 (being very conservative there)
Dorky hero (1) 0 He's an idiot, but he's not a dork.
...who has a unique power (1) 1
Klutzy heroine (1) 0 Akane may be klutzy in comparison to the grandmaster martial artists who litter the show, but in everyday terms, no.
...who has a unique power (1) 0 Access to malletspace is hardly unique.
Love expressed as violence (1) 1 I can only award one point?
Obvious choice (1) 1
Women with exaggerated figures (1) 0 for the TV series, but definitely 1 for the movies. Shampoo is pretty well-built even in the TV series, but not exaggeratedly so.
Jiggle (1) 1
Panty flashes (1) 1
Ecchi (1) 1 Not frequent, but it is there.
Joshikousei (1) 1 They're everywhere!!
Meido-san (1) 0
Accidental exposure (1) 1 And intentional, of course.
Accidental groping (1) 1
Swimsuits at the beach (1) 1
Bathing and yukatas in a bathhouse (1) 0 I could be wrong, but I don't recall any yukatas.
Kimonos at a summer festival or cultural festival (1) 0 I'm sure I'm wrong this time, but I can't recall a specific instance.
Girl's locker room (1) 1 Panty thief! Get him, girls!
Cosplay (1) 0 Unless you count Romeo and Juliette.
Romances among secondary characters (1) 0 Well, there's Mousse and Shampoo, but that doesn't really get anywhere.
Meganekko (1) 1 Ran-ko.
Annoying relatives (1) 1 You betcha.
Meddlers (friends or family) (1) 1 Big time.
No romantic resolution at the end (1) 0 I haven't seen the end, so just guessing here.
So 27 points for Ranma.
Tomorrow: Urusei Yatsura. Which gets complicated. You'd think no-one would be interested in Ataru, but he nearly gets married more than once. Hard to say who's serious (Elle, Kurama... sort of) and who's just trying to annoy Lum (Ran-chan, Oyuki). And then there's all the boys chasing Lum. And then there's poor Shinobu. And at least half the characters aren't human, so bonus points everywhere...
And I can still only award one point for love expressed as violence? "Darling no BAKA!" FZZZT!
Sunday, May 21
Michael Novak, foaming at the mouth over at National Review Online:
The professor Hanks plays makes plain that he believes that Jesus is only a manâ€”a man and that's all. A great moral teacher, perhaps, but only a man.Sorry Michael, but this is complete tripe.
That, of course, is the one thing that the Jesus himself does not allow us to believe. If Jesus is only a man, he is no great moral teacher. He is on the contrary a fraud, a pretender, a horrible spendthrift with his own life and the lives of his apostlesâ€”all twelve of whom met a martyrdom like his, some of them crucified, all of them most brutally killed without the utterance of a single recantation. If He was not the Son of God, one with the Father and the Holy Spirit, he was either a mountebank or a lunatic, and deserves our contempt, not our praise. His every moral teaching would be vitiated by its radical emptiness and fraudulence.
One of the very meanings of being secular today, of course, is to believe that Jesus was exactly all these thingsâ€”a lunatic or a fraud and, more important than anything else, no more than a man.
Secularism necessarily implies that Jesus is not the son of God, because it involves a lack of belief in gods.
All the rest is your own construction.
So The Da Vinci Code will not exactly be stating any new thesis that secular people don't already accept. What it may succeed in doing, however, is to make dramatically manifest the silliness, madness, and love of illusion in what being secular means, at least to these film makers. It is for this reason, perhaps, that so many secular critics have found this movie repellent. Although it seeks to mock Christians and Jews, it actually makes a purely secular view seem absolutely batty.(My emphasis.)
That there are secularist moonbats around is an uncontestable fact. But attributing their faults to secularism itself is as false as attributing Pat Robertson's faults to Christianity at large. More so, if anything.
Having said all that, it does sound like the film* is a steaming mound of hyena offal.
* The Da Vinci Code.
Saturday, May 20
Here are the promised screencaps. I've resized them to fit on the blog; click for the original size.
First up, we have our Sammy-chan:
And Mama and Papa:
Sasami's friends, who probably have names, but I didn't catch them:
I think this is Misao, but they call her "Shinohara". In Magical Girl Pretty Sammy, Misao's surname was Amano.
Where the old Misao was just terribly shy, this one's a gloompuddle.
Anyway, Sasami with her friends:
Washuu is back, and she hasn't changed at all:
And look who's with her:
We don't normally associate Ryo-ohki with Washuu, but it makes perfect sense.
I don't know who's scarier, Washuu or Haruhi, but when they get that look, it's best not to be in the same universe:
A girl explains the facts of life to a boy:
Ah, the old mirror-on-the-shoe-trick:
Is something wrong?
That's got to be a bit drafty, surely:
I started watching Sasami: Mahou Shoujo Club, which is a spin-off of a spin-off of a spin-off of Tenchi Muyo. But it may contain Pixy Misa, so I need to at least give it a go. It hasn't been fansubbed yet; I'm watching it in the original Klingon. But then I did that with Magical Girl Pretty Sammy too, and back then I knew even less Japa - uh, Klingon - than I do now.
Okay, so we have Sasami, who is more or less recognisable, and Washuu and Ryo-ohki, who are the same as ever, and Mihoshi... We'll come back to Mihoshi.
I didn't have high hopes for this series, because the character designs made the show look like it was targeted at six-year-old girls. As it turns out, appearances can be deceiving.
Here we are in the first episode, and one of the boys in Sasami's class has done the old mirror-on-the-shoe trick so he can look up Miho-sensei's skirt. Sasami's girlfriends think this is a typical stupid boy trick, but Sasami thinks it's kind of neat.
The kicker is, when Mihoshi turns up, she's not wearing a skirt. I don't mean she's wearing slacks, I mean she's wearing a skirt, except not.
Which lead to a certain amount of re-evaluation of my guess as to the show's target audience.
At about that point I ran out of .avi, because I stupidly turned off my notebook while copying the file, so I will have to report back with more thoughts and screen caps.
Secondly, there's this: more...
The next telco sales rep who tells me that we have to connect to them using ATM because they are selling a business grade product is going to get a punch in the snoot.
Don't give me that "guaranteed delivery" crap. Yes, ethernet is best-effort, but it's a hell of a lot cheaper than ATM. If I can do a gig of ethernet for half the price of your OC-3, I know whose packets are going to end up on the computer room floor. If you're out of bandwidth, you're out of bandwidth.
(And I'm informed that Australia is out of bandwidth. As far as I can tell, all the major telcos here are being run by idiots. Which is no change at all from 1995 when I first started dealing with them. No wonder Telstra's shares are in the toilet.)
Friday, May 19
Brian Tiemann explains in excruciating detail.
mu.nu has moved servers three times over the past three years, from the original baby Celeron box, to a nice Athlon, to a dual Xeon, to the current pair of dual-core Pentium D's.
What probably nobody remembers is that the server itself moved once, as well.
Back in the early days, our hosting company, whose name is lost in the mists of time, was bought out by another hosting company. And lo, they decided to transfer all their servers to the new owner's data centre. Unlike Managed.com, though, they actually got it right: They chartered a 737, called in every vaguely technical person they knew, hoiked all the (carefully labelled) servers out of the racks and into a truck, zoomed off to the airport, flew them down to Florida, and had them all plugged in and running again in less than 12 hours. Well, at least my server was up and running in less than 12 hours, which is what counts.
Managed.com pulled the drives out of the old servers and stuck them in new machines. As recipes for disaster go, that's a simmer for three hours, feeds 24 starving grizzlies, gold-plate special.
Thursday, May 18
Update: Except, possibly, for these guys. Maybe.
Update: I was wondering why I hadn't run into the Kano Technologies iSCSI products before. Answer: They were launched today. The only reason I found them was that I was looking for eSATA storage at the time.
Update: Yay! Kano don't suck. They're not what I'd call cheap, but once you've bought the system, you're free to buy your own drives and slot them in. When you've seen the markups other vendors charge on standard disk drives, you realise that this is a huge win.
Powered by Minx 1.1.4-pink.