Moog Little Phatty User manual

Moog Little Phatty User manual
VST-AU Little Phatty Editor™ 2.1.0
User Manual
Windows XP, Vista, Windows 7 (32 & 64 bit)
OSX 10.5, 10.6, 10.7 (32 & 64 bit)
1
VST-AU Little Phatty Editor™ 2.1.0
User Manual
Table of Contents
» Introduction
» Installation
» MIDI Setup
» Working with the VST-AU Little Phatty Editor™
» Graphical User Interface
» Working with Patches
» How to Get Your Current Bank
» MIDI Implementation
» Legal Information
2
Introduction
Thank you for choosing the Moog Music VST-AU Little Phatty Editor™. The VST-AU Little Phatty Editor™ (referred to in this
manual as 'Editor') is a real-time MIDI Synth Editor that allows you full control of every parameter of the sound on the Moog
Music Little Phatty™ and Slim Phatty™ synthesizers (referred to in this manual as 'Synth') running the latest OS 3.12.680 or
above. With it, you can view, manage and edit all your Patches with detail on the computer, visually. All parameters are fully
automatable in your favorite 32 bit or 64 bit VST or Audio Unit DAW Host (referred to in this manual as 'Host') . Please see
product web page for current DAW Host support. This gives you the ability to visually program the Little Phatty or Slim
Phatty to your music via the Host sequencer. This ability to model your Synth Patches in real-time, inside your main music
production environment is part of what makes the VST-AU Little Phatty Editor™ unique when compared to other hardware
Synth Editors. If you don't need or use a DAW Host, you can still manage the Patches with the Standalone version. The
VST-AU Little Phatty Editor™ is developed and supported by reKon audio (http://www.rekonaudio.com).
Complete Synth Editor
The VST-AU Little Phatty Editor™ is a visual editor allowing you to view and edit every parameter of a Little Phatty or Slim
Phatty Patch and supports the all the latest Little Phatty OS version 3.12.680 parameters. All knobs send and receive in
14bit precision mode (0-4095) and are step-able in increments of 1 using the mouse scroll wheel.
Advanced Patch Librarian
The VST-AU Little Phatty Editor™ includes an advanced 'Patch Manager' view that allows you to rename and arrange
Patches to create your Bank. Drag and drop Patches where you want them with a complete overview of the Bank in either
Swap, Copy, or Move mode. You can load and save your Patches and Banks as standard .FXB/.FXP files.
Patch Randomizer
The VST-AU Little Phatty Editor™ also includes a 'Patch Randomizer' that allows you to easily create randomly generated
Patches.
MIDI Input and Output Monitoring
The 'MIDI Monitor' view allows you to view all MIDI data coming into and out of the VST-AU Little Phatty Editor™ for both
the Host and Editor MIDI data paths. Easily switch between Host and Editor views. You can even copy the data from the
event logs for pasting and saving into standard text editors or other applications.
MIDI Setup
The VST-AU Little Phatty Editor™ is based on an entirely new framework that allows you to select the MIDI input and output
ports and channels directly from within the Editor itself. This allows you to send and receive MIDI data directly to and from
your Synth. You are no longer limited by any Host MIDI incapability. 'MIDI Setup' also allows you to filter out specific MIDI
data for both Host and Editor MIDI data paths or toggle MIDI In and Out operations.
3
Installation
This product includes an installer which will help you with the installation of the product. Please follow the detailed
instructions below to install and register your License Key to begin using the software product.
Windows users:
1. Be sure to read this User Manual before you begin using this product. It contains detailed information regarding the MIDI
setup procedures required to successfully connect to your computer and synthesizer.
2. Run the installer file. This will install the VST and Standalone application and related files to the following folders on your
computer:
For 32-bit Windows operating systems:
VST: Program Files/Common Files/VST2/Moog Music/VST-AU Little Phatty Editor/
Standalone: Program Files/Moog Music/VST-AU Little Phatty Editor/
Settings: ProgramData/Moog Music/VST-AU Little Phatty Editor/
For 64-bit Windows operating systems:
VST: Program Files (x86)/Common Files/VST2/Moog Music/VST-AU Little Phatty Editor/
Standalone : Program Files (x86)/Moog Music/VST-AU Little Phatty Editor/
Settings: ProgramData/Moog Music/VST-AU Little Phatty Editor/
*Note that you may need to show hidden folders on your system to be able to see the 'ProgramData/' folder. To show your
hidden folders on your system; Use Tools/Folder Options/View' and select the 'Show Hidden Folders and Files' option
3. Place your provided license key (.rkl file) into the 'Settings' folder to begin using the product.
Mac OSX users:
1. Be sure to read the provided PDF manual before you begin using this product. It contains detailed information regarding
the 'MIDI Setup' procedures required to successfully connect to your computer and synthesizer.
2. Run the installer file. This will install the VST, AU and Standalone application and related files to the following folders on
your computer:
AU: Library/Audio/Plug-Ins/Components/Moog Music/VST-AU Little Phatty Editor/
VST: Library/Audio/Plug-Ins/VST/Moog Music/VST-AU Little Phatty Editor/
Standalone: Applications/Moog Music/VST-AU Little Phatty Editor/
Settings: Library/Application Support/Moog Music/VST-AU Little Phatty Editor/
*Note that you may need to copy the VST and Component folder files to your ~User/Library/Audio/Plug-Ins/ folder for your
Host to be able to find them.
3. Place your provided license key (.rkl file) into the 'Settings' folder to begin using the product.
4
MIDI Setup
Assumptions
It is assumed that the user is familiar with the basic functionality of the hardware synthesizer, its User Manual and the basic
concept of MIDI itself. Without this knowledge, utilizing the Editor may be a bit more challenging to set up and use properly.
By familiarizing yourself with the synthesizer manufacturers User Manual, this User Manual, and having a basic
understanding of MIDI, you should be able to get up and running in a short amount of time.
Setting Up the Synth
Make sure you have your MIDI ports and channels set up and matching properly and that all cables are working and
connected properly.
1. This software is designed to be used with LP firmware version 3.11 674/32. Firmware versions above this may or may not
be supported by this version of the VST-AU Little Phatty Editor™. If you need to update your firmware, follow the directions
provided with your firmware installer from Moog Music.
2. On the Synth, set the Master/MIDI Setup/Send CC's to 'All CC's'.
3. Set Master/MIDI Setup/Send 14bit to Off.
4. Set the MIDI IN and Out ports and channels to the one connected to your computer.
Setting Up the Plug-in for your Host (DAW)
The setup procedure will vary by Host. Each Host will support plug-ins differently. Please refer to the 'Supported Hosts' list
for this products support web page on the reKon audio web site at www.rekonaudio.com. Also, please refer to the setup
instructions provided with your Host application for setting up a VST or AU plug-in.
Syncing both the DAW Host and the Editor with the Synth
The Editor gives you several options for routing MIDI data bidirectionally. As a result, you can send Host MIDI data into the
Editor, which in turn, will get sent on to the Synth via the Editors MIDI Out port. In this process, the MIDI data is actually
transferring between two separate MIDI systems; the Host's, and the Editor's. This transfer process may work fine for
previewing your sounds, and possibly smaller projects, but will likely not suffice for a lot of sequenced data. If you are having
issues with syncing and hearing delayed or offset playback from the Synth when using the Host to send MIDI data to the
Synth through the Editor, then you can create a setup that prevents the latency/syncing issues.
You can use a Virtual MIDI Cable and a MIDI Routing Application to allow BOTH the DAW host and the Editor direct access
to the same MIDI Output port using their own systems. This allows you to have the DAW host sequencer send its data
straight to the Synth. And, the Editor will have its direct connection to the Synth as well.
Here's how to set it all up. (In this example, the following tools were used. Other tools may work in a similar way):
•
•
•
•
•
Windows 7 64bit (with a MOTU MIDI Express XT using port 8 to connect to the Synth MIDI In and Out)
MIDI-Ox (a free MIDI Routing App)
LoopBe (Virtual MIDI Cable). (MIDI Yoke and Maple MIDI will work with 32bit Win OS, but not 64bit Win OS).
Any reKon audio or Moog Music VST-AU Editor™ product.
Cubase 5 32bit (DAW host).
5
1. Open the DAW host. In the DAW host MIDI setup (typically found under 'Preferences') disable the port that you are using
to connect the Synth to the Editor. (ex. port 8).
2. Using a Virtual MIDI Cable (MIDI Yoke, Maple MIDI or LoopBe for Windows, it's free. Use 'Audio MIDI Setup' app on Mac
and create a virtual device, also free). Make sure the VMC is installed and working properly first!
3. Using a MIDI Routing app (MIDI-Ox for Windows, it's free. Use 'Audio MIDI Setup' app on Mac, also free). Open MIDI-Ox
and make the following connections:
1. Open the 'Options/MIDI Devices' view and make sure you have selected the MIDI Out port you are using to
connect to the Synth (ex. port 8).
2.
Open the 'MIDI Port Routing' view and disconnect all cables first. Then connect the 'LoopBe MIDI Input' port to the
MIDI port going to the Synth (ex. port 8 Output).
3.
4.
5.
6.
7.
8.
9.
Also connect the 'LoopBe MIDI Output' port to the 'MIDI-OX Event Port'.
Also connect the 'MIDI-OX Event Port' to the port connected to the Synth (ex. port 8).
Load the VST-AU Editor plug-in. (see your host documentation for using soft-synth plug-ins).
Open the 'MIDI Setup' view in the VST-AU Editor.
Set the 'Editor MIDI In' and 'Editor MIDI Out' ports and channels to that connected to the Synth (ex. port 8).
In the DAW host, select the track that was created for the plug-in
Note that you do not need (or want, in this case) to connect the MIDI tracks I/O's to any MIDI Inputs or Outputs, or
to the Editor. Instead, you can use this track to send Note On/Off, Pitch, Modwheel, etc. data straight to the Synth
by doing the following:
- Set the track's MIDI Input to a MIDI Controller Keyboard.
- Set the track's MIDI Output to the 'LoopBe Internal MIDI' port. This will send the Note On/Off, Pitch, Modwheel
data to the Synth directly from your Host sequencer track instead of through the Editor.
In this arrangement, the Editor has direct access to the Synth AND the DAW Host sequencer also has direct access to the
Synth.
Your music should now be in sync with the DAW host and still have automation control through the plug-in. The Editor also
has direct communication with the Synth.
IMPORTANT NOTE!!! When using the plug-in in a Host application, you must first disable the MIDI port
that you will be using the hardware Synth/ Editor on in the Host's MIDI setup. This will then make that port
available for use within the plug-ins' MIDI setup. Failing to do this will not allow the MIDI port in the plug-in
to work and the software will not be able to communicate with the hardware. You can use a virtual MIDI
port (loopBe, etc.) if you wish to have your MIDI ports available to both the Host and the Editor.
Setup Example for Cubase 4-6
To setup the Moog Music VST-AU Little Phatty Editor™ for Cubase SX 2-3 or Cubase 4-6:
1. First be sure to open Cubase 'MIDI Setup' dialog and deactivate the MIDI ports you will be using to connect the Synth to
the Editor. Be sure to check your Host's VST Instrument plug-ins folder to make sure the Editor got installed there properly.
Also make sure the License Key and Preferences files are copied to the same folder as the plug-in.
2. Open Cubase.
3. Create a new project.
4. Open your 'VST Instruments' panel and then select the 'Moog Music VST-AU Little Phatty Editor™' VST in a VST slot.
Add a MIDI Track for this if you want one (useful for MIDI keyboard control to the Synth).
5. Click the 'MIDI Setup' button in the Editor and select the MIDI Input and Output port your Synth is attached to.
6. Open the 'MIDI Monitor' view to make sure data is transmitted properly between Synth and Editor.
7 If you are running the software for the first time, you will need to load the default bank file into the Editor via the 'Patch
Manager'. Once loaded and saved in your host, your host should remember the settings you last used automatically. You
should always save your bank files manually to be certain you are not losing anything important.
Automation:
1. Select the track the Editor is on. In the 'VST Instrument' track you will see one automated parameter showing called
'Volume', you can use the menu there to select the parameter(s) you wish to automate. Please refer to the Cubase User
Manual for more information on using automation.
6
Setup Example for Ableton Live 8
To setup the Moog Music VST-AU Little Phatty Editor™ for Ableton Live 8:
1. First be sure to open the 'Preferences' dialog and deactivate the MIDI ports you will be using to connect the Synth to the
Editor. Be sure to check your Host's VST Instrument plug-ins folder to make sure the Editor got installed there properly. Also
make sure the License Key and Preferences files are copied to the same folder as the plug-in.
2. Open Ableton Live 8. Create an Empty Project.
3. Drag the plug-in from the 'Plug-In Devices' box to the track screen The Editor should appear.
4. In the Instrument track that was created, click the 'MIDI From' combo box and select a MIDI port that you wish to use for a
MIDI controller keyboard. Activate this track to allow MIDI to go through.
5. Open the 'MIDI Setup' view in the Editor and select the MIDI ports that are connected to your Synth for both the Editor
MIDI In and Editor MIDI Out sections. Close the MIDI Setup view.
6. Turn a knob in the Editor, you should see MIDI data being sent out to the port you selected in step 5. Open the 'MIDI
Monitor' view to make sure data is transmitted properly between Synth and Editor.
7. If you are running the software for the first time, you will need to load the default bank file into the Editor via the 'Patch
Manager'. Once loaded and saved in your host, your host should remember the settings you last used automatically. You
should always save your bank files manually to be certain you are not losing anything important.
8.Create another 'Audio' track and route the audio from the audio port your Synth is connected to.
Automation:
1. Select the track the Editor is on. In the 'Info View' panel in Live, click the 'Configure' button. Now select the parameters
you wish to automate by clicking on them in the Editor. When you are done, click the 'Configure' button again. You can now
automate these parameters in your Live tracks. Please refer to the Live User Manual for more information on using
automation.
*Note that Live 8 does not automatically create or show automated parameters for plug-ins that have more than 32
parameters. You have to add them manually using 'configure' mode. See the Live User Manual section 16.2.1 for more
information on the subject.
Setup Example for Logic Pro 9
To setup the Moog Music VST-AU Little Phatty Editor™ for Logic Pro 9:
1.Be sure to check your Host's VST Instrument plug-ins folder to make sure the Editor got installed there properly. Also
make sure the License Key and Preferences files are copied to the same folder as the plug-in.
2. Open Logic Pro 9. Create an Empty Project.
3. In the 'New Tracks' dialog that automatically pops up, select 'Type= Software Instrument'. Click 'Create' button.
4. In the Instrument track that was created, click the 'I/O' button (located on the far left near the bottom right below the 'I/O'
label and above the 'Stereo Out' button).
5. Select the Editor under 'AU Instruments/Moog Music/VST-AU Little Phatty Editor'. The plug-in should appear.
6. Open the 'MIDI Setup' view in the Editor and select the MIDI ports that are connected to your Synth for both the Editor
MIDI In and Editor MIDI Out sections. Close the MIDI Setup view.
7. Turn a knob in the Editor, you should see MIDI data being sent out to the port you selected in step 5. You can open the
MIDI Monitor to verify this as well and see what messages are being sent or your MIDI hardware MIDI activity LED's.
8. Open the 'Patches' window and load in a bank of patches. You can use the default bank provided with the software to
start with. When you change patches, the Editor patch data will be sent to the Synth.
9. In Logic, create another 'Audio' track and route the audio from the audio port your Synth is connected to.
Automation:
1. Select the track the Editor is on and click the 'View' menu and select 'Automation' (or use the 'A' key). You will see the
automation lanes for the Editor. You can add automation lanes for parameters you wish to automate. Please refer to the
Logic User Manual for more information on using automation.
*Note that Logic Pro does not have a MIDI Setup dialog that would allow you to select the ports you wish to activate or
deactivate. It uses the Mac IAC driver (OSX Audio/MIDI Setup application) for its MIDI ports. As a result, choose routings
carefully to avoid MIDI feedback loops or breaking the Editor's MIDI connection.
NOTES- Setup for other Hosts is similar to those listed above. Please refer to your Hosts documentation for setting up a
plug-in.
7
Notes on DAW Host Automation
If you want to turn knobs on the synth and have these knob movements recorded as automation of the plug-in parameters,
you’ll need to use your DAW to map MIDI from the knobs to the plug-in parameters, the same as you would map a generic
MIDI knob controller to the parameters of any other plug-in. The Editor’s knobs will automatically send the correct MIDI CCs
out to the synth, but associating CCs coming in from the synth to these same knobs is a mapping function of your DAW.
Manually drawing in parameter automation for the Editor knobs will send the correct CCs to your synth.
Setting Up the Plug-in for Standalone
The setup procedure for Standalone operation is fairly straightforward...
1. If other Audio/MIDI applications are already open, then take this into consideration when using the Standalone
application. Make sure the MIDI port you will be using is available for use with the VST-AU Little Phatty Editor™.
2. Open the VST-AU Little Phatty Editor™.
3. Open the 'Devices' dialog and select the preferred audio card settings and 'Host' MIDI Input. This is useful for controlling
the Synth from a remote MIDI keyboard.
4. Click the 'MIDI Setup' button in the Editor and select the MIDI Input and Output port your Synth is attached to.
5. Open the 'MIDI Monitor' view to make sure data is transmitted properly between Synth and Editor.
8
Working With the VST-AU Little Phatty Editor™
About Sound
The VST-AU Little Phatty Editor™ is a plug-in that deals only with MIDI data. As a result the VST-AU Little Phatty Editor™
makes no sound of its own. It is not an emulation software synth. The sound comes from the actual hardware synth itself,
which is what you want (pure analog hardware generated sound, but with plug-in control). Connect your Synth to your audio
card inputs as you normally would and use the Host to manage the audio tracks.
Using the Controls
Most controls on the VST-AU Little Phatty Editor™ are self explanatory as to their use. The display readouts will vary based
on the related ranges and values for that particular control.
Mouse Wheel Support
You can use the mouse wheel to change knob and slider parameters in single increments for fine-tuned parameter control.
Receiving MIDI Data
The VST-AU Little Phatty Editor™ can receive and interpret MIDI pitch wheel, modulation and control change data. All Editor
controls will respond to their correlated MIDI messages from the hardware itself. All controls respond to their correlated MIDI
CC numbers as listed in the Little Phatty User Manual.
The MIDI LED Indicators
When the VST-AU Little Phatty Editor™ receives or transmits Host or Editor MIDI data, the corresponding MIDI LED's will
blink to notify you. You can turn off the MIDI LED's in the 'MIDI Setup' view.
The About Screen
To view the About screen, click on the VST-AU Little Phatty Editor™ logo button. The about screen shows your registered
name and serial number as well as the product version.
9
The Graphical User Interfaces
Using The Graphical User Interface
The graphical user interface of the VST-AU Little Phatty Editor™ is designed for maximum ease of use, giving you easy
access to all of the parameters right on one screen. You are also able to rename, modify and browse the Patches right
inside the Editor itself. All controls are handled via either a slider, knob, combo box, button or text edit box.
The Main User Interface
The VST-AU Little Phatty Editor™ main screen (not to scale)...
The Patch Interface
The 'Patch' area allows you to access all the functions of the Patch:
1. Patch Name - Shows the Patch name. Click on this to edit the Patch name (limit 16 characters). Some hosts do not allow
plug-ins to use keystrokes on the main plug-in window. You can still use the Patch Manager to rename the Patch in this
case.
2. Patch Number - Shows the Patch number. Click on this to select the Patch number from a list.
3. Patch Increment - Move up one Patch.
4. Patch Decrement - Move down one Patch.
5. COPY button - Copy this Patch to clipboard.
6. PASTE button - Paste from clipboard to Patch.
7. GET PATCH button - This will get the current patch from the Synth and overwrite the Editor's patch.
10
8. RAND button - Click to randomize the Patch.
9. PATCHES button - Opens the 'Patch Manager' view (see 'Patch Manager' section).
10. SETUP button - Opens the 'MIDI Setup' view (see 'MIDI Setup' section).
11. MON button - Opens the 'MIDI Monitor' view (see 'MIDI Monitor' section).
MIDI Setup
To access the 'MIDI Setup' view, click the 'MIDI Setup' button. The 'MIDI Setup' view allows you to connect and control the
MIDI data coming into and out of the Editor and Host. You will need to open this view directly after instantiating the software
in order to setup up communication between the Synth and Editor. Once you have done this, the software will remember
your settings. You can toggle the filtering of specific MIDI data for both the Host and Editor MIDI data paths.
If you carefully inspect the diagram in the middle, you can see exactly what data gets routed where. To make things a bit
easier to differentiate, there is a color coding scheme for the MIDI data. The 'MIDI Monitor' view will show messages in these
same colors.
IMPORTANT NOTICE!!! Since this software allows you to route and filter MIDI data bidirectionally, it is best to activate only
the check boxes for the specific messages you require. Otherwise, it may be possible to create a MIDI feedback loop under
certain circumstances. It is up to the user to determine and understand the routings and connections being made to and
from the Editor and also diagnose where any problems may be occurring.
11
Host MIDI Setup
The top portion of the screen is for the 'Host' MIDI IN and Out data path. This is data that comes from and goes to the DAW
Host. MIDI port selection is achieved in the Host's MIDI setup.
Host MIDI In (data from Host):
The left portion is the Host MIDI In'. This is data that comes from the Host into the Editor. You may want to activate these if
you are using a MIDI keyboard controller for sending Note, Pitch, Modwheel data to/from the Synth or if you are sending
Host sequencer Note, Pitch, Modwheel data to the Synth through the Editor. You can activate these with the button on the
top right of the module. Set the filtering options. Only activate the data paths and messages that you need. It is
recommended to turn off the 'Program Change' functionality for all modules to avoid conflicts with the Editor.
Host MIDI Out (data to Host):
The right portion is the 'Host MIDI Out'. This is data that comes from the Editor to the Host. You may want to activate these if
you are sending data from the Synth or Editor for track recording in the Host. Set the filtering options. Only activate the data
paths and messages that you need. It is recommended to turn off the 'Program Change' functionality for all modules to avoid
conflicts with the Editor. Be sure to read the section on 'A note on Sysex MIDI and Host Plug-in Capabilities' as you normally
cannot send Sysex MIDI data to a Host. Also, Hosts will differ on how and what MIDI data they can interpret. Please refer to
your Host User Manual for this information.
Editor MIDI Setup
The bottom portion of the screen is for the 'Editor' MIDI IN and Out data path. These should be activated to allow
communication between the Editor and the Synth. You can activate these with the button on the top right of the module.
Editor MIDI In (data from Synth):
The left portion is the 'Editor MIDI In'. This is data that comes from the Synth into the Editor. All Editor controls will respond
to their correlated MIDI messages from the hardware itself. All controls respond to their correlated MIDI CC numbers as
listed in the Little Phatty Users Manual. Set the MIDI port and channel that the Synth is connected to. Set the filtering
options. Only activate the data paths and messages that you need. It is recommended to turn off the 'Program Change'
functionality for all modules to avoid conflicts with the Editor.
Editor MIDI Out (data to Synth):
The right portion is the 'Editor MIDI Out. This is data that comes from the Editor to the Synth. Set the MIDI port and channel
that the Synth is connected to. Set the filtering options. Only activate the data paths and messages that you need. It is
recommended to turn off the 'Program Change' functionality for all modules to avoid conflicts with the Editor. You will need
all the other options turned on except the 'MIDI Clock' data for proper communication between Synth and Editor.
12
The MIDI Monitor
To access the 'MIDI Monitor' view, click the 'MIDI Monitor' button. The 'MIDI Monitor' allows you to view all MIDI data that is
coming into or out of the Host and Editor. By default the view will show MIDI In/Out data from the Editor MIDI data path. You
can switch between Host and Editor MIDI In and MIDI Out views independently. The colors of messages are related to the
color coding found in the 'MIDI Setup' diagram. The 'Clear' button will clear the data in that view. The log view will show up
to 1500 messages before clearing itself automatically. You can copy the data in the log view to other applications if
necessary. The 'All' button will select and automatically copy to the clipboard that entire view's data. You can turn on/off the
view with the button on the right.
13
The Patch Manager
To access the 'Patch Manager' view, click the 'Patch Manager' 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 and Banks
the way you like. Patch slots allow you to rename and organize your Patches by simply dragging and dropping them to
another slot in either Swap, Copy, or Move mode. To do this, click on the Patch number box (with red numbers) and while
holding down the mouse button drag this Patch to another location by dropping it on the Patch name box (with white letters).
A valid drop target will be indicated by a red outline. You can also double click on a Patch number to go to that Patch. It is
14
recommended that you use only the 'Patch Manager' to load and save .FXB/.FXP files, as some Hosts may add data to the
header of the file and this may corrupt the interpretation of the file when reloading it.
The Patch Randomizer
The Patch randomizer allows you to easily create randomly generated Patches. Note that randomization applies to the
currently selected Patch and will overwrite the existing Editor Patch data. The randomized Patch will also be sent to the
Synth. The Patch name will be changed to 'Random #', so you know it has been changed. You may want to rename the
randomized Patch. Press the 'RAND' button to randomize a Patch.
Working With Patches
How Patches work
A Patch in the Editor represents a Patch on the Synth. When you change Patches in the Editor, the Patch data is sent to the
Synth in the form of MIDI CC messages. As a result, this data is sent to the Synth, but NOT permanently stored in the Synth.
15
This allows you to listen to Patches from the Editor while still preserving your original Patches that reside in the Synth. If you
wish to store the Patch data the Editor sent the Synth, then store it on the Synth by using the Synths 'write' function (refer to
the Little Phatty manual for information on how to store a Patch).
Using the Patch Manager
The 'Patch Manager' is the easiest way to work with Patches. For more information refer to the 'Patch Manager' section of
this manual. It is recommended that you use only the 'Patch Manager' to load and save .FXB/.FXP files, as some Hosts will
add data to the header of the file and this may corrupt the interpretation of the file when reloading it.
Changing the Current Patch
Use the arrow inc/dec buttons to the right of the display to change the currently selected Patch. Or you can use the Patch
number (ex. 1 of 99) combo box to jump directly to a specific Patch.
Renaming the Current Patch
To rename your Patch, simply click on the name in the display readout and type the new name of your Patch, then hit the
'Enter' key. Little Phatty Patch names are limited to 13 characters.
If you cannot type in text, then try using the Patch Manager to rename patches instead.
Using the Copy/Paste Button
You can easily copy and paste Patches to and from the currently selected Patch to another location. First select the Patch
you wish to copy by navigating to it. Now, click the 'Copy' button (you will notice the 'Copy' button light up). Next, navigate to
the Patch you wish to paste to. Now click the 'Paste' button (the 'Copy' button will turn off). This tool is invaluable for creating
variations of your favorite Patches and allows you to quickly build your library up.
How to Get Your Current Bank
Loading a Bank into the Editor from the Little Phatty
You can load existing patches that are already on your Little Phatty into the Editor by following a couple of setup steps first.
You will want to change these settings back when you are finished.
16
1. Make sure the Synth and Editor are connected bidirectionally.
2. Open the 'MIDI Setup' view and set the 'Editor MIDI Out' 'Program Change' to 'On'.
3. Now, when you change patches in the Editor, the Editor will be 'receiving' the patches directly from the Synth.
4. Simply scroll through patches to build your bank in the Editor.
5. Be sure to turn ' Program Change' to 'Off' when you are finished.
Using the 'Get Patch' Button
The Get Patch' function allows you to get the current 'Edit Buffer' in the Synth This may be useful if you have manually
edited the patch on the Little Phatty and need to get a 'snapshot' of the changes into the Editor. Clicking the 'Get Patch'
button after changing a patch in the Editor will appear to have no effect, but it is really just getting the same values it just
sent to the Synth, so there is no apparent change to the user.
MIDI Implementation Chart
The following MIDI data is transmitted (Tx) and Received (Rx) from the Editor and may be filtered as well...
Message
Channel
Tx
o
Rx
o
Notes
1-16
17
Mode
Note On/Off
Velocity
Aftertouch
Poly Pressure
Pitch bend
Modulation
Continuous Controller (+NRPN)
Program Change
System Common
System Real-time
System Exclusive
x
o
o
o
o
o
o
o
o
x
x
o
x
o
o
o
o
o
o
o
o
x
x
o
Omni mode
note numbers 0-127
0-127
0-127
0-127
0-127
0-127
0-127
0-127
x = no
o = yes
For a full list of the parameters and their value ranges, please refer to the Little Phatty User Manual.
Legal Information
License Agreement
1. This is an agreement between Licensor and Licensee, who is being licensed to use the named Software.
18
2. Licensee acknowledges that this is only a limited nonexclusive license. Licensor is and remains the owner of all titles,
rights, and interests in the Software.
3. This License permits Licensee to install the Software on more than one computer system, as long as the Software will not
be used on more than one computer system simultaneously. Licensee will not make copies of the Software or allow copies
of the Software to be made by others, unless authorized by this License Agreement. Licensee may make copies of the
Software for backup purposes only.
4. This Software is subject to a limited warranty. Licensor warrants to Licensee that the physical medium on which this
Software is distributed is free from defects in materials and workmanship under normal use, the Software will perform
according to its printed documentation, and to the best of Licensor's knowledge Licensee's use of this Software according to
the 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 the extent permitted by law, THE ABOVE-STATED LIMITED WARRANTY
REPLACES ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, AND LICENSOR DISCLAIMS ALL IMPLIED
WARRANTIES INCLUDING ANY IMPLIED WARRANTY OF TITLE, MERCHANTABILITY, NONINFRINGEMENT, OR OF
FITNESS FOR A PARTICULAR PURPOSE. No agent of Licensor is authorized to make any other warranties or to modify
this limited warranty. Any action for breach of this limited warranty must be commenced within one year of the expiration of
the warranty. Because some jurisdictions do not allow any limit on the length of an implied warranty, the above limitation
may not apply to this Licensee. If the law does not allow disclaimer of implied warranties, then any implied warranty is limited
to 365 days after delivery of the Software to Licensee. Licensee has specific legal rights pursuant to this warranty and,
depending on Licensee's jurisdiction, may have additional rights.
5. Notwithstanding the foregoing, LICENSOR IS NOT LIABLE TO LICENSEE FOR ANY DAMAGES, INCLUDING
COMPENSATORY, SPECIAL, INCIDENTAL, EXEMPLARY, 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 the 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 the Software upon termination of the License.
9. This License Agreement is the 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 the earlier of Licensee's
signature or Licensee's use of the Software.
Disclaimer
By installing and using this product you agree to the terms and conditions set forth in the License Agreement as illustrated in
the installation of the software.
Moog Music, and the Little Phatty and Slim Phatty names and logos are the property of Moog Music. Steinberg and the VST
name and logos are the property of Steinberg Media, GmbH. Apple Computer and the Audio Units name and logos are the
property of Apple Computer.
19
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement