Machine blacklist

From Jeskola Buzz Wiki
Revision as of 17:11, 31 July 2009 by Zephod (Talk | contribs) (WM errors)

Jump to: navigation, search

Here is the list of the machines that will cause buzz to become unstable - even if you don't use them in your songs. They must be completely removed from your Buzz install folders. (Experienced users, if you must use these machines, you are recommended to maintain a separate install in which to do so.)

  • A new feature of Buzz is the Debug Console. (Run Buzz, go to View/Debug Console.) The Debug Console has a Command-style interface, scroll through the messages, and view information about about your initialization, specifically regarding 'machine load errors'.

Terms and conventions

  • Effects suffixed by the bracketed statement '(Stereo)', are the stereo-wrapped versions of mono machines.
  • The term 'Blacklisted' refers to buzz machines, forcibly excluded by the program.
  • Buzz generators and effects can be run within several different hosts, for example, Buzé.

Blacklisted in Jeskola Buzz

  • 11-MidiCCout.dll

Blacklisted in gear.xml

These are machines Oskari has marked by default as they conflict with the buzz builds from 2008 onwards.

  • CyanPhase Buzz OverLoader
  • CyanPhase DX Instrument Adapter
  • CyanPhase DX Effect Adapter
  • CyanPhase DMO Effect Adapter
  • 11-MidiCCout

Blacklisted in Buzé

These machines cause problems in Buzé, some may also cause problems in buzz, let's go through Buzé's blacklist, my comments are in itallics, edit if you know better.

These are unstable/unusable:


I have heard of people having problems with Argüelles machines in Buzz, but the others should be fine..?

  • Effect/Static Duafilt II

Not to be confused with Static Duafilt, which is a stable , useful machine.

Crashes on startup:


Also blacklisted in Buzz's gear.xml

The mono versions of these need a patch to run, so their stereo-wrapped counterparts are unusable:

Note you can download fixed versions of these in from the Buze website.


The patches of these are only needed for Buzé and they should be fine in Buzz as far as I know...

Makes no sound and does nothing useful in libzzub anyway:


This is only for overloader extended output and no use in Buzz builds from 2008 and on. If using Buzz 1.2b (Oct 2000 version) there's no problem using this

Cannot be used with libzzub and have been replaced by Audio Input and Audio Output:


Polac's ASIO in/out/shake-it-all-abouts are the best input/output machines in Buzz for those of us with ASIO drivers

Machine behavior-quirks and anomalies

The machines listed below are not blacklisted, and they are all stable and recommended for your use. These machines may, under certain circumstances, appear to behave strangely or incorrectly during use. These quirks and anomalies are not necessarily faults, and are either of the authors' design, or an unavoidable byproduct of the hosts' handling of the plugin.

Sample rate compatibility

  • Some poorly written machines will not work correctly when Buzz runs at a sampling rate other than 44100 Hz.

( Configuring Buzz_View/ Preferences/ Wave Output/ Config ).

Copy/Paste parameters into a pattern

  • Some machines do not appear to handle copying of a Machine Parameters, and pasting into a pattern, correctly. After pasting, some, or sometimes all, of the pasted data shows incorrect values.

WM errors

  • Some Buzz machines generate WM (Work Mode) errors, the CPU Monitor window will display these errors as a numerical value. Users do not need to be concerned about these errors, unless some other machines show excessive CPU usage due to denormal processing. (effects might wrongly expect actual audio in the buffer due to the result of the previous effect/gen, resulting in extremely low floating point values)

If the cpu usage explodes, you can either replace the offending WM-erroring effect by something similar, or insert some denormalizer/dc-offset machine between the 2.

Machines persist to emit sound

  • A small number of Buzz generators and effects continue to emit sound when play is stopped, or in a few rare cases, start to emit sound the instant they are evoked. This is a design feature of the machine's author, users need not to be concerned. Users may wish to control the sound output from such a machine by using a gain, amp or mute effect, or by adding a mute command to your sequence.