click here for editors for both the Waldorf Microwave and Microwave II.Click the image for the full size shot. Note the Wave Control Table Editor. "Dead Beef?"
Wednesday, December 19, 2007
Waldorf Microwave Editor for Macintosh
click here for editors for both the Waldorf Microwave and Microwave II.Click the image for the full size shot. Note the Wave Control Table Editor. "Dead Beef?"
2 comments:
To reduce spam, comments for posts older than one week are not displayed until approved, usually same day. Do not insult people. For items for sale, do not ask if it is still available. Check the auction link and search for the item. Auctions are from various sellers and expire over time. Posts remain for the pics and historical purposes. This site is meant to be a daily snapshot of some of what was out there in the world of synths.
PREVIOUS PAGE
NEXT PAGE
HOME
© Matrixsynth - All posts are presented here for informative, historical and educative purposes as applicable within fair use.
MATRIXSYNTH is supported by affiliate links that use cookies to track clickthroughs and sales. See the privacy policy for details.
MATRIXSYNTH - EVERYTHING SYNTH
© Matrixsynth - All posts are presented here for informative, historical and educative purposes as applicable within fair use.
MATRIXSYNTH is supported by affiliate links that use cookies to track clickthroughs and sales. See the privacy policy for details.
MATRIXSYNTH - EVERYTHING SYNTH
Subscribe to:
Post Comments (Atom)
0xDEADBEEF means that the wavetable data is of the "Speech Robot" type where you'd use some old Atari ST program to take a text string and turn it into an awesomely crude synthesized speech table that would generate phonemes sort of resembling the original phrase.
ReplyDeleteThis feature was broken in the Microwave II and beyond... too bad!
I might finally be selling my old Microwave 1 soon. It's an awesome instrument, but my tastes have shifted away from oldschool MIDI racks.
Hmm. Not sure bout that significance. In general computer programming, 0xdeadbeef is used a lot to fill memory before user programs touch it. So, when you do a hex dump, and see
ReplyDeletedeadbeefdeadbeefdeadbeef ...
you know that your nice little program hasn't initialized it to something more likely like
000000000000000000000000 ...