About

Buzztard aims to be a music studio that allows one to compose songs using only a computer with a soundcard. If you’ve used tracker programs like FastTracker, Impulse Tracker, or the original AMIGA SoundTracker, that will give you an idea of how one can sequence music in Buzztard. The Buzztard editor uses a similar concept, where a song consists of a sequence with tracks and in each track one uses patterns with events (musical notes and control changes). In contrast to other Tracker programs, tracks are not simply sample players: a user can make a song using an arrangment of virtual audio plugins that are linked together to create different effects. Each of these machines can be controlled realtime or via patterns in the sequencer.

The buzztard editor will be just one possible application of the framework we are implementing. Tools like a dj mixing application or a live session composer are other things that can be built using our framework.

News:

buzztard project status 01/01/2012

Finally after a long time, I managed to release a 0.6 of buzztard. So far only one regression was found and bml-0.6.1 was released to fix it.

A few things happened before the release still. At first after updating my distro, I made a lot of changes to avoid deprecated gtk+ api. For now . . . → Read More

ANN: buzztard 0.6.0

The buzztard team has released version 0.6.0 “black beats blue” of its buzz-alike music composer. All modules got extensive improvements over the last release from more than two years ago. Give it a try, join hacking and report bugs.

bml Improved machine compatibility.

bsl Several bug fixes and better compatibility.

buzztard Main feature of . . . → Read More

buzztard project status 01/12/2011

Over the last 2 month I did quite a bit of work on the GStreamer side. Right now we’re working on 0.10 and 0.11 in parallel. I worked on the audiovisualizers and opencv elements in 0.10. I added a freeverb port to 0.10. In 0.11 I updated the controller susbsystem. If is now a . . . → Read More

buzztard project status 01/10/2011

This month I focused on testing for the next release. My free time for the project was a big short anyway, as my family move to our new home and I had quite some janitorial work to do.

One lesson learned for the start. Some time ago I had problems with tests going crazy . . . → Read More

buzztard project status 01/09/2011

After lots of changes I have switched the code permanently to the new sequence model. It saves about 170 lines of code in the sequence-page source. There is some potential to save more though.

I also did more work on state persistence. A song now contains more information (selected machines, pattern, options) and these . . . → Read More

Jhbuild polished

After a while we have tried to check if our Jhbiuld works as before. Now we have fixed some small issues with the Jhbuild.rc files. If you compile and run buzztard now with our Jhbuild instructions, you will also have the installed buzz-machines available and can direct start to compose.

more machines available

For the poor people who are not on a x86-32bit platform – go and update your buzzmachines checkout. I ported 8 more machines (and I am not done yet).

buzztard project status 01/08/2011

Another month with good progress. I’ve started with the undo/redo parts in the sequencer view. Most of the edits are handled now. I am still stuck with one problem though. So far the order of signal handler on object removal did not matter. Now it does :/ There are things that when they get . . . → Read More

buzztard project status 01/07/2011

This month I made great progress. I have been making several small demo songs and found+fixed quite many bugs and glitches along with that.

After a little break I took up undo/redo work and could make good progress. Now also pattern property changes (name and length) are tracked. In the sequence the boilerplate code . . . → Read More

buzztard project status 01/06/2011

In the begining of the month I finished the new treeview models. There were a couple of corner cases I did not handled yet. I did some thinking about the remaining model, but did not yet write any code for it. Instead I did some code review of the whole project leading to numerous . . . → Read More