Steinberg Cubase 6 Manual

							391
The MIDI editors
•Clicking and dragging with the Line tool in Line mode 
allows you to create events in a straight line.
This is the best way to draw linear controller ramps.
•The Parabola mode works in the same way, but ar-
ranges the values on a parabola curve instead, giving 
more “natural” curves and fades.
Note that the result depends on the direction from which you draw the 
parabola.
•In Parabola mode, you can use modifier keys to deter-
mine the shape of the parabola curve.
If you press [Ctrl]/[Command], the parabola curve will be reversed. If you 
press [Alt]/[Option]-[Ctrl]/[Command] while Snap is activated, you can 
change the position of the whole curve (in both cases the snap value for 
the positioning will be a quarter of the quantize value). If you press [Shift], 
the exponent will be increased or decreased.
ÖIn Line and Parabola modes, the Length Quantize 
value determines the “density” of created controller curves 
(if Snap is activated). For very smooth curves, use a small 
Length Quantize value or turn off Snap. To avoid over-
dense controller curves (which may cause MIDI playback 
to “stutter”), use a medium-low density. 
ÖIf Length Quantize is set to “Quantize Link” and you 
enter data in Sine, Triangle or Square mode, the density of 
the events depends on the Zoom factor.
•The Sine, Triangle and Square modes create events 
with values aligned to continuous curves.
In these modes, the quantize value determines the period of the curve 
(the length of one curve “cycle”) and the Length Quantize value deter
-
mines the density of the events (the lower the Length Quantize note 
value, the smoother the curve).
•In Sine, Triangle and Square mode you can also use 
modifier keys to determine the shape of the curve.
If you press [Ctrl]/[Command] you can change the phase of the beginning 
of the curve, if you press [Alt]/[Option]-[Ctrl]/[Command] while snap is ac
-tivated you can change the position of the whole curve (in both cases the 
snap value for the positioning will be a quarter of the quantize value).
ÖYou can also set the curve period freely by holding 
down [Shift] when you insert events in Sine, Triangle or 
Square mode. Activate Snap, [Shift]-click and drag to set 
the length of one period. The period length will be a multi
-
ple of the quantize value.
•In Triangle and Square mode, you can press [Shift]- 
[Ctrl]/[Command] to change the maximum position of the 
triangle curve (to create sawtooth curves) or the pulse of 
the square curve.
Converting a controller curve to a ramp using the 
Line tool. 
						

							392
The MIDI editors
Moving events
You can move events in a controller lane, much like you 
can with notes:
1.Click with the Arrow tool to select the events that you 
want move or copy.
You can also click and drag to create a selection rectangle encompassing 
the desired events.
2.Click on a curve point inside the selection and drag 
the events.
The events inside the selection are moved to the new position. If Snap is 
activated, this determines to which positions you can move the events 
(see 
“Snap” on page 381). 
Using cut, copy and paste
You can use the standard Cut, Copy and Paste options on 
the Edit menu to copy and paste events in the controller 
display:
1.Select the events you want to cut or copy.
2.Select Cut or Copy from the Edit menu.
3.If you want to paste the events into another MIDI part, 
open that part in another Key Editor window.
4.Position the project cursor where you want to paste 
the events.
5.Select Paste from the Edit menu.
The events on the clipboard are added, starting at the project cursor po-
sition, maintaining their relative distances. If a pasted event ends up at 
the same position as an existing event of the same type, the old event is 
replaced. 
Deleting events in the controller display
You delete events by clicking on them with the Erase tool 
or by selecting them and pressing [Backspace]. Deleting a 
controller event makes the last event before this valid up 
until the next event. It does not “zero” any controller 
changes.
•You can delete notes by deleting their velocity bars in 
the controller display.
Please be aware that if there is more than one note at the same position, 
there may still only be one velocity bar visible – make sure that you delete 
only the desired notes!
Editing continuous controllers on the controller lane
When a continuous controller is selected for a controller 
lane, additional data is displayed on the controller lane. 
This is due to the fact that MIDI controller data can be re
-
corded (or entered) either for an automation track or for a 
MIDI part (see 
“MIDI controller automation” on page 241). 
The following applies:
•On the “Controller Selection and Functions” pop-up 
menu, an asterisk is displayed next to the controller name 
if automation data already exists for this controller.
This can be either controller data you entered in a MIDI editor (the data 
will then be displayed on the controller lane), or controller data recorded 
on an automation track in the Project window (in which case no events 
are displayed on the controller lane). 
!Remember that a non-note event does not have a 
length – it is “valid” until the next event (see 
“The 
controller display” on page 379).
!When the Auto Select Controllers button is activated 
in the Key Editor toolbar, selecting notes will also se
-
lect the corresponding controller events. Moving 
events (either using cut/copy/paste or drag & drop) 
in the note display will also move the corresponding 
controller events (see also 
“Selecting controllers 
within the note range” on page 384). 
						

							393
The MIDI editors
•If conflicting controller data exists in two different 
places, you can specify what will happen on playback by 
making settings for the Automation Merge Mode (see 
“Merging automation data” on page 241). The resulting 
curve is displayed in addition to the curve you entered on 
the controller lane.
•On the controller lane, you can also see the controller 
curve that is applied before the part starts. That way, you 
know which controller value (if any) is currently being used 
at the starting point of the part so that you can choose the 
start value accordingly. 
Note that this value also depends on the Automation Merge Mode.
Editing velocity values
When “Velocity” is selected, the lane shows the velocity of 
each note as a vertical bar.
Velocity values are edited with the Pencil or the Line tool. 
The Arrow tool automatically switches to the Pencil tool 
when you move the pointer into the controller display. If 
you want to use the Arrow tool to select events in the con
-
troller display, press [Alt]/[Option]. The different tools and 
Line tool modes offer several possibilities:
•You can use the Pencil tool to change the velocity of a 
single note: click on its velocity bar and drag the bar up or 
down.
While you drag, the current velocity value is shown in the display to the left.
•You can use the Pencil tool or the Line tool in Paint 
mode to change the velocity values of several notes by 
painting a “freehand curve”.
When editing velocity, these two methods have the same functionality.
•Use the Line tool in Line mode for creating linear veloc-
ity ramps.
Click where you want the ramp to start and drag the cursor to where you 
want the ramp to end. When you release the mouse button, the velocity 
values are aligned with the line between the two points.
•Parabola mode works in the same way, but aligns the 
velocity values to a Parabola curve instead.
Use this for smooth, “natural” velocity fades, etc.
Controller curve 
entered on the 
controller laneResulting controller curve (if controller automa-
tion was also recorded on a track). These values 
depend on the selected Automation Merge Mode.
The controller curve before the part starts. This curve depends on the 
existing controller data (if any) and on the selected Merge Mode. 
						

							394
The MIDI editors
•The remaining three Line tool modes (Sine, Triangle and 
Square) align the velocity values to continuous curve 
shapes.
If there is more than one note at the same position (e. g. a 
chord), their velocity bars will overlap on the controller 
lane. If none of the notes are selected, all notes at the 
same position will be set to the same velocity value when 
you draw. To edit the velocity of only one of the notes at 
the same position, first select the note in the note display. 
Now, editing will only affect the velocity of the selected 
note.
ÖIf the Speaker icon (Acoustic Feedback) is activated 
on the toolbar, the notes will be played back when you ad
-
just the velocity, allowing you to audition your changes.
ÖYou can also adjust the velocity of a single note by se-
lecting it and changing its velocity value on the info line.
Editing articulations (Cubase only)
It is also possible to add and edit musical expressions or 
articulations in the controller lane. This is described in de
-
tail in the chapter “Expression maps (Cubase only)” on 
page 419. 
Editing dynamics (Cubase only)
Provided that the Dynamics mapping is set up and acti-
vated for the track, you can insert 12 dynamics symbols in 
the lower part of the Articulations/Dynamics lane. Dynam
-
ics are described in detail in the section “Working with 
mapped dynamics” on page 685).
•To insert a dynamics symbol, click in the controller lane 
with the pencil tool.
A mezzo forte symbol is inserted.
•To select another dynamics symbol for an event, click 
on the triangle in the upper left corner of the event and se
-
lect a symbol from the pop-up menu.
If several events are selected, the same symbol will be applied to all the 
events.
•To step through the available dynamics symbols, use 
the mouse wheel or the key commands “One down” and 
“One up” (in the Key Commands dialog, Score Functions 
category).
If several events are selected, they will all change in increments, i. e. rela-
tive to the original values. 
ÖMoving and copying dynamics events works as with 
other events on the controller lane.
You can modify the settings for the Dynamics symbols in 
the Dynamics Mapping Setup dialog. You can open this 
dialog via the pop-up menu for a dynamics event or by se
-
lecting “Dynamics Mapping…” on the “Controller Selec-
tion and Functions” pop-up menu.
Adding and editing Poly Pressure events
Poly Pressure events are special, in that they “belong to” a 
specific note number (key). That is, each Poly Pressure 
event has two editable values: the note number and the 
amount of pressure. Therefore, when Poly Pressure is se
-
lected on the “Controller Selection and Functions” pop-
up menu, there are two value fields to the left of the con
-
troller display, one for the note number and one for the 
amount. 
						

							395
The MIDI editors
To add a new Poly Pressure event, proceed as follows:
1.Select Poly Pressure on the “Controller Selection and 
Functions” pop-up menu.
2.Set the note number by clicking on the keyboard dis-
play.
The selected note number is displayed in the upper value field to the left 
of the controller display. Note that this only works for the topmost lane. If 
you have selected “Poly Pressure” for several controller lanes, you have 
to type in the desired note number directly in the lower value field to the 
left of each lane. 
3.Use the Pencil tool to add a new event, just as when 
adding regular controller events.
To view and edit existing Poly Pressure events, proceed 
as follows:
1.Select Poly Pressure on the “Controller Selection and 
Functions” pop-up menu.
2.Click on the arrow button next to the note number field 
to the left of the controller lane.
A pop-up menu appears, listing all note numbers for which there already 
are Poly Pressure events.
3.Select a note number from the pop-up menu.
The Poly Pressure events for the selected note number are shown in the 
controller lane.
4.Use the Pencil tool to edit the events as usual.
Press [Alt]/[Option] to edit existing events without adding any new ones.
•Poly Pressure events can also be added and edited in 
the List Editor.
Working with selection ranges
The controller lane editor allows you to perform additional 
scaling operations for selection ranges on existing con
-
troller curves.
•To open the controller lane editor, use the Arrow tool to 
create a selection rectangle on the controller lane, encom
-
passing the desired controller events.
For Velocity lanes, press [Alt]/[Option] to get the Arrow tool.
ÖFor Velocity lanes, the editor also opens if you select 
multiple MIDI notes in the note display.
In the controller lane editor, controls (so called “smart 
spots”) appear on the borders of the editor. These smart 
spots allow you to activate a specific editing mode:
!The controller lane editor is not available for Articula-
tion or Dynamics lanes.
Editing 
modeTo activate this 
mode…Description
Move 
VerticallyClick in an empty 
area on the upper 
border of the editor.This mode allows you to move the 
entire curve up or down, which is 
useful to boost or attenuate an oth
-erwise perfect curve. 
Scale 
VerticallyClick the smart spot 
in the middle of the 
upper border of the 
editor.Use this mode to relatively scale the 
curve, i. e. to raise or lower the values 
in percent (not by absolute 
amounts).
Tilt the left/
right part of 
the curveClick the smart spot 
in the upper left/
right corner of the 
editor.These modes allow you to tilt the left 
or the right part of the curve, respec-tively. This is useful if the curve form 
is exactly the way you want it, but the 
start or end needs to be boosted or 
attenuated a bit.
Compress 
the left/right 
part of the 
curve[Alt]/[Option]-click 
the smart spot in 
the upper left/right 
corner of the editor.These modes allow you to compress 
the left or the right part of the curve.
Scale Around 
Absolute 
CenterClick the smart spot 
in the middle of the 
right border of the 
editor.This mode allows you to scale the 
curve around the absolute center, 
i.
 e. horizontally around the center of 
the editor.
Scale Around 
Relative 
Center [Alt]/[Option]-click 
the smart spot in 
the middle of the 
right border of the 
editor.This mode allows you to scale the 
curve relative to its center.
StretchClick and drag in 
the lower part of the 
editor (not avail
-able for Velocity 
lanes).
This allows you to stretch the se-lected controller events. 
						

							396
The MIDI editors
ÖIf you hold down [Shift] while clicking on any of the 
smart spots, you get the vertical scaling mode.
•To move the whole selection up/down or left/right, click 
on a controller event inside the editor and drag the curve.
By pressing [Ctrl]/[Command] when clicking and dragging, you can re-
strict the direction to horizontal or vertical movement, depending on the 
direction in which you start dragging.
ÖSnap is taken into account when moving controller 
curves horizontally.
The In-Place Editor
The In-Place Editor makes it possible to edit MIDI parts di-
rectly in the Project window, for quick and efficient editing 
in context with other tracks. 
To open the In-Place Editor for one or more selected 
tracks, you have the following possibilities:
•Select “Open In-Place Editor” on the MIDI menu.
•Use the Edit In-Place key command, by default [Ctrl]/
[Command]-[Shift]-[I].
•To open the In-Place Editor for a single MIDI track, click 
the corresponding Edit In-Place button in the track list (if 
necessary, expand the track list to display the button).
This expands the MIDI track to show something like a min-
iature Key Editor, allowing you to edit MIDI notes and con-
trollers.
•To zoom or scroll the In-Place Editor, point at the left 
part of the piano keyboard display so that the pointer 
changes to a hand. Now you can click and drag to the 
right or left to zoom in or out vertically, and drag up or 
down to scroll the editor.
•Clicking on the gray triangle in the upper right corner of 
the track list for the edited track brings up a local toolbar 
with some settings specific to the In-Place Editor.
For descriptions of these settings, see “The toolbar” on page 377.
Just like in the Key Editor, you can edit controller data and 
articulations at the bottom of the In-Place Editor.
•To add or remove controller lanes, right-click below the 
controller name field and select an option from the context 
menu.
When you select a MIDI note, the Project window info line 
shows information about that note, just like the info line in 
the Key Editor. You can perform the same editing here as 
on the Key Editor info line, see 
“Editing on the info line” on 
page 386.
•The Snap button and Snap Type pop-up menu on the 
Project window toolbar govern snapping in the In-Place 
Editor, but the snap grid is set using the Quantize pop-up 
menu.
•To close the In-Place Editor for one or several selected 
tracks, you can use the Edit In-Place key command, by de
-
fault [Ctrl]/[Command]-[Shift]-[I].
•To close the In-Place Editor for one track, you can click 
the Edit In-Place button in the track list or double-click be
-
low the controller display in the In-Place Editor.
ÖIf you have opened the In-Place Editor for multiple 
parts, you can drag and drop notes between the parts. 
						

							397
The MIDI editors
The Drum Editor – Overview 
The toolbar, status line, info line, and 
Inspector
These are much the same as the toolbar, status line, info 
line, and Inspector in the Key Editor (see 
“The Key Editor 
– Overview” on page 377), with the following differences:
•The toolbar has a Solo Instrument button that allows 
you to mute all sounds except the selected one, see 
“Mut-
ing notes and drum sounds” on page 399.
•The Drum Editor has a Drumstick tool (for entering and 
removing notes) and a Line tool with various line and curve 
modes (for drawing several notes in one go or editing 
controller events).
These tools replace the Pencil tool.
•The pitch in the Mouse Note Position display on the sta-
tus line shows is shown as a drum sound name rather than 
a note number.
•The Use Global Quantize button allows you to select 
which value is used when Snap is activated – the global 
quantize value on the toolbar or the individual quantize val
-
ues for the drum sounds.
•There is an Insert Length pop-up menu instead of the 
Length Quantize pop-up menu.
It is used in much the same way, as described on the following pages.
•There are no Scissors and Glue Tube tools in the Drum 
Editor.
•The status line does not contain a chord display.
The drum sound list
The drum sound list lists all drum sounds by name (ac-
cording to the selected drum map or name list – see be-
low), and lets you adjust and manipulate the drum sound 
setup in various ways.
The drum sound list for the GM Map
The following settings are available in the drum sound list:
Toolbar
Note 
display
Controller 
display Inspector
Drum 
map
Info line
Status line
Ruler
Drum 
sound list
ColumnDescription
PitchThe actual note number of the drum sound. This is what 
links notes on a MIDI track to drum sounds. For example, 
with the GM Map, all MIDI notes with the pitch C1 are 
mapped to the Bass Drum sound.
InstrumentThe name of the drum sound.
QuantizeThis value is used when entering and editing notes as de-scribed in the sections “Creating and editing notes” on page 398 and “Moving, duplicating, or repeating notes” on page 399. 
						

							398
The MIDI editors
Please note the following:
•The number of columns in the list depends on whether a 
drum map is selected for the track or not.
See “Working with drum maps” on page 400.
•You can reorder the columns by dragging the column 
headings, and resize them by dragging the dividers be
-
tween the column headings.
The note display
The note display of the Drum Editor displays notes as dia-
mond symbols. The vertical position of the notes corres-
ponds to the drum sound list to the left, while the horizontal 
position corresponds to the note’s position in time, just as 
in the Key Editor. Note, however, that the diamond symbols 
do not indicate the length of the notes. This makes sense, 
since drum sounds most often are “one-shot” samples that 
play to their end regardless of the note lengths.
Drum map and names pop-up menus
Below the drum sound list there are two pop-up menus, 
used for selecting a drum map for the edited track or (if no 
drum map is selected) a list of drum sound names. For an 
explanation of drum maps, see 
“Working with drum maps” 
on page 400.
Controller display
The controller display in the Drum Editor is the same as in 
the Key Editor, see 
“Using the controller display” on page 
388.
When you select a line in the drum sound list (to the left of 
the event display), only the velocity controller events be
-
longing to the note events on this line are displayed in the 
controller display.
•If you select more than one line in the drum sound list, 
the controller lane shows all velocity controller events for 
all notes on the selected lines.
This helps you when having to adjust the controller values between dif-
ferent drum sounds.
Drum Editor operations
The basic handling (zooming, playback, auditioning, etc.) 
is the same as in the Key Editor (see 
“Key Editor opera-
tions” on page 380). The following sections describe the 
procedures and features specific to the Drum Editor.
Creating and editing notes
The standard way of entering notes in the Drum Editor is 
to click with the Drumstick tool.
MuteAllows you to mute a drum sound, excluding it from play-back, see “Muting notes and drum sounds” on page 399.
I-NoteThis is the “input note” for the drum sound. When this 
MIDI note is sent into Cubase, (i. e. played by you), the 
note is mapped to the corresponding drum sound (and 
automatically transposed according to the Pitch setting 
for the sound).
O-NoteThis is the “output note”, i. e. the MIDI note number that is 
sent out every time the drum sound is played back. 
ChannelThe drum sound is played back on this MIDI channel.
OutputThe drum sound is played back on this MIDI output. If you 
set this to “Default”, the MIDI output selected for the 
track is used.
Column Description 
						

							399
The MIDI editors
The position of the created note depends on the following 
factors:
•If Snap is deactivated on the toolbar, the note appears 
exactly where you clicked.
In this mode, notes can be positioned freely.
•If Snap is activated and Use Global Quantize is deacti-
vated on the toolbar, the note snaps to positions accord-
ing to the quantize value set for the sound in the drum 
sound list.
You can set up different quantize values for different drum sounds. You 
may for example want hi-hat notes snap to sixteenth notes, but snare and 
bass drum snap to eighth notes.
•If Snap and Use Global Quantize are activated, the note 
snaps to positions according to the Quantize setting on 
the toolbar.
The length of the inserted note is determined by the Insert 
Length setting on the toolbar. However, if this is set to 
“Drum-Map Link”, the note gets the length of the quantize 
value for the drum sound.
•You can quickly audition the drum sounds by clicking in 
the leftmost column in the drum sound list. 
This plays the corresponding note.
•Clicking with the Drumstick tool on an existing note re-
moves it. 
This makes drum pattern editing very quick and intuitive.
Selecting notes
Selecting notes is done by any of the following methods:
•Use the Arrow tool.
The standard selection techniques apply.
•Use the Select submenu on the context menu (see “Se-
lecting notes” on page 383).
•Use the left and right arrow keys on the computer key-
board to step from one note to the next or previous note.
If you press [Shift] and use the arrow keys, the current selection is kept, 
allowing you to select several notes.
•You can also press [Shift] and double-click on a note to 
select all the following notes for the same drum sound.
Moving, duplicating, or repeating notes
To move or copy notes in the editor (to other positions or 
other drum sounds), you use the same methods as in the 
Key Editor: click and drag, use the arrow keys or Edit 
menu functions, etc. (see 
“Moving and transposing notes” 
on page 384). To help you identify the right notes, the 
drum sound names as defined in the drum map are dis-
played in the Pitch field in the Drum Editor info line and, 
when dragging notes in the event display, in the text fields 
displayed next to the mouse pointer.
There is one other thing to note:
If the moved/copied notes have different quantize values 
and Snap is activated but Use Global Quantize is deacti
-
vated, the largest value determines snapping. For exam-
ple, if you are moving two notes, with the quantize values 
1/16 and 1/4 respectively, the notes snap to quarter 
notes (1/4).
ÖYou can also adjust the position of notes by quantizing 
(see 
“Quantizing MIDI and audio” on page 108).
Muting notes and drum sounds
You can mute individual notes by clicking or enclosing 
them with the Mute tool or by using the Mute function on 
the Edit menu (see 
“Muting notes” on page 386).
Furthermore, if a drum map is selected (see “Selecting a 
drum map for a track” on page 401), the drum sound list 
has a Mute column. Click in the Mute column for a drum 
sound to mute that sound. Clicking the Solo Instrument 
button mutes all drum sounds other than the selected one.
Deleting notes
To delete notes, click on them with the Drumstick or Erase 
tool, or select them and press [Backspace].
!Please note that the mute state for drum sounds is 
part of the drum map. Therefore, any other tracks us-
ing the same map are also affected.  
						

							400
The MIDI editors
Working with drum maps
Background
A drum kit in a MIDI instrument is most often a set of dif-
ferent drum sounds with each sound placed on a separate 
key (i.
 e. the different sounds are assigned to different 
MIDI note numbers). One key plays a bass drum sound, 
another a snare, and so on.
Unfortunately, different MIDI instruments often use differ-
ent key assignments. This can be troublesome if you have 
made a drum pattern using one MIDI device, and then 
want to try it on another. When you switch devices, it is 
very likely that your snare drum becomes a ride cymbal or 
your hi-hat becomes a tom, etc. – just because the drum 
sounds are distributed differently in the two instruments.
To solve this problem and simplify several aspects of MIDI 
drum kits (like using drum sounds from different instru
-
ments in the same “drum kit”), Cubase features so-called 
drum maps. A drum map is a list of drum sounds, with a 
number of settings for each sound. When you play back a 
MIDI track for which you have selected a drum map, the 
MIDI notes are “filtered” through the drum map before be
-
ing sent to the MIDI instrument. Among other things, the 
map determines which MIDI note number is sent out for 
each drum sound, and so which sound is played in the re
-
ceiving MIDI device.
A solution to the problem above therefore is to set up 
drum maps for all your instruments. When you want to try 
your drum pattern on another instrument, you simply 
switch to the corresponding drum map and your snare 
drum sound remains a snare drum sound.
Drum map settings
A drum map consists of settings for 128 drum sounds 
(one for each MIDI note number). To get an overview of 
these settings, open the Drum Editor and use the Map 
pop-up menu below the drum sound list to select the “GM 
Map” drum map.
This drum map is set up according to the General MIDI 
standard. For information on how to load, create and se
-
lect other drum maps, see “Managing drum maps” on 
page 401.
ÖAll settings in a drum map (except the pitch) can be 
changed directly in the drum sound list (see 
“The drum 
sound list” on page 397) or in the Drum Map Setup dialog 
(see “The Drum Map Setup dialog” on page 402). These 
changes affect all tracks that use the drum map.
About pitch, I-note, and O-note
This can be a somewhat confusing area, but once you 
have grasped how it all works it is not very complicated. 
Going through the following “theory” helps you make the 
most out of the drum map concept – especially if you want 
to create your own drum maps.
As mentioned earlier, a drum map is a kind of “filter”, 
transforming notes according to the settings in the map. It 
does this transformation twice; once when it receives an 
incoming note (i.
 e. when you play a note on your MIDI 
controller) and once when a note is sent from the program 
to the MIDI sound device.
In the following example, we have modified the drum map 
so that the Bass Drum sound has different pitch, I-note, 
and O-note values.
I-notes (input notes)
When you play a note on your MIDI instrument, the pro-
gram looks for this note number among the I-notes in the 
drum map. If you play the note A1, the program finds that 
this is the I-note of the Bass Drum sound.
This is where the first transformation happens: the note 
gets a new note number according to the Pitch setting for 
the drum sound. In our case, the note is transformed to a 
C1 note, because that is the pitch of the Bass Drum 
sound. If you record the note, it is recorded as a C1 note.