Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
It's funny.  Laugh. Bug Operating Systems Software Windows

Computer Glitch Halts Seattle New Year's Fireworks 202

supersat writes "At the stroke of midnight New Year's Eve, Seattle's fireworks show ground to a halt. The source of the problem is reported to be a corrupted file that wasn't checked until the last minute. After two reboots, the fireworks had to be detonated manually. And yes ... one blog commenter, claiming to have worked on prior shows, said that the shows run on Windows."
This discussion has been archived. No new comments can be posted.

Computer Glitch Halts Seattle New Year's Fireworks

Comments Filter:
  • by aethera ( 248722 ) on Tuesday January 01, 2008 @01:01PM (#21874922)
    From what little we have to go on in the article, it looks like there was a problem with syncing to time code. It's been a few years since I last did time as a tech at a major theme park, but our fireworks shows looked a little like this: There was a dedicated computer running the pyro controls, one running sound playback, one controlling the lasers, one controlling lights and fog, and one controlling some miscellany such as a 70mm film projector and the large water pumps that produced a screen the movie was rear-projected onto. All of these computers could be a little buggy given that this was in the days of windows 98 and getting device drivers to play nice was always a problem. But this stuff was worked out long before showtime. The biggest problem that could show up at the last minute would be the SMPTE time code that keeps it all synced up. One intermittent cabling problem somewhere in the system could cause a computer to get bad or no time code signal at all, causing at least that one element to not playback correctly. The best way to solve this problem was to notice it ASAP, usually in the few seconds of preroll before the show starts so that you can manually sync everything at a predetermined point. But there really is no ability to pause just one element or speed up others. Once you're off time code, you're going to have to go manual, and at least with pyro with all of the different fuse delays involved, manual just isn't going to be quite right. The only other last minute problem I could think of would be a corrupted file, or more than likely a revision that wasn't saved correctly or an outdated file being loaded automatically by the show control software and no one verifying that it was the proper version. These holiday shows are a one off, of course, so there is no dress rehearsel. You can run all the simulations you want, but you only get to fire off the pyro once.

Old programmers never die, they just hit account block limit.

Working...