4 ms·

Some background on Buzz for others: Buzz was a tragic case of not using version control. Apparently the author had a hard drive die, and his only copy of the so

Some background on Buzz for others: Buzz was a tragic case of not using version control. Apparently the author had a hard drive die, and his only copy of the source control went with it. It had a unique routing UX (https://en.wikipedia.org/wiki/Jeskola_Buzz#/media/File:BuzzScreenshot.png https://en.wikipedia.org/wiki/Jeskola_Buzz#/media/File:BuzzS...) that allowed you to chain sources and effects using a graph. Bitwig has a similar idea in The Grid (https://www.bitwig.com/the-grid/ https://www.bitwig.com/the-grid/), though that's limited to just one track; Buzz did this for the entire composition. There was at least one rewrite attempt, and there are various clones (Aldrin) but they never quite made it.

stavros 1y ago
Sounds like a tragic case of not making backups, to me. Even if the author used a VCS, when the drive died it would have taken the repo with it all the same.
HexDecOctBin 1y ago
Is the "routing" similar to Sunvox? https://warmplace.ru/soft/sunvox/images/t/01/01.png https://warmplace.ru/soft/sunvox/images/t/01/01.png
pierrec 1y ago
I believe the event you describe is pretty ancient, and Buzz recovered and continued development for many years after. I wrote some plugins for the more recent versions of Buzz, the plugin API was always nice to work with (compared to VST at least!)
- Intermernet 1y ago
  It had a device called "amen" that did exactly what you'd expect. Pretty sure I used it on every track I made :-)
NetOpWibby 1y ago
> Buzz was a tragic case of not using version control. Apparently the author had a hard drive die, and his only copy of the source control went with it. Yeah, lemme go ahead and commit this code I've been working on for weeks without creating a repo...
whizzter 1y ago
Actually from 2008 to 2016 there was updates, they sent off the disk to a recovery firm and got a mostly latest copy and built from that. The newer versions used .NET and the main improvment in those builds was a new pattern-system (XP-patterns) so you could make patterns that selected parameters from one or more machines. So the annoyance of having to work in different patterns when your "instrument" was made out of a chain of discrete modules went away (also useful for making chords from primitive machines since you could hook multiple generators in one pattern).

stavros 1y ago

Sounds like a tragic case of not making backups, to me. Even if the author used a VCS, when the drive died it would have taken the repo with it all the same.

HexDecOctBin 1y ago

Is the "routing" similar to Sunvox? https://warmplace.ru/soft/sunvox/images/t/01/01.png https://warmplace.ru/soft/sunvox/images/t/01/01.png

pierrec 1y ago

I believe the event you describe is pretty ancient, and Buzz recovered and continued development for many years after. I wrote some plugins for the more recent versions of Buzz, the plugin API was always nice to work with (compared to VST at least!)

Intermernet 1y ago
It had a device called "amen" that did exactly what you'd expect. Pretty sure I used it on every track I made :-)

NetOpWibby 1y ago

> Buzz was a tragic case of not using version control. Apparently the author had a hard drive die, and his only copy of the source control went with it. Yeah, lemme go ahead and commit this code I've been working on for weeks without creating a repo...

whizzter 1y ago

Actually from 2008 to 2016 there was updates, they sent off the disk to a recovery firm and got a mostly latest copy and built from that. The newer versions used .NET and the main improvment in those builds was a new pattern-system (XP-patterns) so you could make patterns that selected parameters from one or more machines. So the annoyance of having to work in different patterns when your "instrument" was made out of a chain of discrete modules went away (also useful for making chords from primitive machines since you could hook multiple generators in one pattern).