readme:
buzz2midi v0.2

1.1. What it does:
-program extracts notes (or triggerdata of some drummachines like rout 808) from bmx- 
or bmw-files, converts them into midievents and save them to a midifile of format 1. 

1.2. What it doesn't:
-every volume-informations are ignored. (velocity will be set to 80)
-only the actual parameter settings of the master for bpm and tpb are read. tempochanges, defined
in a master-pattern, will not be included in the midifiles tempotrack.


2. Scanning machine-dlls:
-like m2buzz buzz2midi needs a file named machine.ini, where the data needed for loading
files is saved 
-use menu <Machines> <Scan Gear-Directory> to create the machine.ini - file. the file isn't
compatible with m2buzz.
-use menu <Machines> <Scan Single File> to scan only one machine and add it to machine.ini. 
-only scan if really necessary! your computer might crash. (it works on my computer and it's 
really hard for one, to solve a problem, which he doesn't have.) i've tried to get almost
every published machine in the machine.ini delivered with the program, so you don't need
to create it for yourself.
-if a machine is missing, the program will ask for a single scan during loading.


3. Converting:
a) open buzzfile, menu <File> <Open>
b) the treeview to the upper left holds the machines. put the machines, you want to convert, 
per drag&drop into the treeview to the right, which can hold up to 64 track-entries.
it is possible to drag&drop the whole generators-entry into the trackwindow at once. 
there are more than one machines per track possible(maximum 64 machines per track). 
each track will be saved as own unit in the midifile. 
machines indicated through a red dot will be ignored by the conversion-routine.
right click on a track or a machine opens a popup-menu, where you can delete the entry from 
the list, delete all entries or apply one preset for the sustain-settings.
c)the treeview at the lower left holds a list of all sequences. the checkboxes indicates whether
the sequence will be included in the conversion or not. make your settings!
d). uses menu <Convert> <Convert> to ... uff... i've forgotten, what this is doing.


4. Sections:

4.1 Track
here you can rename the name of the track. it will be written to the beginning of every track 
in the midifile.

4.2. Machine:
- here you can define the midichannel, on which the notes of the machine shall play, and
how long the notes will be played.
noteevents in midifiles are divided into two events: note_on, which starts playing the note
and note_off, which stops it. buzz-notes are played another way, mainly there is only 
the note_on - event. the note stops playing, if a off-event occurs in the pattern or a break - or
mute-event in the sequencer, the next note in the track starts to play, the song ends or 
the machine itself has a dca-release and mutes the note.
to generate the missing information about the playlength of a note, there are two variables 
for every machine declared: release and max_release.
the program calculates the distance from one note to the next note-, off-, mute-, break- or
songend-event and set the playlength to the percentage you've defined for the machine.
set it to hundred for full length, decrease it for staccato.
to prevent playing a note over several minutes, because there are no other stop-events behind it,
the variable max_release is declared.
if the release-length of a note (in buzz-ticks) is greater than max_release, it will stop. 
- it is possible, to use the notes, a machine plays, as trigger for a constant note. it could be
usefull, if you use sampletrackers for playing drumsamples and want to let the drums played by a
drummachine like the waldorf attack. put them in one track, for example set c4 for the basedrum, 
d4 for the snare and enjoy. (base octave is the octave of the constant note, the note itself is 
set in the specific-section)

4.3. Specific:
- if the machine is one of the supported drummachines, a listcontrol will appear, where you can
set the note for each triggerswitch(note that some switches only influence the behaviour of a
drummachine in buzz. buzz2midi don't know the purpose of a switch.), which will be played, 
when the corresponding switch-value becomes 1(TRUE).
you can save your settings as preset, so you don't have to do the work every time, you want to
convert some 808-patterns to a miditrack for a vsti-drummachine. 
push the button "add" and the settings will be added to the preset list below the listcontrol. 
"apply" will apply the selected preset and "del" deletes the current preset.
renaming a preset is simple: just type the name you want in the editcontrol. the spinbutton to 
the right is for browsing througt the presets.
- if the machine is none of the supported drummachines and have a note-parameter, some radiobuttons
and a checkbox will appear. as mentioned before it is possible, to use a noteevent only as trigger 
for a constant note. if the checkbox is active, every note played by the machine will be 
interpreted as the note-value you've defined by the radiobuttons and the base octave -entry in the
machine-section. 


additional notes:
-at the moment zephod ht-700 drums will be ignored. 
-if you use buzz2midi, you do it on your own risk. if your computer explodes, don't give the 
responsibility to me!

advertisment:
you can find my music (mainly composed with buzz) on:
(nam dans)
http://www.meet-music.com/shared_elements/meetbox/show_meetbox.phtml?sid=0f5a5198d06cb67577d9e19eaf3325f9&sylangu=DE&status=S&bandnummer=0&u_id=66c17286539248b28843fbfcc1c14ffa

and
(heschl's gyri)
http://www.meet-music.com/shared_elements/meetbox/show_meetbox.phtml?sid=0f5a5198d06cb67577d9e19eaf3325f9&sylangu=DE&status=S&bandnummer=1&u_id=66c17286539248b28843fbfcc1c14ffa

and finally some tunes generated with a little bmx-hack, i wrote, and which was the base of buzz2midi
(binary)
http://www.meet-music.com/shared_elements/meetbox/show_meetbox.phtml?sid=0f5a5198d06cb67577d9e19eaf3325f9&sylangu=DE&status=S&bandnummer=2&u_id=66c17286539248b28843fbfcc1c14ffa

