# Instrument definition file goes here
```############# POLY Example 1 #############
VERSION 1 # Currently, this should only be 1.
###### DEFINITIONS
# Supports all alphanumeric ASCII, and ' ', '_', '-', '+'
# Can also be omitted or NULL to not override the current track name, e.g. "TRACKNAME NULL"
TRACKNAME sh4d
# Can be POLY, DRUM, MPE, or NULL
TYPE POLY
# Can be A, B, C, D, USBD, USBH, CVGx (x between 1&4), CVx, Gx, or NULL
OUTPORT B
# Can be x (between 1-16), or NULL -- this is ignored if output port is not MIDI
OUTCHAN 11
# Can be NONE, ALLACTIVE, A, B, USBH, USBD, CVG, or NULL
INPORT NULL
# Can be x (between 1-16), ALL, or NULL -- ignored if INPORT is NONE, ALLACTIVE or CVG
INCHAN NULL
# PC
# Syntax: NUMBER NAME
# number must be either:
# - A number (for simple PC)
# - Three numbers, delimited by ':', which represent PC:MSB:LSB. You can put 'NULL' to not set the MSB/LSB.
# PC must be between 1...128
# MSB/LSB must be between 0...127
[PC]
1:88:64 Sh4d b1
1:88:65 Sh4d b2
1:88:66 Sh4d b3
1:88:67 Sh4d b4
1:88:68 Sh3d
1:88:69 Sync
1:88:70 Sh 101
1:88:71 Juno 106
1:88:72 XFM
1:88:73 Ring
1:88:74 Wavetable
1:88:75 Chord
1:88:76 Drawing
1:88:77 PCM
[/PC]
# CC
# Syntax: CC_NUMBER NAME or CC_NUMBER:DEFAULT=xx NAME
# DEFAULT_VALUE must be a valid number between 0 and 127
[CC]
1 MOD
7 VOLUME
11 PAN
74 CUTOFF
71 RESO
90 DRIVE
79 HPF CUTOFF
81 FILTER ENV
78 FILTER KEY
82 FILTER ATTACK
83 FILTER DECAY
28 FILTER SUSTAIN
29 FILTER RELEASE
73 AMP ATTACK
75 AMP DECAY
31 AMP SUSTAIN
72 AMP RELEASE
21 PITCH
77 TIMBRE
85 SLIDER 1
86 SLIDER 2
87 SLIDER 3
88 SLIDER 4
84 PORTAMENTO
16 LFO RATE
20 LFO FADE TIME
18 LFO PITCH
19 LFO FILTER
80 LFO AMP
64 PEDAL HOLD
66 SOSTENUTO
[/CC]
# This section will be readable from Hapax.
[COMMENT]
BE EXCELLENT TO EACH OTHER PARTY ON DUDES
[/COMMENT]
*Comments about your instrument definition goes here*
sh4d template for a trk
PC for 1st patch of each sh4d model and cc
midi output B ch 11
I'll do one for the drums trk asap
1 Like
thank you so much. could you also do one for the drumtrack? would totally appreciate it!
1 Like
I would very much appreciate a def file for the drum track as well! Thanks for this!
1 Like
Hi , I didn’t get round to doing the drm trk , as there were no cc and 26 drums per kit , to the 8 slots on the hapax
I think pc might be useful to change kit but that’s it off the top of my head .
I no longer have the sh4d , but I could still throw one together if you have any requests, of how you’d want it
Thank you kindly for the offer!
I just swapped out the SH-4d for an MC-707 which has 16 drums – found a def file for that here (MC 707 Instrument Definition - #4 by Luilu). The author, Luilu, split drums into 2 Hapax tracks. Works, not ideal. But I hear that Hapax may get more than 8 lanes per track soon(?).
Anywho, no need for a def file here but someone else would surely appreciate it I bet.
1 Like
For anyone wondering how to access the user patches add this to your PC section:
1:87:0 USER 1
1:87:1 USER 129
and for drums:
1:86:0 USER
1:86:64 RYTHM
Btw, the drum lane only supports CC 7 for part volume and 10 for pan, although this pans all of the drums sounds so seems of rather limited use.
Full drum def:
VERSION 1
TRACKNAME SH-4D R
TYPE POLY
OUTPORT NULL
OUTCHAN NULL
INPORT ALLACTIVE
INCHAN NULL
MAXRATE NULL
[PC]
1:86:0 USER
1:86:64 RYTHM
[/PC]
[CC]
7 LVL
10 PAN
[/CC]
[ASSIGN]
1 CC:7
[/ASSIGN]
[AUTOMATION]
[/AUTOMATION]
[COMMENT]
SH-4d rhythm part
[/COMMENT]