# Audio Damage Bitcom Now Available... - Site: Analog Industries - Author: Chris Randall - Date: 2013-01-31 - URL: https://analogindustries.com/2013/01/audio-damage-bitcom-now-available/ [![Audio Damage Bitcom Now Available...](https://analogindustries.com/images/blog/bitcom_ss_ai.png)](http://www.audiodamage.com/) To say that Bitcom took longer than expected would be to understate the matter in a somewhat ludicrous fashion. We decided to bang out a simple, fun sequencer-based bit-basher in August. It was supposed to take a couple weeks to make. Real Life, along with a fairly stupendous collection of computer and code problems, proceeded to kick us in the face. So don't let the lengthy dev time fool you. Some plug-ins want to be born quickly. Others require some pushing and lubrication. This was of the latter sort. But we're not going to pass on the sadness, dismay, and lack of a will to exist to you. This bad boy is $39.00. Go get one. Please. VST/AU 32/64. And yeah, there is no VST3 in this release. If you want to know what making this plug-in in VST3 was like, watch this video. In the metaphor, Adam is Chef, the boat is VST2.4, and the tiger is VST3. I am, of course, Captain Willard. Because it's my metaphor. Absolutely god-damn right. ## Comments (17) **R.A.W.** (2013-01-31): First... not only to post, but also to purchase. Received the mail and instantly bought it. Now I get no sleep at all - it's almost 1 am in Germany and I have to work tomorrow. ;) Nice! **Chris Randall** (2013-01-31): You are, as it happens, the first Bitcom buyer. Grats! -CR **darklordjames** (2013-02-01): Oh shit! I just watched that for the first time recently. The special effects hold up so very well. It was so nice not seeing digital mutilation and digital blood on everything for a change. Practical effects, yo. That's the way to go. **seancostello** (2013-02-01): Congratulations on the release! And I'm impressed on how quickly you recovered from the VST3 SDK bugs. **R.A.W.** (2013-02-01): Cool, I didn't really think I'd be the buyer, that was just a wild guess. Anyway, now it means even more to me. :D Just went through the presets and this thing is sick, can't wait to dig in deeper tomorrow. Just stopped by again to say, that my fav presets so far are 'Alias Bass' and 'Invader'. ;) **R.A.W.** (2013-02-01): ... "1st buyer" is what I meant... this blog needs an edit button ;) **dpirone** (2013-02-01): purchased! thank for creating awesome creative fun at a great price. "zap em with your horn" - djp **noisetheorem** (2013-02-01): so...what you're saying is that bitcom tastes like mangos? **Chris Randall** (2013-02-01): No. We needed mangos to finish the VST3. We didn't get any because we got attacked by a tiger. So, to continue this shaky metaphor, Bitcom most pointedly does _not_ taste like mangos. -CR **boobs** (2013-02-01): tastes great w/o mangos.. i just wanna fuck'n cook man. **studio nebula** (2013-02-01): @DGillespie: yes, actually, aside from the strange GUI. The first time I saw that movie I thought, wow, he must've sat around watching programmers to prep for that role. As far as I'm concerned, it's weirdly accurate, right down to the swearing at the computer, peering at the monitor from across the room, and the emotional roller coaster. And thanks. Thanks to everyone for your support and your biz. As CR alluded, some really bad shit went down in Real Life for me over the past seven or so months. This plug-in would've happened faster if it weren't for that, even taking the technical disaster into account. --Adam **joshua-s** (2013-02-01): Purchased + installed. Sadly it might be a bit before I can really try it out. I'll consider it a present to my future self. Hopefully this pushes ya'll closer to that 24 sales record. @Adam - sorry to hear about the IRL troubles. Hope things are sorting themselves out. **beauty pill** (2013-02-01): Adam, I'm sorry for any stress you've endured. You're obviously a good dude. Best wishes. - c **Chris Randall** (2013-02-02): To answer Intelliko's question, we had to remove the preset management system; it is written for VST3, and the internal workings of VST3 and VST2.4 are very different. It would have been necessary to re-write it from scratch for the new (old) framework. In the interests of releasing this plug-in some time this decade, we decided to nix it, as our previous method worked fine for 29 of our other 30 releases. And a further point: don't post problems/issues/crashes/whatever here. Send them to info@ad with a _complete_ description of what occurred, steps to repeat it, and your system information. Saying "I had a crash in Live. What's wrong?" is not even remotely informative, and I'm not going to get in to a lengthy debugging exchange here in the comments of AI. -CR **joshua-s** (2013-02-03): I've changed my mind and made time for this. Sounds like everything in my DAW is now utterly and completely broken. I highly recommend throwing rough rider pro or some other form of compression (and then a limiter, perhaps) after bitcom in the fx chain. -J **fussylizard** (2013-02-04): Finally watched the video Adam linked...Having done lots of programming I would have to agree it is a decent (though exaggerated) representation of late night programming sessions. They just missed the fingers crossed and quietly saying "please work, please work, please work..." while compiling / testing. Oh, and most development work involves staring at screen after screen of text, not bizarre graphical stuff as depicted. But screens of text are not sexy enough for the movies... **Crashproof** (2013-02-18): Yep, even working on graphics-related stuff, you tend to stare at screens of text. I finally got around to playing with Bitcom over the weekend. Fun stuff. Synth in triangle mode, modulating the level, bask in the weird artifacts. Working on a track now that has 1-3 instances of Bitcom on every channel... good times.