5-Oct-2002 (Sat)

I've been kind of lax about updating lately, I know... What happens is, it gets near the end of the week, and I think back and say to myself, ``eh, nothing really happened that's worth writing about.'' Then I finally sit down and force myself to start typing, and one of these 700+ word giganto-entries like this one comes rolling out.

Let us begin...

At the Adam Freeland show, someone brought in a giant boombox. And by ``giant'' I mean ``filled the whole stage!'' It's an easy guess that this was something left over from Burning Man, but it was exactly the right size for our stage: it looked like it had been built for us. The DJ stood in the place where the cassette door would have gone, and the VU meters above him were actually hooked up to the mixer, so they were accurate. It was pretty cool. I didn't have my camera with me that night, so here are a few shots I pulled off the webcast (mostly taken after closing):

We got new bulbs for all the intelligent lighting, and this combined with the fact that our hazer is working well again means that the lights have been looking really good lately: I guess they'd been growing gradually dimmer, because it seemed like a pretty dramatic difference after the bulbs were replaced. (Nice fact about intelligent lighting: it's a bad idea to wait until bulbs burn out to replace them, because they tend to fail catastrophically (i.e., explode) and damage the light.)

We've been having the usual assortment of computer troubles:

  • Last week our main gateway/router OpenBSD machine decided to just stop allowing most new connections to be established (but only, like, 99% of them.) Existing, established connections were fine, though, and sometimes connections could get through. I couldn't figure out what was going on, so I rebooted it, which ``fixed'' it. Then it did the same thing again three days later (and so did I.) I hope this isn't becoming a habit.

  • Every now and then, the audio on the RealVideo stream turns to static. I don't know why, it just does. Sometimes it fixes itself, and sometimes not. It always starts working again if I restart the server. Of course, I have no way to make the computers detect this, and auto-restart the server, since Real uses a proprietary, secret protocol. I have scripts that will restart the server if it crashes or otherwise goes down, but if it goes to static, I'll never notice, so I have to rely on people emailing me about it. That's kind of weak.

  • As far as I can tell from looking at the bandwidth charts, nobody ever uses our wireless network. Or, perhaps, people are trying and it doesn't work. I wonder which it is. If you've tried to use it and failed, let me know! I'm leaning toward ``nobody cares about it'', myself.

The restaurant next door, Dulcinea Cafe, is finally open! Yesterday (thursday) was their first day. The food is just great, we're all going be eating there a lot. Ok, well, we'd probably be eating there a lot regardless, it being next door and all, but it really is good!

I put up some photos of thursday's Capacitor performance. It was super cool: if you missed it, you have three more chances, since it's happening every thursday at 8pm until October 24th. There was a review of an earlier incarnation of this show in Wired a few months ago.

We've got a few special events coming up that I'm looking forward to:

  • On Monday, October 28, we've got a live performance by My Life with the Thrill Kill Kult, with Cherrie Blue and Voodoo.

  • On Thursday, October 31, our second annual Halloween party, with Rosin Coven (who performed on Halloween last year as well), Butoh dancers, a bunch of goth djs in the main room, and CODE residents in the lounge; plus the requisite costume contest, prizes, etc.

  • On November 14, 15, 16, and 17 we've got the four day Beyond the Pale festival, with Neurosis plus fourteen other bands. It's probable that all four nights are going to sell out, so get your tickets early if you're interested...

Let's see, what else is new... We've got a new weekly friday event, Remedy, and it seems to be going pretty well. By which I mean, there are a lot of people. It's basically the same crap house music as most of our weekend events have always been, though I'd have to say that this one seems even a little more unabashedly disco than OM and Melon, which I wouldn't have thought possible. The crowd seems a lot more mainstream too. But, that's offset by the fact that they hire the Go Go Pro dancers every week, who always have really creative costumes (and do things like stilt-walking, etc.)

10 Responses:

  1. icis_machine says:

    it was so good even b liked it and he hates formal dance. thanks for housing it.

  2. baconmonkey says:

    re: RA going to static...

    have a machine play RA stream and loop-back the output audio to it's own input.
    analyze input.
    when it goes batshit, communicate with streaming server in some way and tell it to restart the RA Daemon.

    a wall of statis should be easy to detect via one of several methods.
    1. unvarying RMS levels
    2. FFT spectral analysis looking for unvarying wall of sound

    • jwz says:

      It's very hard to do that, because it's very hard to keep RealPlayer running: if there's ever a network glitch, it'll stop, and you have to click "Play" again, possibly after clicking "OK" on the dialog box first. There's no non-GUI batch-mode version of RealPlayer, nor is there (I think) any way to remote-control it. (Maybe something with JavaScript and plugins, but that's a whole other ball of worms: web browsers that can run JavaScript and plugins don't work real well in batch mode either.)

      I'm trying not to just be kneejerk about this, but it really is another example of the superiority of open standards: if the protocol was documented then this problem would be solvable in any number of ways:

      • there would be a way to play audio batch-mode without needing user interaction through the GUI;
      • there would be a way to decode and analyse the stream in software instead of going through a hardware loopback cable;
      • there would be a way to turn on verbose diagnostics in the player, so I could just restart the stream whenever the player started spitting out a lot of messages about bad frames or whatnot;
      • and, realistically, the code probably wouldn't have this bug in the first place, because someone would have fixed it by now.
      • baconmonkey says:

        there's nothing knee-jerk about it.
        well, other than wanthing to KNEE the JERK who started RA in the groin.

        but I digress.
        MS and apple's video standards are not exactly open, but there are SDKs and developers resources, such that one could write a program to monitor a stream, even if one doesn't know the specifics of the innards of the stream. there might be an RA SDK, but it'd probably cost a fair ammount of $$. have you looked for any 3rd part RA tools? I mean, you can't be the only one to have this problem...

        • jwz says:

          As far as I know, there are no third party RealVideo tools. I really wish I could just ditch Real entirely, but there aren't any alternatives. The MS and Apple offerings are, of course, useless to me, because there are no players that work on Linux. (Running Windows emulators doesn't count, saying "Quicktime works fine! Oh, unless you want Sorensen" makes me throw things.)

          I assume other people who do RealVideo broadcasting solve this problem by having staff watching it all the time.

          • baconmonkey says:

            "I assume other people who do RealVideo broadcasting solve this problem by having staff watching it all the time."

            when have you known a large company to view that as a valid response to off-the-shelf products?
            sure it inevetably happens, but that's when there is internal development added on top of purchased products. no company would buy a server that is that unreliable without some sort of software fail-safe. either something is greivously wrong with your config, or there is a product out there to monitor the daemon. or REAL has managed to scam the world yet again.

            • jwz says:

              If you want to do large-scale RealVideo broadcasting, it costs over $100k in licenses alone. Anyone paying that can afford to make it be an admin's job to keep the damned server up, and/or have the fellatio-hotline to Real's developers who actually know how to fix things.

              • baconmonkey says:

                I dunno, I still can't see even the dumbest of corporate buyers purchasing the full thing when the answer to "how reliable is this $100K server you're trying to sell us?" ends up being:
                "Oh very reliable, as long as you have one of our patented Reboot Monkeys (TM) on the payroll. You see, little Bonzo here is trained to press the shiy red reboot button if he hears more than 3 seconds of static in his headphones. He also knows how to make coffee and change his own diaper."

                no company with a brain would buy something that is admitted to being that unreliable - even if they can afford a crack team of slackers to sit and listen to their streams 24/7. would you buy a web server that had similar disclaimers on it's stability? plus there would inevetably be a competitor popping up if it really was that shoddy. MS and QT are not really geared towards real-time broadcasts, so they don't count.

                • jwz says:

                  Who said they admit it's not reliable? Nobody who sells software ever does that, and software is very rarely reliable. Anyway, for all I know, it's 10x more reliable when running on NT instead of Linux (though that's kind of hard to believe.) The manual makes it clear that the NT version of RealProducer is far more polished than the Linux version, so I assume that's where most of their customers are.

                  MS and QT are not really geared towards real-time broadcasts, so they don't count.

                  What sites do realtime 24/7 streaming besides mine? I'm sure there are some, but I can't think of any, which makes me think there aren't too many of them. I suspect that most people either: only do realtime stuff every now and then, for the duration of an event, and have someone to babysit it (and press the start and stop buttons); or, more commonly, they're people like CNN and IFilm who do non-realtime streaming of short-ish pre-recorded clips.

                  • naturalborn says:

                    It's true, the hardest part of large Real deployments is keeping the damn servers running. There have been a number of big deployments which didn't go so well and everybody thought the problem was bandwidth when in fact there was plenty of bandwidth and the servers kept crashing.

                    The ability of people to be incompetent at writing software never ceases to astound me. A Real server has to do encoding and compression on the fly, but it only does that once, and thereafter uses the same data for all downloaders, so as it scales up it's really just pushing the same data to more downloaders. The servers are written in C++, spewing out basically raw data to a large number of downloaders, and yet crash constantly and are frequently CPU hogs. This after years of development by several teams of people.

                    My own networking app can push out huge quantities of data with no glitches and hardly using any CPU, and it's written in Python. I don't know how they do it.