Vous êtes sur la page 1sur 35


(Cubendo Power User)

user manual

ver. 1.0

Section 1 - Introduction 3

Section 2 - Installation 4

Section 3 - GUI overview 15

Section 4 - Features 21

4.1 Assigning a function to a button 21

4.2 Quick Access buttons 25
4.3 Trackslider / Timeslider 27
4.4 Quick Controls sliders (CPU-A and CPU-B) 29
4.5 Macro button/s 31
4.6 Track buttons on the CPU-C 31
4.7 Specials on the CPU-C 32
4.8 Cubase vs. Nuendo 33
4.9 Extra button text 34

Section 5 - FAQ 35

(click here for the online version of the manual)

- Section 1 - Introduction -

THANK YOU for purchasing the CPU-BUNDLE - a new professional

tool designed for speeding up your workflow with Cubase or Nuendo!

Such a modern software for creating music or professional audio post production like
Cubase and Nuendo can have hundreds useful functions that aren’t directly accessible through
keyboard shortcuts, buttons or on-screen icons. There is just not enough space on the software’s
GUI for all of them at the same time. We can find them in menus and sub-menus but for a quick
access, You -the User- need to assign them to your computer’s keyboard or external controllers.

My initial idea for the CPU-BUNDLE was to create a tool that would help me with many
day-to-day tasks during my professional work as a composer and sound designer.

Modern technology was always a big part of a professional audio environment and that
is why I am a firm believer that in few months/years every professional in our field of work will
use some kind of touch device for a more natural and easy access to commonly used tools and
functions. We all have our own approaches to how we work and what tools we use to achieve
our goals. With this in mind I have developed a software controller that will allow You to quickly
setup available buttons or sliders to functions and commands inside of Cubase/Nuendo.

Many of them are already pre-programmed by me but some assignable buttons and sliders can
and should be programmed by the user.

The Generic Remote concept I use extensively for over 10 years now was introduced in
Cubase 4 in 2006. The whole CPU-BUNDLE consists of 4 VST plugins (CPU-A, -B, -C and -D) and
is a marriage between Steinberg’s GR’s, Logical Editor presets, Project Logical Editor presets
and a clever GUI design all packed in a VST plugin format for easy installation, accessibility and
siple exchange between Your projects. There is also no need for any WiFi network connections.
CPU plugins reside inside Your DAW and are not a 3rd party software that runs next to Cubase or
Nuendo thus don’t need to be instantiated before your DAW starts. I went with the VST format
also for another important reason - as is the case all other VST instruments, we can easily make
our own .vstpresets! Skipping through them and selecting a setting that suits our needs at the
moment is a breeze and makes CPU a very powerful tool. Although using a 10-point touch screen
with a 1920 x 1080 resolution would be the optimal setup, a regular mouse and a non-touch
monitor will also work and still be fun to use. Please refer to the next parts of this manual for
further instructions on how to install, setup and use the CPU-BUNDLE.

Please visit my 14bitMIDI YouTube channel for more videos and please feel free to contact me
for more personal support using Skype: a_14bitMIDI_support

I wish You fun with this product!

Karol Obara
- Section 2 - Installation -

Please unpack the downladed .zip file to your Desktop.

Inside you should find folders with all the needed assets for Windows and for OSX.

Windows users should run the provided .exe installer and follow the instructions on the screen.
More steps are described below.
Mac users will have to manually copy/paste files into certain folders following the steps below.

The whole “installation” process takes few minutes and consists of:

Step 1. setting up virtual MIDI ports for two-way communication between the
plugin and the DAW’s Generic Remote instances (using free 3rd party
loopMIDI on Windows and Apple’s own IAC Driver on OSX)

Step 2. copy/paste of the provided Logical Editor presets into the DAW’s
LE preset folder

Step 3. copy/paste of the provided Project Logical Editor presets into the DAW’s
PLE preset folder

Step 4. copy/paste of the CPU-A, -B, -C and -D .dll files into your 64-bit VST
plugins folder
(this need to be done manually on OSX, on Windows provided
“14bitMIDI_CPU-BUNDLE.exe” takes care of this step)

Step 5. copy/paste of the provided Default.vstpresets into the DAW’s VST3 Presets
(this need to be done manually on OSX, on Windows provided
“14bitMIDI_CPU-BUNDLE.exe” takes care of this step)

Step 6. creating and setting up 20 new Generic Remote instances, routign MIDI INs
and OUTs and importing provided GR-1, -2, -3, -4 and GR-5.xml’s

Installation steps explained:

Step 1.

Windows: download and install a free 3rd party software loopMIDI
A computer restart might be needed after the installation.
Double-click on the loopMIDI icon in your taskbar to open
the setup window.

Highlight any existing default ports and delete them using the
“-” button.
Give a new name for the new port: “CPU-A-IN” and use “+” to
create it. It is very important to name all the new ports exactly
as described here!

Create 8 new ports altogether: CPU-A-IN, CPU-A-OUT, CPU-B-IN,
Tip: Activate the “Autostart loopMIDI” and your ports will always
be available after system restart without the need to start
them manually.


OSX: search for “Audio MIDI Setup” and under “Window”open

“Show MIDI Studio”:
Open the “IAC Driver Properties” and using the “+” button create 8
new ports:

Rename them accordingly: CPU-A-IN, CPU-A-OUT, CPU-B-IN, CPU-B-OUT,
CPU-C-IN, CPU-C-OUT, CPU-D-IN, CPU-D-OUT Make sure the new ports
are named exactly as desicribed, this is very important!

Make sure your Device Name reads “IAC Driver”!

This is Apple’s default name and if for whatever reason you have
changed it and use a different name instead, contact me for a
solution. CPU plugins are looking for this default name and will
not work properly otherwise. I will send you new OSX build with
your custom name used if needed.

Step 2 & 3. Copy/paste the provided Logical Editor presets into the DAW’s
LE preset folder

Copy/paste the provided Project Logical Editor presets into the

DAW’s PLE preset folder

Windows: Unpack the two .zip files created by the .exe installer inside the C:\Users\*YOURUSERNAME*\Documents\
VST XMLs\14bitMIDI folder. The entire unzipped “14bitMIDI” folder containing .xml files for the LE and PLE need to
be manually copied to the appropriate locations (see below).

OSX: Open the unzipped folder,inside you will find following two folders with “14bitMIDI” sub-folders that need to
be manually copied to the appropriate locations.

The unzipped folders:

Paths for Logical Editor presets:


C:\Users\<<YOURUSERNAME>>\AppData\Roaming\Steinberg\<<YOURDAW>>\Presets\Logical Edit


file:///Applications/>>YOURDAW.app<</Contents/presets/Logical Edit

Paths for Project Logical Editor presets:


C:\Users\<<YOURUSERNAME>>\AppData\Roaming\Steinberg\<<YOURDAW>>\Presets\Project Logical Editor


file:///Applications/>>YOURDAW.app<</Contents/presets/Project Logical Editor


!*!*! If you plan to use CPU plugins with both DAW’s - Cubase and Nuendo - make sure !*!*!
!*!*! that you copy LE and PLE presets to both - Cubase and Nuendo presets folders !*!*!
Mac users!
To “Show Package Contents” of your DAWs .app ctrl+click
(or click Right mouse button) on the .app icon inside “Applications”.

Please copy the “14bitMIDI” folders with all theirs sub-folders to the
locations described above! CPU will search for those presets and will not
work properly if they can’t be found!

Step 4. Copy/paste the CPU-A, -B, -C and -D .dll files into your 64-bit VST
plugins folder
(this need to be done manually on OSX, on Windows provided
“14bitMIDI_CPU-BUNDLE.exe” takes care of this step)

Please paste CPU-A, -B, -C and -D.vst files into your main VST plugins folder:

Your DAW will find any new VST plugins next time it starts. You can also use
the “Plug-in Manager” (Devices > Plug-in Manager) to manually rescan this
directory. Please contact me if you encounter any problems with this step.
Step 5. Copy/paste the provided Default.vstpresets into the DAW’s VST
Presets folder (this need to be done manually on OSX, on Windows
provided “14bitMIDI_CPU-BUNDLE.exe” will take care of this step)

Please copy/paste the entire “14bitMIDI” folder found inside the
“vstpresets” to this Presets location on your system:

CPU will search for those presets and will not work properly if they
can’t be found!

Step 6. Creating and setting up 20 new Generic Remote instances,

routing MIDI INs and OUTs and importing provided
GR-1, -2, -3, -4 and GR-5.xml’s

This step is done exactly the same way on both OS platforms.

Open your DAW of choice and go to “Device Setup”.

Before you set anything else, please select the “MIDI Port Setup” inside
the MIDI folder in your “Device Setup” window and deselect all “x”
marks found in the “In ALL MIDI” column next to your newly created
CPU MIDI ports. The “State” column should show “Inactive” on all of
the new MIDI ports created with loopMIDI (PC) or IAC Driver (OSX).
This way we will avoid problems with two-way communication between
CPU plugins and your DAW!

Now you need to add 20 new Generic Remote instances (5 for each
CPU plugin - A, B, C and D). To do that click on the “+” sign in the
upper left corner of the “Device Setup” window and choose “Generic
Remote” from the pop-up list. A new GR instance should appear in the
left column of the “Device Setup” window under “Remote Devices”.
Do this 19 more times and you will create and see the new GR’s 2-20.

Select the first GR from the “Remote Devices” column on the left side.
Assign MIDI Input to “CPU-A-IN” and MIDI Output to “CPU-A-OUT”.
Do the same for GR instances 2-5. Generic Remotes 6-10 should be
routed to “CPU-B-IN” and “CPU-B-OUT”, GR’s 11-15 to “CPU-C-IN”
and “CPU-C-OUT” and GR’s 15-20 to “CPU-D-IN” and “CPU-D-OUT”.
After every change made to the GR’s you need to press “Apply” to save
the changes and make them permanent.

At this point there is one last but very important task ahead of you.
The import of the correspodning .xml files. If you are on a Mac, you
can find the “XML’s” folder inside the main unzipped folder. If you are
on PC, the .exe installer has already created a “VST XMLs” folder
inside your Documents folder.

C:\Users\<<YOURUSERNAME>>\Documents\VST XMLs

There you can find all the .xml’s (GR-1.xml, GR-2.xml, GR-3.xml,
GR-4.xml and the GR-5.xml) needed for this last step.

Select the first Generic Remote instance from the column on the left
and click on the “Import” button in the upper right corner of the
“Device Setup” window. New “Import Generic Remote” window will
appear and you need to point to the “GR-1.xml” file. Apply. Done.

Now select the second Generic Remote instance “Generic Remote 2”,
press “Import” and point to the “GR-2.xml” file. Apply. Done.

Ok, I hope you get the idea here, now select the third Generic Remote
instance “Generic Remote 3”, press “Import” and point to the
“GR-3.xml” file. Apply. Same drill for “Generic Remote 4” >> Import >>
“GR-4.xml” and finally for “Generic Remote 5” >> Import >>

This way you have imported all the .xml’s needed for the CPU-A to
work properly.

Do the same for CPU-B (GR’s 6-10 >> GR-1.xml - GR-5.xml),

for CPU-C (GR’s 11-15 >> GR-1.xml - GR-5.xml) and finally for CPU-D
(GR’s 16-20 >> GR-1.xml - GR-5.xml).


For a quick tour around the CPU’s GUI and features please refer to the next section.
- Section 3 - GUI overview -

As you already know the CPU-BUNDLE consists of 4 separate VSTi plugins

(CPU-A, -B, -C, -D) that share a lot of the same features and GUI elements.
Since there are many users with different needs and since I wasn’t able to put
all the GUI element I wanted on one panel without being forced to make them too
small, too hard to read or to operate, I have decided to create 4 different ones
with slight changes to each one of them. This way I was able to include (almost) all
the features I wanted the way I feel makes most sense for the end user. You can
decide for yourself which CPU flavor fits your workflow best or maybe, like me, you
will decide to use different versions for different projects.

The one thing that confuses some people at first is that you load the CPU as a VST
Instrument. Technically it isn’t an instrument in the usual sense of the definition.
It is not producing any sounds and all it does is creates a link between the user and
all of the cool functions inside your DAW. Plus few more. I have decided to go this
route because this way the end user can benefit from the .vstpresets saving option
and from the fact that this “Instrument” will be saved and recalled with every
session it was used on!

So, let’s start with the GUI. First load the CPU-A into your session. You should be
able to see all 4 VST’s after you choose to “Add Instrument Track”:

This is how the CPU-A GUI looks like:

This is the smallest version of the 4 available plugins. The fixed size of the GUI is
1920 x 700 px. and takes up more than a half the hight of a 1920 x 1080 px. screen.
The fixed size of CPU-B, -C and -D is 1920 x 1080 px. and fills the whole screen.

Below you can see a 1920 x 1080 screenshot with the CPU-A and a little mix
console above sharing the same screen.



You can already recognize certain building blocks that are used on all versions
and some specific elements used only for that particular plugin flavor.

1. User-assignable buttons for

executing commands and
Process >> Plug-in’s.

2. Panorama and Volume section

with 14-bit resolution sliders
and buttons triggering
pre-defined values.

3. Quick Controls section with
8+8 14-bit resolution sliders
for seamless track or VST
Instrument control.

4. Quick Access section with

main pre-defined category
buttons and 4 sub-category
buttons for switching through

5. Pre-defined buttons for

triggering commands, LE or
PLE presets depending on the
Quick Access buttons selection.

6. Pre-defined buttons for

Time Range selection
(for use with Trackslider)
and some other functions
(here the Quantization selection).
7. Extra buttons for triggering
various tasks depending on
the combination or state of
other buttons (triggering
random QC slider values,
resetting values, labels etc).

8. Trackslider - a 14-bit resolution

slider for quick navigation
between tracks or through
sessions timeline depending on
what Time Range preset has been

9. Play / Edit button - allows

access to a drop-down list of
all available commands for
each assignable button, Cubase
or Nuendo mode selection and
few others functions depending
on the plugin version selected.

The main difference between CPU-A and CPU-B is of course the size and thus the
amount of assignable buttons available to the user - 8 on CPU-A vs. 96 on CPU-B!
Other then that, they are pretty much the same with few minor differences like the
extra sends sliders, click volume slider and midi velocity buttons on the CPU-B.

CPU-C brings some more “Process >> Plug-in” buttons - 24 vs. 8 - and instead of 16 big
sliders for Quick Controls you can find 16 small ones for QC’s and Sends, 64 buttons
for a direct selection of the first 64 tracks in your session, midi channel selector, extra
sliders for various LE and PLE presets (track colors, fades, velocity and events position
randomization, buttons for moving events, buttons for triggering popular commands etc).

CPU-D is very button-heavy - 96 assignable buttons for commands and 96 assignable

buttons for “Process >> Plug-in”. In the lower part you will find Quick Access buttons
that you have already seen in previous CPU versions.

This concludes the quick GUI overview. In the next section you will find more details
about specific operations while using the CPU-BUNDLE.

- Section 4 - Features -

My main goal at the beginning of this project was to create a system that

- will allow me to quickly assign commands to buttons on the screen,

- to be able to click on them or to touch them and trigger a certain behavior,
- to be able to re-assign them if my needs should change,
- to be able to save my settings as presets and recall them for later use,
- to be a part of my Cubase / Nuendo session and not a 3rd party app running next to it,
- to look nice and simple since I will have to stare at it for hours ;)

I am convinced that I have achieved my initial goals and during the development process
few more functions were introduced and implemented!

1. Assigning a function to a button

In the default state all the assignable function buttons are grey and shows “EMPTY...”:

The “Process >> Plug-in” buttons are also grey and shows “NO PLUGIN...”
(BTW: they are not used to open/call insert plugins but to process a selected audio
event with a plugin from a drop-down menu!)

Press the Play/Edit button to activate the EDIT state of the plugin (“14 bit MIDI” text).
Two things will happen: the “14 bit MIDI” text will start to roll and all the assignable
buttons will show you a coloured corners indicating the EDIT mode:
Now, press the button you want to assign a function to, a menu list with all available
categories should appear:

Let’s say you want to assign the “Set Timecode” function to a button.
Select the “Project” category and the “Set Timecode” function:

Your button should change

and should look like this:
Press another empty button, select the “Channel & Track Visibility” category and choose
the “Create Track Visibility Configutarion” function:

Your button should change

and should look like this:

Press the rotating Play/Edit button (“14bitMIDI” text) and this will take you back to the
Play mode. Coloured corners will dissapear and the button will stop rolling that fast.
Both buttons should be active and ready to use. This is how easy it is to assign function to
a button!

In the upper part of the button the category name will be displayed (in color),
in the lower part the selected function will be shown (in white).

I tried to make this process as easy as it gets and after many iteration this is the final
version where only few clicks/touches are needed to create a new button assignement.

The steps are exactly the same for “Process >> Plug-in” buttons with the only difference
that in the standard version of the VST, the pop-up list will show you only the Steinberg’s
default plugins and a Waves plugins collection as an added bonus since many audio
professionals own and use them on a regular basis. If you don’t own any Waves plugins
but assign a button to the plugin from a list, the button will just do nothing.

If you would like to make use of all the plugins you own and use on your system, please
contact me and depending on the amount of work involved in the implementation of this
custom feature, I will make you an offer for the customization fee.

Assigned buttons:

2. Quick Access buttons

Quick Access buttons are pre-assigned by me to execute certain useful functions and
can not be re-assigned by the user. They make use of commands, Logical Editor presets,
Project Logical Editor presets and some other functions programmed into the plugin.

All CPU plugins use some version of Quick Access buttons - they might be positioned
differently on the GUI and may use various numbers of buttons but the main idea behind
stays the same - some buttons select the main category, others selects sub-categories and
depending on the selection another group of buttons changes their look and assignement.
It might sound complicated but is actually a very simple concept as soon as we see it in

Please select the “TRANSPOSE, CC’s, LANES...” button on the lower left side and the
“TRANSPOSE SELECTED” button on the lower right (CPU-A). Notice how the selected
buttons change to “orange corners” and “blue text” indicating the active selection.

In-between these two groups of (rather grey) buttons you see (more colorful) buttons
that will change their assignements, names and look depending on the combination
made above.

Now, select the “ADD PITCH TO SEL.” button on the lower right side of the GUI...

... followed by the “CC’s +/-” sub-category ...

... and finally the “LANES & MORE” sub-category.

At this point you get the idea and with some math we can come to a conclusion that
on the CPU-A we are having 40 buttons that (at least in theory) can be changed by
the combination of other 10x4 buttons giving us staggering 1600 possible assignements!
Of course in reality I have decided to go with less than that for various, mostly aesthetic
and logical reasons, but now you understand the mechanics of it a bit better.
Please play with these buttons and explore all the categories that hopefully will be
usefull in your work.
As already mentioned before, the buttons placement may differ between CPU-A,B,C,D
but the logic behind is the same and you will quickly recognize them on each GUI.

Here yet another example using the “SELECT SHOW/HIDE OPEN” category but this time
using the CPU-C.




3. Trackslider / Timeslider

The Trackslider can be found on each of the four VST plugins.

It is this big, horizontal, 14-bit resolution slider located on the bottom of the GUI and
spreading over the entire width of the plugin window. You can imagine the beginning of
the slider on the far left as a 0% mark and the endpoint on the far right as the 100% mark.
It doesn’t matter how many or how little tracks there are in your session (including all
the Inputs and Outputs) this slider will allow you to quickly scroll through all of them!
Its function is very simple yet very helpful, especially when dealing with sessions
containing huge track counts.

|<---------- 25% ---------->|<--------- 25% ---------->|<----------- 25%--------->|<--------- 25% ----------->|

The graphic elements used for the creation of this slider clearly indicate 4 parts, each
taking up 1/4 of the entire width. Let’s say your session consists of 400 tracks, in that
case avery 25% range will scroll thru roughly 100 tracks. If your whole session uses only
4 tracks ... well, you’ve guessed it right ;) Just try, and you will get the feel for it pretty
fast. This is one of those features I personally couldn’t live without anymore.

There will be some situations where we would like to switch this function temporarily off.
You can easily do this by pressing the “TRACKSLIDER IS ON/OFF” button. Just to make
sure we always know in what state the slider currently is, you will see a red line when it
is switched off. Same goes for the “...ON/OFF” button.

Double-clicking/tapping on the slider will take the “sniper finder” to the exact center
position. This will be important later on when some other functions will depend on the
position of the “finder”.

On this occasion I would like to explain how is Cubase/Nuendo counting and ordering
tracks. We could imagine a big analog mixing board where all the Inputs are on the far
left side of the console, all the Outputs are on the far right of the console and between
them are all the tracks we add or import into our session. Let’s pretend our project
consists of 8 Inputs, 10 audio tracks, 10 midi tracks and a single stereo Output.
In the main project window we will see 10 audio and 10 midi tracks numbered 1-20.
The mix console window will show us all 3 parts of our “imaginary mixing console” with
all of the 8 + 20 + 1 tracks:

The Trackslider will always follow the way the mix console is “counting” tracks, not the
project window. Following this example the Trackslider will select “Stereo In 1” if the
slider position is all the way left, “Audio 07” if in the middle 50% position and the
“Stereo Out” if all the way to the right. “Audio 07” happens to be the exact middle of
all tracks in our project: 14 + 1 + 14.
If there would be no Inputs in our session and only 10 audio tracks, 10 midi tracks
and a single Stereo Out the first selected track (0% mark) would be the “Audio 01”,
“Audio 11” would be the exact middle (50% mark) and the “Stereo Out” would be the
last track (100% to the right). In other words, when selecting tracks using Trackslider
all the Inputs and Outputs in the project are taken into account.

“Timesliding” - this is another feature of the slider that I use extensively in my own work.
Being able to move the sessions playhead through timeline using just a finger or a mouse
was always a requested feature of mine and now it is here!

First, you need to select a time-range in which the slider will operate.
To test this, please select the first “1 MIN.” button:

Notice the subtle change of the “sniper finder” from grey “TRACK” to orange “TIME”.

Now you can move your playhead in the range of the first 60 seconds. As you can see
tha range can be extended up to 4h 30min. That should give every user plenty of options.
The beginning of the slider (0% mark) will always indicate the beginning of the timeline.
The maximum position (100% to the right) will be the maximum of the range selected.
Again, try for yourself to get the feel for it. To go back to “Tracksliding” just press the
time-range button again. You can also deactivate this function temporarily by pressing

4. Quick Controls sliders (CPU-A and CPU-B)

This sliders should be in a way self explanatory.

Sometimes I meet people that confuse both concepts though - VST QC’s vs. Track QC’s.
I will try to clarify here.

VST Quick Controls.

If you for example create a new Instrument Track and select Padshop as its Instrument,
Cubase/Nuendo will create a new track and load one Padshop instance into the VST
Instruments Rack. If you take a look at the VST Instr. Rack, you will see one Padshop
instance panel with 8 rotary knobs for various parameters - Master Volume, Master Tune
etc. This is what VST QC’s will control when the Padshop track will be selected or
whenever you set the Remote Control Focus for the VST QC’s by pressing the orange
icon on the panel (see picture below).

Now you can change this first bank of 8 parameters by moving VST QC’s sliders.
Please note, that as soon as you change the “Page 1” to “Page 2” another bank of
new 8 parameters will be shown and assigned to the 8 VST QC’s sliders.

Track Quick Controls.

When you select a track in the project window and your Inspector is visible, the last
category shown in the Inspector are Quick Controls and to be exact, they should actually
be called Track Quick Controls, who knows, maybe this is the reason for the confusion.
If you click on the little cube(?) icon next to the “Quick Controls” text (properly called
Preset Management), a dropdown list with some predefined presets will appear. Now,
depending on what kind of track you are at the moment, some of the presets will work
and some will not. I know, right, Steinberg can confuse sometimes :) Let’s assume for a
moment that you have selected an audio track. Select the first preset “Volume/Pan/
Pre-Filter/Sends”. All 8 of the QC’s should be populated by parameters now. This is what
the Track Quick Control sliders will control on that track from now on.

Of course you can change the assignements,

make use of the “Learn” function, save own
presets etc. The key here is to experiment
with different kinds of tracks.
There are differences if the track is an audio
track or a VST Instrument track.
I like to use them for controlling Sends FX’s
and various parameters of all the Virtual
Instruments I use in my work.

On the GUI of the plugin you can find two small buttons named “RNDM”.
I have implemented an option to randomize the values of all the QC’s sliders.
Let’s say you are creating new patches for your VST synth and would like to roll the dice
so to speak. The results might be interesting since all 8 sliders will change at once.
I have found out that sometimes I need just a bit of randomization without going too
crazy, this is where the two implemented random modes comes in play.

First, press the “TRACKSLIDER IS ON/OFF” and make sure the Trackslider is turned off
(red line, remember?). Press the “RNDM” button. If the Trackslider was in the exact
middle position (double-click/tap to put him there) the values of sliders changed to
100% random values, if the Trackslider was anywhere but in the exact middle position,
the sliders values changed randomly by +/- 10% only. This is very useful if you have
already found a setting you like but wish to change/morph it a bit. Remember that you
can write/record the parameter automation changes when you press the “RNDM” while
the “Write” for a track is enabled. I hope this will give you some ideas for how to use
this feature in your work.

During the initial betatests, some users asked me for an option to change the colors of
the QC’s sliders. Here it is. Press the Play/Edit “button” (the “14bit MIDI” text) to go
to the Edit mode. Now you can see that the generic names under each slider changed to
some color names. Press on that name to browse through the available colors for each
slider. Someday you will wish to change all 8 sliders colors at once. To do this, while still
in Edit mode, deactivate the “Trackslider” (“TRACKSLIDER IS ON/OFF” button) and
select a color under the first slider. This little trick will change all of them in one go.

I have mentioned already generic names under each slider. By double clicking them
you will be able to change the sliders name. If you want to keep your changes - sliders
names and colors assigned - you need to save the vst preset. To do it, click on the little
cube(?) symbol on the plugins GUI:

This is the standard way of saving

presets in Cubase/Nuendo and
I am sure you don’t need any
further explanation at this point.
5. Macro button/s

Sometimes you might need to trigger a sequence of few commands in a row to speed
up things even more. This can be achieved by pressing the “FIRE 1-8 MACRO” button
on the CPU-A or one of 8 little macro buttons on the CPU-B, CPU-C or CPU-D.

In case of the CPU-A, this triggers each of the 8 assignable buttons in a sequence with a
slight delay between each button press (4 buttons from the upper row left to right and
4 from the lower row left to right).

On other GUI’s you can see little numbers 1-8. Pressing the “1” for example, will trigger
all 12 buttons from the upper horizontal row left to right. Pressing the “2” triggers the
second horizontal row of 12 buttons left to right etc.

To avoid accidental triggering of the macro buttons, they will be active only when the
“Trackslider” is turned off!

Tip: If you need a longer break between two adjecent command execution, leave one
“EMPTY..” button in between, this way you will add extra 30ms between commands.

6. Track buttons on the CPU-C

You can quickly select from the first 64 tracks using this buttons (remember that Input
tracks are also included). While in Edit mode (press on the “14bitMIDI” text), you
can rename this buttons to better describe what exactly is on those tracks. This
changes will be saved with the .vstpresets allowing you to create different sets for
different sessions or templates. If you want to restore the button names to their
default form all at once, set the “Trackslider” all the way to the right to its maximum
position and press the “XTRA” button.


7. Specials on the CPU-C

On the CPU-C you can find a group of special sliders and buttons that are targeting
some commonly used operations when composing with midi, mixing audio etc.

“SELECT MIDI CHANNEL” - if a midi track is selected this slider/buttons will change the
Midi In channel number. This feature does not work with the
Instrument Tracks! (for a reason still unknown to me). Be
aware that if you select a midi track and change its midi In
channel number and proceed to a track of another type
(Audio, Instrument etc.) and move the slider or buttons, the
last selected midi track will still be active for changes! This
is an issue that I am aware of and I am inverstigating ATM.

Next are buttons for changing the Velocity or Position (or both) of selected midi events.
Very usefull for “humanizing” quantized midi. Selected CC’s can also be changed by
small steps up and down. “VELO” is just a velocity slider changing the velocity value of
selected events. “COLOR” slider will change the color of selected track or event
(or both) depending on the selection made with buttons. To keep things easier for the
user, I am using only default 16 colors here. More sophisticated settings (the whole color
pallete) are available for custom clients as an extra customization option. The little
“Rndm” button will select a random color for us. “FADE” slider can change the fades of
a selected audio event (In, Out or both depending on the selection) by the amount
selected in the Quantize Presets drop down menu. For smaller/smoother in-, and
decrements use smaller quantization values (1/32-nds, 1/64-ths, 1/128-ths etc.).
“MOVE” buttons will do to the selected audio event exactly what they say depending on
the selection of course. Just try for yourself. “TRACK VOL” is self explanatory.
Last but not least you have mini sliders for Sends and Track QC’s. You can change their
names with a double-click on the default names. New names will be saved with the
.vstpreset. You can restore all the default names in one go using this combination:
“Trackslider” off and in the 0% (all the way to the left) position + press on the “XTRA”
button for QC’s, same but with the slider in the exact middle position for the Sends.
8. Cubase vs. Nuendo

The CPU-BUNDLE supports the most current versions of both DAWs (Cubase in version
8.5.15 and Nuendo in version 7.0.40) and works with previous versions of both.
Of course, features/commands introduced in Cubase 8.5 can’t triggered on systems
using Cubase v.6 or v.7 but this is somehow to be expected ;)

Even with the most current versions there are some differences in features between
Cubase and Nuendo. The ADR track for example, can only be found in Nuendo and
some new Cubase 8.5 features are still to be implemented for the Nuendo users.

The CPU-BUNDLE takes this differences into account.

Look at the GUI and search for the small “CPU-C” text (in case of the CPU-C plugin).
Go into Edit mode and this text will change to CUBASE or NUENDO (depending on the
current selection).

This way you can check in which DAWs mode you are at the moment.
If you wish to change from Cubase to Nuendo, just click on the “CUBASE” text and it will
change to “NUENDO” and vice versa.

Now the important bit: After switching from let’s say Cubase to Nuendo mode, press
the “14bitMIDI” rolling text to leave the Edit mode and click
on the “cube”(?) symbol (Preset Management) and choose
“Save as Default Preset” option! Confirm with a “Yes”. Remove
the plugin (just closing the plugin window is not enough) and
reopen the VST plugin (“Add Instrument Track...” again).
Now the CPU plugin is in Nuendo mode! To make sure go to Edit
mode and check what is displayed: “NUENDO” or “CUBASE”.

This are the categories menus for Cubase vs. Nuendo side-be side:

9. Extra button text

One of the categories shown in the pop-up menu after selecting a button in Edit mode is
the “Select Track” category. This way you can set up a button to always select a certain
track in your session. In this standard version of the CPU you can select from the first 128
tracks. If you need much more, please contact me for custom solution.

Let’s say I want to be able to select tracks

12, 24, 92 and 126. This is how they look
after the connetion to buttons was made:

There is an option to give tracks extra names.

Please double-click on the very small spot
in the upper part between first two buttons
(ca. only 3 pixels wide).

A text box will appear and you should be able to input a name. Click Enter. Done.
Repeat the operation from all other buttons (double-click the outside of the upper
right corner) and your buttons should look something like this:

The new names will be saved with the .vstpreset but be careful, when you change the
button assignment to new command from a new category, the extra text will still be
there causing an unpleasant text-mess! You can clear the extra names one-by-one the
same way you have created them or you can do it in one go for ALL buttons using this
“Trackslider” off and in the 100% position (all the way to the right) + the “XTRA” button.
I hope that I haven’t skipped anything important and all the functions of remaining
buttons and sliders that wasn’t explained so far are easy to understand.
In case there are more questions, feel free to contact me and I’ll do my best to clarify.

- Section 5 - F.A.Q -

1. Can I resize the GUI for use with different screen resolutions?
- No. The 1920 x 1080 res. was my target from the beginning since this size is commonly
used for touch screens, big enough to read small text on it and still small enough to put
on the desk in front of you.

2. Can I change the background color of the GUI? It is too dark for my taste.
- Not in this version. After initial tests, black BG proved to be best for long hours in the
studio and screens generates least amount of heat with it. Maybe next version though.

3. Can I reposition elements like buttons or sliders on the GUI the way I wish?
- No, by design this isn’t possible. At least not in current version. I spent many hours
designing the look and feel of the GUI and hopefully spare you the “fun” of doing it.
Please let me know if you have any ideas for improvement. I’m open for your input.

4. Can I freely assign Continous Controllers to QC sliders?

- You can program your VST instrument this way that QC’s write parameters like
Modulation, Volume, Expression etc. As of freely assigning CC’s, this is not possible at
the moment but I am already working on some ideas to make it happen in the future.
This has to do with how CPU communicates with the DAW and how many midi ports it
can handle at any given moment.

5. Are future updates going to be paid updates?

- Updates that will enhace already existing features, fix bugs, add small features etc.
will be certainly free. Entirely new versions involving new scripting and development
has to be charged for. I need serious amounts of coffee to live, just so you know ;)

6. Why is 14-bit midi slider better?

- 14-bit resolution (aka high resolution midi) allows for 16.384 equal steps between the
minimum and maximum. The usual 7-bit allows for 128 steps. For many tasks 7-bit is
totally fine. For controlling parameters like volume, pitch changes, filters, etc.,
the higher resolution the better - more smaller steps vs. fewer bigger steps in between
changes - our ears are very hard to fool when it comes to subtle differences.

7. Is it possible to develop a custom CPU-”x” for me, tailored for my personal needs,
workflow, libraries, colors, pictures, graphics etc.?
- Of course. This falls under the definition of a custom job. Just let me know what you
need and we can plan this project together over Skype, mail or face-to-face.
Knowing the amount of work involved, I can estimate the cost and the delivery date.

8. How big is your team?

- My team is fairly small at the moment and consists of only ... me ;)
Sometimes if I’m stuck on a particular issue a developer friends here and there are
getting calls from me in the middle of the night or are forced to read long e-mails
during a day.

Skype: a_14bitMIDI_support
email: info@14bitMIDI.com