Apache and BeTips

BeTips is now running Apache, rather than Robin Hood. Forget about Xitami. Have done a bunch of benchmarking, and Xitami is slow as molasses compared to Apache and RH. Maybe Xitami does well on single-threaded platforms, but on a dual-proc BeOS machine, it’s all about multithreading, and single-threaded just doesn’t cut it.

Learning a lot by learning to configure Apache. I’ve never had the opportunity to do it before. Not difficult, just brand new territory for me. Enjoying the changeover. Now have everything working but SSI, and that seems to be an acknowledged problem. We’ll lick it.

Have been using Microsoft’s Web Application Stress Tool for the benchmarking. Pretty sophisticated. Did an 8-hour run against Apache last night, requesting alternating HTML and CGI pages as fast as possible. Did nearly half a million overnight. Would have been a lot more, but running through the slow pcmcia network card in my laptop, and my CGI pages do a lot of work. Apache also comes with ab, so I can do stress testing on the local BeOS machine without having the network in the way — huge difference.

Out of Words

Memory:

My grandfather had a very husky, slow, quiet voice. When I was very young I took this to mean that he was running out of words – I thought he had used up his lifetime supply. I thought I had to be very careful because I didn’t want to run out of words too. I went through a period where I didn’t say much, because I was trying to be careful and not run out.

White Boy Dreadlock

What I don’t understand is why most of the posts here are complaining about people who are critical of white dreads, when none of the posts here are critical of white dreads! And in fact, the original post that started this discussion (which I wrote) does not criticize white dreads. So… uh… is there like, a persecution syndrome happening here?

Xitami

Cool – Rob Judd just compiled the Xitami web server for BeOS, so I’m running betips on xitami rather than RobinHood now. RH is great, but there are some things it doesn’t do, like output standard Apache log format. Xitami does, so I’ll finally be able to parse my traffic logs with analog.

I’ve also wanted to see whether frequent server stoppages are a result of BONE or RH. Wanted to test with Apache, but was never able to get Apache to compile under BONE. Anyway, this test is going very well so far. Spent a couple hours configuring last night and all is good.

Already reported one bug last night, and Judd sent me a new binary by this morning with the problem fixed. Wow – a responsive developer!

The BeOS Paradox in 2001

I just posted this on BeNews. Re-posting here because it summarizes my thinking about the operating system that was one of the most important things in my life for the past four or five years. I’ve had to go through a lot of gear-gnashing to come to terms with the current state of things. This sums up where I stand with it today.

Many people seem to misunderstand my current position on BeOS. If my words and my actions seem contradictory, it is because of the apparent paradox of these two true statements:

1) The BeOS _marketplace_ is extinct, done for, and beyond hope of resurrection. This fact would not change even if a major new BeOS release appeared (which I feel is highly doubtful) — it’s far too late for that and too many businesses have been burned by attempting BeOS development. There is no money to be made on the platform. Without either monetary incentive or open source momentum (we have neither), the future growth and evolutionary potential of BeOS and BeOS apps is extremely limited.

2) Despite its shortcomings and missing mature applications, BeOS is the best desktop operating system ever developed, period. So good, in fact, that people will continue to enjoy finding uses for BeOS despite the truth value of #1.

I am bitter because of #1, but I still (sometimes) use and promote BeOS because of #2.

Teeth butcher

“Deep cleaning,” my dentist calls it. So deep they only do half the mouth at a time. Had the left side done two weeks ago, and the right side done today. Sawing between the teeth with diamond dust to make more room for floss. Incessant grinding with sinister looking tools. Polishing, scraping, nitty gritty mouth madness. Such a complete and thorough brutalization of the mouth that I walked out of their office with… get this… another Vicodin prescription. God, what’s happening to me? I used to be immortal. Now I’m just broken all over.

MP3 Fidelity Results

Spent a few hours last night at Mike’s house listening to the MP3 fidelity test discs I burned the other day. The discs included these tracks:

Coltrane – Resolution (the Michael Cuscuna – produced version of A Love Supreme)
Alban Berg: Three Pieces for Orchestra, Ostinato (on RCA Living Presence)
Rob Wasserman – Angel Eyes (cello / vocal duet – superb recording)
Klip – Dyslexiana
Theresa Anderson – Summertime (my fave female vocals test and fave cover of this song)
Gerry Hemingway – Endpiece 1 (from Special Detail)
Tim Buckley – Hullucinations (from Live Dreamletter)

We did not get around to listening to all four versions of all seven pieces. The system we used was:

Audio Alchemy CD transport with DTI Pro jitter reduction
Audible Illusions Modulus 20 pre-amp (heavily modified)
Muse 100 amplifier
NHT 3.3 speakers

System value approximately $20,000

I’m still trying to figure out what we learned from all of this. First of all, I can unambiguously say that I have never heard MP3s sound this good in my life. Second, this is the first time I’ve ever been able to distinguish between 256kbps MP3 and the original source material. However, I also learned how much the mind plays tricks on you in tests like this, and hence why audio mags often avoid them. The only valid test is really to live with the material, doing what you do normally, whether that be sitting down and doing concentrated listening or playing it in the background while going about your business. In other words, if we listened to these tracks over and over again, and if we lived with them and subsumed their presence into the subconscious, we would be able to discern additional differences we didn’t notice yesterday.

I also have to say that Mike has a lifetime of intensive experience and training in audiophile listening environments, and in building hifi audio equipment. I care a lot about fidelity, but don’t have ears as well trained as his. He was able to discern more differences than I was.

Mike also pointed out some problems with the methodology of my experiment. Because each track can last 5-10 minutes, it’s extremely difficult if not impossible to make meaningful comparison notes without a standard of reference. IOW, I wanted for us to try and pick out the reference track blind, while he felt it would be more meaningful to know in advance which one was the uncompressed WAV, so we could compare the other bitrates to it. His point made more sense after we listened blind for a while – your mind really does play tricks on you. For example, you might hear more air in a cymbal splash in one track, but you could be unsure whether that “air” is in the reference (a good thing) or an artifact of the encoding process (a bad thing). So in the end we did most of our listening with knowledge of which track was the WAV reference.

Neither of us had any difficulty picking out the 160kbps tracks, which was disappointing knowledge for me, as I’ve encoded tons of music at 160kbps. From here on in, I’ll use 160 only for crappy old recordings, 192kbps for average stuff, 256kbps for stuff I really love or that’s really well recorded, and 320kbps for those amazing gems that are stellar both as music and as recordings.

Mike is going even higher. His argument is that disk space is just so cheap now, there’s no point in compressing at all. Why risk it? It’s interesting because this is the same argument I made in the intro to my MP3 book – that the only reason we even talk about compression is because storage is too expensive and the internet is slow. But think about it – 40GB drives are under $100. It’s possible to fit around 60-70 albums on a 40GB drive in uncompressed WAV format. That’s about $1.50 per album in storage space. If you care enough about your music to have a system like his but you still want the flexibility of soft storage for your collection, why compress at all? Then you just build an array of 10 or so IDE drives to house your collection, which would be like spending a grand on an important new stereo component – worth it.

I counter that by saying that the difference b/w 256kbps and WAV is so incredibly subtle, and 320kbps would be virtually indistinguishable in every important way. You still get around 4x compression at 320kbps, and you have the advantage of ID3 tags. Why not take advantage of it?

I could tell there was a difference between the 256 and the WAV in the Wasserman duet/vocal, but had trouble putting my finger on the difference. Mike nailed it down, and had me focus on the spatial relationship or distance between the vocalist near the middle of the room and the cello in the rear left of the room. At 256kbps, there is a sort of “veil” that enshrouds the vocals, and ties it spatially to the cellist in the rear left. It’s subtle, but he’s right – the spatial distinction between them is just not as pronounced at 256kbps as it is with the WAV. But the fact that it had to be pointed out to me, and that I had to concentrate to find the difference even then, tells me that this is a difference I can live with, even if he feels he can’t.

However, the same effect at 160kbps is atrocious. It sounds like there’s a blanket thrown over the whole production – like you’re listening through a thin layer of gauze that sort of erases or diminishes the space between musicians. However, it requires a system better than most people own or have even heard in their lives to reveal some of these differences. On a standard Japanese consumer stereo, 160 might be adequate for most people.

My problem is that I haven’t followed my own advice. I have professed that people’s MP3 collections would eventually migrate to their home stereos, and have warned that they shouldn’t trust their computer sound systems to tell the whole story. Nevertheless, I’ve encoded almost everything at 160kbps, and now have a collection that will translate to the home stereo with less than stellar results. Hrmmm…