[beast] DOCS: import online docs for 0.7.6 release
- From: Tim Janik <timj src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [beast] DOCS: import online docs for 0.7.6 release
- Date: Thu, 25 Oct 2012 01:18:05 +0000 (UTC)
commit 523aa3941885c0658aa5895bc2614912ad803cf4
Author: Tim Janik <timj gnu org>
Date: Thu Oct 25 02:37:24 2012 +0200
DOCS: import online docs for 0.7.6 release
docs/import/Beast-Quickstart | 98 ++++++++++++
docs/import/Beast_FAQ | 119 ++++++++++++++
docs/import/beast.1 | 117 ++++++++++++++
docs/import/bse.5 | 60 +++++++
docs/import/bsescm.1 | 121 ++++++++++++++
docs/import/bsewavetool.1 | 359 ++++++++++++++++++++++++++++++++++++++++++
docs/import/sfidl.1 | 91 +++++++++++
docs/import/stamp | 1 +
8 files changed, 966 insertions(+), 0 deletions(-)
---
diff --git a/docs/import/Beast-Quickstart b/docs/import/Beast-Quickstart
new file mode 100644
index 0000000..9673f78
--- /dev/null
+++ b/docs/import/Beast-Quickstart
@@ -0,0 +1,98 @@
+<table id="toc" class="toc"><tr><td><div id="toctitle"><h2>Contents</h2></div>
+<ul>
+<li class="toclevel-1 tocsection-1"><a href="#BEAST.2FBSE_Quickstart_Guide"><span class="tocnumber">1</span> <span class="toctext">BEAST/BSE Quickstart Guide</span></a>
+<ul>
+<li class="toclevel-2 tocsection-2"><a href="#First_Start_At_Synthesis"><span class="tocnumber">1.1</span> <span class="toctext">First Start At Synthesis</span></a>
+<ul>
+<li class="toclevel-3 tocsection-3"><a href="#Creating_A_Synthesizer_Network"><span class="tocnumber">1.1.1</span> <span class="toctext">Creating A Synthesizer Network</span></a></li>
+<li class="toclevel-3 tocsection-4"><a href="#Creating_And_Connecting_Synthesis_Modules"><span class="tocnumber">1.1.2</span> <span class="toctext">Creating And Connecting Synthesis Modules</span></a></li>
+<li class="toclevel-3 tocsection-5"><a href="#Starting_And_Stopping_Playback"><span class="tocnumber">1.1.3</span> <span class="toctext">Starting And Stopping Playback</span></a></li>
+</ul>
+</li>
+<li class="toclevel-2 tocsection-6"><a href="#Setting_Up_Songs"><span class="tocnumber">1.2</span> <span class="toctext">Setting Up Songs</span></a>
+<ul>
+<li class="toclevel-3 tocsection-7"><a href="#What_Is_A_Synthesis_Instrument.3F"><span class="tocnumber">1.2.1</span> <span class="toctext">What Is A Synthesis Instrument?</span></a></li>
+<li class="toclevel-3 tocsection-8"><a href="#Creating_A_Synthesis_Instrument"><span class="tocnumber">1.2.2</span> <span class="toctext">Creating A Synthesis Instrument</span></a></li>
+<li class="toclevel-3 tocsection-9"><a href="#Setting_Up_Parts_And_Tracks"><span class="tocnumber">1.2.3</span> <span class="toctext">Setting Up Parts And Tracks</span></a></li>
+<li class="toclevel-3 tocsection-10"><a href="#Postprocessing_Tracks_and_Songs"><span class="tocnumber">1.2.4</span> <span class="toctext">Postprocessing Tracks and Songs</span></a></li>
+</ul>
+</li>
+</ul>
+</li>
+</ul>
+</td></tr></table>
+<h1> <span class="mw-headline" id="BEAST.2FBSE_Quickstart_Guide"> BEAST/BSE Quickstart Guide </span></h1>
+<p>This guide attempts to give a few brief hints for new users, in order to get started with the most basic tasks that can be accomplished with <a href="http://testbit.eu/Beast"; title="Beast">Beast</a>.
+</p>
+<h2> <span class="mw-headline" id="First_Start_At_Synthesis"> First Start At Synthesis </span></h2>
+<p>The most basic task <a href="http://testbit.eu/Beast"; title="Beast">Beast</a> is able to accomplish is the creation of new musical sounds which is done by using a variety of music producers, called âModulesâ. Forming a network of multiple modules to create a new sound is most generally being refered to as âSynthesisâ.
+</p>
+<h3> <span class="mw-headline" id="Creating_A_Synthesizer_Network"> Creating A Synthesizer Network </span></h3>
+<ol><li> Select ``/Project/Add Custom Synthesizer`` from the menu to create a new network.
+</li><li> In the newly created synthesizer network <code>Unnamed</code>, on the notebook page <b>Properties</b>, enable the <b>Auto Activate</b> property to enable automated playback of this network.
+</li><li> Select the <b>Routing</b> notebook page.
+</li></ol>
+<h3> <span class="mw-headline" id="Creating_And_Connecting_Synthesis_Modules"> Creating And Connecting Synthesis Modules </span></h3>
+<p>The synthesis network routing editor allowes for creation of synthesis modules, establishing connections between module inputs and outputs, and for adjustment of a module's parameter set.
+</p><p>Here's how to setup a very simple test case:
+</p>
+<ol><li> Create two modules by selecting them from either the pallete window or from the Button-3 popup menu of the <b>Routing</b> notebook page and then clicking into the routing area. The two modules you need are <a href="http://testbit.eu/index.php?title=BsePcmOutput&action=edit&redlink=1"; class="new" title="BsePcmOutput (page does not exist)">BsePcmOutput</a> and <a href="http://testbit.eu/index.php?title=BseStandardOsc&action=edit&redlink=1"; class="new" title="BseStandardOsc (page does not exist)">BseStandardOsc</a>.
+</li><li> Connect the <b>Audio Out</b> output channel of the oscillator to the input channels <b>Left Audio In</b> and <b>Right Audio In</b> of the output module.
+</li></ol>
+<h3> <span class="mw-headline" id="Starting_And_Stopping_Playback"> Starting And Stopping Playback </span></h3>
+<p>Playback of a <a href="http://testbit.eu/Beast"; title="Beast">Beast</a> project can be started or restarted by selecting the menu item ``/Project/Play``. Similarly, playback is halted by selecting ``/Project/Stop``.
+</p>
+<h2> <span class="mw-headline" id="Setting_Up_Songs"> Setting Up Songs </span></h2>
+<p>To be able to playback songs with <a href="http://testbit.eu/Beast"; title="Beast">Beast</a>, synthesis instruments have to be created which are used to playback the notes contained in the parts of a song. Songs are created through the menu by selecting ``/Project/New Song``.
+</p>
+<h3> <span class="mw-headline" id="What_Is_A_Synthesis_Instrument.3F"> What Is A Synthesis Instrument? </span></h3>
+<p>A synthesis instrument is a special kind of synthesizer network, it has particular properties:
+</p>
+<ul><li> A synthesis instrument doesn't need to have its <b>Auto Activate</b> property enabled. That's because the song using the instrument will take care of activating it when neccessary.
+</li><li> A dedicated module type is used as input to the synthesis instrument so information about the note to be played can be fed into it.
+</li><li> A dedicated module type is used as output of the synthesis instrument to jointly compose the sound output together with other synthesis instruments being used.
+</li></ul>
+<h3> <span class="mw-headline" id="Creating_A_Synthesis_Instrument"> Creating A Synthesis Instrument </span></h3>
+<p>Here is how to create a simple synthesis instrument with one oscillator producing the basic tone, an envelope to control a note's volume, and an amplifier to adjust overall volume and apply the envelope to the oscillator.
+</p>
+<ol><li> Select ``/Project/New Custom Synthesizer`` from the menu.
+</li><li> Switch to the networks's <b>Routing</b> notebook page.
+</li><li> Create an <a href="http://testbit.eu/index.php?title=BSeInstrumentInput&action=edit&redlink=1"; class="new" title="BSeInstrumentInput (page does not exist)">BSeInstrumentInput</a> and an <a href="http://testbit.eu/index.php?title=BseInstrumentOutput&action=edit&redlink=1"; class="new" title="BseInstrumentOutput (page does not exist)">BseInstrumentOutput</a> module.
+</li><li> Create the three modules making up the actual instrument: a <a href="http://testbit.eu/index.php?title=BseStandardOsc&action=edit&redlink=1"; class="new" title="BseStandardOsc (page does not exist)">BseStandardOsc</a>, a <a href="http://testbit.eu/index.php?title=BseSimpleADSR&action=edit&redlink=1"; class="new" title="BseSimpleADSR (page does not exist)">BseSimpleADSR</a> (the envelope) and an <a href="http://testbit.eu/index.php?title=BseAmplifier&action=edit&redlink=1"; class="new" title="BseAmplifier (page does not exist)">BseAmplifier</a>.
+</li><li> To control the oscillating frequency, and to trigger the oscillator wave at note start, connect the output channels <b>Frequency</b> and <b>Gate</b> of the <a href="http://testbit.eu/index.php?title=BseInstrumentInput&action=edit&redlink=1"; class="new" title="BseInstrumentInput (page does not exist)">BseInstrumentInput</a> module to the input channels <b>Freq In</b> and <b>Sync In</b> of the <a href="http://testbit.eu/index.php?title=BseStandardOsc&action=edit&redlink=1"; class="new" title="BseStandardOsc (page does not exist)">BseStandardOsc</a> module respectively.
+</li><li> To let the <a href="http://testbit.eu/index.php?title=BseAmplifier&action=edit&redlink=1"; class="new" title="BseAmplifier (page does not exist)">BseAmplifier</a> shape the volume of the oscillating tone and to provide actual output, connect the output channel <b>Audio Out</b> of the <a href="http://testbit.eu/index.php?title=BseStandardOsc&action=edit&redlink=1"; class="new" title="BseStandardOsc (page does not exist)">BseStandardOsc</a> to one of the <b>Audio</b> input channels of the <a href="http://testbit.eu/index.php?title=BseAmplifier&action=edit&redlink=1"; class="new" title="BseAmplifier (page does not exist)">BseAmplifier</a> and connect the <a href="http://testbit.eu/index.php?title=BseAmplifier&action=edit&redlink=1"; class="new" title="BseAmplifier (page does not exist)">BseAmplifier</a>'s output channel <b>Audio Out</b> to the two input channels <b>Right Audio</b> and <b>Left Audio</b> of the <a href="http://testbit.eu/inde
x.php?title=BseInstrumentOutput&action=edit&redlink=1" class="new" title="BseInstrumentOutput (page does not exist)">BseInstrumentOutput</a>.
+</li><li> It is recommended to intially reduce the <b>Master Volume</b> property of the <a href="http://testbit.eu/index.php?title=BseAmplifier&action=edit&redlink=1"; class="new" title="BseAmplifier (page does not exist)">BseAmplifier</a> to avoid overdriving the output later on. The properties of a module can be adjusted in it's property dialog which is offered by the Button-3 popup menu of each module.
+</li><li> Connect the input channel <b>Gate In</b> of the <a href="http://testbit.eu/index.php?title=BseSimpleADSR&action=edit&redlink=1"; class="new" title="BseSimpleADSR (page does not exist)">BseSimpleADSR</a> to the output channel <b>Gate</b> of the <a href="http://testbit.eu/index.php?title=BseInstrumentInput&action=edit&redlink=1"; class="new" title="BseInstrumentInput (page does not exist)">BseInstrumentInput</a> to trigger the envelope at note start. Connect the <b>Ctrl Out</b> output channel of the <a href="http://testbit.eu/index.php?title=BseSimpleADSR&action=edit&redlink=1"; class="new" title="BseSimpleADSR (page does not exist)">BseSimpleADSR</a> to one of the <b>Control</b> input channels of the <a href="http://testbit.eu/index.php?title=BseAmplifier&action=edit&redlink=1"; class="new" title="BseAmplifier (page does not exist)">BseAmplifier</a>.
+</li><li> <b>IMPORTANT:</b> Synthesis instruments are used to play multiple notes sequentially. In order to determine when an instrument has finished playing a certain note and is thusly free to play a new note, the <b>Synth Done</b> channel of the <a href="http://testbit.eu/index.php?title=BseInstrumentOutput&action=edit&redlink=1"; class="new" title="BseInstrumentOutput (page does not exist)">BseInstrumentOutput</a> must be connected to a signal going high at note end. For this example, connect the <b>Synth Done</b> channel to the <b>Done Out</b> output channel of the <a href="http://testbit.eu/index.php?title=BseSimpleADSR&action=edit&redlink=1"; class="new" title="BseSimpleADSR (page does not exist)">BseSimpleADSR</a> module, this output channel produces a signal which is low while the envelope is active and goes high past the envelope end.
+</li></ol>
+<p>While the synthesis instrument is ready for use now, it can't be used or tested directly, but has to be deployed in a song or [BseMidiSynth]] (offered by the main menu under ``/Project/New MIDI Synthesizer``) which leads us to the next Topic.
+</p>
+<h3> <span class="mw-headline" id="Setting_Up_Parts_And_Tracks"> Setting Up Parts And Tracks </span></h3>
+<p>Songs basically consist of notes kept in âPartsâ which are arranged in âTracksâ. The tracks control the order in which parts are played and what instrument is used to play a certain part. So the steps to a simple test setup for a synthesis instrument are:
+</p>
+<ol><li> Switch to the <b>Tracks</b> notebook page of a song and add a track to the song.
+</li><li> Click into the track's tact area to create a new part within it.
+</li><li> Click onto the newly created part to start up a piano roll editor to arrange notes within parts.
+</li><li> Use the piano roll editor to create some notes in the part to be played back.
+</li><li> Select a synthesis network (created as shown in the last section) as synthesis input for this track by editing the <b>Synth</b> property.
+</li></ol>
+<p>A song with parts, instruments and tracks setup can be played back via the main menu by selecting the menu item ``/Project/Play``.
+</p>
+<h3> <span class="mw-headline" id="Postprocessing_Tracks_and_Songs"> Postprocessing Tracks and Songs </span></h3>
+<p>The sound generated by the tracks of a song and the song itself can be postprocessed by synthesis networks to add effects and adjust the sound to your needs. Postprocessing networks are created as follows:
+</p>
+<ol><li> Select ``/Project/New Custom Synthesizer`` from the menu to create a new network.
+</li><li> Add a virtual input and output, i.e. a <a href="http://testbit.eu/index.php?title=BseSubIPort&action=edit&redlink=1"; class="new" title="BseSubIPort (page does not exist)">BseSubIPort</a> and a <a href="http://testbit.eu/index.php?title=BseSubOPort&action=edit&redlink=1"; class="new" title="BseSubOPort (page does not exist)">BseSubOPort</a> module, to the network.
+</li><li> Connect the first two input and output channels between the two modules, these carry the left and right channel sound of a track respectively, so the sound signals may pass through the postprocessing network.
+</li><li> Alternatively, rather than simply connecting the inputs to the outputs, you may use an effect such as the free reverb module <a href="http://testbit.eu/index.php?title=BseFreeVerb&action=edit&redlink=1"; class="new" title="BseFreeVerb (page does not exist)">BseFreeVerb</a> inbetween the input and output connections.
+</li></ol>
+<p>To postprocess the sound of a single track in a song, select the synthesis network as postprocessing network for the track by editing the tracks âPostâ property. To apply the network to a song, select it as postprocessing network for the song by editing the songs âCustom Postprocess Netâ property.
+</p>
+<!--
+NewPP limit report
+Preprocessor node count: 38/1000000
+Post-expand include size: 0/2097152 bytes
+Template argument size: 0/2097152 bytes
+Expensive parser function count: 0/100
+-->
+<!-- Saved in parser cache with key mediawikidb:pcache:idhash:19-1!*!0!!en!*!* and timestamp 20121025003655 -->
diff --git a/docs/import/Beast_FAQ b/docs/import/Beast_FAQ
new file mode 100644
index 0000000..a6902c8
--- /dev/null
+++ b/docs/import/Beast_FAQ
@@ -0,0 +1,119 @@
+<table id="toc" class="toc"><tr><td><div id="toctitle"><h2>Contents</h2></div>
+<ul>
+<li class="toclevel-1 tocsection-1"><a href="#Introduction"><span class="tocnumber">1</span> <span class="toctext">Introduction</span></a>
+<ul>
+<li class="toclevel-2 tocsection-2"><a href="#Authors"><span class="tocnumber">1.1</span> <span class="toctext">Authors</span></a></li>
+<li class="toclevel-2 tocsection-3"><a href="#Document_History"><span class="tocnumber">1.2</span> <span class="toctext">Document History</span></a></li>
+<li class="toclevel-2 tocsection-4"><a href="#Contact_Information_and_Resources"><span class="tocnumber">1.3</span> <span class="toctext">Contact Information and Resources</span></a></li>
+</ul>
+</li>
+<li class="toclevel-1 tocsection-5"><a href="#Questions_.26_Answers"><span class="tocnumber">2</span> <span class="toctext">Questions & Answers</span></a>
+<ul>
+<li class="toclevel-2 tocsection-6"><a href="#Why_do_I_get_.22Cannot_access_memory_at_address_0x706f6e6d.22_when_running_BEAST_in_gdb.3F"><span class="tocnumber">2.1</span> <span class="toctext">Why do I get "Cannot access memory at address 0x706f6e6d" when running <i>BEAST</i> in gdb?</span></a></li>
+<li class="toclevel-2 tocsection-7"><a href="#Why_doesn.27t_my_synthesis_network_produce_any_sound.3F"><span class="tocnumber">2.2</span> <span class="toctext">Why doesn't my synthesis network produce any sound?</span></a></li>
+<li class="toclevel-2 tocsection-8"><a href="#Why_can.27t_I_get_the_synthesis_networks_to_work.3F"><span class="tocnumber">2.3</span> <span class="toctext">Why can't I get the synthesis networks to work?</span></a></li>
+<li class="toclevel-2 tocsection-9"><a href="#Why_do_I_see_BEAST-WARNING_.2A.2A:_strange.2C_can.27t_find_any_plugins.2C_please_check_....2Fplugins_on_startup.3F"><span class="tocnumber">2.4</span> <span class="toctext">Why do I see BEAST-WARNING **: strange, can't find any plugins, please check .../plugins on startup?</span></a></li>
+<li class="toclevel-2 tocsection-10"><a href="#Why_can.27t_I_get_BEAST_to_load_my_.mp3.2C_.aiff.2C_.something_sample_files.3F"><span class="tocnumber">2.5</span> <span class="toctext">Why can't I get <i>BEAST</i> to load my .mp3, .aiff, .something sample files?</span></a></li>
+<li class="toclevel-2 tocsection-11"><a href="#Why_does_BEAST_sometimes_crash_with_a_segmentation_fault_on_startup.3F"><span class="tocnumber">2.6</span> <span class="toctext">Why does <i>BEAST</i> sometimes crash with a segmentation fault on startup?</span></a></li>
+<li class="toclevel-2 tocsection-12"><a href="#Why_doesn.27t_BEAST_0.4.0_play_songs_from_earlier_versions.3F"><span class="tocnumber">2.7</span> <span class="toctext">Why doesn't <i>BEAST</i> 0.4.0 play songs from earlier versions?</span></a></li>
+<li class="toclevel-2 tocsection-13"><a href="#What_is_a_.bse_file.3F"><span class="tocnumber">2.8</span> <span class="toctext">What is a .bse file?</span></a></li>
+<li class="toclevel-2 tocsection-14"><a href="#What_are_the_minimum_hardware_requirements_for_BEAST.3F"><span class="tocnumber">2.9</span> <span class="toctext">What are the minimum hardware requirements for <i>BEAST</i>?</span></a></li>
+<li class="toclevel-2 tocsection-15"><a href="#BEAST_crashes_upon_creation_of_new_synthesis_networks.3F"><span class="tocnumber">2.10</span> <span class="toctext"><i>BEAST</i> crashes upon creation of new synthesis networks?</span></a></li>
+<li class="toclevel-2 tocsection-16"><a href="#How_do_i_get_MIDI_to_work.3F"><span class="tocnumber">2.11</span> <span class="toctext">How do i get MIDI to work?</span></a></li>
+<li class="toclevel-2 tocsection-17"><a href="#GCC.2FG.2B.2B_crashes_or_leaks_or_hangs_when_compiling_BEAST"><span class="tocnumber">2.12</span> <span class="toctext">GCC/G++ crashes or leaks or hangs when compiling <i>BEAST</i></span></a></li>
+<li class="toclevel-2 tocsection-18"><a href="#Unwanted_signal_distortion_when_using_multiple_tracks"><span class="tocnumber">2.13</span> <span class="toctext">Unwanted signal distortion when using multiple tracks</span></a></li>
+<li class="toclevel-2 tocsection-19"><a href="#What_platforms_are_supported.3F"><span class="tocnumber">2.14</span> <span class="toctext">What platforms are supported?</span></a></li>
+<li class="toclevel-2 tocsection-20"><a href="#Why_does_nothing_happen_on_Play.3F"><span class="tocnumber">2.15</span> <span class="toctext">Why does nothing happen on <i>Play</i>?</span></a></li>
+</ul>
+</li>
+</ul>
+</td></tr></table>
+<h1> <span class="mw-headline" id="Introduction"> Introduction</span></h1>
+<h2> <span class="mw-headline" id="Authors"> Authors </span></h2>
+<p>The main author of <i>BEAST/BSE</i> is Tim Janik. A list of the various contributions is given in the About box of <i>BEAST</i>.
+</p><p><br/>
+</p>
+<h2> <span class="mw-headline" id="Document_History"> Document History </span></h2>
+<p>This FAQ was written by <a rel="nofollow" class="external text" href="mailto://timj beast gtk org">Tim Janik</a>. Initial markup was done by Dave Seidel, until <a rel="nofollow" class="external text" href="mailto://dirt gtk org">Alper Ersoy</a> implemented a new markup parser for <i>BEAST</i> documentation. Around the 0.4.1 release, the docs got migrated to texinfo format. After the 0.6.6 release, the documentation system was rewritten, so all docs inclusing the FAQ got migrated to doxer format. In 2011 the FAQ got incorporated into the Beast wiki.
+</p><p><br/>
+</p>
+<h2> <span class="mw-headline" id="Contact_Information_and_Resources"> Contact Information and Resources </span></h2>
+<ul><li> WWW: <a rel="nofollow" class="external free" href="http://beast.testbit.eu";>http://beast.testbit.eu</a>
+</li><li> Mailing List: <a rel="nofollow" class="external free" href="http://mail.gnome.org/mailman/listinfo/beast/";>http://mail.gnome.org/mailman/listinfo/beast/</a>.
+</li></ul>
+<h1> <span class="mw-headline" id="Questions_.26_Answers"> Questions & Answers</span></h1>
+<h2> <span class="mw-headline" id="Why_do_I_get_.22Cannot_access_memory_at_address_0x706f6e6d.22_when_running_BEAST_in_gdb.3F"> Why do I get "Cannot access memory at address 0x706f6e6d" when running <i>BEAST</i> in gdb? </span></h2>
+<p>Some versions of gdb have problems figuring dynamic plugins, we can only hope that this is going to be fixed some time soon. Newer versions of gdb may already figure what's going on with the plugins if you simply restart <i>BEAST</i> within gdb.
+</p><p><b>UPDATE:</b> This problem has not been reproduced with gdb versions newer than 5.
+</p>
+<h2> <span class="mw-headline" id="Why_doesn.27t_my_synthesis_network_produce_any_sound.3F"> Why doesn't my synthesis network produce any sound? </span></h2>
+<p>There are various possible causes for this. First, make sure you have <i>BEAST</i> correctly installed and accessing your sound card by running one of the synthesis tests in the ./test/ subdirectory. For custom synthesis networks, make sure you have something noisy (e.g. the audio output of an oscillator) hooked up to a PcmOutput module, and have the network's "Auto Activate" parameter (on it's "Parameters" notebook page, section "Playback Settings") enabled.
+</p>
+<h2> <span class="mw-headline" id="Why_can.27t_I_get_the_synthesis_networks_to_work.3F"> Why can't I get the synthesis networks to work? </span></h2>
+<p>This is probably a plugin loading problem, most synthesis networks require plugins and won't work if there are any problems loading/finding them. <i>BEAST</i> loads its plugins from some common installation directory. It therefore needs to be properly installed before you can make use of its plugins. Simply starting it from within the build directory is not sufficient.
+</p>
+<h2> <span class="mw-headline" id="Why_do_I_see_BEAST-WARNING_.2A.2A:_strange.2C_can.27t_find_any_plugins.2C_please_check_....2Fplugins_on_startup.3F"> Why do I see <tt>BEAST-WARNING **: strange, can't find any plugins, please check .../plugins</tt> on startup? </span></h2>
+<p>See previous question.
+</p>
+<h2> <span class="mw-headline" id="Why_can.27t_I_get_BEAST_to_load_my_.mp3.2C_.aiff.2C_.something_sample_files.3F"> Why can't I get <i>BEAST</i> to load my .mp3, .aiff, .something sample files? </span></h2>
+<p>Import functionality for foreign sample types is always being worked on, but due to the sheer multitude of formats out there chances are that a specific format is not yet supported. However, sample file loaders have much improved in the last versions, and at this point exist for Ogg/Vorbis, MPEG Audio 1.0/2.0/2.5 Layer I/II/III, RIFF/WAVE, and .bsewave (<i>BSE</i> multi sample format) files.
+</p>
+<h2> <span class="mw-headline" id="Why_does_BEAST_sometimes_crash_with_a_segmentation_fault_on_startup.3F"> Why does <i>BEAST</i> sometimes crash with a segmentation fault on startup? </span></h2>
+<p>This was due to a bug in the X Keyboard extension. <i>BEAST</i> tries to figure the country specifics of the keyboard layout, using the XKB extension. Apparently, there are some allocation problems in XkbFreeKeyboard() or XkbFreeClientMap() in libX11, which can cause random crashes. Usually <i>BEAST</i> will run fine when restarted.
+</p><p><b>UPDATE:</b> Recent versions of XKB seem to have fixed this problem.
+</p>
+<h2> <span class="mw-headline" id="Why_doesn.27t_BEAST_0.4.0_play_songs_from_earlier_versions.3F"> Why doesn't <i>BEAST</i> 0.4.0 play songs from earlier versions? </span></h2>
+<p>The song support was completely rewritten for this version. If lots of compatiblity problem reports occur, a converter might be implemented at some point.
+</p>
+<h2> <span class="mw-headline" id="What_is_a_.bse_file.3F"> What is a <tt>.bse</tt> file? </span></h2>
+<p><i>BEAST</i> stores saved data in <i>BSE</i> files. These files can hold everything associated with a project, such as the definition of synthesis networks, songs with their notes and tracks, and even complete music sample files. Except for raw sample data, the contents are stored in a human readable text form using lisp syntax. The textual file contents may even be manually edited, as long as the binary appendix used to store wave data doesn't get corrupted.
+The recommended mime type image for <i>BSE</i> files looks like this: <a href="http://testbit.eu/index.php?title=Special:Upload&wpDestFile=Bse-mime"; class="new" title="File:Bse-mime">,,BSE-Mime-Logo,png</a>
+</p>
+<h2> <span class="mw-headline" id="What_are_the_minimum_hardware_requirements_for_BEAST.3F"> What are the minimum hardware requirements for <i>BEAST</i>? </span></h2>
+<p>This depends a lot on how you utilise <i>BEAST</i>. If you simply want to create synthesis networks or very simple songs, any Pentium II ought to suffice. If you want to lay down a few tracks with effects you may need something more modern like a CPU with 1 GHz or higher core frequency.
+</p>
+<h2> <span class="mw-headline" id="BEAST_crashes_upon_creation_of_new_synthesis_networks.3F"> <i>BEAST</i> crashes upon creation of new synthesis networks? </span></h2>
+<p><i>BEAST</i> uses the <a rel="nofollow" class="external text" href="ftp://ftp.gnome.org/pub/GNOME/sources/libgnomecanvas/";>GnomeCanvas Library</a> to display synthesis networks. That library has a malicious redrawing bug in versions up to (including) 2.2.0.1 triggering an assertion if the code is compiled with debugging output, which looks like this <a rel="nofollow" class="external text" href="http://developer.gnome.org/doc/API/2.0/libgnomecanvas/GnomeCanvas.html#GnomeCanvas";>GnomeCanvas</a> error:
+<code>
+GnomeCanvas-ERROR **: file gnome-canvas.c: line 3509 (gnome_canvas_request_update_real): assertion failed: (canvas->idle_id != 0)
+aborting...
+</code>
+This issue got fixed with version 2.2.0.2, so users encountering crashes with <i>BEAST</i> upon creation of synthesis networks will need to upgrade their <a rel="nofollow" class="external text" href="http://developer.gnome.org/doc/API/2.0/libgnomecanvas/GnomeCanvas.html#GnomeCanvas";>GnomeCanvas</a> Library to at least 2.2.0.2.
+</p>
+<h2> <span class="mw-headline" id="How_do_i_get_MIDI_to_work.3F"> How do i get MIDI to work? </span></h2>
+<p><i>BEAST</i> comes with a <i><tt>test/midi-test.bse</tt></i> file in the <i><tt>test/</tt></i> directory of recent releases, it works out of the box with properly setup MIDI drivers and MIDI pianos. Setting up MIDI drivers can be a tough task on its own but is beyond the scope of this FAQ and is already taken care of by <a rel="nofollow" class="external text" href="http://www.midi-howto.com/";>The Linux MIDI-HOWTO</a>, which provides good descriptions and further links to related documentation.
+</p>
+<h2> <span class="mw-headline" id="GCC.2FG.2B.2B_crashes_or_leaks_or_hangs_when_compiling_BEAST"> GCC/G++ crashes or leaks or hangs when compiling <i>BEAST</i></span></h2>
+<p>Recent versions of <i>BEAST</i> make use of C++ templates pretty heavily. This allowes us to greatly simplify some code portions (for instance the plugin implementations), but it's also a stress-test for the compilers out there. So people encountering problems compiling C++ code in <i>BEAST</i> should try to upgrade their compilers as a first meassure.
+</p>
+<h2> <span class="mw-headline" id="Unwanted_signal_distortion_when_using_multiple_tracks"> Unwanted signal distortion when using multiple tracks </span></h2>
+<p>The signal output of a song's tracks in <i>BEAST</i> are added up before they are routed to the sound output driver. If this added-up signal exceeds the maximum amplitude supported by the output driver (usually the machine's sound card), the output values are clipped to the supported range, causing the audio signal to encounter distortion of varying amounts, depending on the signal utilization of the channels. In the current version (0.6.2), the distortion can be circumvented by adding a post-processing network to songs which attenuates the incoming signals (left and right). The Quick Start Guide has a section detailing the setup of postprocessing networks. For future versions, a mixer is already in development, which will allow to handle this situation in much more flexible and adequate ways.
+</p>
+<h2> <span class="mw-headline" id="What_platforms_are_supported.3F"> What platforms are supported? </span></h2>
+<p>Beast is mainly developed under Linux and has been ported to some BSD versions. The <a href="http://testbit.eu/Beast_Download"; title="Beast Download"> Download page</a> of the Beast website links to the available packages and source code repositories for the various supported Linux and BSD variants.
+Some effort also went into a Windows port, more details about the state of which can be found on the <a href="http://testbit.eu/Beast_Windows_Port"; title="Beast Windows Port">Beast Windows Port</a> wiki page.
+Other operating systems are currently not supported, but the project is always taking patches and looks for new volounteers. So to start a new port, simply write your patch and contact the <a href="http://testbit.eu/Beast_Contact"; title="Beast Contact"> mailing list and developers</a>.
+</p>
+<h2> <span class="mw-headline" id="Why_does_nothing_happen_on_Play.3F"> Why does nothing happen on <i>Play</i>? </span></h2>
+<p>If correctly installed, <i>BEAST</i> should play the demo song from the Demo-menu out of the box, unless it cannot acquire a suitable PCM device. To debug PCM problem causes, the following can be used:
+</p>
+<pre> $ beast --bse-debug=pcm
+</pre>
+<p>This can produce message like the following:
+</p>
+<pre> beast-0.7.1[999]:BSE-ALSA:1: ALSA: opening PCM "hw:0,0" readable=1 writable=1: Device or resource busy
+</pre>
+<p>This is an indication that you have other audio programs (players or sound servers) which currently access your PCM device and block it for <i>BEAST</i>. Stopping or closing the other applications should free the audio device for use by <i>BEAST</i>.
+</p>
+<pre> beast-0.7.1[26493]:BSE-ALSA:1: ALSA: opening PCM "hw:0,0" readable=0 writable=1: Failed to configure device frequency
+</pre>
+<p>This one is a bit more tricky. Some ALSA drivers only allow very specific playback rates to be used by audio applications. <i>BEAST</i> uses the playback rate specified in the user preferences which comes with plausible defaults upon installation. If you see this message, try to adjust the "Synth Mixing Frequency" on the "BSE" page of the Edit/Preferences dialog.
+</p>
+<!--
+NewPP limit report
+Preprocessor node count: 90/1000000
+Post-expand include size: 0/2097152 bytes
+Template argument size: 0/2097152 bytes
+Expensive parser function count: 0/100
+-->
+<!-- Saved in parser cache with key mediawikidb:pcache:idhash:49-1!*!0!!en!2!* and timestamp 20121025003655 -->
diff --git a/docs/import/beast.1 b/docs/import/beast.1
new file mode 100644
index 0000000..4abd7ea
--- /dev/null
+++ b/docs/import/beast.1
@@ -0,0 +1,117 @@
+<table id="toc" class="toc"><tr><td><div id="toctitle"><h2>Contents</h2></div>
+<ul>
+<li class="toclevel-1 tocsection-1"><a href="#BEAST.281.29_-_Better_Audio_System"><span class="tocnumber">1</span> <span class="toctext">BEAST(1) - Better Audio System</span></a>
+<ul>
+<li class="toclevel-2 tocsection-2"><a href="#NAME"><span class="tocnumber">1.1</span> <span class="toctext">NAME</span></a></li>
+<li class="toclevel-2 tocsection-3"><a href="#SYNOPSIS"><span class="tocnumber">1.2</span> <span class="toctext">SYNOPSIS</span></a></li>
+<li class="toclevel-2 tocsection-4"><a href="#DESCRIPTION"><span class="tocnumber">1.3</span> <span class="toctext">DESCRIPTION</span></a></li>
+<li class="toclevel-2 tocsection-5"><a href="#OPTIONS"><span class="tocnumber">1.4</span> <span class="toctext">OPTIONS</span></a>
+<ul>
+<li class="toclevel-3 tocsection-6"><a href="#Development_Options:"><span class="tocnumber">1.4.1</span> <span class="toctext">Development Options:</span></a></li>
+<li class="toclevel-3 tocsection-7"><a href="#Gtk.2B_Options:"><span class="tocnumber">1.4.2</span> <span class="toctext">Gtk+ Options:</span></a></li>
+</ul>
+</li>
+<li class="toclevel-2 tocsection-8"><a href="#SEE_ALSO"><span class="tocnumber">1.5</span> <span class="toctext">SEE ALSO</span></a></li>
+</ul>
+</li>
+</ul>
+</td></tr></table>
+<h1> <span class="mw-headline" id="BEAST.281.29_-_Better_Audio_System"> BEAST(1) - Better Audio System </span></h1>
+<p>Manual: Testbit Wiki Pages <br/>
+Release: Revision 319 <br/>
+Updated: 2011-05-9 <br/>
+</p>
+<h2> <span class="mw-headline" id="NAME"> NAME </span></h2>
+<p>beast - Music composition and modular synthesis application.
+</p>
+<h2> <span class="mw-headline" id="SYNOPSIS"> SYNOPSIS </span></h2>
+<p><b>beast</b> [<i>OPTIONS</i>] [<i>FILES...</i>]
+</p>
+<h2> <span class="mw-headline" id="DESCRIPTION"> DESCRIPTION </span></h2>
+<p><b>beast</b> is the <b>BE</b>tter <b>A</b>udio <b>S</b>ys<b>T</b>em. It is a music composition and
+modular synthesis application released as free software under the GNU LGPL.
+</p><p><b>beast</b> comes with various synthesis modules which can be arranged in
+networks for modular synthesis. It is capable of monophonic and polyphonic
+voice processing, provides MIDI sequencer functionality and supports
+external sequencer sources. A huge set of extra modules is available through
+the support for LADSPA (Linux Audio Developer's Simple Plugin API) plugins.
+</p><p><b>beast'</b>s underlying sound engine <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> also comes with a scheme scripting
+extension which allows for advanced non-interactive processing via
+<a href="http://testbit.eu/Bsescm.1"; title="Bsescm.1">bsescm.1</a> and creation of additional GUI functionality for <b>beast</b>.
+</p>
+<h2> <span class="mw-headline" id="OPTIONS"> OPTIONS </span></h2>
+<p><b>beast</b> follows the usual GNU command line syntax, with long options starting with two dashes ('-').
+</p>
+<dl><dt> <b>--skinrc</b> <i>FILENAME</i>
+</dt><dd> Read skin resources from <i>FILENAME</i>.
+</dd><dt> <b>--print-dir</b> <i>RESOURCE</i>
+</dt><dd> Print the directory for a specific resource (e.g. 'plugins' or 'images'). Giving just <b>--print-dir</b> without an extra argument causes <b>beast</b> to print the list of available resources.
+</dd><dt> <b>--merge</b>
+</dt><dd> Causes the following files to be merged into the previous or first project.
+</dd><dt> <b>--devel</b>
+</dt><dd> Enrich the GUI with hints useful for (script) developers
+</dd><dt> <b>-h</b>, <b>--help</b>
+</dt><dd> Shows a brief help message.
+</dd><dt> <b>-v</b>, <b>--version</b>
+</dt><dd> Prints out <b>beast</b> and component versions and file paths.
+</dd><dt> <b>-n</b> <i>NICELEVEL</i>
+</dt><dd> Execute with priority <i>NICELEVEL</i>, this option only takes effect for the root suid wrapper 'beast'.
+</dd><dt> <b>-N</b>
+</dt><dd> Disables renicing to execute with existing priority.
+</dd><dt> <b>--display</b> <i>DISPLAY</i>
+</dt><dd> X server display for the GUI; see <a rel="nofollow" class="external text" href="http://www.xfree86.org/current/X.7.html";>X(7)</a>.
+</dd><dt> <b>--bse-latency</b> <i>USECONDS</i>
+</dt><dd> Set the allowed synthesis latency for <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> in milliseconds.
+</dd><dt> <b>--bse-mixing-freq</b> <i>FREQUENCY</i>
+</dt><dd> Set the desired synthesis mixing frequency in Hz.
+</dd><dt> <b>--bse-control-freq</b> <i>FREQUENCY</i>
+</dt><dd> Set the desired control frequency in Hz, this should be much smaller than the synthesis mixing frequency to reduce CPU load. The default value of approximately 1000 Hz is usually a good choice.
+</dd><dt> <b>--bse-pcm-driver</b> <i>DRIVER-CONF</i>
+</dt><dt> <b>-p</b> <i>DRIVER-CONF</i>
+</dt><dd> This options results in an attempt to open the PCM driver <i>DRIVER-CONF</i> when playback is started. Multiple options may be supplied to try a variety of drivers and unless <i>DRIVER-CONF</i> is specified as 'auto', only the drivers listed by options are used. Each <i>DRIVER-CONF</i> consists of a driver name and an optional comma seperated list of arguments attached to the driver withan equal sign, e.g.: <b>-p oss=/dev/dsp2,rw -p auto</b>
+</dd><dt> <b>--bse-midi-driver</b> <i>DRIVER-CONF</i>
+</dt><dt> <b>-m</b> <i>DRIVER-CONF</i>
+</dt><dd> This option is similar to the <b>--bse-pcm-driver</b> option, but applies to MIDI drivers and devices. It also may be specified multiple times and features an 'auto' driver.
+</dd><dt> <b>--bse-driver-list</b>
+</dt><dd> Produce a list of all available PCM and MIDI drivers and available devices.
+</dd><dt> <b>--</b>
+</dt><dd> Stop argument processing, interpret all remaining arguments as file names.
+</dd></dl>
+<h3> <span class="mw-headline" id="Development_Options:"> Development Options: </span></h3>
+<dl><dt> <b>--debug</b> <i>KEYS</i>
+</dt><dd> Enable certain verbosity stages.
+</dd><dt> <b>--debug-list</b>
+</dt><dd> List possible debug keys.
+</dd><dt> <b>-:</b>[<i>flags</i>]
+</dt><dd> This option enables or disables various debugging specific flags for beast core developers. Use of <b>-:</b> is not recommended, because the supported flags may change between versions and cause possibly harmful misbehaviour.
+</dd></dl>
+<h3> <span class="mw-headline" id="Gtk.2B_Options:"> Gtk+ Options: </span></h3>
+<dl><dt> <b>--gtk-debug</b> <i>FLAGS</i>
+</dt><dd> Gtk+ debugging flags to enable.
+</dd><dt> <b>--gtk-no-debug</b> <i>FLAGS</i>
+</dt><dd> Gtk+ debugging flags to disable.
+</dd><dt> <b>--gtk-module</b> <i>MODULE</i>
+</dt><dd> Load additional Gtk+ modules.
+</dd><dt> <b>--gdk-debug</b> <i>FLAGS</i>
+</dt><dd> Gdk debugging flags to enable.
+</dd><dt> <b>--gdk-no-debug</b> <i>FLAGS</i>
+</dt><dd> Gdk debugging flags to disable.
+</dd><dt> <b>--g-fatal-warnings</b>
+</dt><dd> Make warnings fatal (abort).
+</dd><dt> <b>--sync</b>
+</dt><dd> Do all X calls synchronously.
+</dd></dl>
+<h2> <span class="mw-headline" id="SEE_ALSO"> SEE ALSO </span></h2>
+<p><a href="http://testbit.eu/Bsescm.1"; title="Bsescm.1">bsescm.1</a>,
+<a href="http://testbit.eu/Bse.5"; title="Bse.5">bse.5</a>,
+<a href="http://testbit.eu/Sfidl.1"; title="Sfidl.1">sfidl.1</a>,
+<a rel="nofollow" class="external text" href="http://beast.gtk.org";>BEAST/BSE Website</a>
+</p>
+<!--
+NewPP limit report
+Preprocessor node count: 50/1000000
+Post-expand include size: 15/2097152 bytes
+Template argument size: 0/2097152 bytes
+Expensive parser function count: 0/100
+-->
+<!-- Saved in parser cache with key mediawikidb:pcache:idhash:61-1!*!0!!en!*!* and timestamp 20121024212153 -->
diff --git a/docs/import/bse.5 b/docs/import/bse.5
new file mode 100644
index 0000000..208261f
--- /dev/null
+++ b/docs/import/bse.5
@@ -0,0 +1,60 @@
+<table id="toc" class="toc"><tr><td><div id="toctitle"><h2>Contents</h2></div>
+<ul>
+<li class="toclevel-1 tocsection-1"><a href="#BSE.285.29_-_Better_Sound_Engine_File_Format"><span class="tocnumber">1</span> <span class="toctext">BSE(5) - Better Sound Engine File Format</span></a>
+<ul>
+<li class="toclevel-2 tocsection-2"><a href="#NAME"><span class="tocnumber">1.1</span> <span class="toctext">NAME</span></a></li>
+<li class="toclevel-2 tocsection-3"><a href="#SYNOPSIS"><span class="tocnumber">1.2</span> <span class="toctext">SYNOPSIS</span></a></li>
+<li class="toclevel-2 tocsection-4"><a href="#DESCRIPTION"><span class="tocnumber">1.3</span> <span class="toctext">DESCRIPTION</span></a></li>
+<li class="toclevel-2 tocsection-5"><a href="#FORMAT"><span class="tocnumber">1.4</span> <span class="toctext">FORMAT</span></a></li>
+<li class="toclevel-2 tocsection-6"><a href="#COMPATIBILITY"><span class="tocnumber">1.5</span> <span class="toctext">COMPATIBILITY</span></a></li>
+<li class="toclevel-2 tocsection-7"><a href="#SEE_ALSO"><span class="tocnumber">1.6</span> <span class="toctext">SEE ALSO</span></a></li>
+</ul>
+</li>
+</ul>
+</td></tr></table>
+<h1> <span class="mw-headline" id="BSE.285.29_-_Better_Sound_Engine_File_Format"> BSE(5) - Better Sound Engine File Format </span></h1>
+<p>Manual: Testbit Wiki Pages <br/>
+Release: Revision 175 <br/>
+Updated: 2011-01-25 <br/>
+</p>
+<h2> <span class="mw-headline" id="NAME"> NAME </span></h2>
+<p> BSE - Better Sound Engine File Format
+</p>
+<h2> <span class="mw-headline" id="SYNOPSIS"> SYNOPSIS </span></h2>
+<p> <i>filename</i><b>.bse</b>
+</p>
+<h2> <span class="mw-headline" id="DESCRIPTION"> DESCRIPTION </span></h2>
+<p> The <b>bse</b> file format is used by the <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">bse</a> library and dependent programs to save
+<a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">bse</a> projects, songs, instruments and sample collections.
+The <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">bse</a> scheme shell <a href="http://testbit.eu/Bsescm.1"; title="Bsescm.1">bsescm.1</a> is able to play back <b>bse</b> files directly.
+</p>
+<h2> <span class="mw-headline" id="FORMAT"> FORMAT </span></h2>
+<p> <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">bse</a> files start out with a special magic string "; BseProject\n" and then contain nested
+expressions in scheme syntax using the ASCII charset.
+Binary data may be appended to a <i>.bse</i> file if it is seperated from the preceeding
+ASCII test by one or more literal NUL characters ('\0').
+This mechanism is used to store arbitrary binary data like <i>.WAV</i> or Ogg/Vorbis files
+in <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">bse</a> projects, while keeping the actuall content user editable (text editors that preserve
+binary sections have to be used, such as vi(1) or emacs(1)).
+</p>
+<h2> <span class="mw-headline" id="COMPATIBILITY"> COMPATIBILITY </span></h2>
+<p> The exact format and sets of objects and properties used in a <b>bse</b> file depend highly
+on the library version that was used to save the file. Compatibility functions are supplied
+by the library itself, so old <b>bse</b> files can be converted when the file is loaded.
+To enable this mechanism, all <b>bse</b> files contain a <b>"bse-version"</b> directive which
+indicates the <b>bse</b> file format version of the supplied content.
+</p>
+<h2> <span class="mw-headline" id="SEE_ALSO"> SEE ALSO </span></h2>
+<p><a href="http://testbit.eu/Beast.1"; title="Beast.1">beast.1</a>,
+<a href="http://testbit.eu/Bsescm.1"; title="Bsescm.1">bsescm.1</a>,
+<a href="http://testbit.eu/Bsewavetool.1"; title="Bsewavetool.1">bsewavetool.1</a>,
+<a rel="nofollow" class="external text" href="http://beast.gtk.org/bse-objects";>BSE Object Reference</a>
+</p>
+<!--
+NewPP limit report
+Preprocessor node count: 46/1000000
+Post-expand include size: 15/2097152 bytes
+Template argument size: 0/2097152 bytes
+Expensive parser function count: 0/100
+-->
+<!-- Saved in parser cache with key mediawikidb:pcache:idhash:62-1!*!0!!en!*!* and timestamp 20121024165007 -->
diff --git a/docs/import/bsescm.1 b/docs/import/bsescm.1
new file mode 100644
index 0000000..cbc2260
--- /dev/null
+++ b/docs/import/bsescm.1
@@ -0,0 +1,121 @@
+<table id="toc" class="toc"><tr><td><div id="toctitle"><h2>Contents</h2></div>
+<ul>
+<li class="toclevel-1 tocsection-1"><a href="#bsescm.281.29_-_BSE_Scheme_Shell"><span class="tocnumber">1</span> <span class="toctext">bsescm(1) - BSE Scheme Shell</span></a>
+<ul>
+<li class="toclevel-2 tocsection-2"><a href="#NAME"><span class="tocnumber">1.1</span> <span class="toctext">NAME</span></a></li>
+<li class="toclevel-2 tocsection-3"><a href="#SYNOPSIS"><span class="tocnumber">1.2</span> <span class="toctext">SYNOPSIS</span></a></li>
+<li class="toclevel-2 tocsection-4"><a href="#DESCRIPTION"><span class="tocnumber">1.3</span> <span class="toctext">DESCRIPTION</span></a></li>
+<li class="toclevel-2 tocsection-5"><a href="#OPTIONS"><span class="tocnumber">1.4</span> <span class="toctext">OPTIONS</span></a>
+<ul>
+<li class="toclevel-3 tocsection-6"><a href="#Guile_Options:"><span class="tocnumber">1.4.1</span> <span class="toctext">Guile Options:</span></a></li>
+</ul>
+</li>
+<li class="toclevel-2 tocsection-7"><a href="#SEE_ALSO"><span class="tocnumber">1.5</span> <span class="toctext">SEE ALSO</span></a></li>
+</ul>
+</li>
+</ul>
+</td></tr></table>
+<h1> <span class="mw-headline" id="bsescm.281.29_-_BSE_Scheme_Shell"> bsescm(1) - BSE Scheme Shell </span></h1>
+<p>Manual: Testbit Wiki Pages <br/>
+Release: Revision 307 <br/>
+Updated: 2011-05-2 <br/>
+</p>
+<h2> <span class="mw-headline" id="NAME"> NAME </span></h2>
+<p>bsescm - A Guile based scheme shell for <a href="http://testbit.eu/Beast"; title="Beast">Beast</a> and <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a>.
+</p>
+<h2> <span class="mw-headline" id="SYNOPSIS"> SYNOPSIS </span></h2>
+<p><b>bsescm</b> [<i>options</i>] [<b>--</b>] <b>...</b>
+</p><p><b>bsescm</b> [<i>options</i>] <i><infile.bse></i> <b>...</b>
+</p>
+<h2> <span class="mw-headline" id="DESCRIPTION"> DESCRIPTION </span></h2>
+<p><b>bsescm</b> is a <i>Guile</i> based scheme shell for <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a>,
+the Better Sound Engine.
+</p><p><b>bsescm</b> provides a shell interface to all procedures exported by the
+<a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> library, so scripts are able to access the full range of functionality
+provided by it, from simple playback of a <i>.bse</i> file to
+full fledged automated creation or editing of synthesis networks.
+</p><p>Alternatively to the linked in <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> library, the <b>bsescm</b> language interface
+can also talk to a remotely running <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> library host, for instance
+<a href="http://testbit.eu/Beast"; title="Beast">Beast</a>.
+By operating on a remotely running <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> core, <b>bsescm</b> can be used to script
+arbitrary <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> programs. The shell is also used directly by the <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> library to
+execute procedures on its behalf, this allows <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> procedures to be written in scheme.
+</p><p>When started, <b>bsescm</b> tests whether the first non-option argument is a <i>.bse</i>
+file and if the test succeeds, attempts to play the command line arguments as
+<i>.bse</i> files.
+</p>
+<h2> <span class="mw-headline" id="OPTIONS"> OPTIONS </span></h2>
+<p><b>bsescm</b> follows the usual GNU command line syntax, with long options starting with two dashes ('--').
+</p>
+<dl><dt> <b>--bse-pipe</b> <i>infd</i> <i>outfd</i>
+</dt><dd> Provide the input and output communication filedescriptors for remote operation.
+</dd><dt> <b>--bse-eval</b> <i>string</i>
+</dt><dd> Execute (eval-string <i>string</i>) instead of going into interactive mode.
+</dd><dt> <b>--bse-enable-register</b>
+</dt><dd> Allowes registration of procedures with the <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> core.
+</dd><dt> <b>--bse-no-load</b>
+</dt><dd> Prevent automated loading of plugins and scripts at startup time in interactive mode.
+</dd><dt> <b>--bse-no-play</b>
+</dt><dd> Prevent automated detection and playback of <i>.bse</i> file command line arguments.
+</dd><dt> <b>--g-fatal-warnings</b>
+</dt><dd> Make runtime warnings fatal (abort).
+</dd><dt> <b>-h</b>, <b>--help</b>
+</dt><dd> Describe command line options and exit.
+</dd><dt> <b>-v</b>, <b>--version</b>
+</dt><dd> Display version and exit.
+</dd><dt> <b>-n</b>=<i>nicelevel</i>
+</dt><dd> Execute with priority <i>nicelevel</i>, this option only takes effect for the root suid wrapper 'beast'.
+</dd><dt> <b>-N</b>
+</dt><dd> Disables renicing to execute with existing priority.
+</dd><dt> <b>--bse-latency</b>=<i>useconds</i>
+</dt><dd> Set the allowed synthesis latency for <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> in milliseconds.
+</dd><dt> <b>--bse-mixing-freq</b>=<i>frequency</i>
+</dt><dd> Set the desired synthesis mixing frequency in Hz.
+</dd><dt> <b>--bse-control-freq</b>=<i>frequency</i>
+</dt><dd> Set the desired control frequency in Hz, this should be much smaller than the synthesis mixing frequency to reduce CPU load. The default value of approximately 1000 Hz is usually a good choice.
+</dd><dt> <b>--bse-pcm-driver</b> <i>driver-conf</i>
+</dt><dt> <b>-p</b> <i>driver-conf</i>
+</dt><dd> This options results in an attempt to open the PCM driver <i>driver-conf</i> when playback is started. Multiple options may be supplied to try a variety of drivers and unless <i>driver-conf</i> is specified as "<b>auto</b>", only the drivers listed by options are used. Each <i>driver-conf</i> consists of a driver name and an optional comma seperated list of arguments attached to the driver withan equal sign, e.g.: <b>-p oss=/dev/dsp2,rw -p auto</b>
+</dd><dt> <b>--bse-midi-driver</b> <i>driver-conf</i>
+</dt><dt> <b>-m</b> <i>driver-conf</i>
+</dt><dd> This option is similar to the <b>--bse-pcm-driver</b> option, but applies to MIDI drivers and devices. It also may be specified multiple times and features an "<b>auto</b>" driver.
+</dd><dt> <b>--bse-driver-list</b>
+</dt><dd> Produce a list of all available PCM and MIDI drivers and available devices.
+</dd></dl>
+<h3> <span class="mw-headline" id="Guile_Options:"> Guile Options: </span></h3>
+<dl><dt> <b>-l</b> <i>file</i>
+</dt><dd> Load scheme source code from file.
+</dd><dt> <b>-e</b> <i>function</i>
+</dt><dd> After reading script, apply <i>function</i> to command-line arguments.
+</dd><dt> <b>-ds</b>
+</dt><dd> Do -s <i>script</i> at this point (note that this argument must be used in conjuction with -s).
+</dd><dt> <b>--debug</b>
+</dt><dd> Start with debugging evaluator and backtraces enabled (useful for debugging scripts).
+</dd><dt> <b>--emacs</b>
+</dt><dd> Enable emacs protocol for use from within emacs (experimental).
+</dd></dl>
+<p>The remaining Guile options stop argument processing, and pass all remaining arguments as the value of (command-line):
+</p>
+<dl><dt> <b>--</b>
+</dt><dd> Stop argument processing, start in interactive mode.
+</dd><dt> <b>-c</b> <i>expr</i>
+</dt><dd> Stop argument processing, evaluate <i>expr</i> as a scheme expression.
+</dd><dt> <b>-s</b> <i>script</i>
+</dt><dd> Load Scheme source from <i>script</i> and execute as a script.
+</dd></dl>
+<p><br/>
+</p>
+<h2> <span class="mw-headline" id="SEE_ALSO"> SEE ALSO </span></h2>
+<p><a href="http://testbit.eu/Beast.1"; title="Beast.1">beast.1</a>,
+<a href="http://testbit.eu/Bse.5"; title="Bse.5">bse.5</a>,
+<a rel="nofollow" class="external text" href="http://beast.testbit.eu";>BEAST/BSE Website</a>,
+<a rel="nofollow" class="external text" href="http://www.gnu.org/software/guile/docs/";>Guile</a>
+</p>
+<!--
+NewPP limit report
+Preprocessor node count: 46/1000000
+Post-expand include size: 15/2097152 bytes
+Template argument size: 0/2097152 bytes
+Expensive parser function count: 0/100
+-->
+<!-- Saved in parser cache with key mediawikidb:pcache:idhash:60-1!*!0!!en!*!* and timestamp 20121025003656 -->
diff --git a/docs/import/bsewavetool.1 b/docs/import/bsewavetool.1
new file mode 100644
index 0000000..744e0a1
--- /dev/null
+++ b/docs/import/bsewavetool.1
@@ -0,0 +1,359 @@
+<table id="toc" class="toc"><tr><td><div id="toctitle"><h2>Contents</h2></div>
+<ul>
+<li class="toclevel-1 tocsection-1"><a href="#Bsewavetool.281.29_-_BEAST.2FBSE_Wave_Tool"><span class="tocnumber">1</span> <span class="toctext">Bsewavetool(1) - BEAST/BSE Wave Tool</span></a>
+<ul>
+<li class="toclevel-2 tocsection-2"><a href="#NAME"><span class="tocnumber">1.1</span> <span class="toctext">NAME</span></a></li>
+<li class="toclevel-2 tocsection-3"><a href="#SYNOPSIS"><span class="tocnumber">1.2</span> <span class="toctext">SYNOPSIS</span></a></li>
+<li class="toclevel-2 tocsection-4"><a href="#DESCRIPTION"><span class="tocnumber">1.3</span> <span class="toctext">DESCRIPTION</span></a></li>
+<li class="toclevel-2 tocsection-5"><a href="#OPTIONS"><span class="tocnumber">1.4</span> <span class="toctext">OPTIONS</span></a></li>
+<li class="toclevel-2 tocsection-6"><a href="#COMMANDS"><span class="tocnumber">1.5</span> <span class="toctext">COMMANDS</span></a>
+<ul>
+<li class="toclevel-3 tocsection-7"><a href="#Store"><span class="tocnumber">1.5.1</span> <span class="toctext">Store</span></a></li>
+<li class="toclevel-3 tocsection-8"><a href="#Create"><span class="tocnumber">1.5.2</span> <span class="toctext">Create</span></a></li>
+<li class="toclevel-3 tocsection-9"><a href="#Oggenc"><span class="tocnumber">1.5.3</span> <span class="toctext">Oggenc</span></a></li>
+<li class="toclevel-3 tocsection-10"><a href="#Add_Chunk"><span class="tocnumber">1.5.4</span> <span class="toctext">Add Chunk</span></a></li>
+<li class="toclevel-3 tocsection-11"><a href="#Add_Raw_Chunk"><span class="tocnumber">1.5.5</span> <span class="toctext">Add Raw Chunk</span></a></li>
+<li class="toclevel-3 tocsection-12"><a href="#Del_Chunk"><span class="tocnumber">1.5.6</span> <span class="toctext">Del Chunk</span></a></li>
+<li class="toclevel-3 tocsection-13"><a href="#XInfo"><span class="tocnumber">1.5.7</span> <span class="toctext">XInfo</span></a></li>
+<li class="toclevel-3 tocsection-14"><a href="#Info"><span class="tocnumber">1.5.8</span> <span class="toctext">Info</span></a></li>
+<li class="toclevel-3 tocsection-15"><a href="#Clip"><span class="tocnumber">1.5.9</span> <span class="toctext">Clip</span></a></li>
+<li class="toclevel-3 tocsection-16"><a href="#Normalize"><span class="tocnumber">1.5.10</span> <span class="toctext">Normalize</span></a></li>
+<li class="toclevel-3 tocsection-17"><a href="#Loop"><span class="tocnumber">1.5.11</span> <span class="toctext">Loop</span></a></li>
+<li class="toclevel-3 tocsection-18"><a href="#Highpass"><span class="tocnumber">1.5.12</span> <span class="toctext">Highpass</span></a></li>
+<li class="toclevel-3 tocsection-19"><a href="#Lowpass"><span class="tocnumber">1.5.13</span> <span class="toctext">Lowpass</span></a></li>
+<li class="toclevel-3 tocsection-20"><a href="#Upsample2"><span class="tocnumber">1.5.14</span> <span class="toctext">Upsample2</span></a></li>
+<li class="toclevel-3 tocsection-21"><a href="#Downsample2"><span class="tocnumber">1.5.15</span> <span class="toctext">Downsample2</span></a></li>
+<li class="toclevel-3 tocsection-22"><a href="#Export"><span class="tocnumber">1.5.16</span> <span class="toctext">Export</span></a></li>
+<li class="toclevel-3 tocsection-23"><a href="#List_Chunks"><span class="tocnumber">1.5.17</span> <span class="toctext">List Chunks</span></a></li>
+</ul>
+</li>
+<li class="toclevel-2 tocsection-24"><a href="#SEE_ALSO"><span class="tocnumber">1.6</span> <span class="toctext">SEE ALSO</span></a></li>
+</ul>
+</li>
+</ul>
+</td></tr></table>
+<h1> <span class="mw-headline" id="Bsewavetool.281.29_-_BEAST.2FBSE_Wave_Tool"> Bsewavetool(1) - BEAST/BSE Wave Tool </span></h1>
+<p>Manual: Testbit Wiki Pages <br/>
+Release: Revision 308 <br/>
+Updated: 2011-05-2 <br/>
+</p>
+<h2> <span class="mw-headline" id="NAME"> NAME </span></h2>
+<p>bsewavetool - A tool for editing the native multisample format for <a href="http://testbit.eu/Beast"; title="Beast">beast</a> and <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a>.
+</p>
+<h2> <span class="mw-headline" id="SYNOPSIS"> SYNOPSIS </span></h2>
+<p><b>bsewavetool</b> [<i>tool-options</i>] command <i><file.bsewave></i> [<i>command-arguments</i>]
+</p>
+<h2> <span class="mw-headline" id="DESCRIPTION"> DESCRIPTION </span></h2>
+<p><b>bsewavetool</b> is a command line tool for editing the native multisample format for <a href="http://testbit.eu/Beast"; title="Beast">beast</a> and <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a>, the <a href="http://testbit.eu/index.php?title=Bsewave&action=edit&redlink=1"; class="new" title="Bsewave (page does not exist)">bsewave</a> format. Some common operations are creating new <a href="http://testbit.eu/index.php?title=Bsewave&action=edit&redlink=1"; class="new" title="Bsewave (page does not exist)">bsewave</a> files, adding chunks to an existing file, encoding the sample data, adding meta information or exporting chunks.
+</p><p>Common uses for <a href="http://testbit.eu/index.php?title=Bsewave&action=edit&redlink=1"; class="new" title="Bsewave (page does not exist)">bsewave</a> files are:
+</p>
+<ul><li> Mapping an individual sample to each midi note (key on the keyboard) - this is mainly useful for drumkits.
+</li><li> Approximating the sound of an instrument (such as a piano) by sampling some notes, and mapping these to the corresponding frequencies in a <a href="http://testbit.eu/index.php?title=Bsewave&action=edit&redlink=1"; class="new" title="Bsewave (page does not exist)">bsewave</a> file - when such a file is loaded by <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> and a note is played, <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> will play the "nearest" note, and - if necessary - pitch it.
+</li></ul>
+<h2> <span class="mw-headline" id="OPTIONS"> OPTIONS </span></h2>
+<p>A number of options can be used with <b>bsewavetool</b> in combination with the commands:
+</p>
+<dl><dt> <b>-o</b> <i><output.bsewave></i>
+</dt><dd> Name of the destination file (default: <file.bsewave>).
+</dd><dt> <b>--silent</b>
+</dt><dd> Suppress extra processing information.
+</dd><dt> <b>--skip-errors</b>
+</dt><dd> Skip errors (may overwrite bsewave files after load errors occoured for part of its contents).
+</dd><dt> <b>-h</b>, <b>--help</b>
+</dt><dd> Show elaborated help message with command documentation.
+</dd><dt> <b>-v</b>, <b>--version</b>
+</dt><dd> Print version information.
+</dd></dl>
+<h2> <span class="mw-headline" id="COMMANDS"> COMMANDS </span></h2>
+<h3> <span class="mw-headline" id="Store"> Store </span></h3>
+<p><b>store</b>
+</p><p>Store the input bsewave as output bsewave. If both file names are the same, the bsewave file is simply rewritten. Allthough no explicit modifications are performed on the bsewave, externally referenced sample files will be inlined, chunks may be reordered, and other changes related to the bsewave storage process may occour.
+</p>
+<h3> <span class="mw-headline" id="Create"> Create </span></h3>
+<p><b>create</b> <i><n_channels></i> [<i>options</i>]
+</p><p>Create an empty bsewave file, <i><n_channels></i>=1 (mono) and <i><n_channels></i>=2 (stereo) are currently supported.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>-N</b> <i><wave-name></i>
+</dt><dd> Name of the wave stored inside of <output.bsewave>.
+</dd><dt> <b>-f</b>
+</dt><dd> Force creation even if the file exists already.
+</dd></dl>
+<h3> <span class="mw-headline" id="Oggenc"> Oggenc </span></h3>
+<p><b>oggenc</b> [<i>options</i>]
+</p><p>Compress all chunks with the Vorbis audio codec and store the wave data as Ogg/Vorbis streams inside the bsewave file.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>-q</b> <i><n></i>
+</dt><dd> Use quality level <i><n></i>, refer to oggenc(1) for details.
+</dd></dl>
+<h3> <span class="mw-headline" id="Add_Chunk"> Add Chunk </span></h3>
+<p><b>add-chunk</b> [<i>options</i>] {<b>-m</b>=<i>midi-note</i>|<b>-f</b>=<i>osc-freq</i>} <i><sample-file></i> ...
+</p><p>Add a new chunk containing <i><sample-file></i> to the wave file. For each chunk, a unique oscillator frequency must be given to determine what note the chunk is to be played back for. Multi oscillator frequency + sample-file option combinations may be given on the command line to add multiple wave chunks. The -f and -m options can be omitted for a sample file, if the oscillator frequency can be determined through auto extract options.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>-f</b> <i><osc-freq></i>
+</dt><dd> Oscillator frequency for the next chunk.
+</dd><dt> <b>-m</b> <i><midi-note></i>
+</dt><dd> Alternative way to specify oscillator frequency.
+</dd><dt> <b>--auto-extract-midi-note</b> <i><nth></i>
+</dt><dd> Automatically retrieve the midi note by extracting the <i><nth></i> number from the base name of <i><sample-file></i>.
+</dd><dt> <b>--auto-extract-osc-freq</b> <i><nth></i>
+</dt><dd> Automatically retrieve the oscillator frequency by extracting the <i><nth></i> number from the base name of <i><sample-file></i>.
+</dd></dl>
+<h3> <span class="mw-headline" id="Add_Raw_Chunk"> Add Raw Chunk </span></h3>
+<p><b>add-raw-chunk</b> [<i>options</i>] {<b>-m</b>=<i>midi-note</i>|<b>-f</b>=<i>osc-freq</i>} <i><sample-file></i> ...
+</p><p>Add a new chunk just like with "add-chunk", but load raw sample data. Additional raw sample format options are supported.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>-R</b> <i><mix-freq></i>
+</dt><dd> Mixing frequency for the next chunk [44100].
+</dd><dt> <b>-F</b> <i><format></i>
+</dt><dd> Raw sample format, supported formats are: alaw, ulaw, float, signed-8, signed-12, signed-16, unsigned-8, unsigned-12, unsigned-16 [signed-16].
+</dd><dt> <b>-B</b> <i><byte-order></i>
+</dt><dd> Raw sample byte order, supported types: little-endian, big-endian [little-endian].
+</dd></dl>
+<h3> <span class="mw-headline" id="Del_Chunk"> Del Chunk </span></h3>
+<p><b>del-chunk</b> {<b>-m</b>=<i>midi-note</i>|<b>-f</b>=<i>osc-freq</i>|<b>--chunk-key</b>=<i>key</i>|<b>--all-chunks</b>}
+</p><p>Removes one or more chunks from the bsewave file.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>-f</b> <i><osc-freq></i>
+</dt><dd> Oscillator frequency to select a wave chunk.
+</dd><dt> <b>-m</b> <i><midi-note></i>
+</dt><dd> Alternative way to specify oscillator frequency.
+</dd><dt> <b>--chunk-key</b> <i><key></i>
+</dt><dd> Select wave chunk using chunk key from list-chunks.
+</dd><dt> <b>--all-chunks</b>
+</dt><dd> Delete all chunks.
+</dd></dl>
+<h3> <span class="mw-headline" id="XInfo"> XInfo </span></h3>
+<p><b>xinfo</b> {<b>-m</b>=<i>midi-note</i>|<b>-f</b>=<i>osc-freq</i>|<b>--chunk-key</b>=<i>key</i>|<b>--all-chunks</b>|<b>--wave</b>} <b>key</b>=[<i>value</i>] ...
+</p><p>Add, change or remove an XInfo string of a bsewave file. Omission of [value] deletes the XInfo associated with the key. Key and value pairs may be specified multiple times, optionally preceeded by location options to control what portion of a bsewave file (the wave, individual wave chunks or all wave chunks) should be affected.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>-f</b> <i><osc-freq></i>
+</dt><dd> Oscillator frequency to select a wave chunk.
+</dd><dt> <b>-m</b> <i><midi-note></i>
+</dt><dd> Alternative way to specify oscillator frequency.
+</dd><dt> <b>--chunk-key</b> <i><key></i>
+</dt><dd> Select wave chunk using chunk key from list-chunks.
+</dd><dt> <b>--all-chunks</b>
+</dt><dd> Apply XInfo modification to all chunks.
+</dd><dt> <b>--wave</b>
+</dt><dd> Apply XInfo modifications to the wave itself.
+</dd></dl>
+<p><br/>
+</p>
+<h3> <span class="mw-headline" id="Info"> Info </span></h3>
+<p><b>info</b> <i>{<b>-m</b>=</i>midi-note<i>|<b>-f</b>=</i>osc-freq<i>|<b>--chunk-key</b>=</i>key<i>|<b>--all-chunks</b>|</i>#--wave<b>} [<i>options</i>]</b>
+</p><p>Print information about the chunks of a bsewave file.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>-f</b> <i><osc-freq></i>
+</dt><dd> Oscillator frequency to select a wave chunk.
+</dd><dt> <b>-m</b> <i><midi-note></i>
+</dt><dd> Alternative way to specify oscillator frequency.
+</dd><dt> <b>--all-chunks</b>
+</dt><dd> Show information for all chunks (default).
+</dd><dt> <b>--chunk-key</b> <i><key></i>
+</dt><dd> Select wave chunk using chunk key from list-chunks.
+</dd><dt> <b>--wave</b>
+</dt><dd> Show information for the wave.
+</dd><dt> <b>--pretty</b>=medium
+</dt><dd> Use human readable format (default).
+</dd><dt> <b>--pretty</b>=full
+</dt><dd> Use human readable format with all details.
+</dd><dt> <b>--script</b> <i><field1></i>,<i><field2></i>,<i><field3></i>,...,<i><fieldN></i>
+</dt><dd> Use script readable line based space separated output.
+</dd></dl>
+<p><b>Valid wave or chunk fields:</b>
+</p>
+<dl><dt> channels
+</dt><dd> Number of channels.
+</dd><dt> label
+</dt><dd> User interface label.
+</dd><dt> blurb
+</dt><dd> Associated comment.
+</dd></dl>
+<p><b>Valid wave fields:</b>
+</p>
+<dl><dt> authors
+</dt><dd> Authors who participated in creating the wave file.
+</dd><dt> license
+</dt><dd> License specifying redistribution and other legal terms.
+</dd><dt> play-type
+</dt><dd> Set of required play back facilities for a wave.
+</dd></dl>
+<p><b>Valid chunk fields:</b>
+</p>
+<dl><dt> osc-freq
+</dt><dd> Frequency of the chunk.
+</dd><dt> mix-freq
+</dt><dd> Sampling rate of the chunk.
+</dd><dt> midi-note
+</dt><dd> Midi note of a chunk.
+</dd><dt> length
+</dt><dd> Length of the chunk in sample frames.
+</dd><dt> volume
+</dt><dd> Volume at which the chunk is to be played.
+</dd><dt> format
+</dt><dd> Storage format used to save the chunk data.
+</dd><dt> loop-type
+</dt><dd> Whether the chunk is to be looped.
+</dd><dt> loop-start
+</dt><dd> Offset in sample frames for the start of the loop.
+</dd><dt> loop-end
+</dt><dd> Offset in sample frames for the end of the loop.
+</dd><dt> loop-count
+</dt><dd> Maximum limit for how often the loop should be repeated.
+</dd></dl>
+<p><b>Chunk fields that can be computed for the signal:</b>
+</p>
+<dl><dt> +avg-energy-raw
+</dt><dd> Average signal energy (dB) of the raw data of the chunk.
+</dd><dt> +avg-energy
+</dt><dd> Average signal energy (dB) using volume xinfo.
+</dd></dl>
+<p>The script output consists of one line per chunk. The individual fields of a line are separated by a single space. Special characters are escaped, such as spaces, tabs, newlines and backslashes. So each line of script parsable output can be parsed using the read(P) shell command. Optional fields will printed as a single (escaped) space.
+</p><p>The human readable output formats (--pretty) may vary in future versions and are not recommended as script input.
+</p>
+<h3> <span class="mw-headline" id="Clip"> Clip </span></h3>
+<p><b>clip</b> {<b>-m</b>=<i>midi-note</i>|<b>-f</b>=<i>osc-freq</i>|<b>--chunk-key</b>=<i>key</i>|<b>--all-chunks</b>} [<i>options</i>]
+</p><p>Clip head and or tail of a wave chunk and produce fade-in ramps at the beginning. Wave chunks which are clipped to an essential 0-length will automatically be deleted.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>-f</b> <i><osc-freq></i>
+</dt><dd> Oscillator frequency to select a wave chunk.
+</dd><dt> <b>-m</b> <i><midi-note></i>
+</dt><dd> Alternative way to specify oscillator frequency.
+</dd><dt> <b>--chunk-key</b> <i><key></i>
+</dt><dd> Select wave chunk using chunk key from list-chunks.
+</dd><dt> <b>--all-chunks</b>
+</dt><dd> Try to clip all chunks.
+</dd><dt> <b>-s</b>=<i><threshold></i>
+</dt><dd> Set the minimum signal threshold (0..32767) [16].
+</dd><dt> <b>-h</b>=<i><head-samples></i>
+</dt><dd> Number of silence samples to verify at head [0].
+</dd><dt> <b>-t</b>=<i><tail-samples></i>
+</dt><dd> Number of silence samples to verify at tail [0].
+</dd><dt> <b>-f</b>=<i><fade-samples></i>
+</dt><dd> Number of samples to fade-in before signal starts [16].
+</dd><dt> <b>-p</b>=<i><pad-samples></i>
+</dt><dd> Number of padding samples after signal ends [16].
+</dd><dt> <b>-r</b>=<i><tail-silence></i>
+</dt><dd> Number of silence samples required at tail to allow tail clipping [0].
+</dd></dl>
+<h3> <span class="mw-headline" id="Normalize"> Normalize </span></h3>
+<p><b>normalize</b> {<b>-m</b>=<i>midi-note</i>|<b>-f</b>=<i>osc-freq</i>|<b>--chunk-key</b>=<i>key</i>|<b>--all-chunks</b>} [<i>options</i>]
+</p><p>Normalize wave chunk. This is used to extend (or compress) the signal range to optimally fit the available unclipped dynamic range.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>-f</b> <i><osc-freq></i>
+</dt><dd> Oscillator frequency to select a wave chunk.
+</dd><dt> <b>-m</b> <i><midi-note></i>
+</dt><dd> Alternative way to specify oscillator frequency.
+</dd><dt> <b>--chunk-key</b> <i><key></i>
+</dt><dd> Select wave chunk using chunk key from list-chunks.
+</dd><dt> <b>--all-chunks</b>
+</dt><dd> Try to normalize all chunks.
+</dd></dl>
+<h3> <span class="mw-headline" id="Loop"> Loop </span></h3>
+<p><b>loop</b> {<b>-m</b>=<i>midi-note</i>|<b>-f</b>=<i>osc-freq</i>|<b>--all-chunks</b>} [<i>options</i>]
+</p><p>Find suitable loop points.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>-f</b> <i><osc-freq></i>
+</dt><dd> Oscillator frequency to select a wave chunk
+</dd><dt> <b>-m</b> <i><midi-note></i>
+</dt><dd> Alternative way to specify oscillator frequency
+</dd><dt> <b>--chunk-key</b> <i><key></i>
+</dt><dd> Select wave chunk using chunk key from list-chunks
+</dd><dt> <b>--all-chunks</b>
+</dt><dd> Try to loop all chunks
+</dd></dl>
+<h3> <span class="mw-headline" id="Highpass"> Highpass </span></h3>
+<p><b>highpass</b> [<i>options</i>]
+</p><p>Apply highpass filter to wave data.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>--cutoff-freq</b> <i><f></i>
+</dt><dd> Filter cutoff frequency in Hz
+</dd><dt> <b>--order</b> <i><o></i>
+</dt><dd> Filter order [64]
+</dd></dl>
+<h3> <span class="mw-headline" id="Lowpass"> Lowpass </span></h3>
+<p><b>lowpass</b> [<i>options</i>]
+</p><p>Apply lowpass filter to wave data.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>--cutoff-freq</b> <i><f></i>
+</dt><dd> Filter cutoff frequency in Hz
+</dd><dt> <b>--order</b> <o>
+</dt><dd> Filter order [64]
+</dd></dl>
+<h3> <span class="mw-headline" id="Upsample2"> Upsample2 </span></h3>
+<p><b>upsample2</b> [<i>options</i>]
+</p><p>Resample wave data to twice the sampling frequency.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>--precision</b> <i><bits></i>
+</dt><dd> Set resampler precision bits [24]. Supported precisions: 1, 8, 12, 16, 20, 24 (1 is a special value for linear interpolation)
+</dd></dl>
+<h3> <span class="mw-headline" id="Downsample2"> Downsample2 </span></h3>
+<p><b>downsample2</b> [<i>options</i>]
+</p><p>Resample wave data to half the sampling frequency.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>--precision</b> <i><bits></i>
+</dt><dd> Set resampler precision bits [24]. Supported precisions: 1, 8, 12, 16, 20, 24 (1 is a special value for linear interpolation).
+</dd></dl>
+<h3> <span class="mw-headline" id="Export"> Export </span></h3>
+<p><b>export</b> {<b>-m</b>=<i>midi-note</i>|<b>-f</b>=<i>osc-freq</i>|<b>--chunk-key</b>=<i>key</i>|<b>--all-chunks</b>|<b>-x</b>=<i>filename</i>} [<i>options</i>]
+</p><p>Export chunks from bsewave as WAV file.
+</p><p><b>Options:</b>
+</p>
+<dl><dt> <b>-x</b> <i><filename></i>
+</dt><dd> Set export filename (supports %N %F and %C, see below).
+</dd><dt> <b>-f</b> <i><osc-freq></i>
+</dt><dd> Oscillator frequency to select a wave chunk.
+</dd><dt> <b>-m</b> <i><midi-note></i>
+</dt><dd> Alternative way to specify oscillator frequency.
+</dd><dt> <b>--chunk-key</b> <i><key></i>
+</dt><dd> Select wave chunk using chunk key from list-chunks.
+</dd><dt> <b>--all-chunks</b>
+</dt><dd> Try to export all chunks.
+</dd></dl>
+<p>The export filename can contain the following extra information:
+</p>
+<dl><dt> %F
+</dt><dd> The frequency of the chunk.
+</dd><dt> %N
+</dt><dd> The midi note of the chunk.
+</dd><dt> %C
+</dt><dd> Cent detuning of the midi note.
+</dd></dl>
+<h3> <span class="mw-headline" id="List_Chunks"> List Chunks </span></h3>
+<p><b>list-chunks</b> [<i>options</i>]
+</p><p>Prints a list of chunk keys of the chunks contained in the bsewave file.
+A chunk key for a given chunk identifies the chunk uniquely and stays valid
+if other chunks are inserted and deleted.
+</p><p>This bash script shows the length of all chunks (like info --all-chunks):
+</p>
+<pre> for key in `bsewavetool list-chunks foo.bsewave` ; do
+ bsewavetool info foo.bsewave --chunk-key $key --script length ;
+ done
+</pre>
+<h2> <span class="mw-headline" id="SEE_ALSO"> SEE ALSO </span></h2>
+<p><a href="http://testbit.eu/Beast.1"; title="Beast.1">beast.1</a>,
+<a rel="nofollow" class="external text" href="http://beast.testbit.eu";>BEAST/BSE Website</a>,
+<a href="http://testbit.eu/Beast_Architecture#Samples_and_Wave_Files"; title="Beast Architecture"> Samples and Wave Files in BEAST</a>
+</p>
+<!--
+NewPP limit report
+Preprocessor node count: 114/1000000
+Post-expand include size: 15/2097152 bytes
+Template argument size: 0/2097152 bytes
+Expensive parser function count: 0/100
+-->
+<!-- Saved in parser cache with key mediawikidb:pcache:idhash:58-1!*!0!!en!*!* and timestamp 20121025003657 -->
diff --git a/docs/import/sfidl.1 b/docs/import/sfidl.1
new file mode 100644
index 0000000..319b2eb
--- /dev/null
+++ b/docs/import/sfidl.1
@@ -0,0 +1,91 @@
+<table id="toc" class="toc"><tr><td><div id="toctitle"><h2>Contents</h2></div>
+<ul>
+<li class="toclevel-1 tocsection-1"><a href="#SFIDL.281.29_-_SFI_IDL_Compiler"><span class="tocnumber">1</span> <span class="toctext">SFIDL(1) - SFI IDL Compiler</span></a>
+<ul>
+<li class="toclevel-2 tocsection-2"><a href="#NAME"><span class="tocnumber">1.1</span> <span class="toctext">NAME</span></a></li>
+<li class="toclevel-2 tocsection-3"><a href="#SYNOPSIS"><span class="tocnumber">1.2</span> <span class="toctext">SYNOPSIS</span></a></li>
+<li class="toclevel-2 tocsection-4"><a href="#DESCRIPTION"><span class="tocnumber">1.3</span> <span class="toctext">DESCRIPTION</span></a></li>
+<li class="toclevel-2 tocsection-5"><a href="#OPTIONS"><span class="tocnumber">1.4</span> <span class="toctext">OPTIONS</span></a>
+<ul>
+<li class="toclevel-3 tocsection-6"><a href="#Language_bindings:"><span class="tocnumber">1.4.1</span> <span class="toctext">Language bindings:</span></a></li>
+<li class="toclevel-3 tocsection-7"><a href="#Language_binding_options:"><span class="tocnumber">1.4.2</span> <span class="toctext">Language binding options:</span></a></li>
+</ul>
+</li>
+<li class="toclevel-2 tocsection-8"><a href="#SEE_ALSO"><span class="tocnumber">1.5</span> <span class="toctext">SEE ALSO</span></a></li>
+</ul>
+</li>
+</ul>
+</td></tr></table>
+<h1> <span class="mw-headline" id="SFIDL.281.29_-_SFI_IDL_Compiler"> SFIDL(1) - SFI IDL Compiler </span></h1>
+<p>Manual: Testbit Wiki Pages <br/>
+Release: Revision 305 <br/>
+Updated: 2011-05-2 <br/>
+</p>
+<h2> <span class="mw-headline" id="NAME"> NAME </span></h2>
+<p>SFIDL - SFI IDL Compiler
+</p>
+<h2> <span class="mw-headline" id="SYNOPSIS"> SYNOPSIS </span></h2>
+<p><b>sfidl</b> [<i>OPTIONS</i>] <i>input.idl</i>
+</p>
+<h2> <span class="mw-headline" id="DESCRIPTION"> DESCRIPTION </span></h2>
+<p><b>sfidl</b> generates glue code for <a href="http://testbit.eu/index.php?title=Bse&action=edit&redlink=1"; class="new" title="Bse (page does not exist)">Bse</a> objects and
+plugins from interface definition language files.
+</p>
+<h2> <span class="mw-headline" id="OPTIONS"> OPTIONS </span></h2>
+<dl><dt> <b>--help</b> [<i>binding</i>]
+</dt><dd> Print general usage information. Or, if <i>binding</i> was specified, print usage information for this language binding.
+</dd><dt> <b>--version</b>
+</dt><dd> Print program version.
+</dd><dt> <b>-I</b> <i>DIRECTORY</i>
+</dt><dd> Add <i>DIRECTORY</i> to include path.
+</dd><dt> <b>--print-include-path</b>
+</dt><dd> Print include path.
+</dd><dt> <b>--nostdinc</b>
+</dt><dd> Prevents standard include path from being used.
+</dd></dl>
+<h3> <span class="mw-headline" id="Language_bindings:"> Language bindings: </span></h3>
+<dl><dt> <b>--client-c</b>
+</dt><dd> Generate C client language binding.
+</dd><dt> <b>--client-c</b>
+</dt><dd> Generate C core language binding.
+</dd><dt> <b>--host-c</b>
+</dt><dd> Generate C host language binding.
+</dd><dt> <b>--client-cxx</b>
+</dt><dd> Generate C++ client language binding.
+</dd><dt> <b>--core-cxx</b>
+</dt><dd> Generate C++ core language binding.
+</dd><dt> <b>--plugin</b>
+</dt><dd> Generate C++ plugin language binding.
+</dd><dt> <b>--list-types</b>
+</dt><dd> Print all types defined in the idlfile. This option is used only for BSE internally to ease transition from C to C++ types.
+</dd></dl>
+<h3> <span class="mw-headline" id="Language_binding_options:"> Language binding options: </span></h3>
+<dl><dt> <b>--header</b>
+</dt><dd> Generate header file, this is the default.
+</dd><dt> <b>--source</b>
+</dt><dd> Generate source file.
+</dd><dt> <b>--prefix</b> <i>prefix</i>
+</dt><dd> C host/client language binding option, sets the prefix for C functions. The prefix ensures that no symbol clashes will occur between different programs/libraries which are using a binding, so it is important to set it to something unique to your application/library.
+</dd><dt> <b>--init</b> <i>name</i>
+</dt><dd> Set the name of the init function for C host/core bindings.
+</dd><dt> <b>--namespace</b> <i>namespace</i>
+</dt><dd> C++ client language binding, sets the namespace to use for the code. The namespace ensures that no symbol clashes will occur between different programs/libraries which are using a binding, so it is important to set it to something unique to your application/library.
+</dd><dt> <b>--lower</b>
+</dt><dd> Select lower case identifiers in the C++ client language binding (create_midi_synth), this is the default.
+</dd><dt> <b>--mixed</b>
+</dt><dd> Select mixed case identifiers in the C++ client language binding (createMidiSynth).
+</dd></dl>
+<h2> <span class="mw-headline" id="SEE_ALSO"> SEE ALSO </span></h2>
+<p><a href="http://testbit.eu/Bsescm.1"; title="Bsescm.1">bsescm.1</a>,
+<a rel="nofollow" class="external text" href="http://beast.testbit.eu/bse-objects";>BSE Object Reference</a>,
+<a rel="nofollow" class="external text" href="http://beast.testbit.eu/bse-interface";>BSE Interface Reference</a>,
+<a rel="nofollow" class="external text" href="http://beast.testbit.eu/sfidl-manual";>SFIDL Documentation</a>
+</p>
+<!--
+NewPP limit report
+Preprocessor node count: 50/1000000
+Post-expand include size: 15/2097152 bytes
+Template argument size: 0/2097152 bytes
+Expensive parser function count: 0/100
+-->
+<!-- Saved in parser cache with key mediawikidb:pcache:idhash:63-1!*!0!!en!*!* and timestamp 20121024191138 -->
diff --git a/docs/import/stamp b/docs/import/stamp
new file mode 100644
index 0000000..1b252bd
--- /dev/null
+++ b/docs/import/stamp
@@ -0,0 +1 @@
+1351125417
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
