VST-AU Blofeld Editor User Manual

Transcription

1 VST-AU Blofeld Editor User Manual Note that information found here is specific to product and synsizer model(s) it was made for. For information that is common and shared across all products, and for DAW Host Setup information, please see Setup Guide. For more information regarding this product and pricing please see Product Details pa ge. Table of Contents - Introduction Requirements Physical Connections Installation Mac Windows - Product Activation Setting up Synth Using The Graphical User Interface The Main User Interface View The MIDI Setup View The MIDI Monitor View The Patch Manager View The Multi Manager View - Working With Patches and Banks Loading and Saving Sysex Patches and Banks MIDI Implementation Chart Getting Additional Support 1 / 30

2 - License Agreement Disclaimer Introduction The VST-AU Blofeld Editor is a real-time MIDI synth editor that allows you full control of every parameter of sound on Waldorf Blofeld keyboard and desktop model synsizers. It is also a complete librarian tool that allows you to view and manage all patch and bank data on modern computing platforms and applications, in smart and efficient ways. Now you can utilize your Blofeld to its full potential in new and interesting ways, and build lasting and meaningful patches that will bring new life to your music. ou can manage, view and edit all your patches on computer itself without hassle of manual dumps. All parameters are fully automatable using your favorite VST or AU capable DAW host, giving you ability to visually program Blofeld to your music in host sequencer. This ability to model your synth patches in real-time, inside your main music production environment is part of what makes VST-AU Blofeld Editor unique when compared to or hardware synth editors. ou may also use standalone application if you do not need to work inside host or if your DAW host is not supported. Please check DAW Host Support chart on web site product page for details. The VST-AU Blofeld Editor will be furr referred to in this manual as 'Editor'. Any 32 bit or 64 bit VST or Audio Unit DAW Host will be furr referred to in this manual as ' Host '. The Waldorf Blofeld synsizer models may be furr referred to in this manual as ' Synth '. This editor will work on Waldorf Blofeld keyboard and desktop model synsizers running OS version 1.16B2, or latest OS version 1.22 firmware. 2 / 30

3 It's a Complete Synth Editor The VST-AU Blofeld Editor is a visual editor allowing you to view and edit every parameter of Waldorf Blofeld synsizer. Here's just some of amazing and useful features Editor offers: - Easily see and edit all parameters of your patch in logical views with logical controls. - It works in real-time! Instantly hear your changes as you play. Craft your patch along with your music as you make it! - Parameters respond to knob movements from external and internal controllers. - Automate parameters in your DAW host via physical knob movements, Editor control movements, or in Host with draw tool. - All edits and automation are remembered and sent out to hardware when you start up your project. - Meticulously thought out and well designed interface and tools that are specific to hardware model! - Available as a VST, Audio Unit and Standalone application. - Supports recent and latest versions of Mac OSX and Windows in both 32 bit and 64 bit versions. - Endless routing possibilities allow for complex MIDI setups and use. It's an Advanced Patch Librarian Manager The VST-AU Blofeld Editor includes a new advanced Patch Manager view that allows you to manage your patches and banks easily in one view. Here's just some of amazing and useful features Patch Manager offers: - Rename patches with ease. - Drag and drop patches or blocks from one slot to anor in copy, swap or move mode. - Highlights or patches in bank which are 'Duplicates by Name', and 'Exact Duplicates'. - Easily remove all 'Exact Duplicate' patches with one click to clear space for or patches. - Undo feature allows for non-destructive editing and reversing mistakes. - Easily copy or swap patches, blocks, or bank A and B. - Randomize a patch or entire banks with one click. - Clear patches or entire banks with one click. 3 / 30

4 - Add/Remove a prefix name to patches or entire banks to easily identify your patches. - Export just Patch names as a.txt file. - Import your existing patch and bank libraries via System Exclusive data dump direct from synth, or load m in from.syx files. - Save as standard.fxp/.fxb files or native.syx file format. Full MIDI message filtering of MIDI Input and Output data MIDI Setup allows you to select MIDI ports and Channels that you are using to connect to hardware synsizer. ou can also filter specific MIDI messages from all MIDI data paths from DAW Host, Editor and Synth. Absolute control of data paths allow for complex MIDI setups that can be saved and loaded for specific uses and applications. By using specific MIDI Setups with different instances of plug-in, you can now use multiple instances of plug-in for multiple machine control. - Create, Load and Save MIDI Setups for instant recall of settings and multiple instance use. - Filter any MIDI message to/from Synth, Editor and Host. Full MIDI Input and Output Monitoring The Midi Monitor view allows you to view all MIDI data coming in to and out of VST-AU Blofeld Editor. - Easily switch between Input and Output views of both Host and Editor/Synth MIDI input and output data. - Copy data from event logs for pasting and saving into standard text editors or or applications. 4 / 30

5 Requirements In order to use software properly you will need following: - The actual model of hardware synsizer product is designed for. - A PC computer running Windows (XP - Win7) or Mac OSX (10.6 or above). - An Audio Card to connect synth to PC audio inputs. - Audio cables to connect your synsizer to Audio Card. - A USB (or or) MIDI device with MIDI In and MIDI Out connectors. - 2 MIDI cables to connect between synth and MIDI device. - A rekon audio Activation Code. - A DAW Plug-In Host (ex. Cubase, Live, Logic) or use Standalone version. - A firm understanding of MIDI, your synsizer, its user manual, and its capabilities. - Some patience in getting things setup and working. This is technical MIDI routing, so take your time. - Double check your routings, settings and equipment. Physical Connections ou will need to make appropriate physical MIDI and audio connections to and from your hardware synsizer and computer first. ou will also need to read and understand user manuals for both your manufacturers hardware synsizer, and VST-AU Editor product you are using. Often, you will need to make some system settings on hardware synsizer in order to be able to send and receive MIDI data appropriately. The basic connections of a typical setup example would look like figure below, but may also be expanded upon. In this example, a remote MIDI controller keyboard is used to play note data into DAW, through editor, and out to hardware synsizer. 5 / 30

6 Installation Mac Installation 1. Before installing new software. First manually delete files below (OSX has no uninstaller for applications). If you cannot find locations using Finder, n make absolutely sure your user account has Administrator rights and that you are showing all hidden files. ou can use any search engine to find apps or tutorials on how to show hidden files on OSX. Here is Terminal command line way to do it: Open Terminal and type: defaults write com.apple.finder AppleShowAllFiles TRUE type 'Enter' key, n, type: killall Finder. type 'Enter' key again. 2. Run.pkg installer file from download. This will install VST, AU and Standalone application and related files to following folders on your computer: - AU 32-bit and 64-bit: /{user}/library/audio/plug-ins/components/rekon audio/[vst-au Editor Name]/ - VST 32-bit and 64-bit: /{user}/library/audio/plug-ins/vst/rekon audio/[vst-au Editor Name]/ - Standalone: /Applications/reKon audio/[vst-au Editor Name]/ * Note that you may need to copy 'VST' and 'Component' files to your '/Library/Audio/Plug-Ins/' folder for your host to be able to find m. ** Note that you may need to change file permissions to (read/write) for all users so that your DAW application can properly license software. - Once installed, n first run Standalone version so you can run Product Activation (see below) without permission interference from a DAW. Note that product will not allow operation without provided license key! 6 / 30

7 Windows Installation 1. Before installing, and if you have a previous version installed, be sure to run Windows Uninstaller and Uninstall current version of software first. Make sure account on your computer has Administrator privileges and that you are showing any hidden files (use File Explorer preferences). 2. Run.msi installer file. This will install VST and Standalone application and related files to following folders on your computer: For 32-bit Windows operating systems: - 32-bit VST: c:/program Files/Common Files/VST2/reKon audio/[vst-au Editor Name]/ - Standalone: c:/program Files/reKon audio/[vst-au Editor Name]/ For 64-bit Windows operating systems: - 32-bit VST: /Program Files (x86)/vstplugins/rekon audio/[vst-au Editor Name]/ - 64-bit VST: /Program Files/VSTPlugins/reKon audio/[vst-au Editor Name]/ - Standalone: /Program Files (x86)/rekon audio/[vst-au Editor Name]/ - Once installed, n first run Standalone version so you can run Product Activation below) without permission interference from a DAW. Note that product will not allow operation without provided license key! (see 7 / 30

8 Product Activation The VST-AU Editor series products now make Activating your product online easy. Simply follow instructions in Product Activation screen in software and you'll be up and running in no time. Product Activation requires that you have an internet connection available. For DAW workstations that are offline, you may still activate product on a computer that is not connected to internet using Offline Activation method, though it will take longer for us to manually process and send your license key to you (up to 48 business hours). Online activation is easiest and quickest way to activate your product and get going with it right away. Products can only be 'Activated' and run on a single computer at a time. Once you have activated this product on a computer, you cannot install and run it on anor computer until you have successfully 'De-Activated' product from computer it was installed on. To 'De-Activate' your product so that you may use it on a different computer or need to re-install it, go to your 'Account Settings/Order Details' page and click 'De-Activate' button. Follow instructions within ' Product De-Activation ' screen. Note - We review ALL Product Activations and Product De-activations to verify ownership and prevent fraud! Setting up Synth ou will need to be using Blofeld firmware OS 1.16B2, or latest version 1.22 firmware OS to properly use software. Connect your Blofeld MIDI via USB. 8 / 30

9 Set your Blofeld settings to: MIDI Channel = omni Device ID = 0 (you can use any setting, just make sure setting in editor matches device ID on unit). Ctrl Send = Ctrl+SysEx Ctrl Receive = On Using The Graphical User Interface The graphical user interface of VST-AU Blofeld Editor is designed for maximum ease of use, giving you easy Waldorf to all of parameters and common functions. ou are also able to rename, modify and browse Patches right inside Editor itself. All controls are handled via eir a slider, knob, combo box, button or text edit box. The MAIN User Interface Bar The Main User Interface (not shown to scale)... 9 / 30

10 - The File menu allows you to save and load Standalone Setup files. It will recall all your patch and bank settings. - The Settings menu allows you to configure your Audio Card Settings and Remote MIDI keyboard controller input. - The Help menu provides links to online help. From top left to right in image figure: 1. Patch Number and Name - Shows Patch name and Patch Number. Click on this to edit Patch name. 2. Bank Select - Select from Banks A - H. 3. Mode Select - Select Single or Multi mode. 4. DeviceID Select - Select DeviceID to send MIDI on. 5. Arrow Up: Patch Increment - Move up one Patch. 6. Arrow Down: Patch Decrement - Move down one Patch. 7. COP button: Copy this Patch to clipboard. 8. PASTE button: Paste from clipboard to Patch. 9. PM button: Opens 'Patch Manager' view (see 'Patch Manager' section). 10. MS button: MIDI SETUP - Opens 'MIDI Setup' view (see 'MIDI Setup' section). 11. MM button: MIDI MONITOR - Opens 'MIDI Monitor' view (see 'MIDI Monitor' section). 12. C button: CLEAR PATCH - Clears current patch. 13.? button: Click to randomize Patch. 14. U button: Undo changes. 15. R button: Redo changes. 16. Top E button: GET EDIT BUFFER - Gets current patch in Blofeld edit buffer. 17. Top P button: GET PATCH - Get's current patch on Blofeld program memory. 18. Top B button: GET BANK - Opens Patch Manager view. Use Sync menu/get Bank to get bank into editor. It will get all patches automatically. 19. Bottom E button: SET EDIT BUFFER- Send current patch to Blofeld edit buffer. Use it only if you need to 're-send' patch. 20. Bottom P button: SET PATCH - Send current patch to Blofeld. This overwrites your existing data on synth. Use wisely! 21. Bottom B button: SET BANK - Opens Patch Manager view. Use Sync menu/get Bank to send bank into synth. This overwrites your existing data on synth. Use wisely! 22.! button: MIDI PANIC- Click to stop all notes and all sounds (Note- may not work on some synsizers if it is not in synths MIDI specification). 23. Colored MIDI LED's: These represent MIDI data that is moving in and out of Editor from DAW host and Editor/Synth. 10 / 30

11 24. Product Logo: Click this to open About screen. This screen will show you your product version, if an update is available, and your license information. Some hosts do not allow plug-ins to use keystrokes on main plug-in window. ou can still use Patch Manager to rename Patch in this case. The SOUND/FX User Interface View The VST-AU Blofeld Editor SOUND/FX tab screen (not shown to scale) / 30

12 - Thearrow FXaviews change based on 1and andknob Effect 2 Types selected.. Mouse Scroll increment slider movements in single Double-click slider orwheel knob tokeyboard set it to 'middle' position. Use buttons on your toeffect move up and down on combo boxes.increments. The MODS/ARP User Interface View The VST-AU Blofeld Editor MODS/ARP screen (not shown to scale) / 30

13 view on Blofeld. update it's based on knob settings. This view matches - setting. The Arp will show of position. steps thatarp are selected forsingle 'Pattern Length' Use Mouse ScrollorWheel tokeyboard increment and movements in increments. Double-click a Diagram slider knob set it number toview 'middle' arrow buttons on your toslider move up and down on combo boxes. The MULTI User Interface View The VST-AU Blofeld Editor Multi screen (not shown to scale) / 30

14 - Note made changing in this Multi that view Programs Multi-mode MUST be indoes sent Editor. not toname send or receive by clicking Sysex Parameter 'Send to Edit Changes! All button, changes by Programs. additional Program screen and controls. These are forbuffer' managing or Multi See Multi Manager section forblofeld more information. The MIDI Setup View To access 'MIDI Setup' view, click 'MS' button. The 'MIDI Setup' view allows you to connect and control (filter) MIDI data coming into and out of Editor and Host. ou will need to open this view directly after instantiating software in order to setup up communication between Synth and Editor. Once you have done this, software will remember your settings. ou can toggle filtering of specific MIDI data for both Host and Editor MIDI data paths. If you carefully inspect diagram in middle, you can see exactly what data gets routed where. To make things a bit easier to differentiate, re is a color coding scheme for MIDI data. The 'MIDI Monitor' view will show messages in se same colors. 14 / 30

15 Since this software allows you to route and filter MIDI data bidirectionally, it is best to activate only check boxes for specific messages you require. Orwise, it may be possible to create a MIDI feedback loop under certain circumstances. It's best to just leave m be, as y are already optimally configured for using editor. However, it is up to user to understand routings and connections being made to and from Editor and also diagnose where any problems may be occurring. IMPORTANT NOTICE!!!The editor gets installed with default settings shown in image (minus MIDI ports, of course) and you shouldn't need to change se settings unless you are absolutely sure you know what you are doing, and that you need that particular data for input or output. Do NOT turn on Program Change options in any of four sections. We do not use se with Editor and y will conflict data or prevent MIDI data transmission. Please keep m off at all times! - The File menu allows you to save and load MIDI Setup files. ou typically will not need to use this as it has a default already. - The View menu provides links to About screen. How MIDI is handled The four sections of filters in MIDI Setup represent different MIDI Inputs and MIDI 15 / 30

16 Outputs Editor uses. This is data that originates from eir DAW host, Synth, or Editor. The editor gets installed with default settings shown in image (minus MIDI ports, of course) and you shouldn't need to change se settings unless you are absolutely sure you know what you are doing, and that you need that particular data for input or output. It's best to just leave m be as y are already optimally configured for using editor. Here is how four sections break out: 1. Host MIDI In: The top-left section deals with MIDI In data that originates from DAW host (DAW MIDI tracks, remote keyboard input, etc.). This is typically musical data such as note On/Offs, pitch bend, modulation wheel, etc. ou should never send sysex data coming from DAW host into Editor, as most DAW's do not handle large enough sysex data formats (through plug-ins) to work properly.we also cannot use MIDI Clock from DAW as it is not sent through plug-ins as MIDI clock data. Instead, we know DAW host timing info in processing block of plug-in and you can choose to use this info to send a 'generated' MIDI Clock signal through 'Editor MIDI Out' and on to hardware synth. See below for more information. 2. Editor MIDI In: The bottom-left section deals with MIDI In data that originates from hardware Synth. Though you can use it to bring in Note On/Off data from synth, it is recommended that you use a separate MIDI keyboard controller to do this through DAW MIDI track. What we want here is to receive MIDI sysex, and CC data that editor can use to make changes. ou should never send MIDI clock data coming from Synth into Editor. 3. Host MIDI Out: The top-right section deals with MIDI Out data that needs to go back to DAW host. Though you can use it to bring in Note On/Off data from synth (also using Editor MIDI In), it is recommended that you use a separate MIDI keyboard controller to handle Note On/Off data through DAW MIDI track. We really do not need to send any of MIDI data back into DAW if we are using a remote MIDI keyboard properly. But we do have that option. Never send MIDI sysex data back to DAW host. Hosts will differ on how and what MIDI data y can interpret and we do not need to send sysex data, or MIDI clock data to DAW Host from Editor under any circumstances. Please refer to your DAW host User Manual for more information on how it uses MIDI Clock sync. 4. Editor MIDI Out: The bottom--right section deals with MIDI Out data that needs to go to Synth. Here we will be sending most of MIDI data to synth including Note On/Off data from DAW Host In, and all changes that occur inside itself. ou will likely want to keep all of se settings on (except for Program Change). The 'Gen Clock' icon (only shown in plug-in versions) in 'Clock' area allows you to toggle sending a 'generated' MIDI Clock signal out to synth. This will be BPM tempo of DAW host. The accuracy of generated MIDI clock may vary depending on your setup and DAW. If you have issues with syncing, re are also or way's of getting DAW MIDI clock sync signal to synth that are discussed in this manual. If this method is not satisfactory for you. It is good for testing of MIDI clocks for Arpeggios, etc. 16 / 30

17 Do not turn on Program Change check boxes! We do not use Program Changes when using an editor like this that works on edit buffer in synth. ou can stay on same patch on hardware synth, and changing patches in editor will change all settings it needs to recreate patch sound without changing patches on synth at all. All of this is done in edit buffer, so no patch change occurred, no skip in sound, no overwritten data in synth, and sysex data editor sends is not interrupted by program change call. 1. Host MIDI In button - Activates Host MIDI In module. Turn this on to receive MIDI data from Host. 2. Host MIDI Out button - Activates Host MIDI Out module. Turn this on to send MIDI data to Host. 3. Editor MIDI In button - Activates Editor MIDI In module. Turn this on to receive MIDI data into Editor from Synth. 4. Editor MIDI Out button - Activates Editor MIDI Out module. Turn this on to send MIDI data to Synth from Editor. 5. MIDI In Port - Select MIDI port that is connected to your Synth MIDI Out port. 6. MIDI In Channel - Select MIDI channel that is being used with your Synth MIDI Out port. 7. MIDI Out Port - Select MIDI port that is connected to your Synth MIDI In port. 8. MIDI Out Channel - Select MIDI channel that is being used with your Synth MIDI In port. 9. MIDI Echo - Turn this on if you want to echo MIDI data that is coming from Synth directly back to synth (When synth is in 'Local Off' mode). 10. MIDI Setup file name - Shows current MIDI Setup file that is being used. 11. Routing Diagram - Shows how data is routed throughout software, including Message color codes. The MIDI Monitor View To access 'MIDI Monitor' view, click 'MM' button. The 'MIDI Monitor' allows you to view all MIDI data that is coming into or out of Host and Editor. By default view will show MIDI In/Out data from Editor MIDI data path. ou can switch between Host and Editor MIDI In 17 / 30

18 and MIDI Out views independently. The colors of messages are related to color coding found in 'MIDI Setup' diagram. The 'Clear' button will clear data in that view. The log view will show up to 1500 messages before clearing itself automatically. ou can copy data in log view to or applications if necessary. The 'All' button will select and automatically copy to clipboard that entire view's data. ou can turn on/off view with button on right. 1. Host or Editor MIDI Input View - Switch between Host and Editor MIDI Input data views. 2. Clear, Copy All, or a selection of data to clipboard. 3. Host or Editor MIDI Output View - Switch between Host and Editor MIDI Output data views. 4. Clear, Copy All, or a selection of data to clipboard. Since MIDI Monitor requires a lot of processing to redraw lists, we recommend you only use MIDI Monitor for trouble shooting or 'glancing' at data. Keep it closed when not using it to improve performance. The MIDI Monitor may not show Sysex input or output data when using Ableton Live. However, sysex data will still be sent out to MIDI device. The Patch Manager View 18 / 30

19 To access 'Patch Manager' view, click 'PM' button. The 'Patch Manager' allows you to load and save Patches and Banks as.fxb/.fxp files. The 'Patch Manager' also allows you to view and organize your Patches, Blocks and Banks way you like. Patch slots and Blocks allow you to organize your Patches by simply dragging and dropping m to anor block/ slot in eir Swap, Copy Replace, or Move mode. To do this, click on Patch number box (with red numbers) and while holding down mouse button drag this Patch to anor patch location by dropping it on Patch name box. A valid drop target will be indicated by a red outline. Drag Blocks to or Block locations by clicking in top left corner and dragging to anor Block title (it will highlight with red bars). ou can also double click on a Patch number to go to that Patch. A new feature is ability to drag and drop.syx patch (not bank) files from any Finder or File Manager type application right into a Patch Manager patch slot location. This makes it very easy to load in several patches from disk to specific locations in Patch Manager. Anor new and useful feature that goes hand-in-hand with drag and drop.syx file, is ability to export entire bank as individual.syx patch files to disk, and later drag and drop m in or banks. It's very easy to manage data with Patch Manager. Also added in version is ability to Clear, Randomize, and drag and drop a block to anor block location using same Copy, Move, Swap option as patch drag and drop functionality. Blocks are sections with grey header bars (patches 1-8 for example). The Patch Manager screen (may or may not be shown to scale) / 30

20 20 / 30

21 and--3..fxp/.fxb. File menu allows you totobank load and save files in several useful formats including.syx patches The oredit banks. menu provides useful features like randomize, clear, and name prefix/suffix for Sync allows you sync data between editor and Synth. View menu provides links to About screen. 1. currently loaded file. 2. loaded. Shows date andfor time file was saved. 4. and Drop cell a block. 5. An unselected Patch. 6. The Selected 7. and Patch Data as selected patch. 8. different Name. Patch Data asselected selected patch, butdifferent has a 9. Patch An Data. unselected patch that shares same Name as patch, but has 10.Drag The Drag andpatch. Drop mode currently inlast use. This applies to Blocks and Patches. The Multi Manager View To access 'Multi Manager' view, click 'PM' button located inside Multi View. The 'Multi Manager' allows you to load and save Multi Patches and Banks as.fxb/.fxp files. The 'Multi Manager' also allows you to view and organize your Patches, Blocks and Bank way you like. Patch slots and Blocks allow you to organize your Patches by simply dragging and dropping m to anor block/ slot in eir Swap, Copy Replace, or Move mode. To do this, click on Patch number box (with red numbers) and while holding down mouse button drag this Patch to anor patch location by dropping it on Patch name box. A valid drop target will be indicated by a red outline. Drag Blocks to or Block locations by clicking in top left corner and dragging to anor Block title (it will highlight with red bars). ou can also double click on a Patch number to go to that Patch. A new feature is ability to drag and drop.syx patch (not bank) files from any Finder or File Manager type application right into a Multi Manager patch slot location. This makes it very easy to load in several patches from disk to specific locations in Multi Manager. Anor new and useful feature that goes hand-in-hand with drag and drop.syx file, is ability to export entire bank as individual.syx patch files to disk, and later drag and drop m in or banks. It's very easy to manage data with Multi Manager. Also new is ability to Clear, Randomize, and drag and drop a block to anor block location using same Copy, Move, Swap option as patch drag and drop functionality. Blocks are sections with grey header bars (patches 1-8 for example). The Multi Manager screen (not shown to scale) / 30

22 22 / 30

23 and--3..fxp/.fxb. File menu allows you totobank load and save files in several useful formats including.syx patches The oredit banks. menu provides useful features like randomize, clear, and name prefix/suffix for Sync allows you sync data between editor and Synth. View menu provides links to About screen. 1. currently loaded file. 2. loaded. Shows date andfor time file was saved. 4. and Drop cell a block. 5. An unselected Patch. 6. The Selected 7. and Patch Data as selected patch. 8. different Name. Patch Data asselected selected patch, butdifferent has a 9. Patch An Data. unselected patch that shares same Name as patch, but has 10.Drag The Drag andpatch. Drop mode currently inlast use. This applies to Blocks and Patches. Working With Patches and Banks How Patches work A Patch in Editor represents a Patch on Synth. When you change Patches in Editor, Patch data is sent to Synt's edit buffer in form of MIDI CC or Sysex messages. As a result, this data is sent to Synth, but NOT permanently stored in Synth. This allows you to listen to Patches from Editor while still preserving your original Patches that reside in Synth. If you wish to store Patch data Editor sent Synth, n store it on Synth by using Synths 'write' function (refer to Blofeld keyboard manual for information on how to store a Patch), or use 'Set Patch' or 'Set Bank' methods. Changing Current Patch ou can double click on patch number area to select that patch. ou may also use arrow keys on keyboard to move up and down, and left and right through patches. Renaming Current Patch To rename your Patch, simply click on name in display readout and type new name of your Patch, n hit 'Enter' key. Use Patch Manager to rename patches when DAW host won't allow you to use keystrokes in main plug-in window. Note that Editor Patch names are limited to 16 characters, or max number of characters supported by synth if it uses names. Drag and Drop Patches and Blocks ou can rearrange Patches and Blocks of patches to or Patches and Blocks using Drag and Drop methods. The Drag and Drop Mode allows you to Copy Replace, Move, or Swap Patches and Blocks. This makes building your bank up a very rapid and painless process. Drag and Drop.syx patch files into Patch Manager ou can Drag and Drop single.syx file patches right into any patch slot in Patch Manager from Finder/Explorer/File Manager applications. ou can export individual.syx patches, or entire bank as individual.syx patches. This also makes building your bank up a very rapid and painless process. 23 / 30

24 What are Colored Outlines on Patches? One new feature of Patch Manager is ability to clearly see what patches in bank share Similar names and/or data, and ability to easily remove m. This makes it easy for you to manage and clean up your banks with only relevant patches. Here's what color coding means: - Red Outline - This is currently selected Patch. - Purple Outline - This is an unselected patch that shares same Name and Patch Data as selected Patch. - Blue Outline - This is an unselected patch that shares same Patch Data as selected Patch, but has a different Name. - Green Outline - This is an unselected patch that shares same Name as selected Patch, but has different Patch Data. Use 'Edit' Menu to 'Clear Exact Duplicates' or 'Clear Data Duplicates'. Loading and Saving Sysex Patches and Banks Loading and Saving Sysex Patches and Banks The VST-AU Blofeld Editor can load and save standard.syx (system exclusive) Patch, Bank, Multi Patch, and Multi Bank files. This makes importing, exporting and sharing your existing Patch libraries very easy. Use 'Patch Manager' to load and save.syx Patch or Bank files. Once you have loaded a.syx Patch or Bank, Editor will update with loaded settings. Importing Patches and Banks into Editor From Synth via Sysex ou can also easily import your existing Patches and Banks directly from Blofeld into Editor. There are a couple ways to do this. Choose method below that is specific to your task. 24 / 30

25 Do not perform se tasks while running Host sequencer. Stop sequencer first! Importing a single Patch (Edit Buffer to current Editor Patch): 1. Make sure you are connected bidirectionally (MIDI IN and Out to and from Synth). 2. Select Patch on Blofeld that you wish to import into Editor. 3. Click 'Shift + Utility' button, n select 'Dump Sound', n press 'Shift + Utility' button again and Patch will be imported into Editor. 4. ou can also use 'Get Edit Buffer' button in Editor to easily get current 'Edit-Buffer' patch data. Importing a single Patch (Program Buffer to current Editor Patch): 1. Make sure you are connected bidirectionally (MIDI IN and Out to and from Synth). 2. Select Patch on Editor that you wish to import to. 3. Click 'Patch Get' button and Patch on Blofeld at current Editor program location will be imported into Editor. Importing a Bank (Programs from Bank A-H into Editor Bank): 1. Make sure you are connected bidirectionally (MIDI IN and Out to and from Synth). 2. Select Bank you wish to import (A-H) from Editor's 'Bank Selection' combo box. Click on 'Get Bank' button. The Patch Manager will open and A dialog will open asking if you wish to proceed. 3. It will take about 60 seconds or so to complete dump from Synth into Editor. ou will see Editor MIDI In LED's lighting up as dump is processing and progress bar showing transfer progress. 4. The process may miss a few of patches in bank while it is iterating patches in bank. The software will go back and try to re-import those patches that were missed until entire bank has been imported. Saving Patches and Banks into Synth via Sysex ou can 'permanently' save Patches and Banks to synth from Editor. Note this will overwrite your existing Patches and Bank data in synth. Be sure to back up your existing Patches and Banks first! 25 / 30

26 Do not perform se tasks while running Host sequencer. Stop sequencer first! Permanently saving a single Patch to synth: 1. Use synth 's 'store' capability if you wish to store a single Patch. Permanently saving a single Patch to synth: 1. Make sure you are connected bidirectionally (MIDI IN and Out to and from Synth). 2. Make sure you turn off 'Program Change' options in 'MIDI Setup' view first! 3. In Editor, click 'Send Patch' button. 4. The Synth will now have permanently stored new Patch data from Editor to Synth. Permanently saving Editor Bank to synth: 1. Make sure you are connected bidirectionally (MIDI IN and Out to and from Synth). 2. Make sure you turn off 'Program Change' options in 'MIDI Setup' view first! 3. In Editor, click 'Bank Send' button. A dialog will open asking if you wish to proceed. Transfer takes about 20 seconds. 4. The Synth will now have permanently stored new Bank data from Editor. Note: A valid Blofeld Sysex Patch file is 392 bytes and is formatted according to sysex specification found in Blofeld User Manual. A valid Blofeld Sysex Bank file is 50,176 bytes for 128 patches, and is formatted according to sysex specification found in Waldorf Blofeld User Manual. The Editor will only accept.syx files that are formatted specifically for Blofeld synsizer. Note this will overwrite your existing Patch and Bank data in synth. Be sure to back up your 26 / 30

27 existing Patches and Banks first! Do not perform se tasks while running Host sequencer. Stop sequencer first! A note on Sysex MIDI and Host Plug-in Capabilities. Sysex data from a VST or Audio Unit plug-in to DAW Host is not widely supported by most Host DAW manufactures. This is why Editor has it's own 'built-in' MIDI ports to connect to hardware Synth. MIDI Implementation Chart The following MIDI data is transmitted (Tx) and Received (Rx) from Editor and may be filtered as well. MIDI Message Tx Rx Channel Mode Note On/Off Velocity Aftertouch Poly Pressure Pitch Wheel Modulation (CC1) Continuous COntrol (CC) Program Change System Common 27 / 30

28 System Realtime System Exclusive x = no o = yes For a full list of parameters and ir value ranges, please refer to Waldorf Blofeld User Manual. Getting Additional Support If you have read through all above material and are still having issues using software, n personal Technical Support is available. Customers will receive ir first Technical Support Response for free. After first Technical Support Response, a fee of $25 will be charged for each Technical Support Response requested. To submit a Technical Support Response, you must provide information below along with your contact request. ou will not receive a Technical Support Response if this information is not provided with your request: - our Full Name our Purchase Order Number The product you need support for The platform you are licensed for (Mac or Windows) The Audio Card and MIDI Device(s) you are using with software The DAW host name and version number you are using software with Describe issue you are having in as much detail as possible License Agreement - By installing and using this product you agree to terms and conditions set forth in 28 / 30

29 License Agreement as illustrated in installation of software. - ou may download, install, run and activate this software on same, single computer, with same Operating System, using same hard drive, as many times as you like. - ou may download, install, run and activate this software on a different computer, only if you have uninstalled and 'De-Activated' any prior product 'Activations' first. - If you need to use software on more than one computer at a time, multi-seat, and/or multi-platform licenses are available at quantity discounted prices. - ou may NOT share, distribute, sell, , pirate, torrent, hack, reverse engineer, or copy this software or user account information in any way. Doing so violates your License and Use, and Terms of Service, and is also illegal. - ou may NOT use this product in any manner that would be considered illegal, harmful, or not as intended for its purpose and use. This includes using product with incompatible hardware or software systems. 1. This is an agreement between Licensor and Licensee, who is being licensed to use named Software. 2. Licensee acknowledges that this is only a limited nonexclusive license. Licensor is and remains owner of all titles, rights, and interests in Software. 3. This License permits Licensee to install Software on more than one computer system, as long as Software will not be used on more than one computer system simultaneously. Licensee will not make copies of Software or allow copies of Software to be made by ors, unless authorized by this License Agreement. Licensee may make copies of Software for backup purposes only. 4. This Software is subject to a limited warranty. Licensor warrants to Licensee that physical medium on which this Software is distributed is free from defects in materials and workmanship under normal use, Software will perform according to its printed documentation, and to best of Licensor's knowledge Licensee's use of this Software according to printed documentation is not an infringement of any third party's intellectual property rights. This limited warranty lasts for a period of 365 days after delivery. To extent permitted by law, THE ABOVE-STATED LIMITED WARRANT REPLACES ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, AND LICENSOR DISCLAIMS ALL IMPLIED WARRANTIES INCLUDING AN IMPLIED WARRANT OF TITLE, MERCHANTABILIT, NONINFRINGEMENT, OR OF FITNESS FOR A PARTICULAR PURPOSE. No agent of Licensor is authorized to make any or warranties or to modify this limited warranty. Any action for breach of this limited warranty must be commenced within one year of expiration of warranty. Because some jurisdictions do not allow any limit on length of an implied 29 / 30

30 warranty, above limitation may not apply to this Licensee. If law does not allow disclaimer of implied warranties, n any implied warranty is limited to 365 days after delivery of Software to Licensee. Licensee has specific legal rights pursuant to this warranty and, depending on Licensee's jurisdiction, may have additional rights. 5. Notwithstanding foregoing, LICENSOR IS NOT LIABLE TO LICENSEE FOR AN DAMAGES, INCLUDING COMPENSATOR, SPECIAL, INCIDENTAL, EXEMPLAR, PUNITIVE, OR CONSEQUENTIAL DAMAGES, CONNECTED WITH OR RESULTING FROM THIS LICENSE AGREEMENT OR LICENSEE'S USE OF THIS SOFTWARE. Licensee's jurisdiction may not allow such a limitation of damages, so this limitation may not apply. 6. Licensee agrees to defend and indemnify Licensor and hold Licensor harmless from all claims, losses, damages, complaints, or expenses connected with or resulting from Licensee's business operations. 7. Licensor has right to terminate this License Agreement and Licensee's right to use this Software upon any material breach by Licensee. 8. Licensee agrees to return to Licensor or to destroy all copies of Software upon termination of License. 9. This License Agreement is entire and exclusive agreement between Licensor and Licensee regarding this Software. This License Agreement replaces and supersedes all prior negotiations, dealings, and agreements between Licensor and Licensee regarding this Software. 10. This License Agreement is valid without Licensor's signature. It becomes effective upon earlier of Licensee's signature or Licensee's use of Software. Disclaimer Waldorf, and Blofeld names and logos are property of Waldorf Music. Steinberg and VST name and logos are property of Steinberg Media, GmbH. Apple Computer and Audio Units name and logos are property of Apple Computer. 30 / 30