User Manual - Time+space

Transcript

USER MANUAL (Revision EN-1.5.0) BloXpander USER MANUAL User manual 3 Table of contents ABOUT THIS MANUAL .................................................................................................................................................................................... 6 Credits .............................................................................................................................................................................................................. 7 Preamble........................................................................................................................................................................................................... 8 BloXpander at a glance... .............................................................................................................................................................................. 10 System requirements .................................................................................................................................................................................... 11 Installation ...................................................................................................................................................................................................... 12 Chapter 1: The Console ................................................................................................................................................................................ 14 Input........................................................................................................................................................................................................... 15 Inserts........................................................................................................................................................................................................ 20 Presets ................................................................................................................................................................................................. 20 « Multi-Out » and « Sidechain »......................................................................................................................................................... 21 Update plug-in screenshot ................................................................................................................................................................ 21 Remove ................................................................................................................................................................................................ 21 Aux Sends and Returns........................................................................................................................................................................... 22 Output........................................................................................................................................................................................................ 23 Master Bus ................................................................................................................................................................................................ 25 « Computer hysteria » ............................................................................................................................................................................. 26 The « Touch Zone » ................................................................................................................................................................................. 27 Chapter 2: The « Plug-ins Case »................................................................................................................................................................. 28 Description................................................................................................................................................................................................ 28 Per-plug-in Options.................................................................................................................................................................................. 29 « Shell » plug-ins...................................................................................................................................................................................... 29 Warning messages .................................................................................................................................................................................. 30 Chapter 3: Libraries ....................................................................................................................................................................................... 31 Description................................................................................................................................................................................................ 31 Managing items of a library..................................................................................................................................................................... 32 Managing libraries ................................................................................................................................................................................... 33 Chapter 4: Sets, Scenes and Subscenes .................................................................................................................................................... 34 Description................................................................................................................................................................................................ 34 Scenes ....................................................................................................................................................................................................... 35 Sets ............................................................................................................................................................................................................ 36 Subscenes ................................................................................................................................................................................................ 37 Scenes MIDI Control ................................................................................................................................................................................ 39 Subscenes MIDI Control .......................................................................................................................................................................... 40 Chapter 5: Software configuration (system panel) .................................................................................................................................... 41 General Settings ....................................................................................................................................................................................... 42 4 eaReckon BloXpander Plug-ins ..................................................................................................................................................................................................... 43 Chapter 6: Information and Expert Options Panel ..................................................................................................................................... 45 Chapter 7: “Big Display”............................................................................................................................................................................... 46 Chapter 8: Main MIDI controller (system panel) ......................................................................................................................................... 47 Configuration using a « basic » controller ............................................................................................................................................ 48 Controller type and connection......................................................................................................................................................... 48 Assignment to the console elements ............................................................................................................................................... 49 Assignment to the plug-ins control .................................................................................................................................................. 49 Configuration using a Mackie Control compatible controller ............................................................................................................. 50 Controller type and connection......................................................................................................................................................... 50 Assignment to the console elements ............................................................................................................................................... 51 Plug-ins control................................................................................................................................................................................... 51 Saving the configuration of the main MIDI controller .......................................................................................................................... 52 Plug-ins control ........................................................................................................................................................................................ 52 Assignment of a « plug-ins call button » to a plug-in ..................................................................................................................... 52 Choice of the controlled parameters ................................................................................................................................................ 53 Chapter 9: How to assign a MIDI control .................................................................................................................................................... 54 Chapter 10: Sysex Messages ....................................................................................................................................................................... 56 Chapter 11: Live View ................................................................................................................................................................................... 59 Chapter 12: Advanced features.................................................................................................................................................................... 61 Visual groups ........................................................................................................................................................................................... 61 Plug-ins transparency ............................................................................................................................................................................. 61 Inserts drag-and-drop .............................................................................................................................................................................. 61 Using the extra outputs of a plug-in (« Multi Out ») ............................................................................................................................. 62 Using the extra inputs of a plug-in (« Sidechain ») .............................................................................................................................. 63 Ferret 4x4 (free plug-in) ........................................................................................................................................................................... 64 Master Record .......................................................................................................................................................................................... 64 Chapter 13: How to load both 32 and 64 bit plug-ins (with jBridge) ........................................................................................................ 65 Appendix 1: Keyboard Shortcuts................................................................................................................................................................. 66 Appendix 2: End User License Agreement (EULA).................................................................................................................................... 67 Appendix 3: Third-party code....................................................................................................................................................................... 73 User manual 5 ABOUT THIS MANUAL The information in this document is subject to change without notice and does not represent a commitment on the part of Philippe DECUYPER. Some screenshots in this manual may show the interface of 3 rd party products that are not delivered with eaReckon BloXpander. In addition, screenshots included in this manual may differ from the actual product. THE SOFTWARE DESCRIBED IN THIS DOCUMENT IS FURNISHED UNDER A LICENSE AGREEMENT OR NONDISCLOSURE AGREEMENT. THE SOFTWARE MAY BE USED OR COPIED ONLY IN ACCORDANCE OF THE TERMS OF THE AGREEMENT. PHILIPPE DECUYPER MAKES NO WARRANTY OF ANY KIND WITH REGARDS TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE. PHILIPPE DECUYPER WILL NOT BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE OR USE OF THIS MATERIAL. eaReckon and the eaReckon logo are trademarks of Philippe DECUYPER. ASIO and VST are trademarks of Steinberg Media Technologies GmbH. Mackie Control is a trademark or a registered trademark of LOUD Technologies Inc. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. jBridge is a software developed by João Fernandes (available from http://jstuff.wordpress.com/) Other company and product names are trademarks or registered trademarks of their respective owners. This manual is copyrighted © 2009-2013 Philippe DECUYPER (eaReckon). No part of this document may be transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose without the express written permission of Philippe DECUYPER. 6 eaReckon BloXpander Credits Conception & Development Artwork English manual correction “Alpha” tests and German translation Philippe DECUYPER Alain LAMBOURG & Philippe DECUYPER Maud MICLOT Jörg HARKENER BETATESTERS Far more than just a dream team of bug hunters... THANK YOU SO MUCH! Damian BLUNT, John BRANER, Jörg HARKENER, Scott HUDDY, Richard LOCKETT, Emmanuel LORANT, Rogue MARECHAL, Benoit MAS, Jerry MATEO, Dave MODISETTE, Wilfredo NANITA, Dieter POLLATSCHEK, Marco SPIES. ADDITIONAL THANKS Marie MASSON and Lucas DECUYPER for their support and patience. The TOONTRACK team Special thanks to Mattias EKLUND, Rogue MARECHAL, Erik PHERSSON and Andreas SUNDGREN. Benoit DELAPORTE Christian BUDDE and all the DELPHI ASIO/VST project contributors. (Tobias Fleischer, Chris Horton, Frederic Vanmol, Maik Menz, Tobias Erichsen, Norbert Stellberg, Marco Spies, Benjamin Rosseaux, Salih Sertkaya, Daniel Terhell, ...) This software uses the following technologies: - VST Plug-In Technology by Steinberg Media Technologies GmbH. - ASIO Interface Technology by Steinberg Media Technologies GmbH. [Website : www.steinberg.net] - “DELPHI ASIO/VST packages” by Christian-W. Budde have been used in this software under the terms of the MPL 1.1 license (Mozilla Public License – Mozilla foundation). [Website & Source Code : delphiasiovst.sourceforge.net] - “DELPHI MIDI I/O Components” by David Churcher / Manuel Kroeber have been used in this software under the terms of the MPL 1.1 license (Mozilla Public License – Mozilla foundation). [Website & Source Code : https://bitbucket.org/h4ndy/midiio-dev] User manual 7 Preamble Welcome to eaReckon BloXpander! BloXpander is a music application originally designed to meet the requirements of musicians and engineers in “live” situations. In this kind of situations, the access to your instruments and effects must be fast and intuitive. The adjustment of these must be done efficiently, and the necessary software sub layers running on your computer should not be your concern when it comes to play or produce music. BloXpander has been designed with in mind, the obsession to provide an easy to use “machine” powered by advanced features. It was important that both the beginner and the professional easily find the features they need, without being visually swamped with what is unnecessary during a session. Nowadays, the musical possibilities offered by our computers are far more than what I could have expected 15 years ago. However, some of us do not have the desire to waste their time in a lot of “computer geeks” activities, because they are just passionate about music. In the past, the access to audio hardware wasn’t that easy because of its price. Today, we have an easier access to many powerful tools but we usually don’t use every available thing on a daily basis. I consider a piece of software in the same manner as a hardware device. I wouldn’t bring 4 full racks of hardware to a small show but even in such a situation, I would like to play my music in a version that is not too “cheap” compared to the original version. Similarly, a sound engineer doesn’t always have the opportunity to hire the device he needs to facilitate his on-site tasks, when the wanted thing remains in the studio. This is why I always have my laptop with me and I consider this machine as a fully-fledged musical instrument. Still I wanted a piece of software that combines the power of a computer and the efficiency of a dedicated device. The interface of BloXpander has been designed to match this basic specification. It is visually attractive and clear, the construction of projects and the access to prepared instruments and effects is very fast. The plug-ins manipulation is direct (especially when BloXpander is coupled to an external MIDI controller). In a live situation, switching from a complete “scene” to another is done with a double-click. Even if BloXpander has been especially thought for live situations, it can also find its place within the studio. There it can be used as an expander or a top notch multi-FX unit. Whatever your current workstation is, it may be interesting to take advantage of the plethora of available plug-ins working under Microsoft Windows, installed on a PC dedicated to BloXpander. BloXpander also has the potential to facilitate the work of music teachers or theatre technicians, providing an immediate and easily transportable access to a remarkable amount of instruments and effects. The versatility of audio tools is not so critical when we can take a full load of them in just a bag. 8 eaReckon BloXpander However, don’t take me wrong. I don’t try to advocate the supremacy of software across hardware, but more humbly to offer a supplementary tool that can certainly find a place aside your current setup. And since computers are a tool that musicians can no longer ignore, I am pleased to share this software solution that is just an attempt to give some credibility to those who claim “a computer can be nothing else than a genuine musical instrument”. Philippe DECUYPER User manual 9 BloXpander at a glance... ASIO Host for VST plug-ins (Windows only) - 24 channels 4 Auxiliary bus + 1 Master bus 6 inserts per channels (theoretical 174 Instruments / FX slots) Advanced support for external MIDI controllers (lets you control the mixer and plug-ins) - Control up to 8 plug-ins (8 parameters each) with just 8 potentiometers + 8 buttons. Displays the controlled targets names on screen Lightning fast configuration procedure Mackie Control protocol supported Advanced routing - Global management of MIDI and Audio streams (MIDI VST Fx supported) Advanced user-defined MIDI Inputs filtering and routing (per channel settings) Assign the same MIDI input port to several channels (MIDI Split) Assign the same Audio inputs to several channels (Audio Split) Assign any available audio and/or MIDI output or the Master bus to any channel Pre/Post fader selector (aux sends) Specific routing solutions for “multi out” and “sidechain capable” plug-ins Audio inputs monitoring Outputs Solo and Mute functions Inserts Bypass function. Full screen friendly and fast interface - - 10 Designed as the panel of a hardware unit Touchscreen friendly (for critical functionalities) No main menu and no massive amount of overlapping windows Auto-created visual representation of your plug-ins (GUI screenshots) "Drag ‘n Drop" your plug-ins and their states from insert to insert (copy / move) Supports multi-screens Netbook friendly eaReckon BloXpander “Libraries” system - Store and callback a plug-in and its state from one double-click on a large zone Custom management of your favorite plug-ins and presets. Sets, Scenes and Subscenes - Store and callback the complete state of BloXpander ("Scene") from one double-click, keyboard strokes or MIDI messages Organize your scenes as “sets” (easy and fast access to what you need during a show) Categorized Plug-ins library (“The Case”) Optimized and secured operations - Analyze your plug-ins compatibility from a stand-alone tool (limits the eventuality of the main application malfunctioning) Fast launching SSE, 3DNow! and Multi-Core CPUs optimization Time Line - Controls: Play/Stop/Next/ Previous measures/… Loop option 2-way synchronization (« MIDI Clock ») Tap tempo feature Time signature Sysex Librarian - Easy management of Sysex reception and emission System requirements Operating system : Processor speed : RAM : Screen Resolution : Plug-ins format : Windows XP, Windows Vista or Windows 7 1.5 GHz (minimum) 1 Go (minimum) (the necessary memory amount depends on the loaded plug-ins) 1024x600 pixels (minimum) VST only BloXpander requires an audio interface with ASIO drivers. An access to the Internet is required to authorize the software. User manual 11 Installation BloXpander is delivered as a single file (setup application) To install BloXpander, double-click on this setup file that will guide you through the installation process. The installation of BloXpander implies the acceptation of the End User License Agreement (EULA) Demo version Once installed, the demo version is ready to be used. This manual is related to the full version and some features described here are not available in the demo version. Demo and Full version are different executable files. There’s no possibility to “transform” the Demo version to Full version. If you want to purchase the full version, please go to www.eareckon.com. A link to the full version setup application will be sent by email after your purchase is validated. Full version 1. Before using BloXpander, you need to register and authorize your product. To do so, please run BloXpander to get your Hardware ID. 12 eaReckon BloXpander 2. Go to www.eareckon.com. Create and/or log into your user account to register your product and get your Authorization Code (the Hardware ID given by BloXpander is required). Your customer account (used to purchase products from the online shop) and your user account (used to register and authorize your products) are different things. Use this button to register your product and get your authorization codes. This button may not be visible if you are not logged into your user account. 3. Launch BloXpander and enter your serial number and authorization code. Thank you for taking the time to install and authorize your product! User manual 13 Chapter 1: The Console BloXpander provides 24 channels, 4 Aux Returns, and 1 Master Bus. The Aux Returns and Master Bus are always visible, while only a part of the 24 channels are visible. The number of visible channels depends on your screen resolution. To switch from a channels page to another, use one of these buttons: As you can see on the first screenshot, the channels, aux returns and the master bus are made of “slots”. There are different kinds of slots available, and this chapter describes the functionalities of the slots. 14 eaReckon BloXpander Input Monitor (audio input) MIDI Input Port Audio Input Port Pan Audio Input Level Level Meter On the input slot, you can select a MIDI input port and Audio inputs (from a right-click). BloXpander will send the audio and MIDI streams to the first non-empty insert of the channel or directly to the output if all the inserts are empty. The panoramic and level controls are related to the audio stream only, as is the level meter. Press the CTRL key of the keyboard and click on a pan or level control to set it to its default value (respectively Centre and 0dB) The button on the top left of this slot, when on, activates the input “monitor” mode. This feature is made to get a preview of the incoming audio stream (once the level and pan settings applied). You can activate this mode on more than one channel (the different streams are then mixed together) BloXpander sends the incoming audio and MIDI streams whatever is the destination plug-in. This allows a simplified use of MIDI VST effects. Though, if the effect or instrument receiving the streams doesn’t send MIDI (or audio) data, the next insert or the output won’t receive anything. Since version 1.1.0, you can access an advanced properties panel from a left-click on MIDI and Audio inputs/outputs selectors. This panel is also an easier way to select a port using a “touch screen”. User manual 15 MIDI Input Properties Port selection Direct access to other properties panels of the current BloXpander channel (MIDI input, Audio input, MIDI output, Audio Output) A right click on “-” or “+” buttons can speed up the setting process! Click here to access the MIDI programs map. Properties of the selected link (green) or global properties if “Omni” mode is selected. The MIDI input Propriétés appliquées au lien sélectionné (vert) ou appliqué globalement Omni est properties panel issi lea mode complex and activé Click here to activate/deactivate « Omni » mode. Transposition. “Global” Transpose is applied to all channels while “Channel” Transpose is applied to the currently edited channel only. powerful tool intended for advanced users. Defined properties are specific to each of the 24 + 4 + 1 BloXpander strips. For example, you can select a same MIDI port on different strips and set different properties for each of these strips. There are a lot of possibilities offered by this module. For example, you can create note/velocity ranges and route MIDI channels as you want in order to control multiple plug-ins or external MIDI devices from a single instrument. In "Omni" mode, properties (located at the bottom of the panel) are globally applied to all 16 MIDI channels. This mode is the easiest to understand. To disable or enable "Omni" mode, just click on the large "Omni" bar. Once disabled, you can create links from your mouse and route MIDI input channels. A single input channel can be routed to multiple output channels. Similarly an output channel can receive messages from various input channels. 16 eaReckon BloXpander When “Omni” mode is disabled, the properties are specific to each link. To view and edit the properties of a link, you must select it by clicking on one of its ends. If multiple links are connected to the same pin, click on it until you access the properties of the desired link. CC Map (Continuous Controllers) It consists of 4 parameters per CC. The first one ("invert"), reverses the received values (Data2) of a specific CC and therefore virtually “reverses the direction” of a potentiometer, a fader or a pedal emitting CC messages. The second and third ones are used to define a “pass-through” range. Messages out of this range will be ignored. The last parameter can be used to modify the CC number. For example, you can control a parameter of your choice from your keyboard modulation wheel. Notes Here you can select a filter type and apply it to a specific note range. Currently available filters are: - NONE: No filter. PASS: Filter notes outside the defined range. FILTER: Filter notes within the defined range. Velocity As for notes, you can apply a filter to a velocity range. In addition to PASS and FILTER which work as defined previously, two additional filters are available: - LIMIT: If the velocity of a note is located outside the limits, the value of one of the two limits will be applied. - SCALE: This filter is a variant of "LIMIT", designed to reduce the allowed velocity range while attempting to preserve dynamics. Transposition These parameters are applied to all incoming notes, whatever the state of the links table. “Global” Transpose is applied to all channels while “Channel” Transpose is applied to the currently edited channel only. On the "MIDI Inputs" block (on the left), large buttons are an easier way to select a port using a touch screen while the selection menu remains a faster way to select a port using a mouse. User manual 17 MIDI Programs Map You access the « programs map » by clicking this button : Back to MIDI properties. Send all defined MIDI messages now. Each items of this grid is related to the MIDI Channel of an insert (or the selected MIDI output on the currently edited channel). You can assign up to 3 messages per cell: Bank Select / Program Change / All Notes Off. The « Bank Select » message will not be sent if it is not associated to a « Program Change » message. On the other hand, a « Program Change » can be sent without any defined « Bank Select ». An “All Notes Off” message can be sent whatever the circumstances. A red text in a cell indicates a problem in your settings (a partial « Bank Select » message or a “Bank Select” message without any “Program Change”, for example). Please click on a cell to configure it (popup menu). Note: as other MIDI properties, this « programs map » is related to the selected channel only. Different settings can be applied to each channel « Programs maps » are stored with scenes and subscenes. All defined MIDI messages will be automatically sent when calling a scene or a subscene. This feature is obviously useful if you have to manage a set of external MIDI devices. In this case, it may be interesting to dedicate one channel (with empty inserts) per MIDI device. The « Programs Map » can also be useful for GM plug-ins or VST Samplers/Romplers which have the possibility to store a large amount of samples in several patches that can be called from a Program Change MIDI message. 18 eaReckon BloXpander Audio Input Properties Port selection Direct access to other properties panels of the current BloXpander channel (MIDI input, Audio input, MIDI output, Audio Output) You can select which channel(s) will be sent to the first stereo pair of the first assigned insert (or to the audio output if no plugin is assigned in the selected channel) User manual 19 Inserts Each channel provides 6 inserts to load effects and instruments in the channel. The inserts of a channel are linked together from top to bottom. The first insert receives the incoming Audio and MIDI streams (as defined in the input slot). The next insert then receives the Audio and MIDI streams treated by the first one, etc… The last insert transmits the streams treated by the whole chain to the output (and auxiliary buses) Empty inserts are considered as direct links. This way, it’s not a problem to have empty inserts between assigned ones. A double-click on an empty insert will show the « Plug-ins Case » in order to let you choose the plug-in you want to assign to this insert. If a plug-in is already assign to an insert, a double-click will show the assigned plug-in and bring it to front. Once a plug-in loaded, a popup menu is available from the insert slot (from a right-click). Presets The content of the presets sub-menu depends on the amount of available presets. If the plug-in has only one preset available, you will have the possibility to save and load the state of the plug-in as an FXB formatted file. If the plug-in has more than one preset, just perform a left-click to activate the preset of your choice. It is possible to save all the presets as a bank (FXB file) or just the active preset (marked with a point) as an FXP file. 20 eaReckon BloXpander You can also rename the active preset in order to create custom banks. « Multi-Out » and « Sidechain » Some plug-ins have more than one input pair or/and more than one output pair. BloXpander provides advanced audio routing features to make use of these extra inputs and outputs. Please refer to the “Advanced Features” part of this manual to know more about these routing capabilities. Update plug-in screenshot The plug-ins are represented as a capture of their interface in both inserts and the « plug-ins case ». This picture is automatically created on the first launch of the plug-in into BloXpander. Though, during this first launch, the state of the plug-in interface may misrepresent it (for example, the plug-in may be in demo mode because it’s not authorized or activated yet, …). Then it’s possible to update the visual representation of the plug-in (in both the insert and the plug-ins case) by clicking on the “update screenshot” item of the insert menu. Remove Use this item to remove the plug-in from the selected insert. User manual 21 Aux Sends and Returns Every channel provides 4 aux sends grouped into one slot. Send Level Mute Pre / Post fader The green controls define “how much of” the processed audio stream is sent to the corresponding aux return. The numbered button on the left of each level control can be used to mute the aux send. The state of the button on the right of each level control defines if the aux send is affected by the output slot settings (“Pre fader” = Green / “Post fader” = Blue). The aux returns collect the audio streams sent from the aux sends of all the channels. A classic use of the aux sends/returns is the assignment of a reverb effect to one of the aux returns. Such an effect is usually very demanding on the computer resources. Having a reverb in an aux return instead of several instances of this same effect in various channels will provide both coherence and performance. 22 eaReckon BloXpander Output The output slot provides the final settings of a channel. As for the input slot, you will have access to controls over the panoramic and audio level. You can also assign a MIDI output port and Audio output channels. If your sound card or audio interface has more than one pair audio output channels, you can route the audio signal to the channels of your choice. If the audio output is set as “MASTER”, the processed audio stream will be route to and processed by the master bus (MASTER). In a similar manner, it is possible to route the processed MIDI stream to a specified port. If the MIDI output is set as “THRU”, the processed MIDI stream will be sent to the Main MIDI output port (cf. “Master Bus” part of this chapter) The top left button (de)activates the “Solo” mode. You can activate this mode on more than one channel. If this mode is activated on at least one channel, only the channels with this mode activated will be audible. The top right button (de)activates the « Mute » function. If one of the channel aux sends is active and set as « Pre-fader », the corresponding aux returns will receive an eventual audio signal, whatever the state of the mute button is. Audio Output Port Mute MIDI Output Port Solo User manual Pan Audio Output Level Level Meter 23 MIDI Output Properties Port selection Direct access to other properties panels of the current BloXpander channel (MIDI input, Audio input, MIDI output, Audio Output) Audio Output Properties Direct access to other properties panels of the current BloXpander channel (MIDI input, Audio input, MIDI output, Audio Output) Output Mode selection By default, all BloXpander channels are set in « Stereo Mode ». Since version 1.3.0, it is possible to select another output mode: MONO: a mono mix is sent to both left and right channels. Port selection MONO MIX TO ONE CHANNEL: this same mono mix is sent to the channel of your choice. The other channel remains silent. ONLY ONE CHANNEL: in this mode, the stereo signal is not mixed. One of the two channels is just muted. In MONO and MONO MIX TO ONE CHANNEL modes, the pan fader lets you define the proportion of left and right signals to be included in the mono mix. 24 eaReckon BloXpander Master Bus The master bus collects the audio streams coming from each channel (with an audio output set as “MASTER”). The 6 inserts of the master bus can be used to finalize the mix and adapt it to the context of diffusion (power amplification, studio monitors, headphones, …) The output slot of the master bus is slightly different compared to the channels output slots. It has 2 extra parameters : - ASIO Driver: here you can select an audio interface if more than one ASIO compatible audio interface is present on your system. Only one ASIO interface can be used. Mono / Stereo switch. Click here to call the ASIO control panel. User manual 25 « Computer hysteria » As any software, the plug-ins and the application itself consume the resources of your computer (cpu, memory, …). When the processor is too much solicited, the computer is no more able to process the audio streams fluidly. The processor solicitation mostly depends on your computer and audio interface specifications, as well as the loaded plug-ins. As a basic rule, you can’t get the same performances from both a netbook and a top notch desktop computer. It is advised to watch regularly the « hysteria » indicator that gives some information about how hard the processor is solicited. What can be done if the level of “computer hysteria” is too high ? 1. Close any connection to the internet or networks and deactivate temporarily your anti-virus software when using BloXpander (at your own risk – please skip this operation if you are not sure about its consequences). 2. Reduce the current sample rate (BloXpander system panel). 3. Set the ASIO buffer size to a higher value (from the ASIO control panel). Warning : this operation can significantly increase the audio latency. 4. If it’s relevant to your project, use the aux sends/returns instead of multiple instances of the same plug-in in channels 1 to 24. 5. Build a lighter version of your project (some plug-ins are very demanding on the computer resources). 26 eaReckon BloXpander The « Touch Zone » The small slots provide a nice way to get a global view of your projects. Though, performing a fine adjustment using the controls of these small slots isn’t an easy task, especially from a touch screen. The « Touch Zone » provides a way to precisely perform such an adjustment. This zone has been especially thought for the owners of a touch screen. To set the target of the touch zone, just click the name label on the top of a channel, or use a control on its input, output or aux sends slot. Once the target channel is set, you can adjust most of its settings from the touch zone. The touch zone also gives a quick access to some important functionalities of BloXpander (transport play, tempo, Live View, …). Use this button to switch to Live View (please read the dedicated chapter of this manual for more information about the Live View) Use this button to open (or close) the Big Display panel which features transport controls and an LCD emulation as described later in this manual. Tempo You can quickly set the tempo by clicking and dragging this label or by double-clicking it. Play button User manual 27 Chapter 2: The « Plug-ins Case » Description The plug-ins case has been thought to provide the fastest possible access to a plug-in of your choice. To reach the plug-ins case from the mixer view, click on the suitcase button: Click here to refresh the plug-ins case (for example, if a new plug-in has been installed during the session) If some plug-ins have never been analyzed, you can launch BloXcanner from this button. Enter a text here. Only the plugins with a name containing this text will be displayed. Information panel. Use this tree view to only display the plug-ins matching chosen criteria. Click here to ignore a plug-in and remove it from the plug-ins case. 28 Click here to close the plugins case. The plug-ins appear as pictures. A sealed “box” indicates that the plug-in has never been loaded into BloXpander. If a plug-in is marked as 32 or 64 (bit), it will not be natively loadable. In this case, jBridge is required to load it. Double-click on a picture to load a plug-in into the currently selected insert (yellow insert). eaReckon BloXpander Per-plug-in Options Some plug-ins may need to be loaded with specific options enabled so they work properly with BloXpander. These “workarounds” can be enabled from the plug-ins case by right-clicking on an item or by selecting an item and pressing the “Options” button: « Shell » plug-ins These special plug-ins are containers. Basically, a “shell” usually contains several plug-ins. After an analysis of your plug-ins performed by BloXcanner, the plug-ins contained in a shell are deployed in the plug-ins case, providing a direct access to them. The “shells” themselves are also available from the plug-ins case if no compatibility issue has been detected. If you double-click on a shell plug-in, a list of the contained plug-ins will be displayed so you can choose one to load. « Shells » are represented by this picture in the plug-ins case: User manual 29 Warning messages Sometimes, a warning message is displayed when you call a plug-in. This phenomenon occurs if the plug-in has never been analyzed by BloXcanner or if a compatibility issue has been detected. It is advised to perform an analysis of your plug-ins each time a significant change occurs (when a plugin has been updated, installed or uninstalled, for example). This way, some critical operations of your plug-ins are tested by BloXcanner and most compatibility issues are detected. Even if a plug-in is considered as compatible by BloXcanner, no warranty is provided regarding its stability once loaded into BloXpander. Though, eaReckon will use its best efforts to make the most possible plug-ins work into BloXpander. 30 eaReckon BloXpander Chapter 3: Libraries Description Libraries allow a custom organization of preset plug-ins. Each element of a library is made of a reference to a plug-in and the state of the plug-in at the moment when the element is created. You can create a library containing a same plug-in in various states or a set of plug-ins related to a musical style. You’re free to organize your libraries the way that suits your needs and habits. A drag ‘n drop functionality is available for libraries items. To use this feature, maintain the CTRL key pressed while clicking on the item you wish to move. User manual 31 Managing items of a library MODIFY AN ELEMENT Move to the right Move to the left Cancel modification Delete item Confirm replacement of this item by the currently selected insert (the yellow one). Use this text box to rename an item. Click here to show the list of available libraries. Click here to show the plug-ins case IMPORTANT NOTE : Perform a right-click on an existing element to modify it (you can move, rename or delete this element) Since version 1.4.0, it is possible to rename an item by pressing the ‘enter’ key during edition. Double-click to load this element into the current insert (yellow insert). The green button can be used to overwrite the edited item by the currently selected insert. If there are too many elements in a library, only a part of the library is shown. Then you can use these buttons to switch to the next or previous page of elements. Use this special element to add the content of the current (yellow) insert to the library. The current insert must not be empty. Click on this tab to show or hide the plug-ins panel. Note : these tabs will be available only if the screen resolution (or the window size) is not large enough to display both “Scenes” and “Plug-ins” panel. Cancel addition Confirm addition Use this text box to name the new item. The name of the plug-in is used by default. 32 ADD AN ELEMENT eaReckon BloXpander Managing libraries Create a new library (named as indicated in the editable text box) Libraries grid. Double-Click = Simple-Click = Load a library. (Current library = blue LED) Select a library (to rename or delete it). (Selected library = red LED) Rename the selected library. (marked with the Delete the selected library. (marked with the symbol) symbol) Show the current library (marked with a point) Quick edit If you want to quickly edit a library, please right-click on it and a dialog will appear on screen: User manual 33 Chapter 4: Sets, Scenes and Subscenes Description A « scene » corresponds to the state of the console (including routing and the state of the loaded plugins) saved after the construction of a project. In a live show situation, a scene could be a song. A double-click on a numbered (and named) slot is enough to switch from a scene to another. A « set » is a group of scenes. Going further with our “live show” example, a set could then be a playlist. And once the right set loaded, one of the musicians just have to double-click on a “scene” to load the complete state of BloXpander suiting the needs of the band for a specific song. The way to use the scenes panel is similar to the operation of the libraries panel. 34 eaReckon BloXpander Scenes MODIFY A SCENE Move to the right Move to the left Cancel modification Delete this scene Overwrite this scene with the current scene. Use this text box to rename the scene. Press the ‘enter’ key if you just want to rename a scene. Perform a right-click on an existing scene to modify it (you can move, rename, delete or overwrite this scene) Double-click to load this scene. Click here to show the list of available sets. Use this special element to add the current scene to the current set. If there are too many scenes in a set, only a part of the scenes is shown. Then you can use these buttons to switch to the next or previous page of scenes. Click here to clear the current scene. Cancel Confirm Use this text box to name the new scene. SAVE THE CURRENT SCENE User manual 35 Sets Sets grid. Double-Click = Simple-Click = Load a set. (The current set is marked with a point) Select a set (to rename or delete it). (The name of the selected set is displayed in an orange box). Create a new set (named as described in the editable text box) Click here to clear the current scene. Rename the selected set ( symbol) Delete the selected set ( symbol) Show the current set (yellow) Quick edit If you want to quickly edit a set, please right-click on it and a dialog will appear on screen: 36 eaReckon BloXpander Subscenes Up to 16 Subscenes can be saved in a Scene. A Subscene is a snapshot of the console state, including: - Inputs and outputs volume and pan levels - Monitor, Mute and Solo switches - Inserts Mute switches - MIDI filters settings - Audio inputs channels arrangement Calling a Subscene does not change the state of loaded plug-ins, active MIDI and Audio ports and generally everything that may require precious seconds to be changed. It is an instant procedure. While switching from a scene to another requires a temporary pause of the audio engine, calling a subscene is done immediately while the engine is running. For example, it is possible to set several channels and mute some of them in a subscene and different ones in another subscene or even set MIDI filters so your master keyboard controls a piano or an organ depending on the called subscene. Basically, it is then possible to instantly switch from an instruments/effects set to another one during a same song. You can store or call subscenes from the graphical interface or via MIDI messages. Controlling Subscenes from the graphical interface Store/Call modes This switch lets define the behavior of the numbered buttons. : Pressing a button will call a subscene (if it is available) : Pressing a button will store the current state of the console as a subscene. The color of a button indicates whether or not a subscene is available: Gray = Empty. Blue = Stored and available. Red = Currently being stored or called. Underlined = Last called subscene. User manual 37 Subscene options - Save plug-ins state with subscenes (global option). If this option is enabled, the plug-ins state will be stored and recalled with subscenes. If you don’t need your plug-ins to be updated with subscenes (but only update the console controls such as levels, pan, …) you can choose to not activate this option. Deactivating this option will drastically speed up subscene calls. - Insert subscene lock Instead of globally “lock” plug-ins’ state by deactivating the previously described global option, you can just lock the inserts of your choice. To do so, please right click on an insert and check the “Subscene Lock” item: 38 eaReckon BloXpander Scenes MIDI Control You can open or change a scene from your MIDI controller instead of having to divert your attention to your computer whilst you are playing. If the 'PRG CHG' button is pressed, any "Program Change" message received from the assigned MIDI input port will make BloXpander load the scene corresponding to the invoked program number. When this option is enabled, "Program Change" MIDI messages coming from this port are not forwarded to plug-ins or MIDI out ports. A delay (2 seconds) allows you to subsequently send multiple messages of this type without loading consecutive scenes. You can also assign two buttons to select a scene in the current set: - Click on one of the two buttons to request its assignment and then press a key or a momentary switch on your MIDI controller to confirm the assignment. - Repeat this operation using the other assignment button. Click on then select the Scene tab to access Scenes control settings. « Program Change » Mode Select the MIDI Channel to be used by the Program Change Mode Assignment buttons Use this box to select the MIDI input port to be used for Scenes and Subscenes MIDI control. You can then use the assigned controller’s elements to navigate within the current set (a red mask indicates which scene is currently selected). After 2 seconds of inactivity, the last selected scene will be loaded. If the selection mask is placed on the last loaded scene (red location), the operation will be cancelled and the current scene won’t be affected by any change. If you don’t have any MIDI controller, you can use your computer keyboard (may it be wireless or not) to select a scene the same way. Keyboard shortcuts are "shift + left arrow" and "shift + right arrow”. Selected scene User manual Last loaded scene 39 Subscenes MIDI Control Click on then select the Scene tab to access Scenes control settings. Use this box to select the MIDI input port to be used for Scenes and Subscenes MIDI control. Right click on a value label to erase or manually edit an assignment. You can call subscenes via « Program Change » MIDI messages. Please assign a MIDI channel to activate this option. Click on one of these buttons then perform an action on a key/switch of your MIDI controller to assign it. This feature accepts MIDI Notes and MIDI CC. Note: as for all MIDI assignment in BloXpander, it is possible to manually assign a MIDI message (and/or define the type of the used hardware control) instead of using the “MIDI learn” process. (see “How to assign a MIDI control”). 40 eaReckon BloXpander Chapter 5: Software configuration (system panel) The system panel from where you can configure BloXpander and the main external MDI controller is accessible from the eaReckon logo on the left of the interface : “Always On Top” Activate this switch to keep the Settings panel over other windows. The general configuration tab is made of 2 parts: General Settings and Plug-ins. User manual 41 General Settings Synchronization (IN) Activate « Sync In » to make BloXpander react to Synchronization related MIDI messages (MIDI Clock, …) incoming from the selected input port. You can define an offset to fine tune synchronization. “Sync In” and “Sync Out” can work concurrently. It is then possible to synchronize all your MIDI devices from a master controller. MIDI Tempo Control You can assign a MIDI control to the tempo tap function and/or another one to directly adjust the tempo value. Left Click = MIDI learn / Right Click = Manual Edition. Synchronization (OUT) Activate « Sync Out » if you want to send synchronization messages to open output MIDI ports (main controller in MC mode and MIDI output ports selected on output slots) Change the application language Select Info Slot mode Show the plug-ins names on the inserts slots. Allow/Disallow plug-ins transparency activation (space bar) Set the default ‘On Top’ property of plug-ins when they are loaded. Once a plug-in is loaded, you can change its ‘On Top’ property by clicking on Press this button to resize BloXpander’s main window to the minimal possible size. Enable Hot Keys (shortcuts) Change the sample rate. WARNING: this feature doesn’t work and/or may be problematic with some audio interfaces. Default Scene Save: Save the current content of BloXpander as the default scene. Load Now: Load the default scene. Auto-Load: With this option enabled, BloXpander will automatically load the default scene on startup. INFORMATION, SUPPORT TOOLS and EXPERT OPTIONS Opens a new panel which is described in the next chapter of this manual. Multicore CPU support By activating this option, BloXpander will make use of your Multicore CPU’s capabilities (if your CPU has multiple cores). Note: In some routing situations (deployed secondary outputs of a plug-in or sidechains), some channels will have to be processed first and their inserts will be processed the “classic” linear way. Also, some plug-ins do not work correctly when they are processed in a multi-threading context. Instead of deactivating the global “Multicore Support” option, you can then force these plug-ins to be linearly processed. This “per plug-in” option is available from the plug-ins case. 42 eaReckon BloXpander Plug-ins In this part of the system panel, you can specify in which directories your plug-ins are installed. Add a directory User-defined plug-ins directories Remove a directory Analyze (Scan) plug-ins (call BloXcanner) Ignored files list Validate selected file Each time a directory is added, it is strongly recommended to perform an analysis of your plug-ins (a « scan »). This analysis provides the information BloXpander needs to make the categorization of the plug-ins case relevant. It’s also a good way to provide more stability to the application that will inform you about the plug-ins having a compatibility issue with BloXpander. VST Plug-ins are files with a .DLL extension. Some files that are not VST plug-ins may have this extension and be located in the user-defined plugins directories. After a scan of your plug-ins, these non-VST files and the plug-ins with compatibility issues will be placed in the “ignored files list”. The “ignored files” don’t appear in the plug-ins case and won’t be analyzed again by BloXcanner. However, you can decide to validate an ignored file. This file will then appear in the plug-ins case. Though, loading this file may seriously affect BloXpander stability. User manual 43 About BloXcanner BloXcanner is the BloXpander plug-ins analysis tool. It is installed with BloXpander and you can call it from 2 buttons (represented by a same symbol) : The first one is located on the settings panel, as previously shown (“Analyze”). The second one is available from the plug-ins case but this one appears only if at least one plug-in needs to be analyzed. Once BloXcanner is launched, you can start the plug-ins analysis from one of its two available buttons : - Full scan : this mode makes BloXcanner scan all the plug-ins located in the user-defined plugins directories, except those appearing in the ignored files list. Update : this mode makes BloXcanner scan the plug-ins that haven’t been analyzed yet. If a new plug-in has been installed on your computer, please use the “Update” mode. If one of your plug-ins changed (consequently to an update, for example), please use the “Full Scan” mode. BloXcanner is a stand-alone executable file. If a problem occurs with a plug-in during a scan, BloXcanner may (or not) become unstable and won’t analyze the remaining unprocessed plug-ins. In such a case, please re-launch BloXcanner and press the “Update” button to continue the analysis (the problematic plug-in won’t be scanned again). Why this choice of a stand-alone analysis tool ? If a problem occurs during a scan, BloXcanner may become unstable, but in most cases BloXpander shouldn’t be affected. BloXpander opens an ASIO driver, MIDI ports, etc… If BloXpander “crashes”, these opened drivers won’t be closed correctly, and it’s usually advised to restart the computer (and lose a nice amount of time) in such a situation. If BloXcanner “crashes”, there’s a good chance BloXpander will continue to work correctly. In theory, you should even be able to play your favorite instrument loaded into BloXpander while BloXcanner is doing its job! (obviously, the overall performances won’t be optimal in this case) 44 eaReckon BloXpander Chapter 6: Information and Expert Options Panel This panel (introduced in version 1.4.0) provides tools that can be useful when detailed information about your system is needed (in the case of a support request, for example). This same panel also provides “expert options” to be used with care. These ‘expert’ options are not intended to be used as “classic” options. However, they can be useful in some situations to tweak the behavior of BloXpander on some specific setups. Please use these options only if you know what you are doing! Click on this menu item to create a full backup of your BloXpander’s data directory. Creating a backup regularly will avoid the lost of all your precious scenes and libraries in the case of a hard disk failure (for example). BloXpander depends on many external libraries (plug-ins, ASIO driver, …) and it is not always easy for the support team to know what is the cause of an eventual problem with BloXpander. If a support archive is requested by the support team, please click on ‘Support>Create Support Archive’ to create a ZIP archive containing a lot of information about BloXpander’s configuration, your hardware configuration, plug-ins, some log files, etc. These files are mostly text files so you can inspect their content before sending them by email. User manual 45 Chapter 7: “Big Display” A special window featuring large controls is available to control the transport section and display an LCD emulator. Even if BloXpander is not a sequencer, it has a tempo setting. Some plug-ins, such beat boxes, act indeed according to a given tempo. Since version 1.0.4, BloXpander also provides a way to control its transport. It may be useful for plug-ins featuring a “time line”. All the time related controls are available from the “Big Display”. Tempo You can quickly set the tempo by clicking and dragging this label, by double-clicking it or by using the ‘+’/’-‘ buttons. You can also set the tempo by “tapping” it. Time signature Click right or left to set the time signature. Loop at… Set last bar of the loop using these + and – buttons. The loop always starts at bar 1. (X = no loop) Current position Use these switches to display the panels of your choice. 46 LCD Emulator The role of this panel is described in the next chapter of this manual. Transport controls Opacity Control eaReckon BloXpander Chapter 8: Main MIDI controller (system panel) An external MIDI controller is efficient to control the console and the plug-ins more directly. Two kinds of MIDI controllers are supported by BloXpander: - « Basic » controllers. These controllers send MIDI messages when one their knobs of buttons are manipulated but they don’t make use of the MIDI messages they receive. Nowadays, some MIDI keyboards have assignable knobs, buttons and/or faders that can be used to control the BloXpander console or plug-ins. - Mackie Control compatible controllers. These controllers usually provide motorized faders, endless knobs (with leds indicator) and a plethora of advanced features. Whatever your controller is, you will have access to an undeniable comfort in the use of BloXpander once your main MIDI controller configured. In addition to the control of the console, an optimized control option of your plug-ins has been implemented. It works from only 8 potentiometers and 8 buttons (or keyboard notes) The 8 Buttons are assignable to desired plug-ins and are used to indicate which of these plug-ins must pass under the control of 8 potentiometers. Thus, you will have the opportunity to control up to 64 parameters (8 per plug-in). To avoid confusion due to the potentially important quantity of controlled parameters, an LCD display emulator has been implemented to show the name of the controlled parameters (you can enable/disable this window from the “Touch Zone”: ). Common settings When active (red), the incoming MIDI messages that are assigned to the main controller are also sent to the mixer. User manual Show and bring to front the plugins called from the « plug-ins call buttons » 47 Configuration using a « basic » controller This part of the manual describes an easy step-by-step procedure to assign a MIDI controller. For more information about MIDI assignments, please read the following chapter: “How to assign a MIDI control”. 2 3 1 Controller type and connection 1  Select the « BASIC » mode  Select the MIDI input port to which your MIDI controller is connected. 48 eaReckon BloXpander 2 Assignment to the console elements  Select the channel to which you want to assign components of your controller.  Click on the channel element and move or push the component of your controller that you want to assign to this element. (The semi-transparent elements are not assignable) If this component was already assigned to a console element, this element will lose its previous assignment.  Repeat the two previous steps for each item of the console that you want to control. Assignment to the plug-ins control 3  To assign a « plug-ins call button » or a « plug-ins control », click on it, then move or push the component of your controller that you want to assign. « Plug-ins controls » accept « Continuous Controller » (CC) MIDI messages only, while « Plug-ins call buttons » accepts CC and notes messages. « Plug-ins controls » User manual « Plug-ins call buttons » 49 Configuration using a Mackie Control compatible controller 2 1 Controller type and connection 1  Select the « MC Protocol » mode  Select the MIDI input port to which your MIDI controller is connected. 50 eaReckon BloXpander - 2 Assignment to the console elements  According to the Mackie Control protocol, very few elements are assignable when the "MC Protocol" mode is selected. However, you can customize the assignment of some functions by clicking on one of them and performing an action on a component of your external controller: Assign the buttons used to change the « virtual pots » target (You can control several kinds of console elements from the 8 virtual pots) Assign the button used to alternate between the control of the 24 BloXpander channels and the control of the Aux returns (+ eventually the Master bus – See below) Push down this button if your controller doesn’t have a 9th fader dedicated to the master bus. Plug-ins control Assign the buttons used to change the channels group under control. (this functionality allows the control of the 24 BloXpander channels from an external controller made of 8 strips) Activate or deactivate Time Code related messages generation. By deactivating this option, your controller will not have its time code display updated but BloXpander’s MIDI engine will be less stressed. Activate or deactivate Meters related messages generation. By deactivating this option, your controller will not have its meters updated but BloXpander’s MIDI engine will be less stressed. The « Select » buttons of your controller will be reserved for the plug-ins control. Pushing such a button will switch from the control of the console to the control of the plug-ins (if this button has been assigned to a plug-in) Then you can use the « virtual pots » to modify the plug-ins parameters. To switch back to the control of the console, push again the button assigned to currently controlled plug-in. Transport Since v1.4.0, BloXpander reacts to transport commands sent from the Main Controller (in MC PROTOCOL mode). BloXpander also (optionally) send the messages your controller needs to animate its meters and time code display. User manual 51 Saving the configuration of the main MIDI controller Once the main controller is configured, you can save its configuration using the « SAVE AS » button. This configuration will then appear in a list and will be callable from a simple click. Controllers configurations list Later it will be possible to update (« SAVE » button), rename or delete this configuration. Plug-ins control Your controller is now configured and you saved its configuration and you probably intuitively took the control over the console’s elements. The following is all about the way to control your plug-ins from your external MIDI controller. Assignment of a « plug-ins call button » to a plug-in 1. 2. Push the CTR button to assign a « plug-ins call button » to this plug-in. If CTR does not become blue, your external controller is probably not correctly configured (tip : are the MIDI ports correctly set ?) Push the « plug-ins call button » you want to assign to this plug-in (on the external controller) This action will assign the chosen “plug-ins call button” to this plug-in. If another plug-in was assigned to this button, it won’t be assigned anymore. Assignment finished ! You can now use the newly assigned « plug-ins call button » and the 8 « plug-ins controls » knobs to control the parameters of this plug-in. 52 eaReckon BloXpander Choice of the controlled parameters You can chose which parameter will be controlled by each knob or fader assigned to the “plug-ins controls” To do so, click the « PAR » button and a list of all the available parameters will appear. WARNING: some plug-ins don’t have any published parameter and this list may be empty. Click the « PAR » button to show or hide the parameters list If a knob or fader is assigned to a parameter, the bubble containing the « plug-ins control » number is colored in blue. You can click on the numbered bubbles to change the current assignments. Important : 1. 2. 3. You can’t assign a same « plug-ins control » to several parameters. A same parameter can’t be controlled by several « plug-ins controls ». The plug-in specific assignments are automatically saved and will be used the next time this plugin is loaded. 4. On a modification of these assignments, if more than one instance of this same plug-in are present, the new assignments are propagated to all the instances of the plug-in. User manual 53 Chapter 9: How to assign a MIDI control Some functions can be controlled from an external MIDI controller: - Console and plug-ins parameters (Main Controller) - Scenes et Subscenes (Scenes MIDI Control) - Synchronization and Tempo. In order to avoid confusion and mishandlings, all MIDI assignments are configurable from the system panel. Since the first version of BloXpander, MIDI assignments can be done by performing a MIDI learn procedure. For information, this procedure consists to click on a button (BloXpander’s interface) and then send the MIDI message to be assigned. Since version 1.3.0, it is possible to manually edit a MIDI assignment by right-clicking on a button or its value label. In the case of the Main Controller in Basic mode, you can also right-click on the grid to edit an element. The popup menu features three options: - MIDI LEARN (same action as left-clicking on a button) - EDIT PROPERTIES which will be detailed later in this chapter. - ERASE. 54 eaReckon BloXpander Manual edition of MIDI properties Clicking « EDIT PROPERTIES » on the previously described popup menu will bring an edit form from which you can manually edit an assigned MIDI message as well as the type of hardware control in use. Control type BloXpander cannot have any information about the hardware control which is used to send the assigned MIDI message (is it a knob, a switch, a fader, … ?). For a more relevant response of BloXpander, it is recommended to manually define the “Control Type” so BloXpander knows what to do with the MIDI messages sent by this control. Four control types are available: Push/Release: a switch or a key which sends a MIDI message when pressed (Value > 0 or Note On) and another one when released (Value = 0 or Note Off). Push Only: a switch which sends a unique message when it is pressed. Two States Switch: this uncommon type of control may be a rocker switch or any control that has two positions. This control sends a message when its state is changed. The Data2 value of this message depends on the new position (positive = ‘On’ or null=’Off’). MID Event Type Note or CC. CC or Note number (MIDI Data1 value) MIDI Channel Special (Data2): instead of an undetermined Data2 value (velocity or CC value), this control sends a specific Data2 value (from 1 to 127) when it is pressed and 0 when it is released. A same CC number can then be used to control several things. Knob or Fader: if the Control Type box displays ‘Knob or Fader’ (grayed), only a knob or a fader can be used because a key or a switch would not be suitable. CC value or Note velocity This parameter is available only if the Control type is set to Special (Data2) Note: You cannot assign any type of control to all parameters. The assignment possibilities have been studied for each parameter in order to avoid confusion. The same rule applies to data ranges. For example, in the case of the Main Controller in MC Protocol mode, you cannot assign a note if its number is lesser than 40 because notes 0 to 40 are already used by other controls (cf. Mackie Control protocol). User manual 55 Chapter 10: Sysex Messages Sysex (System Exclusive) messages let you backup and restore the state of a MIDI device. While the amount of available internal presets is often limited by the memory of external MIDI devices, Sysex messages provide a way to store a virtually unlimited amount of presets. Since version 1.1.0, BloXpander integrates an easy to use Sysex tool so you can receive, store and send Sysex messages. This tool isn’t a complete and complex Sysex Librarian but at least it provides an easy way to manage your external MIDI devices pool. Here's how to use it: 1. Select a MIDI Input port and press « LISTEN ». Input MIDI port selection Sysex listening mode (de)activation 2. Request a Sysex dump from your external MIDI device which is connected to the selected MIDI input port (please check the manual of your MIDI device for more information). An indication of the dump progression appears in the small green frame. Warning ! The incoming Sysex buffer is cumulative. If more than one Sysex is received once the LISTEN button pressed, all these messages will be saved in a same file during the next step. If you want to separately save more than one Sysex, please deactivate and reactivate listening mode between each dump. 56 eaReckon BloXpander 3. Give a name to the received Sysex then save it to the library. 4. Your Sysex message(s) is (are) now saved in the library. Sysex are ordered by manufacturer name. Click here to destroy the selected Sysex (you cannot undo this operation) User manual Use this edit box and the associated button to rename the selected Sysex. You can import .SYX files in the library. 57 5. In order to send one or more Sysex messages to one or more external MIDI devices, simply drag and drop desired files from the library to MIDI output ports then press « SEND SELECTED » or « SEND ALL ». Should you have some problems with the emission of a Sysex message to a specific external MIDI device, please adjust buffer size and delay (this delay occurs each time a buffer is sent). 58 eaReckon BloXpander Chapter 11: Live View During live situations, we do not always need to fine tune the content of a scene and just want to quickly access an essential set of large enough controls. The Live View has been thought to provide such a possibility but can also be used to easily manage sets and scenes. MIDI Panic Press this button to send a MIDI Panic stream to plug-ins and MIDI outputs. “Computer Hysteria” This indicator will turn to red if the “hysteria” ration is greater than 50% Close BloXpander Switch to Console View Full Screen / Windowed SETS Double-click to load a set. The current set is marked with a blue rectangle. SUBSCENES Click to call a subscene. The last called subscene appears in yellow and its number is underlined. Available subscenes appears in blue. SCENES Double-click to load a scene. The last loaded scene is marked with a blue square. TIME These controls are similar to those found on the “Big Display”. Please read the chapter related to the “Big Display” for more information. MIDI (in) activity Master Record Master Pan Master Volume Master level meter User manual 59 Managing scenes and sets from the Live View From the Live View, you can move or copy a scene to another set, rename/delete scenes and sets and finally change the order of the scenes in a set. COPY/MOVE A SCENE TO ANOTHER SET To move a scene to another set, please press and hold the CTRL key and perform a drag n drop action from the scene list to the set list. To copy a scene to another set, please press and hold CTRL+ALT keys and perform a drag n drop action. EDIT A SET Right-click on a set to rename or delete it. 60 EDIT A SCENE Right-click on a scene to rename, delete it or change its index in the set. eaReckon BloXpander Chapter 12: Advanced features Visual groups BloXpander has been thought to limit the amount of overlapping windows in order to improve the interface visibility. However, each loaded plug-in is placed into a new window that you can show or hide. Manipulating these windows the classic way can be time consuming in a situation that requires fast access to the plug-ins interface. The visual groups are an answer to this problem. There are 9 visual groups. To store a Visual group, which basically is the current disposition of the plug-ins on-screen (visibility, location), hold down the CTRL+SHIFT keys, and then press one of the keys 1 to 9 (not the numeric keypad numbers keys nor functions F1 to F9 keys !) You can then call a Visual group by holding CTRL and pressing the previously assigned number key. The visual group #0 can’t be assigned. When this visual group is called, all the visible plug-ins are hidden, giving an access to the whole console. A “scene” includes Visual groups thus defined. Using visual groups, it is for example possible to quickly switch from the plug-ins assigned to a channel to those assigned to another channel, view the effects of the same type, or even quickly view the plug-ins involved in the treatment of a particular instrument... Plug-ins transparency In some situations, you may want to see the state of the console for a few seconds, without having to hide the visible plug-ins you’re working on. Pressing the SPACE BAR, the visible plug-ins will become transparent. To give back an opaque aspect to all the plug-ins, press the SPACE BAR again. Inserts drag-and-drop In some situations, a same plug-in must be assigned to several inserts, or moved from an insert to another. To copy an insert (i.e. the assigned plug-in and its state), hold down CTRL + SHIFT keys and then drag-and-drop into the destination insert. To move the content of an insert slot, hold down the CTRL key and then drag-and-drop into the destination insert. User manual 61 Using the extra outputs of a plug-in (« Multi Out ») Some plug-ins have more than 2 outputs. The first 2 outputs (2 mono outputs or 1 stereo pair) of the plug-ins are always routed to the next plug-in in the chain or the output of the channel. By default, the other outputs (if they are available) are routed the same way as the first pair (« stereo downmix ») However, you can assign these extra outputs to the other channels of the console. If a plug-in has more than 2 outputs, an indicator appears on the insert slot this plug-in is assigned to. This plug-in has more than 2 mono outputs or more than 1 stereo output. In this case, the insert popup menu has an extra item (« MultiOut”) List of the plug-in outputs. (the first stereo pair is grayed because it is not assignable) List of the assignable channels The « grayed » channels are not assignable. The unauthorized assignments are impossible or problematic (an audio loop could occur, …) Once the outputs of a plug-in assigned to another channel, you can’t assign audio inputs to this channel. The text ‘VST’ is then displayed in blue on the input slot of this channel, and the inputs popup menu is replaced by the name the plug-ins outputs assigned to this channel : 62 eaReckon BloXpander You can assign different outputs of various plug-ins to a same channel. Using the extra inputs of a plug-in (« Sidechain ») Some plug-ins have more than 2 inputs. We will call such a plug-in a “sidechain capable” plug-in. A sidechain capable plug-in may be, for example, a compressor processing the signal coming from its first inputs pair, depending on the signal coming from its second inputs pair. Such a plug-in is identified by the presence of an indicator on the insert slot it is loaded in. This plug-in has at least one “SideChain” At least one “sidechain capable” plug-in is loaded into BloXpander. The plug-in features multiple outputs You can assign the first outputs pair of the other plug-ins to the additional inputs of a sidechain capable plug-in. If at least one « sidechain capable » plug-in is loaded into BloXpander, all the non empty inserts have an extra item in their popup menu. List of « sidechain capable » plug-ins User manual List of available extra inputs. 63 Ferret 4x4 (free plug-in) If the BloXpander routing capabilities still doesn’t suit your needs, a free plug-in by eaReckon has been made to go even further. This plug-in, with its 4 inputs pairs and 4 outputs pairs, is available from www.eareckon.com It is recognized by BloXpander as a « Multi-Out » « Sidechain capable » plug-in providing extended routing options. Even if this free plug-in should work in most of the3rd party VST host applications, it’s been especially design to work with BloXpander. Master Record It is possible to record the master bus signal as a stereo WAV file. This functionality can be interesting in the context of a rehearsal to record an idea, for example. However, we cannot consider this option as a replacement for a full-featured recorder but more modestly as a basic practical tool. You can record a new file by pressing the button on the Live View (“Master” section) or the button located on the master strip of the console (Console View). Press one of these button again to stop recording. Note 1: The sample rate of the WAV file will be the same as the ASIO Driver sample rate. Note 2: The recording will be automatically stopped each time the audio engine must restart (when (un)loading a plug-in, for example). In this case, you can record a new file by pressing or again. 64 eaReckon BloXpander Chapter 13: How to load both 32 and 64 bit plug-ins (with jBridge) Since version 1.4.0, BloXpander is delivered as a 32-bit and a 64-bit application. However, BloXpander x32 and BloXpander x64 are two separate applications. For practical reasons, they do not share the same data folder, … BloXpander x32 can natively load 32-bit plug-ins only while BloXpander x64 can natively load 64-bit plug-ins only. jBridge is a software wrapper for VST plug-ins which provides necessary tools to load 32-bit VST plug-ins in a 64bit VST host (and vice versa). BloXpander provides “direct support” for jBridge which means that once jBridge is installed on your system, BloXpander automatically detects its presence and allows both 32-bit and 64-bit VST plug-ins to be loaded, whatever the version (x32 or x64) of BloXpander you are using. This is why you do not have to use the “jBridger” to create wrapped versions of your plug-ins prior to get them working in the context of BloXpander. Just install jBridge and you are ready to go… Please note that jBridge is not an eaReckon product and thus it is not delivered with BloXpander. jBridge is developed by João Fernandes and can be purchased from http://jstuff.wordpress.com/ at a very affordable price. To enable or disable jBridge’s support, please use the dedicated switch in the settings panel: User manual 65 Appendix 1: Keyboard Shortcuts CTRL + SHIFT + SPACE BAR CTRL +  or  SHIFT +  or  CTRL + DRAGDROP (De)Activate the plug-ins transparency Change the channels page Select and load a scene (SHIFT +  to cancel loading) Change the location of a library item or scene SHIFT + F4 SHIFT + DEL Minimize BloXpander Unload plug-in in the selected insert (yellow insert) F1 F2 F3 F5 F6 Show the User Manual Show / Hide the system panel Show / Hide the plug-ins case Show / Hide the plug-ins panel Show / Hide the scenes panel F8 ALT+F8 F9 Center the selected plug-in (loaded into the yellow insert) Center all plug-ins Disable/Enable level meters and the “hysteria meter” F11 MIDI Panic CTRL + SHIFT + 1..9 CTRL + 1..9 CTRL + 0 Store a visual group Call a visual group Hide All Plug-ins NUMPAD 1..9 CTRL+ NUMPAD 0..6 Call Subscene 1..9 Call Subscene 10..16 SHIFT + ESC Unlock User Input (when the ‘Please Wait’ mask is active) Note: This shortcut should be used only if a problem occurred while loading a plug-in (if you need to get the control back on the interface). 66 eaReckon BloXpander Appendix 2: End User License Agreement (EULA) IMPORTANT LEGAL NOTICE CAREFULLY READ THE FOLLOWING LEGAL AGREEMENT BEFORE YOU START USING THE SOFTWARE. BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE, YOU CONSENT TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS AND CONDITIONS OF THIS AGREEMENT, CANCEL THE INSTALLATION OF THE SOFTWARE AND DO NOT INSTALL THE SOFTWARE. AFTER ACCEPTING THE LICENSE AGREEMENT YOU HAVE THE RIGHT TO USE THE SOFTWARE IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THIS AGREEMENT. 1. DEFINITIONS 1.1 Software means software including any Updates, User Manual and related materials. 1.2 the Rightholder (owner of all rights, whether exclusive or otherwise to the Software) means Philippe DECUYPER, a registered “auto-entrepreneur” as defined by the laws of France. The Rightholder may be referenced as “eaReckon”, a trademark of Philippe DECUYPER. 1.3 Computer(s) means hardware(s), including personal computers, laptops, workstations, or other electronic devices for which the Software was designed where the Software will be installed and/or used. 1.4 End User (You/Your) means individual(s) installing or using the Software on his or her own behalf or who is legally using a copy of the Software; or, if the Software is being downloaded or installed on behalf of an organization, such as an employer, "You" further means the organization for which the Software is downloaded or installed and it is represented hereby that such organization has authorized the person accepting this agreement to do so on its behalf. For purposes hereof the term "organization" without limitation, includes any partnership, limited liability company, corporation, association, joint stock company, trust, joint venture, labor organization, unincorporated organization, or governmental authority. 1.5 Partner(s) means organizations or individual(s), who distributes the Software based on an agreement and license with the Rightholder. 1.6 Update(s) means all upgrades, revisions, patches, enhancements, fixes, modifications, copies, additions or maintenance packs etc. 1.7 User Manual means user manual, administrator guide, reference book and related explanatory or other materials. 2. GRANT OF LICENSE The Rightholder hereby grants You a non-exclusive license to store, load, install, execute, and display (to “use”) the Software provided You comply with all terms and conditions of this EULA. 2.1. INSTALLATION You may install and use the Software on more than one computer only if these computers form a single production unit or constitute separate workstations necessary for the task at hand and belong to the User manual 67 same owner. The number of concurrent installations is limited by the authorization process and this number may be changed without notice. 2.2 COPY You have the right to make a copy of the Software solely for back-up purposes and only to replace the legally owned copy if such copy is lost, destroyed or becomes unusable. This back-up copy cannot be used for other purposes and must be destroyed when You lose the right to use the Software or when Your license is terminated for any reason according to the legislation in force in the country of Your principal residence or in the country where You are using the Software. 2.3 NO RENTAL You may not rent, sell, lease or lend, the Software. You may not modify or create derivative works based on the Software in whole or in part. You may not permit third parties to benefit from the use of functionality of the Software through a timesharing, service bureau or other arrangement. 2.4 TRANSFER You may move the Software to a computer which You own other than the computer on which the Software was originally installed provided the provisions of Item 2.1 are complied with. You may not transfer the Software or this EULA to another End User. Exceptions may be granted at our discretion if You request such consent prior to concluding arrangements with the party interested in acquiring the Software and EULA. 2.5 NOT FOR RESALE SOFTWARE Software identified as “Not for Resale”, “NFR”, "Evaluation Copy", or “Demo” is collectively referred to herein as “Demo Software”. Only Software which is registered with the Rightholder will be fully functional and You are granted the warranties and remedies herein only with respect with to registered Software. All other Software not registered will also be deemed Demo Software. Notwithstanding anything to the contrary herein, Demo Software: (i) may not be used for any purpose other than demonstration, test or evaluation; (ii) will not have all the functionality or features of the registered Software; (iii) is provided with no representations or warranties whatsoever, but is provided solely on an “AS IS” basis; and (iv) will not be provided any support or maintenance, and You will receive no upgrades, updates or supplements for the Demo Software. Furthermore, notwithstanding anything to the contrary herein, You are not entitled to any remedies, monetary or replacement, with respect to Demo Software provided to You. Although the Demo Software does not have all the rights of the fully registered Software, You nevertheless agree to be bound by any obligation and acknowledgement herein which is applicable to any Demo Software. 3. TERMS OF USE You may only use the Software only for the purpose of composing musical arrangements and giving live performances. 68 eaReckon BloXpander 4. LIMITATION ON REVERSE ENGINEERING, DECOMPILING, COPYING AND DISASSEMBLY You may NOT reverse engineer, decompile, copy or disassemble the Software. 5. TERMINATION Without prejudice to any other remedy in law or in equity that the Rightholder may have, in the event of any breach by You of any of the terms and conditions of this Agreement, the Rightholder shall at any time without notice to You be entitled to terminate this License to use the Software without refunding the purchase price or any part thereof. 6. CONSENT TO USE OF DATA You agree that the Rightholder and its affiliates may collect, store and use information about You as a person including Your name, address, email address and payment history, and Your computer as part of registration and/or authorization process and to provide support services related to the Software. The Rightholder will take customary industry measures to assure that the information stored in the Rightholder’s database about You and Your computer cannot be used to identify You or Your Computer. The Rightholder may engage other companies and individuals (“subcontractors”) to perform functions on its behalf, such as payment processing, order fulfilment, marketing programs and customer service. The Rightholder may share Your information with such subcontractors in order to perform these and other functions. The Rightholder also may transfer this information to a third party who purchases eaReckon or the division distribution of the Software. For more detailed information on the collection, use and transfer of Your personal information, and for information on how to opt out of or unsubscribe from the communications described above, please read the eaReckon privacy policy on the eaReckon website (http://www.eareckon.com). 7. UPGRADES – UPDATES – SUPPLEMENTS This EULA applies to upgrades, updates or supplements to the original Software provided by the Rightholder, unless other terms are provided along with the upgrade, update or supplement. Such upgrades, updates and supplements may include a separate end user license agreement (“Component Agreement”) which You must review and agree to before using any such upgrade, update or supplement. In the event of any inconsistencies between this EULA and any Component Agreement, the terms of this EULA shall control. 8. OWNERSHIP The Software is protected by copyright and other intellectual property laws and treaties. The Rightholder or its suppliers own the title, copyright, and other intellectual property rights in the Software. Any copy of the Software You make must contain the same proprietary notices as contains in the original copy delivered to You. 9. LIMITED WARRANTY AND DISLCAIMER User manual 69 9.1 You acknowledge, accept and agree that no software is error free and You are advised to back-up the Computer, with frequency and reliability suitable for You. 9.2 The Rightholder does not provide any guarantee that such-and-such 3rd party product (a “plug-in”, for example) will work correctly with the Software. 9.3 THE SOFTWARE IS PROVIDED "AS IS" AND THE RIGHTHOLDER MAKES NO REPRESENTATION AND GIVES NO WARRANTY AS TO ITS USE OR PERFORMANCE. EXCEPT FOR ANY WARRANTY, CONDITION, REPRESENTATION OR TERM THE EXTENT TO WHICH CANNOT BE EXCLUDED OR LIMITED BY APPLICABLE LAW THE RIGHTHOLDER AND ITS PARTNERS MAKE NO WARRANTY, CONDITION, REPRESENTATION, OR TERM (EXPRESSED OR IMPLIED, WHETHER BY STATUTE, COMMON LAW, CUSTOM, USAGE OR OTHERWISE) AS TO ANY MATTER INCLUDING, WITHOUT LIMITATION, NONINFRINGEMENT OF THIRD PARTY RIGHTS, MERCHANTABILITY, SATISFACTORY QUALITY, INTEGRATION, OR APPLICABILITY FOR A PARTICULAR PURPOSE. YOU ASSUME ALL FAULTS, AND THE ENTIRE RISK AS TO PERFORMANCE AND RESPONSIBILITY FOR SELECTING THE SOFTWARE TO ACHIEVE YOUR INTENDED RESULTS, AND FOR THE INSTALLATION OF, USE OF, AND RESULTS OBTAINED FROM THE SOFTWARE. WITHOUT LIMITING THE FOREGOING PROVISIONS, THE RIGHTHOLDER MAKES NO REPRESENTATION AND GIVES NO WARRANTY THAT THE SOFTWARE WILL BE ERROR-FREE OR FREE FROM INTERRUPTIONS OR OTHER FAILURES OR THAT THE SOFTWARE WILL MEET ANY OR ALL YOUR REQUIREMENTS WHETHER OR NOT DISCLOSED TO THE RIGHTHOLDER. 10. EXCLUSION AND LIMITATION OF LIABILITY TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE RIGHTHOLDER OR ITS PARTNERS BE LIABLE FOR ANY SPECIAL, INCIDENTAL, PUNITIVE, INDIRECT, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING, BUT NOT LIMITED TO, DAMAGES FOR LOSS OF PROFITS OR CONFIDENTIAL OR OTHER INFORMATION, FOR BUSINESS INTERRUPTION, FOR LOSS OF PRIVACY, FOR CORRUPTION, DAMAGE AND LOSS OF DATA OR PROGRAMS, FOR FAILURE TO MEET ANY DUTY INCLUDING ANY STATUTORY DUTY, DUTY OF GOOD FAITH OR DUTY OF REASONABLE CARE, FOR NEGLIGENCE, FOR ECONOMIC LOSS, AND FOR ANY OTHER PECUNIARY OR OTHER LOSS WHATSOEVER) ARISING OUT OF OR IN ANY WAY RELATED TO THE USE OF OR INABILITY TO USE THE SOFTWARE, THE PROVISION OF OR FAILURE TO PROVIDE SUPPORT OR OTHER SERVICES, INFORMATON, SOFTWARE, AND RELATED CONTENT THROUGH THE SOFTWARE OR OTHERWISE ARISING OUT OF THE USE OF THE SOFTWARE, OR OTHERWISE UNDER OR IN CONNECTION WITH ANY PROVISION OF THIS AGREEMENT, OR ARISING OUT OF ANY BREACH OF CONTRACT OR ANY TORT (INCLUDING NEGLIGENCE, MISREPRESENTATION, ANY STRICT LIABILITY OBLIGATION OR DUTY), OR ANY BREACH OF STATUTORY DUTY, OR ANY BREACH OF WARRANTY OF THE RIGHTHOLDER OR ANY OF ITS PARTNERS, EVEN IF THE RIGHTHOLDER OR ANY PARTNER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. YOU AGREE THAT IN THE EVENT THE RIGHTHOLDER AND/OR ITS PARTNERS ARE FOUND LIABILE, THE LIABILITY OF THE RIGHTHOLDER AND/OR ITS PARTNERS SHALL BE LIMITED BY THE COSTS OF THE SOFTWARE. IN NO CASE SHALL THE LIABILITY OF THE RIGHTHOLDER AND/OR ITS PARTNERS EXCEED THE FEES PAID FOR THE SOFTWARE TO THE RIGHTHOLDER OR THE PARTNER (AS MAY BE APPLICABLE). NOTHING IN THIS AGREEMENT EXCLUDES OR LIMITS ANY CLAIM FOR DEATH AND PERSONAL INJURY. FURTHER IN THE EVENT ANY DISCLAIMER, EXCLUSION OR LIMITATION IN THIS 70 eaReckon BloXpander AGREEMENT CANNOT BE EXLUDED OR LIMITED ACCORDING TO APPLICABLE LAW THEN ONLY SUCH DISCLAIMER, EXCLUSION OR LIMITATION SHALL NOT APPLY TO YOU AND YOU CONTINUE TO BE BOUND BY ALL THE REMAINING DISCLAIMERS, EXCLUSIONS AND LIMITATIONS. 11. THIRD PARTY LICENSES The Software may include some software programs that are licensed (or sublicensed) to the user under the Mozilla Public License 1.1 (MPL 1.1 – Mozilla Foundation) or other similar free software licenses which, among other rights, permit the user to copy, modify and redistribute certain programs, or portions thereof, and have access to the source code ("Open Source Software"). If such licenses require that for any software, which is distributed to someone in an executable binary format, that the source code also be made available to those users, then the source code should be made available by sending the request to info[AT]eareckon[DOT]com or the source code is supplied with the Software. If any Open Source Software licenses require that the Rightholder provide rights to use, copy or modify an Open Source Software program that are broader than the rights granted in this Agreement, then such rights shall take precedence over the rights and restrictions herein. 12. GOVERNING LAW This Agreement will be governed by and construed in accordance with the laws of France without reference to conflicts of law rules and principles. Any dispute arising out of the interpretation or application of the terms of this Agreement or any breach thereof shall, unless it is settled by direct negotiation, be settled by in the Tribunals of Lille, France. 13. ENTIRE AGREEMENT – SEVERABILITY – NO WAIVER This Agreement is the entire agreement between You and the Rightholder and supersedes any other prior agreements, proposals, communications or advertising, oral or written, with respect to the Software or to subject matter of this Agreement. You acknowledge that You have read this Agreement, understand it and agree to be bound by its terms. If any provision of this Agreement is found by a court of competent jurisdiction to be invalid, void, or unenforceable for any reason, in whole or in part, such provision will be more narrowly construed so that it becomes legal and enforceable, and the entire Agreement will not fail on account thereof and the balance of the Agreement will continue in full force and effect to the maximum extent permitted by law or equity while preserving, to the fullest extent possible, its original intent. No waiver of any provision or condition herein shall be valid unless in writing and signed by You and an authorized representative of the Rightholder provided that no waiver of any breach of any provisions of this Agreement will constitute a waiver of any prior, concurrent or subsequent breach. The Rightholder’s failure to insist upon or enforce strict performance of any provision of this Agreement or any right shall not be construed as a waiver of any such provision or right. User manual 71 14. CONTACT INFORMATION Should You have any questions concerning this Agreement, or if You desire to contact the Rightholder for any reason, please contact: Philippe DECUYPER (registered as an « auto-entrepreneur » - SIRET 518.286.794.00020) E-mail : info[AT]eareckon[DOT]com Web site : www.eareckon.com 72 eaReckon BloXpander Appendix 3: Third-party code Third-party code was used during BloXpander development. Delphi ASIO & VST Project Some files of The Delphi ASIO & VST Project were used during the development of BloXpander. Note: The source code of this 3rd party library was used under the terms of the Mozilla Public License Version 1.1 License: MPL 1.1 or LGPL 2.1 with linking exception. The contents of this library are subject to the Mozilla Public License Version 1.1 (the "License"); you may not use this library except in compliance with the License. You may obtain a copy of the License at http://www.mozilla.org/MPL/ Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. Alternatively, the contents of this library may be used under the terms of the Free Pascal modified version of the GNU Lesser General Public License Version 2.1 (the "FPC modified LGPL License"), in which case the provisions of this license are applicable instead of those above. The initial developer of this code is Tobias Fleischer and Christian-W. Budde, based on a code snipped by Frederic Vanmol. Portions created by Christian-W. Budde are Copyright (C) 2003-2009 by Christian-W. Budde. All Rights Reserved. Contributors: Christian-W. Budde Tobias Fleischer Chris Horton Frederic Vanmol Maik Menz Tobias Erichsen Norbert Stellberg Marco Spies Benjamin Rosseaux Salih Sertkaya Daniel Terhell User manual 73 Delphi MIDI I/O Components Some files of Delphi MIDI I/O Components were used during the development of BloXpander. Note: The source code of this 3rd party library was used under the terms of the Mozilla Public License Version 1.1 License: Version: MPL 1.1/GPL 3.0/LGPL 3.0 The contents of this file are subject to the Mozilla Public License Version 1.1 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.mozilla.org/MPL/ Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. The Original Code is MIDI constants. The Initial Developer of the Original Code is David Churcher. Portions created by the Initial Developer are Copyright (C) 1997 the Initial Developer. All Rights Reserved. Contributor(s): turboPASCAL < http://www.delphipraxis.net/user13047.html > Manuel Kroeber < https://bitbucket.org/h4ndy/midiio-dev > Alternatively, the contents of this file may be used under the terms of either the GNU General Public License Version 3 or later (the "GPL"), or the GNU Lesser General Public License Version 3 or later (the "LGPL"), in which case the provisions of the GPL or the LGPL are applicable instead of those above. If you wish to allow use of your version of this file only under the terms of either the GPL or the LGPL, and not to allow others to use your version of this file under the terms of the MPL, indicate your decision by deleting the provisions above and replace them with the notice and other provisions required by the GPL or the LGPL. If you do not delete the provisions above, a recipient may use your version of this file under the terms of any one of the MPL, the GPL or the LGPL. 74 eaReckon BloXpander