| 16 |
to an annoying "missing Normative/Informative References" error message --> |
to an annoying "missing Normative/Informative References" error message --> |
| 17 |
<?rfc strict="no" ?> |
<?rfc strict="no" ?> |
| 18 |
|
|
| 19 |
<rfc category="std" ipr="full3978" docName="LSCP 1.2"> |
<rfc category="std" ipr="full3978" docName="LSCP 1.4"> |
| 20 |
<front> |
<front> |
| 21 |
<title>LinuxSampler Control Protocol</title> |
<title>LinuxSampler Control Protocol</title> |
| 22 |
<author initials='C.S.' surname="Schoenebeck" fullname='C. |
<author initials='C.S.' surname="Schoenebeck" fullname='C. |
| 34 |
<email>schoenebeck at software minus engineering dot org</email> |
<email>schoenebeck at software minus engineering dot org</email> |
| 35 |
</address> |
</address> |
| 36 |
</author> |
</author> |
| 37 |
<date month="December" year="2006"/> |
<date month="December" year="2008"/> |
| 38 |
<workgroup>LinuxSampler Developers</workgroup> |
<workgroup>LinuxSampler Developers</workgroup> |
| 39 |
<keyword>LSCP</keyword> |
<keyword>LSCP</keyword> |
| 40 |
<abstract> |
<abstract> |
| 61 |
(front-end) and server (LinuxSampler) respectively. Lines in |
(front-end) and server (LinuxSampler) respectively. Lines in |
| 62 |
examples must be interpreted as every line being CRLF |
examples must be interpreted as every line being CRLF |
| 63 |
terminated (carriage return character followed by line feed |
terminated (carriage return character followed by line feed |
| 64 |
character as defined in the ASCII standard), thus the following |
character as defined in the ASCII standard <xref target="RFC20"/>), |
| 65 |
example:</t> |
thus the following example:</t> |
| 66 |
|
|
| 67 |
<t> |
<t> |
| 68 |
<list> |
<list> |
| 2061 |
or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref> |
or <xref target="LIST MIDI_INPUT_DEVICES">"LIST MIDI_INPUT_DEVICES"</xref> |
| 2062 |
command, <port> by the MIDI port number, <key> by the name of |
command, <port> by the MIDI port number, <key> by the name of |
| 2063 |
the parameter to change and <value> by the new value for this |
the parameter to change and <value> by the new value for this |
| 2064 |
parameter.</t> |
parameter (encapsulated into apostrophes) or NONE (not encapsulated into apostrophes) |
| 2065 |
|
for specifying no value for parameters allowing a list of values.</t> |
| 2066 |
|
|
| 2067 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 2068 |
<t> |
<t> |
| 2089 |
<t>Example:</t> |
<t>Example:</t> |
| 2090 |
<t> |
<t> |
| 2091 |
<list> |
<list> |
| 2092 |
<t></t> |
<t>C: "SET MIDI_INPUT_PORT_PARAMETER 0 0 ALSA_SEQ_BINDINGS='20:0'"</t> |
| 2093 |
|
<t>S: "OK"</t> |
| 2094 |
|
</list> |
| 2095 |
|
</t> |
| 2096 |
|
<t> |
| 2097 |
|
<list> |
| 2098 |
|
<t>C: "SET MIDI_INPUT_PORT_PARAMETER 0 0 ALSA_SEQ_BINDINGS=NONE"</t> |
| 2099 |
|
<t>S: "OK"</t> |
| 2100 |
</list> |
</list> |
| 2101 |
</t> |
</t> |
| 2102 |
</section> |
</section> |
| 2121 |
number of the sampler channel the instrument should be assigned to. |
number of the sampler channel the instrument should be assigned to. |
| 2122 |
Each sampler channel can only have one instrument.</t> |
Each sampler channel can only have one instrument.</t> |
| 2123 |
|
|
| 2124 |
|
<t>Notice: since LSCP 1.2 the <filename> argument supports |
| 2125 |
|
escape characters for special characters (see chapter |
| 2126 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>" |
| 2127 |
|
for details) and accordingly backslash characters in the filename |
| 2128 |
|
MUST now be escaped as well!</t> |
| 2129 |
|
|
| 2130 |
<t>The difference between regular and NON_MODAL versions of the command |
<t>The difference between regular and NON_MODAL versions of the command |
| 2131 |
is that the regular command returns OK only after the instrument has been |
is that the regular command returns OK only after the instrument has been |
| 2132 |
fully loaded and the channel is ready to be used while NON_MODAL version |
fully loaded and the channel is ready to be used while NON_MODAL version |
| 2162 |
</t> |
</t> |
| 2163 |
</list> |
</list> |
| 2164 |
</t> |
</t> |
| 2165 |
<t>Example:</t> |
<t>Example (Unix):</t> |
| 2166 |
<t> |
<t> |
| 2167 |
<list> |
<list> |
| 2168 |
<t></t> |
<t>C: LOAD INSTRUMENT '/home/joe/gigs/cello.gig' 0 0</t> |
| 2169 |
|
<t>S: OK</t> |
| 2170 |
|
</list> |
| 2171 |
|
</t> |
| 2172 |
|
<t>Example (Windows):</t> |
| 2173 |
|
<t> |
| 2174 |
|
<list> |
| 2175 |
|
<t>C: LOAD INSTRUMENT 'D:/MySounds/cello.gig' 0 0</t> |
| 2176 |
|
<t>S: OK</t> |
| 2177 |
</list> |
</list> |
| 2178 |
</t> |
</t> |
| 2179 |
</section> |
</section> |
| 2451 |
<list> |
<list> |
| 2452 |
<t>DESCRIPTION - |
<t>DESCRIPTION - |
| 2453 |
<list> |
<list> |
| 2454 |
<t>arbitrary description text about the engine</t> |
<t>arbitrary description text about the engine |
| 2455 |
|
(note that the character string may contain |
| 2456 |
|
<xref target="character_set">escape sequences</xref>)</t> |
| 2457 |
</list> |
</list> |
| 2458 |
</t> |
</t> |
| 2459 |
<t>VERSION - |
<t>VERSION - |
| 2537 |
<list> |
<list> |
| 2538 |
<t>the file name of the loaded instrument, "NONE" if |
<t>the file name of the loaded instrument, "NONE" if |
| 2539 |
there's no instrument yet loaded for this sampler |
there's no instrument yet loaded for this sampler |
| 2540 |
channel</t> |
channel (note: since LSCP 1.2 this path may contain |
| 2541 |
|
<xref target="character_set">escape sequences</xref>)</t> |
| 2542 |
</list> |
</list> |
| 2543 |
</t> |
</t> |
| 2544 |
<t>INSTRUMENT_NR - |
<t>INSTRUMENT_NR - |
| 2548 |
</t> |
</t> |
| 2549 |
<t>INSTRUMENT_NAME - |
<t>INSTRUMENT_NAME - |
| 2550 |
<list> |
<list> |
| 2551 |
<t>the instrument name of the loaded instrument</t> |
<t>the instrument name of the loaded instrument |
| 2552 |
|
(note: since LSCP 1.2 this character string may contain |
| 2553 |
|
<xref target="character_set">escape sequences</xref>)</t> |
| 2554 |
</list> |
</list> |
| 2555 |
</t> |
</t> |
| 2556 |
<t>INSTRUMENT_STATUS - |
<t>INSTRUMENT_STATUS - |
| 2582 |
<t>VOLUME - |
<t>VOLUME - |
| 2583 |
<list> |
<list> |
| 2584 |
<t>optionally dotted number for the channel volume factor |
<t>optionally dotted number for the channel volume factor |
| 2585 |
(where a value < 1.0 means attenuation and a value > |
(where a value < 1.0 means attenuation and a value > |
| 2586 |
1.0 means amplification)</t> |
1.0 means amplification)</t> |
| 2587 |
</list> |
</list> |
| 2588 |
</t> |
</t> |
| 3254 |
</t> |
</t> |
| 3255 |
</section> |
</section> |
| 3256 |
|
|
| 3257 |
|
<section title="Adding an effect send to a sampler channel" anchor="CREATE FX_SEND"> |
| 3258 |
|
<t>The front-end can create an additional effect send on a specific sampler channel |
| 3259 |
|
by sending the following command:</t> |
| 3260 |
|
<t> |
| 3261 |
|
<list> |
| 3262 |
|
<t>CREATE FX_SEND <sampler-channel> <midi-ctrl> [<name>]</t> |
| 3263 |
|
</list> |
| 3264 |
|
</t> |
| 3265 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3266 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3267 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, that is the |
| 3268 |
|
sampler channel on which the effect send should be created on, <midi-ctrl> |
| 3269 |
|
is a number between 0..127 defining the MIDI controller which can alter the |
| 3270 |
|
effect send level and <name> is an optional argument defining a name |
| 3271 |
|
for the effect send entity. The name does not have to be unique, but MUST be |
| 3272 |
|
encapsulated into apostrophes and supports escape sequences as described in chapter |
| 3273 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>".</t> |
| 3274 |
|
|
| 3275 |
|
<t>By default, that is as initial routing, the effect send's audio channels |
| 3276 |
|
are automatically routed to the last audio channels of the sampler channel's |
| 3277 |
|
audio output device, that way you can i.e. first increase the amount of audio |
| 3278 |
|
channels on the audio output device for having dedicated effect send output |
| 3279 |
|
channels and when "CREATE FX_SEND" is called, those channels will automatically |
| 3280 |
|
be picked. You can alter the destination channels however with |
| 3281 |
|
<xref target="SET FX_SEND AUDIO_OUTPUT_CHANNEL">"SET FX_SEND AUDIO_OUTPUT_CHANNEL"</xref>. |
| 3282 |
|
</t> |
| 3283 |
|
|
| 3284 |
|
<t>Note: Create effect sends on a sampler channel only when needed, because having effect |
| 3285 |
|
sends on a sampler channel will decrease runtime performance, because for implementing channel |
| 3286 |
|
effect sends, separate (sampler channel local) audio buffers are needed to render and mix |
| 3287 |
|
the voices and route the audio signal afterwards to the master outputs and effect send |
| 3288 |
|
outputs (along with their respective effect send levels). A sampler channel without effect |
| 3289 |
|
sends however can mix its voices directly into the audio output devices's audio buffers |
| 3290 |
|
and is thus faster. |
| 3291 |
|
</t> |
| 3292 |
|
|
| 3293 |
|
<t>Possible Answers:</t> |
| 3294 |
|
<t> |
| 3295 |
|
<list> |
| 3296 |
|
<t>"OK[<fx-send-id>]" - |
| 3297 |
|
<list> |
| 3298 |
|
<t>in case a new effect send could be added to the |
| 3299 |
|
sampler channel, where <fx-send-id> reflects the |
| 3300 |
|
unique ID of the newly created effect send entity</t> |
| 3301 |
|
</list> |
| 3302 |
|
</t> |
| 3303 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3304 |
|
<list> |
| 3305 |
|
<t>when a new effect send could not be added, i.e. |
| 3306 |
|
due to invalid parameters</t> |
| 3307 |
|
</list> |
| 3308 |
|
</t> |
| 3309 |
|
</list> |
| 3310 |
|
</t> |
| 3311 |
|
|
| 3312 |
|
<t>Examples:</t> |
| 3313 |
|
<t> |
| 3314 |
|
<list> |
| 3315 |
|
<t>C: "CREATE FX_SEND 0 91 'Reverb Send'"</t> |
| 3316 |
|
<t>S: "OK[0]"</t> |
| 3317 |
|
</list> |
| 3318 |
|
</t> |
| 3319 |
|
<t> |
| 3320 |
|
<list> |
| 3321 |
|
<t>C: "CREATE FX_SEND 0 93"</t> |
| 3322 |
|
<t>S: "OK[1]"</t> |
| 3323 |
|
</list> |
| 3324 |
|
</t> |
| 3325 |
|
</section> |
| 3326 |
|
|
| 3327 |
|
<section title="Removing an effect send from a sampler channel" anchor="DESTROY FX_SEND"> |
| 3328 |
|
<t>The front-end can remove an existing effect send on a specific sampler channel |
| 3329 |
|
by sending the following command:</t> |
| 3330 |
|
<t> |
| 3331 |
|
<list> |
| 3332 |
|
<t>DESTROY FX_SEND <sampler-channel> <fx-send-id></t> |
| 3333 |
|
</list> |
| 3334 |
|
</t> |
| 3335 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3336 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3337 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, that is the |
| 3338 |
|
sampler channel from which the effect send should be removed from and |
| 3339 |
|
<fx-send-id> is the respective effect send number as returned by the |
| 3340 |
|
<xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3341 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command.</t> |
| 3342 |
|
|
| 3343 |
|
<t>Possible Answers:</t> |
| 3344 |
|
<t> |
| 3345 |
|
<list> |
| 3346 |
|
<t>"OK" - |
| 3347 |
|
<list> |
| 3348 |
|
<t>on success</t> |
| 3349 |
|
</list> |
| 3350 |
|
</t> |
| 3351 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3352 |
|
<list> |
| 3353 |
|
<t>in case it failed, providing an appropriate error code and |
| 3354 |
|
error message</t> |
| 3355 |
|
</list> |
| 3356 |
|
</t> |
| 3357 |
|
</list> |
| 3358 |
|
</t> |
| 3359 |
|
|
| 3360 |
|
<t>Example:</t> |
| 3361 |
|
<t> |
| 3362 |
|
<list> |
| 3363 |
|
<t>C: "DESTROY FX_SEND 0 0"</t> |
| 3364 |
|
<t>S: "OK"</t> |
| 3365 |
|
</list> |
| 3366 |
|
</t> |
| 3367 |
|
</section> |
| 3368 |
|
|
| 3369 |
|
<section title="Getting amount of effect sends on a sampler channel" anchor="GET FX_SENDS"> |
| 3370 |
|
<t>The front-end can ask for the amount of effect sends on a specific sampler channel |
| 3371 |
|
by sending the following command:</t> |
| 3372 |
|
<t> |
| 3373 |
|
<list> |
| 3374 |
|
<t>GET FX_SENDS <sampler-channel></t> |
| 3375 |
|
</list> |
| 3376 |
|
</t> |
| 3377 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3378 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3379 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 3380 |
|
|
| 3381 |
|
<t>Possible Answers:</t> |
| 3382 |
|
<t> |
| 3383 |
|
<list> |
| 3384 |
|
<t>The sampler will answer by returning the number of effect |
| 3385 |
|
sends on the given sampler channel.</t> |
| 3386 |
|
</list> |
| 3387 |
|
</t> |
| 3388 |
|
|
| 3389 |
|
<t>Example:</t> |
| 3390 |
|
<t> |
| 3391 |
|
<list> |
| 3392 |
|
<t>C: "GET FX_SENDS 0"</t> |
| 3393 |
|
<t>S: "2"</t> |
| 3394 |
|
</list> |
| 3395 |
|
</t> |
| 3396 |
|
</section> |
| 3397 |
|
|
| 3398 |
|
<section title="Listing all effect sends on a sampler channel" anchor="LIST FX_SENDS"> |
| 3399 |
|
<t>The front-end can ask for a list of effect sends on a specific sampler channel |
| 3400 |
|
by sending the following command:</t> |
| 3401 |
|
<t> |
| 3402 |
|
<list> |
| 3403 |
|
<t>LIST FX_SENDS <sampler-channel></t> |
| 3404 |
|
</list> |
| 3405 |
|
</t> |
| 3406 |
|
<t>Where <sampler-channel> is the respective sampler channel |
| 3407 |
|
number as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3408 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command.</t> |
| 3409 |
|
|
| 3410 |
|
<t>Possible Answers:</t> |
| 3411 |
|
<t> |
| 3412 |
|
<list> |
| 3413 |
|
<t>The sampler will answer by returning a comma separated list |
| 3414 |
|
with all effect sends' numerical IDs on the given sampler |
| 3415 |
|
channel.</t> |
| 3416 |
|
</list> |
| 3417 |
|
</t> |
| 3418 |
|
|
| 3419 |
|
<t>Examples:</t> |
| 3420 |
|
<t> |
| 3421 |
|
<list> |
| 3422 |
|
<t>C: "LIST FX_SENDS 0"</t> |
| 3423 |
|
<t>S: "0,1"</t> |
| 3424 |
|
</list> |
| 3425 |
|
</t> |
| 3426 |
|
<t> |
| 3427 |
|
<list> |
| 3428 |
|
<t>C: "LIST FX_SENDS 1"</t> |
| 3429 |
|
<t>S: ""</t> |
| 3430 |
|
</list> |
| 3431 |
|
</t> |
| 3432 |
|
</section> |
| 3433 |
|
|
| 3434 |
|
<section title="Getting effect send information" anchor="GET FX_SEND INFO"> |
| 3435 |
|
<t>The front-end can ask for the current settings of an effect send entity |
| 3436 |
|
by sending the following command:</t> |
| 3437 |
|
<t> |
| 3438 |
|
<list> |
| 3439 |
|
<t>GET FX_SEND INFO <sampler-channel> <fx-send-id></t> |
| 3440 |
|
</list> |
| 3441 |
|
</t> |
| 3442 |
|
<t>Where <sampler-channel> is the sampler channel number |
| 3443 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3444 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command and |
| 3445 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3446 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3447 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command. |
| 3448 |
|
</t> |
| 3449 |
|
|
| 3450 |
|
<t>Possible Answers:</t> |
| 3451 |
|
<t> |
| 3452 |
|
<list> |
| 3453 |
|
<t>The sampler will answer by sending a <CRLF> separated list. |
| 3454 |
|
Each answer line begins with the settings category name |
| 3455 |
|
followed by a colon and then a space character <SP> and finally |
| 3456 |
|
the info character string to that setting category. At the |
| 3457 |
|
moment the following categories are defined:</t> |
| 3458 |
|
|
| 3459 |
|
<t> |
| 3460 |
|
<list> |
| 3461 |
|
<t>NAME - |
| 3462 |
|
<list> |
| 3463 |
|
<t>name of the effect send entity |
| 3464 |
|
(note that this character string may contain |
| 3465 |
|
<xref target="character_set">escape sequences</xref>)</t> |
| 3466 |
|
</list> |
| 3467 |
|
</t> |
| 3468 |
|
<t>MIDI_CONTROLLER - |
| 3469 |
|
<list> |
| 3470 |
|
<t>a value between 0 and 127 reflecting the MIDI controller |
| 3471 |
|
which is able to modify the effect send's send level</t> |
| 3472 |
|
</list> |
| 3473 |
|
</t> |
| 3474 |
|
<t>LEVEL - |
| 3475 |
|
<list> |
| 3476 |
|
<t>optionally dotted number reflecting the effect send's |
| 3477 |
|
current send level (where a value < 1.0 means attenuation |
| 3478 |
|
and a value > 1.0 means amplification)</t> |
| 3479 |
|
</list> |
| 3480 |
|
</t> |
| 3481 |
|
<t>AUDIO_OUTPUT_ROUTING - |
| 3482 |
|
<list> |
| 3483 |
|
<t>comma separated list which reflects to which audio |
| 3484 |
|
channel of the selected audio output device each |
| 3485 |
|
effect send output channel is routed to, e.g. "0,3" would |
| 3486 |
|
mean the effect send's output channel 0 is routed to channel |
| 3487 |
|
0 of the audio output device and the effect send's output |
| 3488 |
|
channel 1 is routed to the channel 3 of the audio |
| 3489 |
|
output device (see |
| 3490 |
|
<xref target="SET FX_SEND AUDIO_OUTPUT_CHANNEL">"SET FX_SEND AUDIO_OUTPUT_CHANNEL"</xref> |
| 3491 |
|
for details)</t> |
| 3492 |
|
</list> |
| 3493 |
|
</t> |
| 3494 |
|
</list> |
| 3495 |
|
</t> |
| 3496 |
|
</list> |
| 3497 |
|
</t> |
| 3498 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 3499 |
|
|
| 3500 |
|
<t>Example:</t> |
| 3501 |
|
<t> |
| 3502 |
|
<list> |
| 3503 |
|
<t>C: "GET FX_SEND INFO 0 0"</t> |
| 3504 |
|
<t>S: "NAME: Reverb Send"</t> |
| 3505 |
|
<t> "MIDI_CONTROLLER: 91"</t> |
| 3506 |
|
<t> "LEVEL: 0.3"</t> |
| 3507 |
|
<t> "AUDIO_OUTPUT_ROUTING: 2,3"</t> |
| 3508 |
|
<t> "."</t> |
| 3509 |
|
</list> |
| 3510 |
|
</t> |
| 3511 |
|
</section> |
| 3512 |
|
|
| 3513 |
|
<section title="Changing effect send's name" anchor="SET FX_SEND NAME"> |
| 3514 |
|
<t>The front-end can alter the current name of an effect |
| 3515 |
|
send entity by sending the following command:</t> |
| 3516 |
|
<t> |
| 3517 |
|
<list> |
| 3518 |
|
<t>SET FX_SEND NAME <sampler-chan> <fx-send-id> <name></t> |
| 3519 |
|
</list> |
| 3520 |
|
</t> |
| 3521 |
|
<t>Where <sampler-chan> is the sampler channel number |
| 3522 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3523 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, |
| 3524 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3525 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3526 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and |
| 3527 |
|
<name> is the new name of the effect send entity, which |
| 3528 |
|
does not have to be unique (name MUST be encapsulated into apostrophes |
| 3529 |
|
and supports escape sequences as described in chapter |
| 3530 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>"). |
| 3531 |
|
</t> |
| 3532 |
|
|
| 3533 |
|
<t>Possible Answers:</t> |
| 3534 |
|
<t> |
| 3535 |
|
<list> |
| 3536 |
|
<t>"OK" - |
| 3537 |
|
<list> |
| 3538 |
|
<t>on success</t> |
| 3539 |
|
</list> |
| 3540 |
|
</t> |
| 3541 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3542 |
|
<list> |
| 3543 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3544 |
|
</list> |
| 3545 |
|
</t> |
| 3546 |
|
</list> |
| 3547 |
|
</t> |
| 3548 |
|
<t>Example:</t> |
| 3549 |
|
<t> |
| 3550 |
|
<list> |
| 3551 |
|
<t>C: "SET FX_SEND NAME 0 0 'Fx Send 1'"</t> |
| 3552 |
|
<t>S: "OK"</t> |
| 3553 |
|
</list> |
| 3554 |
|
</t> |
| 3555 |
|
</section> |
| 3556 |
|
|
| 3557 |
|
<section title="Altering effect send's audio routing" anchor="SET FX_SEND AUDIO_OUTPUT_CHANNEL"> |
| 3558 |
|
<t>The front-end can alter the destination of an effect send's audio channel on a specific |
| 3559 |
|
sampler channel by sending the following command:</t> |
| 3560 |
|
<t> |
| 3561 |
|
<list> |
| 3562 |
|
<t>SET FX_SEND AUDIO_OUTPUT_CHANNEL <sampler-chan> <fx-send-id> <audio-src> <audio-dst></t> |
| 3563 |
|
</list> |
| 3564 |
|
</t> |
| 3565 |
|
<t>Where <sampler-chan> is the sampler channel number |
| 3566 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3567 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, |
| 3568 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3569 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3570 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command, |
| 3571 |
|
<audio-src> is the numerical ID of the effect send's audio channel |
| 3572 |
|
which should be rerouted and <audio-dst> is the numerical ID of |
| 3573 |
|
the audio channel of the selected audio output device where <audio-src> |
| 3574 |
|
should be routed to.</t> |
| 3575 |
|
|
| 3576 |
|
<t>Note that effect sends can only route audio to the same audio output |
| 3577 |
|
device as assigned to the effect send's sampler channel. Also note that an |
| 3578 |
|
effect send entity does always have exactly as much audio channels as its |
| 3579 |
|
sampler channel. So if the sampler channel is stereo, the effect send does |
| 3580 |
|
have two audio channels as well. Also keep in mind that the amount of audio |
| 3581 |
|
channels on a sampler channel might be dependant not only to the deployed |
| 3582 |
|
sampler engine on the sampler channel, but also dependant to the instrument |
| 3583 |
|
currently loaded. However you can (effectively) turn an i.e. stereo effect |
| 3584 |
|
send into a mono one by simply altering its audio routing appropriately.</t> |
| 3585 |
|
|
| 3586 |
|
<t>Possible Answers:</t> |
| 3587 |
|
<t> |
| 3588 |
|
<list> |
| 3589 |
|
<t>"OK" - |
| 3590 |
|
<list> |
| 3591 |
|
<t>on success</t> |
| 3592 |
|
</list> |
| 3593 |
|
</t> |
| 3594 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 3595 |
|
<list> |
| 3596 |
|
<t>if audio output channel was set, but there are noteworthy |
| 3597 |
|
issue(s) related, providing an appropriate warning code and |
| 3598 |
|
warning message</t> |
| 3599 |
|
</list> |
| 3600 |
|
</t> |
| 3601 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3602 |
|
<list> |
| 3603 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3604 |
|
</list> |
| 3605 |
|
</t> |
| 3606 |
|
</list> |
| 3607 |
|
</t> |
| 3608 |
|
<t>Example:</t> |
| 3609 |
|
<t> |
| 3610 |
|
<list> |
| 3611 |
|
<t>C: "SET FX_SEND AUDIO_OUTPUT_CHANNEL 0 0 0 2"</t> |
| 3612 |
|
<t>S: "OK"</t> |
| 3613 |
|
</list> |
| 3614 |
|
</t> |
| 3615 |
|
</section> |
| 3616 |
|
|
| 3617 |
|
<section title="Altering effect send's MIDI controller" anchor="SET FX_SEND MIDI_CONTROLLER"> |
| 3618 |
|
<t>The front-end can alter the MIDI controller of an effect |
| 3619 |
|
send entity by sending the following command:</t> |
| 3620 |
|
<t> |
| 3621 |
|
<list> |
| 3622 |
|
<t>SET FX_SEND MIDI_CONTROLLER <sampler-chan> <fx-send-id> <midi-ctrl></t> |
| 3623 |
|
</list> |
| 3624 |
|
</t> |
| 3625 |
|
<t>Where <sampler-chan> is the sampler channel number |
| 3626 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3627 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, |
| 3628 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3629 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3630 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and |
| 3631 |
|
<midi-ctrl> reflects the MIDI controller which shall be |
| 3632 |
|
able to modify the effect send's send level.</t> |
| 3633 |
|
|
| 3634 |
|
<t>Possible Answers:</t> |
| 3635 |
|
<t> |
| 3636 |
|
<list> |
| 3637 |
|
<t>"OK" - |
| 3638 |
|
<list> |
| 3639 |
|
<t>on success</t> |
| 3640 |
|
</list> |
| 3641 |
|
</t> |
| 3642 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 3643 |
|
<list> |
| 3644 |
|
<t>if MIDI controller was set, but there are noteworthy |
| 3645 |
|
issue(s) related, providing an appropriate warning code and |
| 3646 |
|
warning message</t> |
| 3647 |
|
</list> |
| 3648 |
|
</t> |
| 3649 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3650 |
|
<list> |
| 3651 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3652 |
|
</list> |
| 3653 |
|
</t> |
| 3654 |
|
</list> |
| 3655 |
|
</t> |
| 3656 |
|
<t>Example:</t> |
| 3657 |
|
<t> |
| 3658 |
|
<list> |
| 3659 |
|
<t>C: "SET FX_SEND MIDI_CONTROLLER 0 0 91"</t> |
| 3660 |
|
<t>S: "OK"</t> |
| 3661 |
|
</list> |
| 3662 |
|
</t> |
| 3663 |
|
</section> |
| 3664 |
|
|
| 3665 |
|
<section title="Altering effect send's send level" anchor="SET FX_SEND LEVEL"> |
| 3666 |
|
<t>The front-end can alter the current send level of an effect |
| 3667 |
|
send entity by sending the following command:</t> |
| 3668 |
|
<t> |
| 3669 |
|
<list> |
| 3670 |
|
<t>SET FX_SEND LEVEL <sampler-chan> <fx-send-id> <volume></t> |
| 3671 |
|
</list> |
| 3672 |
|
</t> |
| 3673 |
|
<t>Where <sampler-chan> is the sampler channel number |
| 3674 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3675 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, |
| 3676 |
|
<fx-send-id> reflects the numerical ID of the effect send entity |
| 3677 |
|
as returned by the <xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref> |
| 3678 |
|
or <xref target="LIST FX_SENDS">"LIST FX_SENDS"</xref> command and |
| 3679 |
|
<volume> is an optionally dotted positive number (a value |
| 3680 |
|
smaller than 1.0 means attenuation, whereas a value greater than |
| 3681 |
|
1.0 means amplification) reflecting the new send level.</t> |
| 3682 |
|
|
| 3683 |
|
<t>Possible Answers:</t> |
| 3684 |
|
<t> |
| 3685 |
|
<list> |
| 3686 |
|
<t>"OK" - |
| 3687 |
|
<list> |
| 3688 |
|
<t>on success</t> |
| 3689 |
|
</list> |
| 3690 |
|
</t> |
| 3691 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 3692 |
|
<list> |
| 3693 |
|
<t>if new send level was set, but there are noteworthy |
| 3694 |
|
issue(s) related, providing an appropriate warning code and |
| 3695 |
|
warning message</t> |
| 3696 |
|
</list> |
| 3697 |
|
</t> |
| 3698 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3699 |
|
<list> |
| 3700 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3701 |
|
</list> |
| 3702 |
|
</t> |
| 3703 |
|
</list> |
| 3704 |
|
</t> |
| 3705 |
|
<t>Example:</t> |
| 3706 |
|
<t> |
| 3707 |
|
<list> |
| 3708 |
|
<t>C: "SET FX_SEND LEVEL 0 0 0.15"</t> |
| 3709 |
|
<t>S: "OK"</t> |
| 3710 |
|
</list> |
| 3711 |
|
</t> |
| 3712 |
|
</section> |
| 3713 |
|
|
| 3714 |
|
<section title="Sending MIDI messages to sampler channel" anchor="SEND CHANNEL MIDI_DATA"> |
| 3715 |
|
<t>The front-end can send MIDI events to specific sampler channel |
| 3716 |
|
by sending the following command:</t> |
| 3717 |
|
<t> |
| 3718 |
|
<list> |
| 3719 |
|
<t>SEND CHANNEL MIDI_DATA <midi-msg> <sampler-chan> <arg1> <arg2></t> |
| 3720 |
|
</list> |
| 3721 |
|
</t> |
| 3722 |
|
<t>Where <sampler-chan> is the sampler channel number |
| 3723 |
|
as returned by the <xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 3724 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> command, |
| 3725 |
|
<arg1> and <arg2> arguments depend on the <midi-msg> argument, which |
| 3726 |
|
specifies the MIDI message type. Currently, the following MIDI messages are supported:</t> |
| 3727 |
|
<t> |
| 3728 |
|
<list> |
| 3729 |
|
<t>"NOTE_ON" - |
| 3730 |
|
<list> |
| 3731 |
|
<t>For turning on MIDI notes, where <arg1> |
| 3732 |
|
specifies the key number and <arg2> the velocity |
| 3733 |
|
as described in the MIDI specification.</t> |
| 3734 |
|
</list> |
| 3735 |
|
</t> |
| 3736 |
|
<t>"NOTE_OFF" - |
| 3737 |
|
<list> |
| 3738 |
|
<t>For turning a currently playing MIDI note off, where <arg1> |
| 3739 |
|
specifies the key number and <arg2> the velocity |
| 3740 |
|
as described in the MIDI specification.</t> |
| 3741 |
|
</list> |
| 3742 |
|
</t> |
| 3743 |
|
</list> |
| 3744 |
|
</t> |
| 3745 |
|
<t>CAUTION: This command is provided for implementations of virtual MIDI keyboards |
| 3746 |
|
and no realtime guarantee whatsoever will be made!</t> |
| 3747 |
|
<t>Possible Answers:</t> |
| 3748 |
|
<t> |
| 3749 |
|
<list> |
| 3750 |
|
<t>"OK" - |
| 3751 |
|
<list> |
| 3752 |
|
<t>on success</t> |
| 3753 |
|
</list> |
| 3754 |
|
</t> |
| 3755 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 3756 |
|
<list> |
| 3757 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 3758 |
|
</list> |
| 3759 |
|
</t> |
| 3760 |
|
</list> |
| 3761 |
|
</t> |
| 3762 |
|
<t>Example:</t> |
| 3763 |
|
<t> |
| 3764 |
|
<list> |
| 3765 |
|
<t>C: "SEND CHANNEL MIDI_DATA NOTE_ON 0 56 112"</t> |
| 3766 |
|
<t>S: "OK"</t> |
| 3767 |
|
</list> |
| 3768 |
|
</t> |
| 3769 |
|
</section> |
| 3770 |
|
|
| 3771 |
<section title="Resetting a sampler channel" anchor="RESET CHANNEL"> |
<section title="Resetting a sampler channel" anchor="RESET CHANNEL"> |
| 3772 |
<t>The front-end can reset a particular sampler channel by sending the following command:</t> |
<t>The front-end can reset a particular sampler channel by sending the following command:</t> |
| 3773 |
<t> |
<t> |
| 3989 |
</t> |
</t> |
| 3990 |
</section> |
</section> |
| 3991 |
|
|
| 3992 |
|
<section title="Current number of active disk streams" anchor="GET TOTAL_STREAM_COUNT"> |
| 3993 |
|
<t>The front-end can ask for the current number of active disk streams on |
| 3994 |
|
the sampler by sending the following command:</t> |
| 3995 |
|
<t> |
| 3996 |
|
<list> |
| 3997 |
|
<t>GET TOTAL_STREAM_COUNT</t> |
| 3998 |
|
</list> |
| 3999 |
|
</t> |
| 4000 |
|
|
| 4001 |
|
<t>Possible Answers:</t> |
| 4002 |
|
<t> |
| 4003 |
|
<list> |
| 4004 |
|
<t>LinuxSampler will answer by returning the number of all active |
| 4005 |
|
disk streams on the sampler.</t> |
| 4006 |
|
</list> |
| 4007 |
|
</t> |
| 4008 |
|
</section> |
| 4009 |
|
|
| 4010 |
<section title="Reset sampler" anchor="RESET"> |
<section title="Reset sampler" anchor="RESET"> |
| 4011 |
<t>The front-end can reset the whole sampler by sending the following command:</t> |
<t>The front-end can reset the whole sampler by sending the following command:</t> |
| 4012 |
<t> |
<t> |
| 4054 |
<list> |
<list> |
| 4055 |
<t>DESCRIPTION - |
<t>DESCRIPTION - |
| 4056 |
<list> |
<list> |
| 4057 |
<t>arbitrary textual description about the sampler</t> |
<t>arbitrary textual description about the sampler |
| 4058 |
|
(note that the character string may contain |
| 4059 |
|
<xref target="character_set">escape sequences</xref>)</t> |
| 4060 |
</list> |
</list> |
| 4061 |
</t> |
</t> |
| 4062 |
<t>VERSION - |
<t>VERSION - |
| 4070 |
complies with (see <xref target="LSCP versioning" /> for details)</t> |
complies with (see <xref target="LSCP versioning" /> for details)</t> |
| 4071 |
</list> |
</list> |
| 4072 |
</t> |
</t> |
| 4073 |
|
<t>INSTRUMENTS_DB_SUPPORT - |
| 4074 |
|
<list> |
| 4075 |
|
<t>either yes or no, specifies whether the |
| 4076 |
|
sampler is build with instruments database support.</t> |
| 4077 |
|
</list> |
| 4078 |
|
</t> |
| 4079 |
</list> |
</list> |
| 4080 |
</t> |
</t> |
| 4081 |
</list> |
</list> |
| 4083 |
<t>The mentioned fields above don't have to be in particular order. |
<t>The mentioned fields above don't have to be in particular order. |
| 4084 |
Other fields might be added in future.</t> |
Other fields might be added in future.</t> |
| 4085 |
</section> |
</section> |
| 4086 |
|
|
| 4087 |
|
<section title="Getting global volume attenuation" anchor="GET VOLUME"> |
| 4088 |
|
<t>The client can ask for the current global sampler-wide volume |
| 4089 |
|
attenuation by sending the following command:</t> |
| 4090 |
|
<t> |
| 4091 |
|
<list> |
| 4092 |
|
<t>GET VOLUME</t> |
| 4093 |
|
</list> |
| 4094 |
|
</t> |
| 4095 |
|
<t>Possible Answers:</t> |
| 4096 |
|
<t> |
| 4097 |
|
<list> |
| 4098 |
|
<t>The sampler will always answer by returning the optional |
| 4099 |
|
dotted floating point coefficient, reflecting the current |
| 4100 |
|
global volume attenuation. |
| 4101 |
|
</t> |
| 4102 |
|
</list> |
| 4103 |
|
</t> |
| 4104 |
|
<t>Note: it is up to the respective sampler engine whether to obey |
| 4105 |
|
that global volume parameter or not, but in general all engines SHOULD |
| 4106 |
|
use this parameter.</t> |
| 4107 |
|
</section> |
| 4108 |
|
|
| 4109 |
|
<section title="Setting global volume attenuation" anchor="SET VOLUME"> |
| 4110 |
|
<t>The client can alter the current global sampler-wide volume |
| 4111 |
|
attenuation by sending the following command:</t> |
| 4112 |
|
<t> |
| 4113 |
|
<list> |
| 4114 |
|
<t>SET VOLUME <volume></t> |
| 4115 |
|
</list> |
| 4116 |
|
</t> |
| 4117 |
|
<t>Where <volume> should be replaced by the optional dotted |
| 4118 |
|
floating point value, reflecting the new global volume parameter. |
| 4119 |
|
This value might usually be in the range between 0.0 and 1.0, that |
| 4120 |
|
is for attenuating the overall volume.</t> |
| 4121 |
|
|
| 4122 |
|
<t>Possible Answers:</t> |
| 4123 |
|
<t> |
| 4124 |
|
<list> |
| 4125 |
|
<t>"OK" - |
| 4126 |
|
<list> |
| 4127 |
|
<t>on success</t> |
| 4128 |
|
</list> |
| 4129 |
|
</t> |
| 4130 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 4131 |
|
<list> |
| 4132 |
|
<t>if the global volume was set, but there are noteworthy |
| 4133 |
|
issue(s) related, providing an appropriate warning code and |
| 4134 |
|
warning message</t> |
| 4135 |
|
</list> |
| 4136 |
|
</t> |
| 4137 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4138 |
|
<list> |
| 4139 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 4140 |
|
</list> |
| 4141 |
|
</t> |
| 4142 |
|
</list> |
| 4143 |
|
</t> |
| 4144 |
|
</section> |
| 4145 |
|
|
| 4146 |
|
<section title="Getting global voice limit" anchor="GET VOICES"> |
| 4147 |
|
<t>The client can ask for the current global sampler-wide limit |
| 4148 |
|
for maximum voices by sending the following command:</t> |
| 4149 |
|
<t> |
| 4150 |
|
<list> |
| 4151 |
|
<t>GET VOICES</t> |
| 4152 |
|
</list> |
| 4153 |
|
</t> |
| 4154 |
|
<t>Possible Answers:</t> |
| 4155 |
|
<t> |
| 4156 |
|
<list> |
| 4157 |
|
<t>LinuxSampler will answer by returning the number for |
| 4158 |
|
the current limit of maximum voices.</t> |
| 4159 |
|
</list> |
| 4160 |
|
</t> |
| 4161 |
|
|
| 4162 |
|
<t>The voice limit setting defines how many voices should maximum |
| 4163 |
|
be processed by the sampler at the same time. If the user |
| 4164 |
|
triggers new notes which would exceed that voice limit, the |
| 4165 |
|
sampler engine will react by stealing old voices for those |
| 4166 |
|
newly triggered notes. Note that the amount of voices triggered |
| 4167 |
|
by a new note can be larger than one and is dependent to the |
| 4168 |
|
respective instrument and probably further criterias.</t> |
| 4169 |
|
</section> |
| 4170 |
|
|
| 4171 |
|
<section title="Setting global voice limit" anchor="SET VOICES"> |
| 4172 |
|
<t>The client can alter the current global sampler-wide limit |
| 4173 |
|
for maximum voices by sending the following command:</t> |
| 4174 |
|
<t> |
| 4175 |
|
<list> |
| 4176 |
|
<t>SET VOICES <max-voices></t> |
| 4177 |
|
</list> |
| 4178 |
|
</t> |
| 4179 |
|
<t>Where <max-voices> should be replaced by the integer |
| 4180 |
|
value, reflecting the new global amount limit of maximum voices. |
| 4181 |
|
This value has to be larger than 0.</t> |
| 4182 |
|
|
| 4183 |
|
<t>Possible Answers:</t> |
| 4184 |
|
<t> |
| 4185 |
|
<list> |
| 4186 |
|
<t>"OK" - |
| 4187 |
|
<list> |
| 4188 |
|
<t>on success</t> |
| 4189 |
|
</list> |
| 4190 |
|
</t> |
| 4191 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 4192 |
|
<list> |
| 4193 |
|
<t>if the voice limit was set, but there are noteworthy |
| 4194 |
|
issue(s) related, providing an appropriate warning code and |
| 4195 |
|
warning message</t> |
| 4196 |
|
</list> |
| 4197 |
|
</t> |
| 4198 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4199 |
|
<list> |
| 4200 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 4201 |
|
</list> |
| 4202 |
|
</t> |
| 4203 |
|
</list> |
| 4204 |
|
</t> |
| 4205 |
|
|
| 4206 |
|
<t>Note: the given value will be passed to all sampler engine instances. |
| 4207 |
|
The total amount of maximum voices on the running system might thus |
| 4208 |
|
be as big as the given value multiplied by the current amount of engine |
| 4209 |
|
instances.</t> |
| 4210 |
|
|
| 4211 |
|
<t>Caution: when adjusting the voice limit, you SHOULD also |
| 4212 |
|
adjust the disk stream limit respectively and vice versa.</t> |
| 4213 |
|
</section> |
| 4214 |
|
|
| 4215 |
|
<section title="Getting global disk stream limit" anchor="GET STREAMS"> |
| 4216 |
|
<t>The client can ask for the current global sampler-wide limit |
| 4217 |
|
for maximum disk streams by sending the following command:</t> |
| 4218 |
|
<t> |
| 4219 |
|
<list> |
| 4220 |
|
<t>GET STREAMS</t> |
| 4221 |
|
</list> |
| 4222 |
|
</t> |
| 4223 |
|
<t>Possible Answers:</t> |
| 4224 |
|
<t> |
| 4225 |
|
<list> |
| 4226 |
|
<t>LinuxSampler will answer by returning the number for |
| 4227 |
|
the current limit of maximum disk streams.</t> |
| 4228 |
|
</list> |
| 4229 |
|
</t> |
| 4230 |
|
|
| 4231 |
|
<t>The disk stream limit setting defines how many disk streams should |
| 4232 |
|
maximum be processed by a sampler engine at the same time. The |
| 4233 |
|
higher this value, the more memory (RAM) will be occupied, since |
| 4234 |
|
every disk streams allocates a certain buffer size for being able |
| 4235 |
|
to perform its streaming operations.</t> |
| 4236 |
|
</section> |
| 4237 |
|
|
| 4238 |
|
<section title="Setting global disk stream limit" anchor="SET STREAMS"> |
| 4239 |
|
<t>The client can alter the current global sampler-wide limit |
| 4240 |
|
for maximum disk streams by sending the following command:</t> |
| 4241 |
|
<t> |
| 4242 |
|
<list> |
| 4243 |
|
<t>SET STREAMS <max-streams></t> |
| 4244 |
|
</list> |
| 4245 |
|
</t> |
| 4246 |
|
<t>Where <max-streams> should be replaced by the integer |
| 4247 |
|
value, reflecting the new global amount limit of maximum disk streams. |
| 4248 |
|
This value has to be positive.</t> |
| 4249 |
|
|
| 4250 |
|
<t>Possible Answers:</t> |
| 4251 |
|
<t> |
| 4252 |
|
<list> |
| 4253 |
|
<t>"OK" - |
| 4254 |
|
<list> |
| 4255 |
|
<t>on success</t> |
| 4256 |
|
</list> |
| 4257 |
|
</t> |
| 4258 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 4259 |
|
<list> |
| 4260 |
|
<t>if the disk stream limit was set, but there are noteworthy |
| 4261 |
|
issue(s) related, providing an appropriate warning code and |
| 4262 |
|
warning message</t> |
| 4263 |
|
</list> |
| 4264 |
|
</t> |
| 4265 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 4266 |
|
<list> |
| 4267 |
|
<t>in case it failed, providing an appropriate error code and error message</t> |
| 4268 |
|
</list> |
| 4269 |
|
</t> |
| 4270 |
|
</list> |
| 4271 |
|
</t> |
| 4272 |
|
|
| 4273 |
|
<t>Note: the given value will be passed to all sampler engine instances. |
| 4274 |
|
The total amount of maximum disk streams on the running system might |
| 4275 |
|
thus be as big as the given value multiplied by the current amount of |
| 4276 |
|
engine instances.</t> |
| 4277 |
|
|
| 4278 |
|
<t>Caution: when adjusting the disk stream limit, you SHOULD also |
| 4279 |
|
adjust the voice limit respectively and vice versa.</t> |
| 4280 |
|
</section> |
| 4281 |
|
|
| 4282 |
</section> |
</section> |
| 4283 |
|
|
| 4284 |
|
|
| 4309 |
cause the sampler to switch to the respective instrument as |
cause the sampler to switch to the respective instrument as |
| 4310 |
reflected by the current MIDI instrument map.</t> |
reflected by the current MIDI instrument map.</t> |
| 4311 |
|
|
| 4312 |
<section title="Create a new MIDI instrument map" anchor="ADD MIDI_INSTRUMENT MAP"> |
<section title="Create a new MIDI instrument map" anchor="ADD MIDI_INSTRUMENT_MAP"> |
| 4313 |
<t>The front-end can add a new MIDI instrument map by sending |
<t>The front-end can add a new MIDI instrument map by sending |
| 4314 |
the following command:</t> |
the following command:</t> |
| 4315 |
<t> |
<t> |
| 4319 |
</t> |
</t> |
| 4320 |
<t>Where <name> is an optional argument allowing to |
<t>Where <name> is an optional argument allowing to |
| 4321 |
assign a custom name to the new map. MIDI instrument Map |
assign a custom name to the new map. MIDI instrument Map |
| 4322 |
names do not have to be unique.</t> |
names do not have to be unique, but MUST be encapsulated |
| 4323 |
|
into apostrophes and support escape sequences as described |
| 4324 |
|
in chapter "<xref target="character_set">Character Set and Escape Sequences</xref>". |
| 4325 |
|
</t> |
| 4326 |
|
|
| 4327 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 4328 |
<t> |
<t> |
| 4493 |
<t>NAME - |
<t>NAME - |
| 4494 |
<list> |
<list> |
| 4495 |
<t>custom name of the given map, |
<t>custom name of the given map, |
| 4496 |
which does not have to be unique</t> |
which does not have to be unique |
| 4497 |
|
(note that this character string may contain |
| 4498 |
|
<xref target="character_set">escape sequences</xref>)</t> |
| 4499 |
|
</list> |
| 4500 |
|
</t> |
| 4501 |
|
<t>DEFAULT - |
| 4502 |
|
<list> |
| 4503 |
|
<t>either true or false, |
| 4504 |
|
defines whether this map is the default map</t> |
| 4505 |
</list> |
</list> |
| 4506 |
</t> |
</t> |
| 4507 |
</list> |
</list> |
| 4515 |
<list> |
<list> |
| 4516 |
<t>C: "GET MIDI_INSTRUMENT_MAP INFO 0"</t> |
<t>C: "GET MIDI_INSTRUMENT_MAP INFO 0"</t> |
| 4517 |
<t>S: "NAME: Standard Map"</t> |
<t>S: "NAME: Standard Map"</t> |
| 4518 |
|
<t> "DEFAULT: true"</t> |
| 4519 |
<t> "."</t> |
<t> "."</t> |
| 4520 |
</list> |
</list> |
| 4521 |
</t> |
</t> |
| 4531 |
</t> |
</t> |
| 4532 |
<t>Where <map> is the numerical ID of the map and |
<t>Where <map> is the numerical ID of the map and |
| 4533 |
<name> the new custom name of the map, which does not |
<name> the new custom name of the map, which does not |
| 4534 |
have to be unique.</t> |
have to be unique (name MUST be encapsulated into apostrophes |
| 4535 |
|
and supports escape sequences as described in chapter |
| 4536 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>"). |
| 4537 |
|
</t> |
| 4538 |
|
|
| 4539 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 4540 |
<t> |
<t> |
| 4567 |
command:</t> |
command:</t> |
| 4568 |
<t> |
<t> |
| 4569 |
<list> |
<list> |
| 4570 |
<t>MAP MIDI_INSTRUMENT <map> |
<t>MAP MIDI_INSTRUMENT [NON_MODAL] <map> |
| 4571 |
<midi_bank> <midi_prog> <engine_name> |
<midi_bank> <midi_prog> <engine_name> |
| 4572 |
<filename> <instrument_index> <volume_value> |
<filename> <instrument_index> <volume_value> |
| 4573 |
[<instr_load_mode>] [<name>]</t> |
[<instr_load_mode>] [<name>]</t> |
| 4581 |
index, <engine_name> a sampler engine name as returned by |
index, <engine_name> a sampler engine name as returned by |
| 4582 |
the <xref target="LIST AVAILABLE_ENGINES">"LIST AVAILABLE_ENGINES"</xref> |
the <xref target="LIST AVAILABLE_ENGINES">"LIST AVAILABLE_ENGINES"</xref> |
| 4583 |
command (not encapsulated into apostrophes), <filename> the name |
command (not encapsulated into apostrophes), <filename> the name |
| 4584 |
of the instrument's file to be deployed (encapsulated into apostrophes), |
of the instrument's file to be deployed (encapsulated into apostrophes, |
| 4585 |
|
supporting escape sequences as described in chapter |
| 4586 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>"), |
| 4587 |
<instrument_index> the index (integer value) of the instrument |
<instrument_index> the index (integer value) of the instrument |
| 4588 |
within the given file, <volume_value> reflects the master |
within the given file, <volume_value> reflects the master |
| 4589 |
volume of the instrument as optionally dotted number (where a |
volume of the instrument as optionally dotted number (where a |
| 4590 |
value < 1.0 means attenuation and a value > 1.0 means |
value < 1.0 means attenuation and a value > 1.0 means |
| 4591 |
amplification). This parameter easily allows to adjust the |
amplification). This parameter easily allows to adjust the |
| 4592 |
volume of all intruments within a custom instrument map |
volume of all intruments within a custom instrument map |
| 4593 |
without having to adjust their instrument files. The |
without having to adjust their instrument files. The |
| 4622 |
<t>"PERSISTENT" - |
<t>"PERSISTENT" - |
| 4623 |
<list> |
<list> |
| 4624 |
<t>The instrument will immediately be loaded |
<t>The instrument will immediately be loaded |
| 4625 |
into memory in the background when this mapping |
into memory when this mapping |
| 4626 |
command is sent and the instrument is kept all |
command is sent and the instrument is kept all |
| 4627 |
the time. Instruments with this mode are |
the time. Instruments with this mode are |
| 4628 |
only freed when the sampler is reset or all |
only freed when the sampler is reset or all |
| 4665 |
load modes of entries, the frontend should retrieve the actual |
load modes of entries, the frontend should retrieve the actual |
| 4666 |
mode by i.e. sending |
mode by i.e. sending |
| 4667 |
<xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref> |
<xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref> |
| 4668 |
command(s). Finally the OPTIONAL <name> argument allows to |
command(s). Finally the OPTIONAL <name> argument allows to set a custom name |
| 4669 |
set a custom name (encapsulated into apostrophes) for the mapping |
(encapsulated into apostrophes, supporting escape sequences as described in chapter |
| 4670 |
entry, useful for frontends for displaying an appropriate name for |
"<xref target="character_set">Character Set and Escape Sequences</xref>") for the |
| 4671 |
|
mapping entry, useful for frontends for displaying an appropriate name for |
| 4672 |
mapped instruments (using |
mapped instruments (using |
| 4673 |
<xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref>). |
<xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref>). |
| 4674 |
</t> |
</t> |
| 4675 |
<t> |
<t> |
| 4676 |
The "MAP MIDI_INSTRUMENT" command |
By default, "MAP MIDI_INSTRUMENT" commands block until the mapping is |
| 4677 |
will immediately return, thus it will not block when an |
completely established in the sampler. The OPTIONAL "NON_MODAL" argument |
| 4678 |
instrument is to be loaded due to a "PERSISTENT" type |
however causes the respective "MAP MIDI_INSTRUMENT" command to return |
| 4679 |
entry as instruments are loaded in the background. As a |
immediately, that is to let the sampler establish the mapping in the |
| 4680 |
consequence this command may not necessarily return an error |
background. So this argument might be especially useful for mappings with |
| 4681 |
i.e. when the given instrument file does not exist or may |
a "PERSISTENT" type, because these have to load the respective instruments |
| 4682 |
turn out to be corrupt. |
immediately and might thus block for a very long time. It is recommended |
| 4683 |
|
however to use the OPTIONAL "NON_MODAL" argument only if really necessary, |
| 4684 |
|
because it has the following drawbacks: as "NON_MODAL" instructions return |
| 4685 |
|
immediately, they may not necessarily return an error i.e. when the given |
| 4686 |
|
instrument file turns out to be corrupt, beside that subsequent commands |
| 4687 |
|
in a LSCP instruction sequence might fail, because mandatory mappings are |
| 4688 |
|
not yet completed. |
| 4689 |
</t> |
</t> |
| 4690 |
|
|
| 4691 |
<t>Possible Answers:</t> |
<t>Possible Answers:</t> |
| 4728 |
</t> |
</t> |
| 4729 |
<t> |
<t> |
| 4730 |
<list> |
<list> |
| 4731 |
<t>C: "MAP MIDI_INSTRUMENT 1 8 120 gig '/home/joe/foodrums.gig' 0 1.0 PERSISTENT 'Foo Drumkit'"</t> |
<t>C: "MAP MIDI_INSTRUMENT NON_MODAL 1 8 120 gig '/home/joe/foodrums.gig' 0 1.0 PERSISTENT 'Foo Drumkit'"</t> |
| 4732 |
<t>S: "OK"</t> |
<t>S: "OK"</t> |
| 4733 |
</list> |
</list> |
| 4734 |
</t> |
</t> |
| 4892 |
name for this mapped instrument. It can be set and |
name for this mapped instrument. It can be set and |
| 4893 |
changed with the |
changed with the |
| 4894 |
<xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref> |
<xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref> |
| 4895 |
command and does not have to be unique.</t> |
command and does not have to be unique. |
| 4896 |
|
(note that this character string may contain |
| 4897 |
|
<xref target="character_set">escape sequences</xref>)</t> |
| 4898 |
</list> |
</list> |
| 4899 |
</t> |
</t> |
| 4900 |
<t>"ENGINE_NAME" - |
<t>"ENGINE_NAME" - |
| 4905 |
</t> |
</t> |
| 4906 |
<t>"INSTRUMENT_FILE" - |
<t>"INSTRUMENT_FILE" - |
| 4907 |
<list> |
<list> |
| 4908 |
<t>File name of the instrument.</t> |
<t>File name of the instrument |
| 4909 |
|
(note that this path may contain |
| 4910 |
|
<xref target="character_set">escape sequences</xref>).</t> |
| 4911 |
</list> |
</list> |
| 4912 |
</t> |
</t> |
| 4913 |
<t>"INSTRUMENT_NR" - |
<t>"INSTRUMENT_NR" - |
| 4919 |
<list> |
<list> |
| 4920 |
<t>Name of the loaded instrument as reflected by its file. |
<t>Name of the loaded instrument as reflected by its file. |
| 4921 |
In contrast to the "NAME" field, the "INSTRUMENT_NAME" field |
In contrast to the "NAME" field, the "INSTRUMENT_NAME" field |
| 4922 |
cannot be changed.</t> |
cannot be changed (note that this character string may contain |
| 4923 |
|
<xref target="character_set">escape sequences</xref>).</t> |
| 4924 |
</list> |
</list> |
| 4925 |
</t> |
</t> |
| 4926 |
<t>"LOAD_MODE" - |
<t>"LOAD_MODE" - |
| 4932 |
<t>"VOLUME" - |
<t>"VOLUME" - |
| 4933 |
<list> |
<list> |
| 4934 |
<t>master volume of the instrument as optionally |
<t>master volume of the instrument as optionally |
| 4935 |
dotted number (where a value < 1.0 means attenuation |
dotted number (where a value < 1.0 means attenuation |
| 4936 |
and a value > 1.0 means amplification)</t> |
and a value > 1.0 means amplification)</t> |
| 4937 |
</list> |
</list> |
| 4938 |
</t> |
</t> |
| 5004 |
</section> |
</section> |
| 5005 |
</section> |
</section> |
| 5006 |
|
|
|
</section> |
|
| 5007 |
|
|
| 5008 |
|
<section title="Managing Instruments Database" anchor="Managing Instruments Database"> |
| 5009 |
|
<t>The following commands describe how to use and manage |
| 5010 |
|
the instruments database.</t> |
| 5011 |
|
<t>Notice:</t> |
| 5012 |
|
<t> |
| 5013 |
|
<list> |
| 5014 |
|
<t>All command arguments representing a path or |
| 5015 |
|
instrument/directory name support escape sequences as described in chapter |
| 5016 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>". |
| 5017 |
|
</t> |
| 5018 |
|
<t>All occurrences of a forward slash in instrument and directory |
| 5019 |
|
names are escaped with its hex (\x2f) or octal (\057) escape sequence. |
| 5020 |
|
</t> |
| 5021 |
|
</list> |
| 5022 |
|
</t> |
| 5023 |
|
|
| 5024 |
|
<section title="Creating a new instrument directory" anchor="ADD DB_INSTRUMENT_DIRECTORY"> |
| 5025 |
|
<t>The front-end can add a new instrument directory to the |
| 5026 |
|
instruments database by sending the following command:</t> |
| 5027 |
|
<t> |
| 5028 |
|
<list> |
| 5029 |
|
<t>ADD DB_INSTRUMENT_DIRECTORY <dir></t> |
| 5030 |
|
</list> |
| 5031 |
|
</t> |
| 5032 |
|
<t>Where <dir> is the absolute path name of the directory |
| 5033 |
|
to be created (encapsulated into apostrophes).</t> |
| 5034 |
|
|
| 5035 |
|
<t>Possible Answers:</t> |
| 5036 |
|
<t> |
| 5037 |
|
<list> |
| 5038 |
|
<t>"OK" - |
| 5039 |
|
<list> |
| 5040 |
|
<t>on success</t> |
| 5041 |
|
</list> |
| 5042 |
|
</t> |
| 5043 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5044 |
|
<list> |
| 5045 |
|
<t>when the directory could not be created, which |
| 5046 |
|
can happen if the directory already exists or the |
| 5047 |
|
name contains not allowed symbols</t> |
| 5048 |
|
</list> |
| 5049 |
|
</t> |
| 5050 |
|
</list> |
| 5051 |
|
</t> |
| 5052 |
|
|
| 5053 |
|
<t>Examples:</t> |
| 5054 |
|
<t> |
| 5055 |
|
<list> |
| 5056 |
|
<t>C: "ADD DB_INSTRUMENT_DIRECTORY '/Piano Collection'"</t> |
| 5057 |
|
<t>S: "OK"</t> |
| 5058 |
|
</list> |
| 5059 |
|
</t> |
| 5060 |
|
</section> |
| 5061 |
|
|
| 5062 |
|
<section title="Deleting an instrument directory" anchor="REMOVE DB_INSTRUMENT_DIRECTORY"> |
| 5063 |
|
<t>The front-end can delete a particular instrument directory |
| 5064 |
|
from the instruments database by sending the following command:</t> |
| 5065 |
|
<t> |
| 5066 |
|
<list> |
| 5067 |
|
<t>REMOVE DB_INSTRUMENT_DIRECTORY [FORCE] <dir></t> |
| 5068 |
|
</list> |
| 5069 |
|
</t> |
| 5070 |
|
<t>Where <dir> is the absolute path name of the directory |
| 5071 |
|
to delete. The optional FORCE argument can be used to |
| 5072 |
|
force the deletion of a non-empty directory and all its content.</t> |
| 5073 |
|
|
| 5074 |
|
<t>Possible Answers:</t> |
| 5075 |
|
<t> |
| 5076 |
|
<list> |
| 5077 |
|
<t>"OK" - |
| 5078 |
|
<list> |
| 5079 |
|
<t>if the directory is deleted successfully</t> |
| 5080 |
|
</list> |
| 5081 |
|
</t> |
| 5082 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5083 |
|
<list> |
| 5084 |
|
<t>if the given directory does not exist, or |
| 5085 |
|
if trying to delete a non-empty directory, |
| 5086 |
|
without using the FORCE argument.</t> |
| 5087 |
|
</list> |
| 5088 |
|
</t> |
| 5089 |
|
</list> |
| 5090 |
|
</t> |
| 5091 |
|
|
| 5092 |
|
<t>Examples:</t> |
| 5093 |
|
<t> |
| 5094 |
|
<list> |
| 5095 |
|
<t>C: "REMOVE DB_INSTRUMENT_DIRECTORY FORCE '/Piano Collection'"</t> |
| 5096 |
|
<t>S: "OK"</t> |
| 5097 |
|
</list> |
| 5098 |
|
</t> |
| 5099 |
|
</section> |
| 5100 |
|
|
| 5101 |
|
<section title="Getting amount of instrument directories" anchor="GET DB_INSTRUMENT_DIRECTORIES"> |
| 5102 |
|
<t>The front-end can retrieve the current amount of |
| 5103 |
|
directories in a specific directory by sending the following command:</t> |
| 5104 |
|
<t> |
| 5105 |
|
<list> |
| 5106 |
|
<t>GET DB_INSTRUMENT_DIRECTORIES [RECURSIVE] <dir></t> |
| 5107 |
|
</list> |
| 5108 |
|
</t> |
| 5109 |
|
<t>Where <dir> should be replaced by the absolute path |
| 5110 |
|
name of the directory. If RECURSIVE is specified, the number of |
| 5111 |
|
all directories, including those located in subdirectories of the |
| 5112 |
|
specified directory, will be returned.</t> |
| 5113 |
|
|
| 5114 |
|
<t>Possible Answers:</t> |
| 5115 |
|
<t> |
| 5116 |
|
<list> |
| 5117 |
|
<t>The current number of instrument directories |
| 5118 |
|
in the specified directory.</t> |
| 5119 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5120 |
|
<list> |
| 5121 |
|
<t>if the given directory does not exist.</t> |
| 5122 |
|
</list> |
| 5123 |
|
</t> |
| 5124 |
|
</list> |
| 5125 |
|
</t> |
| 5126 |
|
|
| 5127 |
|
<t>Example:</t> |
| 5128 |
|
<t> |
| 5129 |
|
<list> |
| 5130 |
|
<t>C: "GET DB_INSTRUMENT_DIRECTORIES '/'"</t> |
| 5131 |
|
<t>S: "2"</t> |
| 5132 |
|
</list> |
| 5133 |
|
</t> |
| 5134 |
|
</section> |
| 5135 |
|
|
| 5136 |
|
<section title="Listing all directories in specific directory" anchor="LIST DB_INSTRUMENT_DIRECTORIES"> |
| 5137 |
|
<t>The front-end can retrieve the current list of directories |
| 5138 |
|
in specific directory by sending the following command:</t> |
| 5139 |
|
<t> |
| 5140 |
|
<list> |
| 5141 |
|
<t>LIST DB_INSTRUMENT_DIRECTORIES [RECURSIVE] <dir></t> |
| 5142 |
|
</list> |
| 5143 |
|
</t> |
| 5144 |
|
<t>Where <dir> should be replaced by the absolute path |
| 5145 |
|
name of the directory. If RECURSIVE is specified, the absolute path names |
| 5146 |
|
of all directories, including those located in subdirectories of the |
| 5147 |
|
specified directory, will be returned.</t> |
| 5148 |
|
|
| 5149 |
|
<t>Possible Answers:</t> |
| 5150 |
|
<t> |
| 5151 |
|
<list> |
| 5152 |
|
<t>A comma separated list of all instrument directories |
| 5153 |
|
(encapsulated into apostrophes) in the specified directory.</t> |
| 5154 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5155 |
|
<list> |
| 5156 |
|
<t>if the given directory does not exist.</t> |
| 5157 |
|
</list> |
| 5158 |
|
</t> |
| 5159 |
|
</list> |
| 5160 |
|
</t> |
| 5161 |
|
<t>Example:</t> |
| 5162 |
|
<t> |
| 5163 |
|
<list> |
| 5164 |
|
<t>C: "LIST DB_INSTRUMENT_DIRECTORIES '/'"</t> |
| 5165 |
|
<t>S: "'Piano Collection','Percussion Collection'"</t> |
| 5166 |
|
</list> |
| 5167 |
|
</t> |
| 5168 |
|
<t> |
| 5169 |
|
<list> |
| 5170 |
|
<t>C: "LIST DB_INSTRUMENT_DIRECTORIES RECURSIVE '/'"</t> |
| 5171 |
|
<t>S: "'/Piano Collection','/Piano Collection/Acoustic','/Piano Collection/Acoustic/New','/Percussion Collection'"</t> |
| 5172 |
|
</list> |
| 5173 |
|
</t> |
| 5174 |
|
</section> |
| 5175 |
|
|
| 5176 |
|
<section title="Getting instrument directory information" anchor="GET DB_INSTRUMENT_DIRECTORY INFO"> |
| 5177 |
|
<t>The front-end can ask for the current settings of an |
| 5178 |
|
instrument directory by sending the following command:</t> |
| 5179 |
|
<t> |
| 5180 |
|
<list> |
| 5181 |
|
<t>GET DB_INSTRUMENT_DIRECTORY INFO <dir></t> |
| 5182 |
|
</list> |
| 5183 |
|
</t> |
| 5184 |
|
<t>Where <dir> should be replaced by the absolute path |
| 5185 |
|
name of the directory the front-end is interested in.</t> |
| 5186 |
|
|
| 5187 |
|
<t>Possible Answers:</t> |
| 5188 |
|
<t> |
| 5189 |
|
<list> |
| 5190 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 5191 |
|
Each answer line begins with the settings category name |
| 5192 |
|
followed by a colon and then a space character <SP> and finally |
| 5193 |
|
the info character string to that setting category. At the |
| 5194 |
|
moment the following categories are defined:</t> |
| 5195 |
|
|
| 5196 |
|
<t> |
| 5197 |
|
<list> |
| 5198 |
|
<t>DESCRIPTION - |
| 5199 |
|
<list> |
| 5200 |
|
<t>A brief description of the directory content. |
| 5201 |
|
Note that the character string may contain |
| 5202 |
|
<xref target="character_set">escape sequences</xref>.</t> |
| 5203 |
|
</list> |
| 5204 |
|
</t> |
| 5205 |
|
<t>CREATED - |
| 5206 |
|
<list> |
| 5207 |
|
<t>The creation date and time of the directory, |
| 5208 |
|
represented in "YYYY-MM-DD HH:MM:SS" format</t> |
| 5209 |
|
</list> |
| 5210 |
|
</t> |
| 5211 |
|
<t>MODIFIED - |
| 5212 |
|
<list> |
| 5213 |
|
<t>The date and time of the last modification of the |
| 5214 |
|
directory, represented in "YYYY-MM-DD HH:MM:SS" format</t> |
| 5215 |
|
</list> |
| 5216 |
|
</t> |
| 5217 |
|
</list> |
| 5218 |
|
</t> |
| 5219 |
|
</list> |
| 5220 |
|
</t> |
| 5221 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 5222 |
|
|
| 5223 |
|
<t>Example:</t> |
| 5224 |
|
<t> |
| 5225 |
|
<list> |
| 5226 |
|
<t>C: "GET DB_INSTRUMENT_DIRECTORY INFO '/Piano Collection'"</t> |
| 5227 |
|
<t>S: "DESCRIPTION: Piano collection of instruments in GigaSampler format."</t> |
| 5228 |
|
<t> "CREATED: 2007-02-05 10:23:12"</t> |
| 5229 |
|
<t> "MODIFIED: 2007-04-07 12:50:21"</t> |
| 5230 |
|
<t> "."</t> |
| 5231 |
|
</list> |
| 5232 |
|
</t> |
| 5233 |
|
</section> |
| 5234 |
|
|
| 5235 |
|
<section title="Renaming an instrument directory" anchor="SET DB_INSTRUMENT_DIRECTORY NAME"> |
| 5236 |
|
<t>The front-end can alter the name of a specific |
| 5237 |
|
instrument directory by sending the following command:</t> |
| 5238 |
|
<t> |
| 5239 |
|
<list> |
| 5240 |
|
<t>SET DB_INSTRUMENT_DIRECTORY NAME <dir> <name></t> |
| 5241 |
|
</list> |
| 5242 |
|
</t> |
| 5243 |
|
<t>Where <dir> is the absolute path name of the directory and |
| 5244 |
|
<name> is the new name for that directory.</t> |
| 5245 |
|
|
| 5246 |
|
<t>Possible Answers:</t> |
| 5247 |
|
<t> |
| 5248 |
|
<list> |
| 5249 |
|
<t>"OK" - |
| 5250 |
|
<list> |
| 5251 |
|
<t>on success</t> |
| 5252 |
|
</list> |
| 5253 |
|
</t> |
| 5254 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5255 |
|
<list> |
| 5256 |
|
<t>in case the given directory does not exists, |
| 5257 |
|
or if a directory with name equal to the new |
| 5258 |
|
name already exists.</t> |
| 5259 |
|
</list> |
| 5260 |
|
</t> |
| 5261 |
|
</list> |
| 5262 |
|
</t> |
| 5263 |
|
|
| 5264 |
|
<t>Example:</t> |
| 5265 |
|
<t> |
| 5266 |
|
<list> |
| 5267 |
|
<t>C: "SET DB_INSTRUMENT_DIRECTORY NAME '/Piano Collection/Acustic' 'Acoustic'"</t> |
| 5268 |
|
<t>S: "OK"</t> |
| 5269 |
|
</list> |
| 5270 |
|
</t> |
| 5271 |
|
</section> |
| 5272 |
|
|
| 5273 |
|
<section title="Moving an instrument directory" anchor="MOVE DB_INSTRUMENT_DIRECTORY"> |
| 5274 |
|
<t>The front-end can move a specific |
| 5275 |
|
instrument directory by sending the following command:</t> |
| 5276 |
|
<t> |
| 5277 |
|
<list> |
| 5278 |
|
<t>MOVE DB_INSTRUMENT_DIRECTORY <dir> <dst></t> |
| 5279 |
|
</list> |
| 5280 |
|
</t> |
| 5281 |
|
<t>Where <dir> is the absolute path name of the directory |
| 5282 |
|
to move and <dst> is the location where the directory will |
| 5283 |
|
be moved to.</t> |
| 5284 |
|
|
| 5285 |
|
<t>Possible Answers:</t> |
| 5286 |
|
<t> |
| 5287 |
|
<list> |
| 5288 |
|
<t>"OK" - |
| 5289 |
|
<list> |
| 5290 |
|
<t>on success</t> |
| 5291 |
|
</list> |
| 5292 |
|
</t> |
| 5293 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5294 |
|
<list> |
| 5295 |
|
<t>in case a given directory does not exists, |
| 5296 |
|
or if a directory with name equal to the name |
| 5297 |
|
of the specified directory already exists in |
| 5298 |
|
the destination directory. Error is also thrown |
| 5299 |
|
when trying to move a directory to a subdirectory |
| 5300 |
|
of itself.</t> |
| 5301 |
|
</list> |
| 5302 |
|
</t> |
| 5303 |
|
</list> |
| 5304 |
|
</t> |
| 5305 |
|
|
| 5306 |
|
<t>Example:</t> |
| 5307 |
|
<t> |
| 5308 |
|
<list> |
| 5309 |
|
<t>C: "MOVE DB_INSTRUMENT_DIRECTORY '/Acoustic' '/Piano Collection/Acoustic'"</t> |
| 5310 |
|
<t>S: "OK"</t> |
| 5311 |
|
</list> |
| 5312 |
|
</t> |
| 5313 |
|
</section> |
| 5314 |
|
|
| 5315 |
|
<section title="Copying instrument directories" anchor="COPY DB_INSTRUMENT_DIRECTORY"> |
| 5316 |
|
<t>The front-end can copy a specific |
| 5317 |
|
instrument directory by sending the following command:</t> |
| 5318 |
|
<t> |
| 5319 |
|
<list> |
| 5320 |
|
<t>COPY DB_INSTRUMENT_DIRECTORY <dir> <dst></t> |
| 5321 |
|
</list> |
| 5322 |
|
</t> |
| 5323 |
|
<t>Where <dir> is the absolute path name of the directory |
| 5324 |
|
to copy and <dst> is the location where the directory will |
| 5325 |
|
be copied to.</t> |
| 5326 |
|
|
| 5327 |
|
<t>Possible Answers:</t> |
| 5328 |
|
<t> |
| 5329 |
|
<list> |
| 5330 |
|
<t>"OK" - |
| 5331 |
|
<list> |
| 5332 |
|
<t>on success</t> |
| 5333 |
|
</list> |
| 5334 |
|
</t> |
| 5335 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5336 |
|
<list> |
| 5337 |
|
<t>in case a given directory does not exists, |
| 5338 |
|
or if a directory with name equal to the name |
| 5339 |
|
of the specified directory already exists in |
| 5340 |
|
the destination directory. Error is also thrown |
| 5341 |
|
when trying to copy a directory to a subdirectory |
| 5342 |
|
of itself.</t> |
| 5343 |
|
</list> |
| 5344 |
|
</t> |
| 5345 |
|
</list> |
| 5346 |
|
</t> |
| 5347 |
|
|
| 5348 |
|
<t>Example:</t> |
| 5349 |
|
<t> |
| 5350 |
|
<list> |
| 5351 |
|
<t>C: "COPY DB_INSTRUMENT_DIRECTORY '/Piano Collection/Acoustic' '/Acoustic/Pianos'"</t> |
| 5352 |
|
<t>S: "OK"</t> |
| 5353 |
|
</list> |
| 5354 |
|
</t> |
| 5355 |
|
</section> |
| 5356 |
|
|
| 5357 |
|
<section title="Changing the description of directory" anchor="SET DB_INSTRUMENT_DIRECTORY DESCRIPTION"> |
| 5358 |
|
<t>The front-end can alter the description of a specific |
| 5359 |
|
instrument directory by sending the following command:</t> |
| 5360 |
|
<t> |
| 5361 |
|
<list> |
| 5362 |
|
<t>SET DB_INSTRUMENT_DIRECTORY DESCRIPTION <dir> <desc></t> |
| 5363 |
|
</list> |
| 5364 |
|
</t> |
| 5365 |
|
<t>Where <dir> is the absolute path name of the directory and |
| 5366 |
|
<desc> is the new description for the directory |
| 5367 |
|
(encapsulated into apostrophes, supporting escape sequences as described in chapter |
| 5368 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>").</t> |
| 5369 |
|
|
| 5370 |
|
<t>Possible Answers:</t> |
| 5371 |
|
<t> |
| 5372 |
|
<list> |
| 5373 |
|
<t>"OK" - |
| 5374 |
|
<list> |
| 5375 |
|
<t>on success</t> |
| 5376 |
|
</list> |
| 5377 |
|
</t> |
| 5378 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5379 |
|
<list> |
| 5380 |
|
<t>in case the given directory does not exists.</t> |
| 5381 |
|
</list> |
| 5382 |
|
</t> |
| 5383 |
|
</list> |
| 5384 |
|
</t> |
| 5385 |
|
|
| 5386 |
|
<t>Example:</t> |
| 5387 |
|
<t> |
| 5388 |
|
<list> |
| 5389 |
|
<t>C: "SET DB_INSTRUMENT_DIRECTORY DESCRIPTION '/Piano Collection' 'A collection of piano instruments in various format.'"</t> |
| 5390 |
|
<t>S: "OK"</t> |
| 5391 |
|
</list> |
| 5392 |
|
</t> |
| 5393 |
|
</section> |
| 5394 |
|
|
| 5395 |
|
<section title="Finding directories" anchor="FIND DB_INSTRUMENT_DIRECTORIES"> |
| 5396 |
|
<t>The front-end can search for directories |
| 5397 |
|
in specific directory by sending the following command:</t> |
| 5398 |
|
<t> |
| 5399 |
|
<list> |
| 5400 |
|
<t>FIND DB_INSTRUMENT_DIRECTORIES [NON_RECURSIVE] <dir> <criteria-list></t> |
| 5401 |
|
</list> |
| 5402 |
|
</t> |
| 5403 |
|
<t>Where <dir> should be replaced by the absolute path |
| 5404 |
|
name of the directory to search in. If NON_RECURSIVE is specified, the |
| 5405 |
|
directories located in subdirectories of the specified directory will not |
| 5406 |
|
be searched. <criteria-list> is a list of search criterias |
| 5407 |
|
in form of "key1=val1 key2=val2 ...". The following criterias are |
| 5408 |
|
allowed:</t> |
| 5409 |
|
<t> |
| 5410 |
|
<t>NAME='<search-string>' |
| 5411 |
|
<list> |
| 5412 |
|
<t>Restricts the search to directories, which names |
| 5413 |
|
satisfy the supplied search string (encapsulated into apostrophes, |
| 5414 |
|
supporting escape sequences as described in chapter |
| 5415 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>").</t> |
| 5416 |
|
</list> |
| 5417 |
|
</t> |
| 5418 |
|
|
| 5419 |
|
<t>CREATED='[<date-after>]..[<date-before>]' |
| 5420 |
|
<list> |
| 5421 |
|
<t>Restricts the search to directories, which creation |
| 5422 |
|
date satisfies the specified period, where <date-after> |
| 5423 |
|
and <date-before> are in "YYYY-MM-DD HH:MM:SS" format. |
| 5424 |
|
If <date-after> is omitted the search is restricted to |
| 5425 |
|
directories created before <date-before>. If |
| 5426 |
|
<date-before> is omitted, the search is restricted |
| 5427 |
|
to directories created after <date-after>.</t> |
| 5428 |
|
</list> |
| 5429 |
|
</t> |
| 5430 |
|
|
| 5431 |
|
<t>MODIFIED='[<date-after>]..[<date-before>]' |
| 5432 |
|
<list> |
| 5433 |
|
<t>Restricts the search to directories, which |
| 5434 |
|
date of last modification satisfies the specified period, where |
| 5435 |
|
<date-after> and <date-before> are in "YYYY-MM-DD HH:MM:SS" |
| 5436 |
|
format. If <date-after> is omitted the search is restricted to |
| 5437 |
|
directories, which are last modified before <date-before>. If |
| 5438 |
|
<date-before> is omitted, the search is restricted to directories, |
| 5439 |
|
which are last modified after <date-after>.</t> |
| 5440 |
|
</list> |
| 5441 |
|
</t> |
| 5442 |
|
|
| 5443 |
|
<t>DESCRIPTION='<search-string>' |
| 5444 |
|
<list> |
| 5445 |
|
<t>Restricts the search to directories with description |
| 5446 |
|
that satisfies the supplied search string |
| 5447 |
|
(encapsulated into apostrophes, supporting escape |
| 5448 |
|
sequences as described in chapter |
| 5449 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>").</t> |
| 5450 |
|
</list> |
| 5451 |
|
</t> |
| 5452 |
|
</t> |
| 5453 |
|
|
| 5454 |
|
<t>Where <search-string> is either a regular expression, or a |
| 5455 |
|
word list separated with spaces for OR search and with '+' for AND search.</t> |
| 5456 |
|
|
| 5457 |
|
<t>Possible Answers:</t> |
| 5458 |
|
<t> |
| 5459 |
|
<list> |
| 5460 |
|
<t>A comma separated list with the absolute path names (encapsulated into |
| 5461 |
|
apostrophes) of all directories in the specified directory that satisfy |
| 5462 |
|
the supplied search criterias.</t> |
| 5463 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5464 |
|
<list> |
| 5465 |
|
<t>if the given directory does not exist.</t> |
| 5466 |
|
</list> |
| 5467 |
|
</t> |
| 5468 |
|
</list> |
| 5469 |
|
</t> |
| 5470 |
|
<t>Example:</t> |
| 5471 |
|
<t> |
| 5472 |
|
<list> |
| 5473 |
|
<t>C: "FIND DB_INSTRUMENT_DIRECTORIES '/' NAME='Piano'"</t> |
| 5474 |
|
<t>S: "'/Piano Collection'"</t> |
| 5475 |
|
</list> |
| 5476 |
|
</t> |
| 5477 |
|
<t> |
| 5478 |
|
<list> |
| 5479 |
|
<t>C: "FIND DB_INSTRUMENT_DIRECTORIES '/' CREATED='..2007-04-01 09:30:13'"</t> |
| 5480 |
|
<t>S: "'/Piano Collection','/Percussions'"</t> |
| 5481 |
|
</list> |
| 5482 |
|
</t> |
| 5483 |
|
</section> |
| 5484 |
|
|
| 5485 |
|
<section title="Adding instruments to the instruments database" anchor="ADD DB_INSTRUMENTS"> |
| 5486 |
|
<t>The front-end can add one or more instruments |
| 5487 |
|
to the instruments database by sending the following command:</t> |
| 5488 |
|
<t> |
| 5489 |
|
<list> |
| 5490 |
|
<t>ADD DB_INSTRUMENTS [NON_MODAL] [<mode>[ FILE_AS_DIR]] <db_dir> <file_path> [<instr_index>]</t> |
| 5491 |
|
</list> |
| 5492 |
|
</t> |
| 5493 |
|
<t>Where <db_dir> is the absolute path name of a directory |
| 5494 |
|
(encapsulated into apostrophes) in the instruments database in which |
| 5495 |
|
only the new instruments (that are not already in the database) will |
| 5496 |
|
be added, <file_path> is the absolute path name of a file or |
| 5497 |
|
directory in the file system (encapsulated into apostrophes). In case |
| 5498 |
|
an instrument file is supplied, only the instruments in the specified |
| 5499 |
|
file will be added to the instruments database. If the optional |
| 5500 |
|
<instr_index> (the index of the instrument within the given file) |
| 5501 |
|
is supplied too, then only the specified instrument will be added. |
| 5502 |
|
In case a directory is supplied, the instruments in that directory |
| 5503 |
|
will be added. The OPTIONAL <mode> argument is only applied |
| 5504 |
|
when a directory is provided as <file_path> and specifies how the |
| 5505 |
|
scanning will be done and has exactly the following possibilities:</t> |
| 5506 |
|
<t> |
| 5507 |
|
<list> |
| 5508 |
|
<t>"RECURSIVE" - |
| 5509 |
|
<list> |
| 5510 |
|
<t>All instruments will be processed, including those |
| 5511 |
|
in the subdirectories, and the respective subdirectory |
| 5512 |
|
tree structure will be recreated in the instruments |
| 5513 |
|
database</t> |
| 5514 |
|
</list> |
| 5515 |
|
</t> |
| 5516 |
|
<t>"NON_RECURSIVE" - |
| 5517 |
|
<list> |
| 5518 |
|
<t>Only the instruments in the specified directory |
| 5519 |
|
will be added, the instruments in the subdirectories |
| 5520 |
|
will not be processed.</t> |
| 5521 |
|
</list> |
| 5522 |
|
</t> |
| 5523 |
|
<t>"FLAT" - |
| 5524 |
|
<list> |
| 5525 |
|
<t>All instruments will be processed, including those |
| 5526 |
|
in the subdirectories, but the respective subdirectory |
| 5527 |
|
structure will not be recreated in the instruments |
| 5528 |
|
database. All instruments will be added directly in |
| 5529 |
|
the specified database directory.</t> |
| 5530 |
|
</list> |
| 5531 |
|
</t> |
| 5532 |
|
</list> |
| 5533 |
|
</t> |
| 5534 |
|
|
| 5535 |
|
<t> If FILE_AS_DIR argument is supplied, all instruments in an instrument |
| 5536 |
|
file will be added to a separate directory in the instruments database, which |
| 5537 |
|
name will be the name of the instrument file with the file extension stripped off. |
| 5538 |
|
</t> |
| 5539 |
|
<t>The difference between regular and NON_MODAL versions of the command |
| 5540 |
|
is that the regular command returns when the scanning is finished |
| 5541 |
|
while NON_MODAL version returns immediately and a background process is launched. |
| 5542 |
|
The <xref target="GET DB_INSTRUMENTS_JOB INFO">GET DB_INSTRUMENTS_JOB INFO</xref> |
| 5543 |
|
command can be used to monitor the scanning progress.</t> |
| 5544 |
|
|
| 5545 |
|
<t>Possible Answers:</t> |
| 5546 |
|
<t> |
| 5547 |
|
<list> |
| 5548 |
|
<t>"OK" - |
| 5549 |
|
<list> |
| 5550 |
|
<t>on success when NON_MODAL is not supplied</t> |
| 5551 |
|
</list> |
| 5552 |
|
</t> |
| 5553 |
|
<t>"OK[<job-id>]" - |
| 5554 |
|
<list> |
| 5555 |
|
<t>on success when NON_MODAL is supplied, where <job-id> |
| 5556 |
|
is a numerical ID used to obtain status information about the job progress. |
| 5557 |
|
See <xref target="GET DB_INSTRUMENTS_JOB INFO">GET DB_INSTRUMENTS_JOB INFO</xref> |
| 5558 |
|
</t> |
| 5559 |
|
</list> |
| 5560 |
|
</t> |
| 5561 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5562 |
|
<list> |
| 5563 |
|
<t>if an invalid path is specified.</t> |
| 5564 |
|
</list> |
| 5565 |
|
</t> |
| 5566 |
|
</list> |
| 5567 |
|
</t> |
| 5568 |
|
|
| 5569 |
|
<t>Examples:</t> |
| 5570 |
|
<t> |
| 5571 |
|
<list> |
| 5572 |
|
<t>C: "ADD DB_INSTRUMENTS '/Piano Collection' '/home/me/gigs/PMI Bosendorfer 290.gig' 0"</t> |
| 5573 |
|
<t>S: "OK"</t> |
| 5574 |
|
</list> |
| 5575 |
|
</t> |
| 5576 |
|
</section> |
| 5577 |
|
|
| 5578 |
|
<section title="Removing an instrument" anchor="REMOVE DB_INSTRUMENT"> |
| 5579 |
|
<t>The front-end can remove a particular instrument |
| 5580 |
|
from the instruments database by sending the following command:</t> |
| 5581 |
|
<t> |
| 5582 |
|
<list> |
| 5583 |
|
<t>REMOVE DB_INSTRUMENT <instr_path></t> |
| 5584 |
|
</list> |
| 5585 |
|
</t> |
| 5586 |
|
<t>Where <instr_path> is the absolute path name |
| 5587 |
|
(in the instruments database) of the instrument to remove.</t> |
| 5588 |
|
|
| 5589 |
|
<t>Possible Answers:</t> |
| 5590 |
|
<t> |
| 5591 |
|
<list> |
| 5592 |
|
<t>"OK" - |
| 5593 |
|
<list> |
| 5594 |
|
<t>if the instrument is removed successfully</t> |
| 5595 |
|
</list> |
| 5596 |
|
</t> |
| 5597 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5598 |
|
<list> |
| 5599 |
|
<t>if the given path does not exist or |
| 5600 |
|
is a directory.</t> |
| 5601 |
|
</list> |
| 5602 |
|
</t> |
| 5603 |
|
</list> |
| 5604 |
|
</t> |
| 5605 |
|
|
| 5606 |
|
<t>Examples:</t> |
| 5607 |
|
<t> |
| 5608 |
|
<list> |
| 5609 |
|
<t>C: "REMOVE DB_INSTRUMENT '/Piano Collection/Bosendorfer 290'"</t> |
| 5610 |
|
<t>S: "OK"</t> |
| 5611 |
|
</list> |
| 5612 |
|
</t> |
| 5613 |
|
</section> |
| 5614 |
|
|
| 5615 |
|
<section title="Getting amount of instruments" anchor="GET DB_INSTRUMENTS"> |
| 5616 |
|
<t>The front-end can retrieve the current amount of |
| 5617 |
|
instruments in a specific directory by sending the following command:</t> |
| 5618 |
|
<t> |
| 5619 |
|
<list> |
| 5620 |
|
<t>GET DB_INSTRUMENTS [RECURSIVE] <dir></t> |
| 5621 |
|
</list> |
| 5622 |
|
</t> |
| 5623 |
|
<t>Where <dir> should be replaced by the absolute path name |
| 5624 |
|
of the directory. If RECURSIVE is specified, the number of all |
| 5625 |
|
instruments, including those located in subdirectories of the |
| 5626 |
|
specified directory, will be returned.</t> |
| 5627 |
|
|
| 5628 |
|
<t>Possible Answers:</t> |
| 5629 |
|
<t> |
| 5630 |
|
<list> |
| 5631 |
|
<t>The current number of instruments |
| 5632 |
|
in the specified directory.</t> |
| 5633 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5634 |
|
<list> |
| 5635 |
|
<t>if the given directory does not exist.</t> |
| 5636 |
|
</list> |
| 5637 |
|
</t> |
| 5638 |
|
</list> |
| 5639 |
|
</t> |
| 5640 |
|
|
| 5641 |
|
<t>Example:</t> |
| 5642 |
|
<t> |
| 5643 |
|
<list> |
| 5644 |
|
<t>C: "GET DB_INSTRUMENTS '/Piano Collection'"</t> |
| 5645 |
|
<t>S: "2"</t> |
| 5646 |
|
</list> |
| 5647 |
|
</t> |
| 5648 |
|
</section> |
| 5649 |
|
|
| 5650 |
|
<section title="Listing all instruments in specific directory" anchor="LIST DB_INSTRUMENTS"> |
| 5651 |
|
<t>The front-end can retrieve the current list of instruments |
| 5652 |
|
in specific directory by sending the following command:</t> |
| 5653 |
|
<t> |
| 5654 |
|
<list> |
| 5655 |
|
<t>LIST DB_INSTRUMENTS [RECURSIVE] <dir></t> |
| 5656 |
|
</list> |
| 5657 |
|
</t> |
| 5658 |
|
<t>Where <dir> should be replaced by the absolute path |
| 5659 |
|
name of the directory. If RECURSIVE is specified, the absolute path |
| 5660 |
|
names of all instruments, including those located in subdirectories |
| 5661 |
|
of the specified directory, will be returned.</t> |
| 5662 |
|
|
| 5663 |
|
<t>Possible Answers:</t> |
| 5664 |
|
<t> |
| 5665 |
|
<list> |
| 5666 |
|
<t>A comma separated list of all instruments |
| 5667 |
|
(encapsulated into apostrophes) in the specified directory.</t> |
| 5668 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5669 |
|
<list> |
| 5670 |
|
<t>if the given directory does not exist.</t> |
| 5671 |
|
</list> |
| 5672 |
|
</t> |
| 5673 |
|
</list> |
| 5674 |
|
</t> |
| 5675 |
|
<t>Example:</t> |
| 5676 |
|
<t> |
| 5677 |
|
<list> |
| 5678 |
|
<t>C: "LIST DB_INSTRUMENTS '/Piano Collection'"</t> |
| 5679 |
|
<t>S: "'Bosendorfer 290','Steinway D'"</t> |
| 5680 |
|
</list> |
| 5681 |
|
</t> |
| 5682 |
|
<t> |
| 5683 |
|
<list> |
| 5684 |
|
<t>C: "LIST DB_INSTRUMENTS RECURSIVE '/Piano Collection'"</t> |
| 5685 |
|
<t>S: "'/Piano Collection/Bosendorfer 290','/Piano Collection/Steinway D','/Piano Collection/Lite/Free Piano'"</t> |
| 5686 |
|
</list> |
| 5687 |
|
</t> |
| 5688 |
|
</section> |
| 5689 |
|
|
| 5690 |
|
<section title="Getting instrument information" anchor="GET DB_INSTRUMENT INFO"> |
| 5691 |
|
<t>The front-end can ask for the current settings of an |
| 5692 |
|
instrument by sending the following command:</t> |
| 5693 |
|
<t> |
| 5694 |
|
<list> |
| 5695 |
|
<t>GET DB_INSTRUMENT INFO <instr_path></t> |
| 5696 |
|
</list> |
| 5697 |
|
</t> |
| 5698 |
|
<t>Where <instr_path> should be replaced by the absolute path |
| 5699 |
|
name of the instrument the front-end is interested in.</t> |
| 5700 |
|
|
| 5701 |
|
<t>Possible Answers:</t> |
| 5702 |
|
<t> |
| 5703 |
|
<list> |
| 5704 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 5705 |
|
Each answer line begins with the settings category name |
| 5706 |
|
followed by a colon and then a space character <SP> and finally |
| 5707 |
|
the info character string to that setting category. At the |
| 5708 |
|
moment the following categories are defined:</t> |
| 5709 |
|
|
| 5710 |
|
<t> |
| 5711 |
|
<list> |
| 5712 |
|
<t>INSTRUMENT_FILE - |
| 5713 |
|
<list> |
| 5714 |
|
<t>File name of the instrument. |
| 5715 |
|
Note that the character string may contain |
| 5716 |
|
<xref target="character_set">escape sequences</xref>.</t> |
| 5717 |
|
</list> |
| 5718 |
|
</t> |
| 5719 |
|
<t>INSTRUMENT_NR - |
| 5720 |
|
<list> |
| 5721 |
|
<t>Index of the instrument within the file.</t> |
| 5722 |
|
</list> |
| 5723 |
|
</t> |
| 5724 |
|
<t>FORMAT_FAMILY - |
| 5725 |
|
<list> |
| 5726 |
|
<t>The format family of the instrument.</t> |
| 5727 |
|
</list> |
| 5728 |
|
</t> |
| 5729 |
|
<t>FORMAT_VERSION - |
| 5730 |
|
<list> |
| 5731 |
|
<t>The format version of the instrument.</t> |
| 5732 |
|
</list> |
| 5733 |
|
</t> |
| 5734 |
|
<t>SIZE - |
| 5735 |
|
<list> |
| 5736 |
|
<t>The size of the instrument in bytes.</t> |
| 5737 |
|
</list> |
| 5738 |
|
</t> |
| 5739 |
|
<t>CREATED - |
| 5740 |
|
<list> |
| 5741 |
|
<t>The date and time when the instrument is added |
| 5742 |
|
in the instruments database, represented in |
| 5743 |
|
"YYYY-MM-DD HH:MM:SS" format</t> |
| 5744 |
|
</list> |
| 5745 |
|
</t> |
| 5746 |
|
<t>MODIFIED - |
| 5747 |
|
<list> |
| 5748 |
|
<t>The date and time of the last modification of the |
| 5749 |
|
instrument's database settings, represented in |
| 5750 |
|
"YYYY-MM-DD HH:MM:SS" format</t> |
| 5751 |
|
</list> |
| 5752 |
|
</t> |
| 5753 |
|
<t>DESCRIPTION - |
| 5754 |
|
<list> |
| 5755 |
|
<t>A brief description of the instrument. |
| 5756 |
|
Note that the character string may contain |
| 5757 |
|
<xref target="character_set">escape sequences</xref>.</t> |
| 5758 |
|
</list> |
| 5759 |
|
</t> |
| 5760 |
|
<t>IS_DRUM - |
| 5761 |
|
<list> |
| 5762 |
|
<t>either true or false, determines whether the |
| 5763 |
|
instrument is a drumkit or a chromatic instrument</t> |
| 5764 |
|
</list> |
| 5765 |
|
</t> |
| 5766 |
|
<t>PRODUCT - |
| 5767 |
|
<list> |
| 5768 |
|
<t>The product title of the instrument. |
| 5769 |
|
Note that the character string may contain |
| 5770 |
|
<xref target="character_set">escape sequences</xref>.</t> |
| 5771 |
|
</list> |
| 5772 |
|
</t> |
| 5773 |
|
<t>ARTISTS - |
| 5774 |
|
<list> |
| 5775 |
|
<t>Lists the artist names. |
| 5776 |
|
Note that the character string may contain |
| 5777 |
|
<xref target="character_set">escape sequences</xref>.</t> |
| 5778 |
|
</list> |
| 5779 |
|
</t> |
| 5780 |
|
<t>KEYWORDS - |
| 5781 |
|
<list> |
| 5782 |
|
<t>Provides a list of keywords that refer to the instrument. |
| 5783 |
|
Keywords are separated with semicolon and blank. |
| 5784 |
|
Note that the character string may contain |
| 5785 |
|
<xref target="character_set">escape sequences</xref>.</t> |
| 5786 |
|
</list> |
| 5787 |
|
</t> |
| 5788 |
|
</list> |
| 5789 |
|
</t> |
| 5790 |
|
</list> |
| 5791 |
|
</t> |
| 5792 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 5793 |
|
|
| 5794 |
|
<t>Example:</t> |
| 5795 |
|
<t> |
| 5796 |
|
<list> |
| 5797 |
|
<t>C: "GET DB_INSTRUMENT INFO '/Piano Collection/Bosendorfer 290'"</t> |
| 5798 |
|
<t>S: "INSTRUMENT_FILE: /home/me/gigs/Bosendorfer 290.gig"</t> |
| 5799 |
|
<t> "INSTRUMENT_NR: 0"</t> |
| 5800 |
|
<t> "FORMAT_FAMILY: GIG"</t> |
| 5801 |
|
<t> "FORMAT_VERSION: 2"</t> |
| 5802 |
|
<t> "SIZE: 2050871870"</t> |
| 5803 |
|
<t> "CREATED: 2007-02-05 10:23:12"</t> |
| 5804 |
|
<t> "MODIFIED: 2007-04-07 12:50:21"</t> |
| 5805 |
|
<t> "DESCRIPTION: "</t> |
| 5806 |
|
<t> "IS_DRUM: false"</t> |
| 5807 |
|
<t> "PRODUCT: GRANDIOSO Bosendorfer 290"</t> |
| 5808 |
|
<t> "ARTISTS: Post Musical Instruments"</t> |
| 5809 |
|
<t> "KEYWORDS: Bosendorfer"</t> |
| 5810 |
|
<t> "."</t> |
| 5811 |
|
</list> |
| 5812 |
|
</t> |
| 5813 |
|
</section> |
| 5814 |
|
|
| 5815 |
|
<section title="Renaming an instrument" anchor="SET DB_INSTRUMENT NAME"> |
| 5816 |
|
<t>The front-end can alter the name of a specific |
| 5817 |
|
instrument by sending the following command:</t> |
| 5818 |
|
<t> |
| 5819 |
|
<list> |
| 5820 |
|
<t>SET DB_INSTRUMENT NAME <instr> <name></t> |
| 5821 |
|
</list> |
| 5822 |
|
</t> |
| 5823 |
|
<t>Where <instr> is the absolute path name of the instrument and |
| 5824 |
|
<name> is the new name for that instrument.</t> |
| 5825 |
|
|
| 5826 |
|
<t>Possible Answers:</t> |
| 5827 |
|
<t> |
| 5828 |
|
<list> |
| 5829 |
|
<t>"OK" - |
| 5830 |
|
<list> |
| 5831 |
|
<t>on success</t> |
| 5832 |
|
</list> |
| 5833 |
|
</t> |
| 5834 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5835 |
|
<list> |
| 5836 |
|
<t>in case the given instrument does not exists, |
| 5837 |
|
or if an instrument with name equal to the new |
| 5838 |
|
name already exists.</t> |
| 5839 |
|
</list> |
| 5840 |
|
</t> |
| 5841 |
|
</list> |
| 5842 |
|
</t> |
| 5843 |
|
|
| 5844 |
|
<t>Example:</t> |
| 5845 |
|
<t> |
| 5846 |
|
<list> |
| 5847 |
|
<t>C: "SET DB_INSTRUMENT NAME '/Piano Collection/Bosendorfer' 'Bosendorfer 290'"</t> |
| 5848 |
|
<t>S: "OK"</t> |
| 5849 |
|
</list> |
| 5850 |
|
</t> |
| 5851 |
|
</section> |
| 5852 |
|
|
| 5853 |
|
<section title="Moving an instrument" anchor="MOVE DB_INSTRUMENT"> |
| 5854 |
|
<t>The front-end can move a specific instrument to another directory by |
| 5855 |
|
sending the following command:</t> |
| 5856 |
|
<t> |
| 5857 |
|
<list> |
| 5858 |
|
<t>MOVE DB_INSTRUMENT <instr> <dst></t> |
| 5859 |
|
</list> |
| 5860 |
|
</t> |
| 5861 |
|
<t>Where <instr> is the absolute path name of the instrument |
| 5862 |
|
to move and <dst> is the directory where the instrument will |
| 5863 |
|
be moved to.</t> |
| 5864 |
|
|
| 5865 |
|
<t>Possible Answers:</t> |
| 5866 |
|
<t> |
| 5867 |
|
<list> |
| 5868 |
|
<t>"OK" - |
| 5869 |
|
<list> |
| 5870 |
|
<t>on success</t> |
| 5871 |
|
</list> |
| 5872 |
|
</t> |
| 5873 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5874 |
|
<list> |
| 5875 |
|
<t>in case the given instrument does not exists, |
| 5876 |
|
or if an instrument with name equal to the name of the |
| 5877 |
|
specified instrument already exists in the destination |
| 5878 |
|
directory.</t> |
| 5879 |
|
</list> |
| 5880 |
|
</t> |
| 5881 |
|
</list> |
| 5882 |
|
</t> |
| 5883 |
|
|
| 5884 |
|
<t>Example:</t> |
| 5885 |
|
<t> |
| 5886 |
|
<list> |
| 5887 |
|
<t>C: "MOVE DB_INSTRUMENT '/Piano Collection/Bosendorfer 290' '/Piano Collection/Acoustic'"</t> |
| 5888 |
|
<t>S: "OK"</t> |
| 5889 |
|
</list> |
| 5890 |
|
</t> |
| 5891 |
|
</section> |
| 5892 |
|
|
| 5893 |
|
<section title="Copying instruments" anchor="COPY DB_INSTRUMENT"> |
| 5894 |
|
<t>The front-end can copy a specific instrument to another directory by |
| 5895 |
|
sending the following command:</t> |
| 5896 |
|
<t> |
| 5897 |
|
<list> |
| 5898 |
|
<t>COPY DB_INSTRUMENT <instr> <dst></t> |
| 5899 |
|
</list> |
| 5900 |
|
</t> |
| 5901 |
|
<t>Where <instr> is the absolute path name of the instrument |
| 5902 |
|
to copy and <dst> is the directory where the instrument will |
| 5903 |
|
be copied to.</t> |
| 5904 |
|
|
| 5905 |
|
<t>Possible Answers:</t> |
| 5906 |
|
<t> |
| 5907 |
|
<list> |
| 5908 |
|
<t>"OK" - |
| 5909 |
|
<list> |
| 5910 |
|
<t>on success</t> |
| 5911 |
|
</list> |
| 5912 |
|
</t> |
| 5913 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5914 |
|
<list> |
| 5915 |
|
<t>in case the given instrument does not exists, |
| 5916 |
|
or if an instrument with name equal to the name of the |
| 5917 |
|
specified instrument already exists in the destination |
| 5918 |
|
directory.</t> |
| 5919 |
|
</list> |
| 5920 |
|
</t> |
| 5921 |
|
</list> |
| 5922 |
|
</t> |
| 5923 |
|
|
| 5924 |
|
<t>Example:</t> |
| 5925 |
|
<t> |
| 5926 |
|
<list> |
| 5927 |
|
<t>C: "COPY DB_INSTRUMENT '/Piano Collection/Bosendorfer 290' '/Acoustic/Pianos/'"</t> |
| 5928 |
|
<t>S: "OK"</t> |
| 5929 |
|
</list> |
| 5930 |
|
</t> |
| 5931 |
|
</section> |
| 5932 |
|
|
| 5933 |
|
<section title="Changing the description of instrument" anchor="SET DB_INSTRUMENT DESCRIPTION"> |
| 5934 |
|
<t>The front-end can alter the description of a specific |
| 5935 |
|
instrument by sending the following command:</t> |
| 5936 |
|
<t> |
| 5937 |
|
<list> |
| 5938 |
|
<t>SET DB_INSTRUMENT DESCRIPTION <instr> <desc></t> |
| 5939 |
|
</list> |
| 5940 |
|
</t> |
| 5941 |
|
<t>Where <instr> is the absolute path name of the instrument and |
| 5942 |
|
<desc> is the new description for the instrument |
| 5943 |
|
(encapsulated into apostrophes, supporting escape sequences as described in chapter |
| 5944 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>").</t> |
| 5945 |
|
|
| 5946 |
|
<t>Possible Answers:</t> |
| 5947 |
|
<t> |
| 5948 |
|
<list> |
| 5949 |
|
<t>"OK" - |
| 5950 |
|
<list> |
| 5951 |
|
<t>on success</t> |
| 5952 |
|
</list> |
| 5953 |
|
</t> |
| 5954 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 5955 |
|
<list> |
| 5956 |
|
<t>in case the given instrument does not exists.</t> |
| 5957 |
|
</list> |
| 5958 |
|
</t> |
| 5959 |
|
</list> |
| 5960 |
|
</t> |
| 5961 |
|
|
| 5962 |
|
<t>Example:</t> |
| 5963 |
|
<t> |
| 5964 |
|
<list> |
| 5965 |
|
<t>C: "SET DB_INSTRUMENT DESCRIPTION '/Piano Collection/Acoustic/Bosendorfer 290' 'No comment :)'"</t> |
| 5966 |
|
<t>S: "OK"</t> |
| 5967 |
|
</list> |
| 5968 |
|
</t> |
| 5969 |
|
</section> |
| 5970 |
|
|
| 5971 |
|
<section title="Finding instruments" anchor="FIND DB_INSTRUMENTS"> |
| 5972 |
|
<t>The front-end can search for instruments |
| 5973 |
|
in specific directory by sending the following command:</t> |
| 5974 |
|
<t> |
| 5975 |
|
<list> |
| 5976 |
|
<t>FIND DB_INSTRUMENTS [NON_RECURSIVE] <dir> <criteria-list></t> |
| 5977 |
|
</list> |
| 5978 |
|
</t> |
| 5979 |
|
<t>Where <dir> should be replaced by the absolute path |
| 5980 |
|
name of the directory to search in. If NON_RECURSIVE is specified, the |
| 5981 |
|
directories located in subdirectories of the specified directory will not |
| 5982 |
|
be searched. <criteria-list> is a list of search criterias |
| 5983 |
|
in form of "key1=val1 key2=val2 ...". The following criterias are |
| 5984 |
|
allowed:</t> |
| 5985 |
|
<t> |
| 5986 |
|
<t>NAME='<search-string>' |
| 5987 |
|
<list> |
| 5988 |
|
<t>Restricts the search to instruments, which names |
| 5989 |
|
satisfy the supplied search string (encapsulated into apostrophes, |
| 5990 |
|
supporting escape sequences as described in chapter |
| 5991 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>").</t> |
| 5992 |
|
</list> |
| 5993 |
|
</t> |
| 5994 |
|
|
| 5995 |
|
<t>SIZE=[<min>]..[<max>] |
| 5996 |
|
<list> |
| 5997 |
|
<t>Restricts the search to instruments, which |
| 5998 |
|
size is in the specified range. If <min> is omitted, |
| 5999 |
|
the search results are restricted to instruments with size less then |
| 6000 |
|
or equal to <max>. If <max> is omitted, the |
| 6001 |
|
search is restricted to instruments with size greater then |
| 6002 |
|
or equal to <min>.</t> |
| 6003 |
|
</list> |
| 6004 |
|
</t> |
| 6005 |
|
|
| 6006 |
|
<t>CREATED='[<date-after>]..[<date-before>]' |
| 6007 |
|
<list> |
| 6008 |
|
<t>Restricts the search to instruments, which creation |
| 6009 |
|
date satisfies the specified period, where <date-after> |
| 6010 |
|
and <date-before> are in "YYYY-MM-DD HH:MM:SS" format. |
| 6011 |
|
If <date-after> is omitted the search is restricted to |
| 6012 |
|
instruments created before <date-before>. If |
| 6013 |
|
<date-before> is omitted, the search is restricted |
| 6014 |
|
to instruments created after <date-after>.</t> |
| 6015 |
|
</list> |
| 6016 |
|
</t> |
| 6017 |
|
|
| 6018 |
|
<t>MODIFIED='[<date-after>]..[<date-before>]' |
| 6019 |
|
<list> |
| 6020 |
|
<t>Restricts the search to instruments, which |
| 6021 |
|
date of last modification satisfies the specified period, where |
| 6022 |
|
<date-after> and <date-before> are in "YYYY-MM-DD HH:MM:SS" |
| 6023 |
|
format. If <date-after> is omitted the search is restricted to |
| 6024 |
|
instruments, which are last modified before <date-before>. If |
| 6025 |
|
<date-before> is omitted, the search is restricted to instruments, |
| 6026 |
|
which are last modified after <date-after>.</t> |
| 6027 |
|
</list> |
| 6028 |
|
</t> |
| 6029 |
|
|
| 6030 |
|
<t>DESCRIPTION='<search-string>' |
| 6031 |
|
<list> |
| 6032 |
|
<t>Restricts the search to instruments with description |
| 6033 |
|
that satisfies the supplied search string (encapsulated into apostrophes, |
| 6034 |
|
supporting escape sequences as described in chapter |
| 6035 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>").</t> |
| 6036 |
|
</list> |
| 6037 |
|
</t> |
| 6038 |
|
|
| 6039 |
|
<t>PRODUCT='<search-string>' |
| 6040 |
|
<list> |
| 6041 |
|
<t>Restricts the search to instruments with product info |
| 6042 |
|
that satisfies the supplied search string (encapsulated into apostrophes, |
| 6043 |
|
supporting escape sequences as described in chapter |
| 6044 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>").</t> |
| 6045 |
|
</list> |
| 6046 |
|
</t> |
| 6047 |
|
|
| 6048 |
|
<t>ARTISTS='<search-string>' |
| 6049 |
|
<list> |
| 6050 |
|
<t>Restricts the search to instruments with artists info |
| 6051 |
|
that satisfies the supplied search string (encapsulated into apostrophes, |
| 6052 |
|
supporting escape sequences as described in chapter |
| 6053 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>").</t> |
| 6054 |
|
</list> |
| 6055 |
|
</t> |
| 6056 |
|
|
| 6057 |
|
<t>KEYWORDS='<search-string>' |
| 6058 |
|
<list> |
| 6059 |
|
<t>Restricts the search to instruments with keyword list |
| 6060 |
|
that satisfies the supplied search string (encapsulated into apostrophes, |
| 6061 |
|
supporting escape sequences as described in chapter |
| 6062 |
|
"<xref target="character_set">Character Set and Escape Sequences</xref>").</t> |
| 6063 |
|
</list> |
| 6064 |
|
</t> |
| 6065 |
|
|
| 6066 |
|
<t>IS_DRUM=true | false |
| 6067 |
|
<list> |
| 6068 |
|
<t>Either true or false. Restricts the search to |
| 6069 |
|
drum kits or chromatic instruments.</t> |
| 6070 |
|
</list> |
| 6071 |
|
</t> |
| 6072 |
|
|
| 6073 |
|
<t>FORMAT_FAMILIES='<format-list>' |
| 6074 |
|
<list> |
| 6075 |
|
<t>Restricts the search to instruments of the supplied format families, |
| 6076 |
|
where <format-list> is a comma separated list of format families.</t> |
| 6077 |
|
</list> |
| 6078 |
|
</t> |
| 6079 |
|
</t> |
| 6080 |
|
|
| 6081 |
|
<t>Where <search-string> is either a regular expression, or a |
| 6082 |
|
word list separated with spaces for OR search and with '+' for AND search.</t> |
| 6083 |
|
|
| 6084 |
|
<t>Possible Answers:</t> |
| 6085 |
|
<t> |
| 6086 |
|
<list> |
| 6087 |
|
<t>A comma separated list with the absolute path names (encapsulated into |
| 6088 |
|
apostrophes) of all instruments in the specified directory that satisfy |
| 6089 |
|
the supplied search criterias.</t> |
| 6090 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 6091 |
|
<list> |
| 6092 |
|
<t>if the given directory does not exist.</t> |
| 6093 |
|
</list> |
| 6094 |
|
</t> |
| 6095 |
|
</list> |
| 6096 |
|
</t> |
| 6097 |
|
<t>Example:</t> |
| 6098 |
|
<t> |
| 6099 |
|
<list> |
| 6100 |
|
<t>C: "FIND DB_INSTRUMENTS '/Piano Collection' NAME='bosendorfer+290'"</t> |
| 6101 |
|
<t>S: "'/Piano Collection/Bosendorfer 290'"</t> |
| 6102 |
|
</list> |
| 6103 |
|
</t> |
| 6104 |
|
<t> |
| 6105 |
|
<list> |
| 6106 |
|
<t>C: "FIND DB_INSTRUMENTS '/Piano Collection' CREATED='2007-04-01 09:30:13..'"</t> |
| 6107 |
|
<t>S: "'/Piano Collection/Bosendorfer 290','/Piano Collection/Steinway D'"</t> |
| 6108 |
|
</list> |
| 6109 |
|
</t> |
| 6110 |
|
</section> |
| 6111 |
|
|
| 6112 |
|
<section title="Getting job status information" anchor="GET DB_INSTRUMENTS_JOB INFO"> |
| 6113 |
|
<t>The front-end can ask for the current status of a |
| 6114 |
|
particular database instruments job by sending the following command:</t> |
| 6115 |
|
<t> |
| 6116 |
|
<list> |
| 6117 |
|
<t>GET DB_INSTRUMENTS_JOB INFO <job-id></t> |
| 6118 |
|
</list> |
| 6119 |
|
</t> |
| 6120 |
|
<t>Where <job-id> should be replaced by the numerical ID |
| 6121 |
|
of the job the front-end is interested in.</t> |
| 6122 |
|
|
| 6123 |
|
<t>Possible Answers:</t> |
| 6124 |
|
<t> |
| 6125 |
|
<list> |
| 6126 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 6127 |
|
Each answer line begins with the settings category name |
| 6128 |
|
followed by a colon and then a space character <SP> and finally |
| 6129 |
|
the info character string to that setting category. At the |
| 6130 |
|
moment the following categories are defined:</t> |
| 6131 |
|
|
| 6132 |
|
<t> |
| 6133 |
|
<list> |
| 6134 |
|
<t>FILES_TOTAL - |
| 6135 |
|
<list> |
| 6136 |
|
<t>The total number of files scheduled for scanning</t> |
| 6137 |
|
</list> |
| 6138 |
|
</t> |
| 6139 |
|
<t>FILES_SCANNED - |
| 6140 |
|
<list> |
| 6141 |
|
<t>The current number of scanned files</t> |
| 6142 |
|
</list> |
| 6143 |
|
</t> |
| 6144 |
|
<t>SCANNING - |
| 6145 |
|
<list> |
| 6146 |
|
<t>The absolute path name of the file which is currently |
| 6147 |
|
being scanned</t> |
| 6148 |
|
</list> |
| 6149 |
|
</t> |
| 6150 |
|
<t>STATUS - |
| 6151 |
|
<list> |
| 6152 |
|
<t>An integer value between 0 and 100 indicating the |
| 6153 |
|
scanning progress percentage of the file which is |
| 6154 |
|
currently being scanned</t> |
| 6155 |
|
</list> |
| 6156 |
|
</t> |
| 6157 |
|
</list> |
| 6158 |
|
</t> |
| 6159 |
|
</list> |
| 6160 |
|
</t> |
| 6161 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 6162 |
|
|
| 6163 |
|
<t>Example:</t> |
| 6164 |
|
<t> |
| 6165 |
|
<list> |
| 6166 |
|
<t>C: "GET DB_INSTRUMENTS_JOB INFO 2"</t> |
| 6167 |
|
<t>S: "FILES_TOTAL: 12"</t> |
| 6168 |
|
<t> "FILES_SCANNED: 7"</t> |
| 6169 |
|
<t> "SCANNING: /home/me/gigs/Bosendorfer 290.gig"</t> |
| 6170 |
|
<t> "STATUS: 42"</t> |
| 6171 |
|
<t> "."</t> |
| 6172 |
|
</list> |
| 6173 |
|
</t> |
| 6174 |
|
</section> |
| 6175 |
|
|
| 6176 |
|
<section title="Formatting the instruments database" anchor="FORMAT INSTRUMENTS_DB"> |
| 6177 |
|
<t>The front-end can remove all instruments and directories and re-create |
| 6178 |
|
the instruments database structure (e.g., in case of a database corruption) |
| 6179 |
|
by sending the following command:</t> |
| 6180 |
|
<t> |
| 6181 |
|
<list> |
| 6182 |
|
<t>FORMAT INSTRUMENTS_DB</t> |
| 6183 |
|
</list> |
| 6184 |
|
</t> |
| 6185 |
|
|
| 6186 |
|
<t>Possible Answers:</t> |
| 6187 |
|
<t> |
| 6188 |
|
<list> |
| 6189 |
|
<t>"OK" - |
| 6190 |
|
<list> |
| 6191 |
|
<t>on success</t> |
| 6192 |
|
</list> |
| 6193 |
|
</t> |
| 6194 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 6195 |
|
<list> |
| 6196 |
|
<t>If the formatting of the instruments database |
| 6197 |
|
failed.</t> |
| 6198 |
|
</list> |
| 6199 |
|
</t> |
| 6200 |
|
</list> |
| 6201 |
|
</t> |
| 6202 |
|
</section> |
| 6203 |
|
|
| 6204 |
|
<section title="Checking for lost instrument files" anchor="FIND LOST DB_INSTRUMENT_FILES"> |
| 6205 |
|
<t>The front-end can retrieve the list of all instrument files in the instruments database |
| 6206 |
|
that don't exist in the filesystem by sending the following command:</t> |
| 6207 |
|
<t> |
| 6208 |
|
<list> |
| 6209 |
|
<t>FIND LOST DB_INSTRUMENT_FILES</t> |
| 6210 |
|
</list> |
| 6211 |
|
</t> |
| 6212 |
|
|
| 6213 |
|
<t>Possible Answers:</t> |
| 6214 |
|
<t> |
| 6215 |
|
<list> |
| 6216 |
|
<t>A comma separated list with the absolute path names |
| 6217 |
|
(encapsulated into apostrophes) of all lost instrument files.</t> |
| 6218 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 6219 |
|
<list> |
| 6220 |
|
<t>in case it failed, providing an appropriate error code and error message.</t> |
| 6221 |
|
</list> |
| 6222 |
|
</t> |
| 6223 |
|
</list> |
| 6224 |
|
</t> |
| 6225 |
|
<t>Example:</t> |
| 6226 |
|
<t> |
| 6227 |
|
<list> |
| 6228 |
|
<t>C: "FIND LOST DB_INSTRUMENT_FILES"</t> |
| 6229 |
|
<t>S: "'/gigs/Bosendorfer 290.gig','/gigs/Steinway D.gig','/gigs/Free Piano.gig'"</t> |
| 6230 |
|
</list> |
| 6231 |
|
</t> |
| 6232 |
|
</section> |
| 6233 |
|
|
| 6234 |
|
<section title="Replacing an instrument file" anchor="SET DB_INSTRUMENT FILE_PATH"> |
| 6235 |
|
<t>The front-end can substitute all occurrences of an instrument file |
| 6236 |
|
in the instruments database with a new one by sending the following command:</t> |
| 6237 |
|
<t> |
| 6238 |
|
<list> |
| 6239 |
|
<t>SET DB_INSTRUMENT FILE_PATH <old_path> <new_path></t> |
| 6240 |
|
</list> |
| 6241 |
|
</t> |
| 6242 |
|
<t>Where <old_path> is the absolute path name of the instrument file |
| 6243 |
|
to substitute with <new_path>.</t> |
| 6244 |
|
|
| 6245 |
|
<t>Possible Answers:</t> |
| 6246 |
|
<t> |
| 6247 |
|
<list> |
| 6248 |
|
<t>"OK" - |
| 6249 |
|
<list> |
| 6250 |
|
<t>on success</t> |
| 6251 |
|
</list> |
| 6252 |
|
</t> |
| 6253 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 6254 |
|
<list> |
| 6255 |
|
<t>in case it failed, providing an appropriate error code and error message.</t> |
| 6256 |
|
</list> |
| 6257 |
|
</t> |
| 6258 |
|
</list> |
| 6259 |
|
</t> |
| 6260 |
|
|
| 6261 |
|
<t>Example:</t> |
| 6262 |
|
<t> |
| 6263 |
|
<list> |
| 6264 |
|
<t>C: "SET DB_INSTRUMENT FILE_PATH '/gigs/Bosendorfer 290.gig' '/gigs/pianos/Bosendorfer 290.gig'"</t> |
| 6265 |
|
<t>S: "OK"</t> |
| 6266 |
|
</list> |
| 6267 |
|
</t> |
| 6268 |
|
</section> |
| 6269 |
|
|
| 6270 |
|
</section> |
| 6271 |
|
|
| 6272 |
|
|
| 6273 |
|
|
| 6274 |
|
<section title="Editing Instruments" anchor="editing_instruments"> |
| 6275 |
|
<t>The sampler allows to edit instruments while playing with the |
| 6276 |
|
sampler by spawning an external (3rd party) instrument editor |
| 6277 |
|
application for a given instrument. The 3rd party instrument |
| 6278 |
|
editor applications have to place a respective plugin DLL file |
| 6279 |
|
into the sampler's plugins directory. The sampler will |
| 6280 |
|
automatically try to load all plugin DLLs in that directory on |
| 6281 |
|
startup and only on startup!</t> |
| 6282 |
|
<t>At the moment there is only one command for this feature set, |
| 6283 |
|
but this will most probably change in future.</t> |
| 6284 |
|
|
| 6285 |
|
<section title="Opening an appropriate instrument editor application" anchor="EDIT INSTRUMENT"> |
| 6286 |
|
<t>The front-end can request to open an appropriate instrument |
| 6287 |
|
editor application by sending the following command:</t> |
| 6288 |
|
<t> |
| 6289 |
|
<list> |
| 6290 |
|
<t>EDIT CHANNEL INSTRUMENT <sampler-channel></t> |
| 6291 |
|
</list> |
| 6292 |
|
</t> |
| 6293 |
|
<t>Where <sampler-channel> should be replaced by the |
| 6294 |
|
number of the sampler channel as given by the |
| 6295 |
|
<xref target="ADD CHANNEL">"ADD CHANNEL"</xref> |
| 6296 |
|
or <xref target="LIST CHANNELS">"LIST CHANNELS"</xref> |
| 6297 |
|
command.</t> |
| 6298 |
|
|
| 6299 |
|
<t>The sampler will try to ask all registered instrument |
| 6300 |
|
editors (or to be more specific: their sampler plugins) |
| 6301 |
|
whether they are capable to handle the instrument on the |
| 6302 |
|
given sampler channel. The sampler will simply use the first |
| 6303 |
|
instrument editor application which replied with a positive |
| 6304 |
|
answer and spawn that instrument editor application within |
| 6305 |
|
the sampler's process and provide that application access |
| 6306 |
|
to the instrument's data structures, so both applications |
| 6307 |
|
can share and access the same instruments data at the same |
| 6308 |
|
time, thus allowing to immediately hear changes with the |
| 6309 |
|
sampler made by the instrument editor.</t> |
| 6310 |
|
|
| 6311 |
|
<t>Note: consequently instrument editors are always spawned |
| 6312 |
|
locally on the same machine where the sampler is running |
| 6313 |
|
on!</t> |
| 6314 |
|
|
| 6315 |
|
<t>Possible Answers:</t> |
| 6316 |
|
<t> |
| 6317 |
|
<list> |
| 6318 |
|
<t>"OK" - |
| 6319 |
|
<list> |
| 6320 |
|
<t>when an appropriate instrument editor was |
| 6321 |
|
launched</t> |
| 6322 |
|
</list> |
| 6323 |
|
</t> |
| 6324 |
|
<t>"WRN:<warning-code>:<warning-message>" - |
| 6325 |
|
<list> |
| 6326 |
|
<t>when an appropriate instrument editor was |
| 6327 |
|
launched, but there are noteworthy issues</t> |
| 6328 |
|
</list> |
| 6329 |
|
</t> |
| 6330 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 6331 |
|
<list> |
| 6332 |
|
<t>when an appropriate instrument editor |
| 6333 |
|
could not be launched</t> |
| 6334 |
|
</list> |
| 6335 |
|
</t> |
| 6336 |
|
</list> |
| 6337 |
|
</t> |
| 6338 |
|
|
| 6339 |
|
<t>Examples:</t> |
| 6340 |
|
<t> |
| 6341 |
|
<list> |
| 6342 |
|
<t>C: "EDIT CHANNEL INSTRUMENT 0"</t> |
| 6343 |
|
<t>S: "OK"</t> |
| 6344 |
|
</list> |
| 6345 |
|
</t> |
| 6346 |
|
</section> |
| 6347 |
|
</section> |
| 6348 |
|
|
| 6349 |
|
<section title="Managing Files" anchor="file_management"> |
| 6350 |
|
<t>You can query detailed informations about files located |
| 6351 |
|
at the same system where the sampler instance is running on. |
| 6352 |
|
Using this command set allows to retrieve file informations |
| 6353 |
|
even remotely from another machine.</t> |
| 6354 |
|
|
| 6355 |
|
<section title="Retrieving amount of instruments of a file" anchor="GET FILE INSTRUMENTS"> |
| 6356 |
|
<t>The front-end can retrieve the amount of instruments |
| 6357 |
|
within a given instrument file by sending the |
| 6358 |
|
following command:</t> |
| 6359 |
|
<t> |
| 6360 |
|
<list> |
| 6361 |
|
<t>GET FILE INSTRUMENTS <filename></t> |
| 6362 |
|
</list> |
| 6363 |
|
</t> |
| 6364 |
|
<t>Where <filename> is the name of the instrument |
| 6365 |
|
file (encapsulated into apostrophes, supporting escape |
| 6366 |
|
sequences as described in chapter |
| 6367 |
|
"<xref target="character_set">Character Set and Escape |
| 6368 |
|
Sequences</xref>").</t> |
| 6369 |
|
|
| 6370 |
|
<t>The sampler will try to ask all sampler engines, |
| 6371 |
|
whether they support the given file and ask the first |
| 6372 |
|
engine with a positive answer for the amount of |
| 6373 |
|
instruments.</t> |
| 6374 |
|
|
| 6375 |
|
<t>Possible Answers:</t> |
| 6376 |
|
<t> |
| 6377 |
|
<list> |
| 6378 |
|
<t>On success, the sampler will answer by |
| 6379 |
|
returning the amount of instruments. |
| 6380 |
|
</t> |
| 6381 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 6382 |
|
<list> |
| 6383 |
|
<t>if the file could not be handled</t> |
| 6384 |
|
</list> |
| 6385 |
|
</t> |
| 6386 |
|
</list> |
| 6387 |
|
</t> |
| 6388 |
|
|
| 6389 |
|
<t>Examples:</t> |
| 6390 |
|
<t> |
| 6391 |
|
<list> |
| 6392 |
|
<t>C: "GET FILE INSTRUMENTS 'D:/Sounds/Foo.gig'"</t> |
| 6393 |
|
<t>S: "10"</t> |
| 6394 |
|
</list> |
| 6395 |
|
</t> |
| 6396 |
|
</section> |
| 6397 |
|
|
| 6398 |
|
<section title="Retrieving all instruments of a file" anchor="LIST FILE INSTRUMENTS"> |
| 6399 |
|
<t>The front-end can retrieve a list of all instruments |
| 6400 |
|
within a given instrument file by sending the |
| 6401 |
|
following command:</t> |
| 6402 |
|
<t> |
| 6403 |
|
<list> |
| 6404 |
|
<t>LIST FILE INSTRUMENTS <filename></t> |
| 6405 |
|
</list> |
| 6406 |
|
</t> |
| 6407 |
|
<t>Where <filename> is the name of the instrument |
| 6408 |
|
file (encapsulated into apostrophes, supporting escape |
| 6409 |
|
sequences as described in chapter |
| 6410 |
|
"<xref target="character_set">Character Set and Escape |
| 6411 |
|
Sequences</xref>").</t> |
| 6412 |
|
|
| 6413 |
|
<t>The sampler will try to ask all sampler engines, |
| 6414 |
|
whether they support the given file and ask the first |
| 6415 |
|
engine with a positive answer for a list of IDs for the |
| 6416 |
|
instruments in the given file.</t> |
| 6417 |
|
|
| 6418 |
|
<t>Possible Answers:</t> |
| 6419 |
|
<t> |
| 6420 |
|
<list> |
| 6421 |
|
<t>On success, the sampler will answer by |
| 6422 |
|
returning a comma separated list of |
| 6423 |
|
instrument IDs. |
| 6424 |
|
</t> |
| 6425 |
|
<t>"ERR:<error-code>:<error-message>" - |
| 6426 |
|
<list> |
| 6427 |
|
<t>if the file could not be handled</t> |
| 6428 |
|
</list> |
| 6429 |
|
</t> |
| 6430 |
|
</list> |
| 6431 |
|
</t> |
| 6432 |
|
|
| 6433 |
|
<t>Examples:</t> |
| 6434 |
|
<t> |
| 6435 |
|
<list> |
| 6436 |
|
<t>C: "LIST FILE INSTRUMENTS 'D:/Sounds/Foo.gig'"</t> |
| 6437 |
|
<t>S: "0,1,2,3,4,5,6,7,8,9"</t> |
| 6438 |
|
</list> |
| 6439 |
|
</t> |
| 6440 |
|
</section> |
| 6441 |
|
|
| 6442 |
|
<section title="Retrieving informations about one instrument in a file" anchor="GET FILE INSTRUMENT INFO"> |
| 6443 |
|
<t>The front-end can retrieve detailed informations |
| 6444 |
|
about a specific instrument within a given instrument |
| 6445 |
|
file by sending the following command:</t> |
| 6446 |
|
<t> |
| 6447 |
|
<list> |
| 6448 |
|
<t>GET FILE INSTRUMENT INFO <filename> |
| 6449 |
|
<instr-id></t> |
| 6450 |
|
</list> |
| 6451 |
|
</t> |
| 6452 |
|
<t>Where <filename> is the name of the instrument |
| 6453 |
|
file (encapsulated into apostrophes, supporting escape |
| 6454 |
|
sequences as described in chapter |
| 6455 |
|
"<xref target="character_set">Character Set and Escape |
| 6456 |
|
Sequences</xref>") and <instr-id> is the numeric |
| 6457 |
|
instrument ID as returned by the |
| 6458 |
|
<xref target="LIST FILE INSTRUMENTS"> |
| 6459 |
|
"LIST FILE INSTRUMENTS"</xref> command.</t> |
| 6460 |
|
|
| 6461 |
|
<t>The sampler will try to ask all sampler engines, |
| 6462 |
|
whether they support the given file and ask the first |
| 6463 |
|
engine with a positive answer for informations about the |
| 6464 |
|
specific instrument in the given file.</t> |
| 6465 |
|
|
| 6466 |
|
<t>Possible Answers:</t> |
| 6467 |
|
<t> |
| 6468 |
|
<list> |
| 6469 |
|
<t>LinuxSampler will answer by sending a <CRLF> separated list. |
| 6470 |
|
Each answer line begins with the settings category name |
| 6471 |
|
followed by a colon and then a space character <SP> and finally |
| 6472 |
|
the info character string to that setting category. At the |
| 6473 |
|
moment the following categories are defined:</t> |
| 6474 |
|
|
| 6475 |
|
<t> |
| 6476 |
|
<list> |
| 6477 |
|
<t>NAME - |
| 6478 |
|
<list> |
| 6479 |
|
<t>name of the instrument as |
| 6480 |
|
stored in the instrument file</t> |
| 6481 |
|
</list> |
| 6482 |
|
</t> |
| 6483 |
|
<t>FORMAT_FAMILY - |
| 6484 |
|
<list> |
| 6485 |
|
<t>name of the sampler format |
| 6486 |
|
of the given instrument</t> |
| 6487 |
|
</list> |
| 6488 |
|
</t> |
| 6489 |
|
<t>FORMAT_VERSION - |
| 6490 |
|
<list> |
| 6491 |
|
<t>version of the sampler format |
| 6492 |
|
the instrumen is stored as</t> |
| 6493 |
|
</list> |
| 6494 |
|
</t> |
| 6495 |
|
<t>PRODUCT - |
| 6496 |
|
<list> |
| 6497 |
|
<t>official product name of the |
| 6498 |
|
instrument as stored in the file |
| 6499 |
|
</t> |
| 6500 |
|
</list> |
| 6501 |
|
</t> |
| 6502 |
|
<t>ARTISTS - |
| 6503 |
|
<list> |
| 6504 |
|
<t>artists / sample library |
| 6505 |
|
vendor of the instrument</t> |
| 6506 |
|
</list> |
| 6507 |
|
</t> |
| 6508 |
|
<t>KEY_BINDINGS - |
| 6509 |
|
<list> |
| 6510 |
|
<t>comma separated list of integer values representing |
| 6511 |
|
the instrument's key mapping in the range between 0 .. 127, |
| 6512 |
|
reflecting the analog meaning of the MIDI specification.</t> |
| 6513 |
|
</list> |
| 6514 |
|
</t> |
| 6515 |
|
<t>KEYSWITCH_BINDINGS - |
| 6516 |
|
<list> |
| 6517 |
|
<t>comma separated list of integer values representing |
| 6518 |
|
the instrument's keyswitch mapping in the range between 0 .. 127, |
| 6519 |
|
reflecting the analog meaning of the MIDI specification.</t> |
| 6520 |
|
</list> |
| 6521 |
|
</t> |
| 6522 |
|
</list> |
| 6523 |
|
</t> |
| 6524 |
|
</list> |
| 6525 |
|
</t> |
| 6526 |
|
<t>The mentioned fields above don't have to be in particular order.</t> |
| 6527 |
|
|
| 6528 |
|
<t>Example:</t> |
| 6529 |
|
<t> |
| 6530 |
|
<list> |
| 6531 |
|
<t>C: "GET FILE INSTRUMENT INFO 'D:/Sounds/Foo.gig' 0"</t> |
| 6532 |
|
<t>S: "NAME: Lunatic Loops"</t> |
| 6533 |
|
<t> "FORMAT_FAMILY: GIG"</t> |
| 6534 |
|
<t> "FORMAT_VERSION: 3"</t> |
| 6535 |
|
<t> "PRODUCT: The Backbone Bongo Beats"</t> |
| 6536 |
|
<t> "ARTISTS: Jimmy the Fish"</t> |
| 6537 |
|
<t> "."</t> |
| 6538 |
|
</list> |
| 6539 |
|
</t> |
| 6540 |
|
</section> |
| 6541 |
|
</section> |
| 6542 |
|
</section> |
| 6543 |
|
|
| 6544 |
<section title="Command Syntax" anchor="command_syntax"> |
<section title="Command Syntax" anchor="command_syntax"> |
| 6545 |
<t>The grammar of the control protocol as descibed in <xref target="control_commands"/> |
<t>The grammar of the control protocol as descibed in <xref target="control_commands"/> |
| 6613 |
</t> |
</t> |
| 6614 |
<t>/ UNSUBSCRIBE SP unsubscribe_event |
<t>/ UNSUBSCRIBE SP unsubscribe_event |
| 6615 |
</t> |
</t> |
|
<t>/ SELECT SP text |
|
|
</t> |
|
| 6616 |
<t>/ RESET SP reset_instruction |
<t>/ RESET SP reset_instruction |
| 6617 |
</t> |
</t> |
| 6618 |
<t>/ CLEAR SP clear_instruction |
<t>/ CLEAR SP clear_instruction |
| 6619 |
</t> |
</t> |
| 6620 |
|
<t>/ FIND SP find_instruction |
| 6621 |
|
</t> |
| 6622 |
|
<t>/ MOVE SP move_instruction |
| 6623 |
|
</t> |
| 6624 |
|
<t>/ COPY SP copy_instruction |
| 6625 |
|
</t> |
| 6626 |
|
<t>/ EDIT SP edit_instruction |
| 6627 |
|
</t> |
| 6628 |
|
<t>/ FORMAT SP format_instruction |
| 6629 |
|
</t> |
| 6630 |
|
<t>/ SEND SP send_instruction |
| 6631 |
|
</t> |
| 6632 |
<t>/ RESET |
<t>/ RESET |
| 6633 |
</t> |
</t> |
| 6634 |
<t>/ QUIT |
<t>/ QUIT |
| 6639 |
<list> |
<list> |
| 6640 |
<t>CHANNEL |
<t>CHANNEL |
| 6641 |
</t> |
</t> |
| 6642 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP db_path |
| 6643 |
|
</t> |
| 6644 |
|
<t>/ DB_INSTRUMENTS SP NON_MODAL SP scan_mode SP db_path SP filename |
| 6645 |
|
</t> |
| 6646 |
|
<t>/ DB_INSTRUMENTS SP NON_MODAL SP scan_mode SP FILE_AS_DIR SP db_path SP filename |
| 6647 |
|
</t> |
| 6648 |
|
<t>/ DB_INSTRUMENTS SP scan_mode SP db_path SP filename |
| 6649 |
|
</t> |
| 6650 |
|
<t>/ DB_INSTRUMENTS SP scan_mode SP FILE_AS_DIR SP db_path SP filename |
| 6651 |
|
</t> |
| 6652 |
|
<t>/ DB_INSTRUMENTS SP NON_MODAL SP db_path SP filename |
| 6653 |
|
</t> |
| 6654 |
|
<t>/ DB_INSTRUMENTS SP NON_MODAL SP db_path SP filename SP instrument_index |
| 6655 |
|
</t> |
| 6656 |
|
<t>/ DB_INSTRUMENTS SP db_path SP filename |
| 6657 |
|
</t> |
| 6658 |
|
<t>/ DB_INSTRUMENTS SP db_path SP filename SP instrument_index |
| 6659 |
|
</t> |
| 6660 |
<t>/ MIDI_INSTRUMENT_MAP |
<t>/ MIDI_INSTRUMENT_MAP |
| 6661 |
</t> |
</t> |
| 6662 |
<t>/ MIDI_INSTRUMENT_MAP SP map_name |
<t>/ MIDI_INSTRUMENT_MAP SP map_name |
| 6665 |
</t> |
</t> |
| 6666 |
<t>subscribe_event = |
<t>subscribe_event = |
| 6667 |
<list> |
<list> |
| 6668 |
<t>CHANNEL_COUNT |
<t>AUDIO_OUTPUT_DEVICE_COUNT |
| 6669 |
|
</t> |
| 6670 |
|
<t>/ AUDIO_OUTPUT_DEVICE_INFO |
| 6671 |
|
</t> |
| 6672 |
|
<t>/ MIDI_INPUT_DEVICE_COUNT |
| 6673 |
|
</t> |
| 6674 |
|
<t>/ MIDI_INPUT_DEVICE_INFO |
| 6675 |
|
</t> |
| 6676 |
|
<t>/ CHANNEL_COUNT |
| 6677 |
|
</t> |
| 6678 |
|
<t>/ CHANNEL_MIDI |
| 6679 |
|
</t> |
| 6680 |
|
<t>/ DEVICE_MIDI |
| 6681 |
</t> |
</t> |
| 6682 |
<t>/ VOICE_COUNT |
<t>/ VOICE_COUNT |
| 6683 |
</t> |
</t> |
| 6687 |
</t> |
</t> |
| 6688 |
<t>/ CHANNEL_INFO |
<t>/ CHANNEL_INFO |
| 6689 |
</t> |
</t> |
| 6690 |
|
<t>/ FX_SEND_COUNT |
| 6691 |
|
</t> |
| 6692 |
|
<t>/ FX_SEND_INFO |
| 6693 |
|
</t> |
| 6694 |
|
<t>/ MIDI_INSTRUMENT_MAP_COUNT |
| 6695 |
|
</t> |
| 6696 |
|
<t>/ MIDI_INSTRUMENT_MAP_INFO |
| 6697 |
|
</t> |
| 6698 |
|
<t>/ MIDI_INSTRUMENT_COUNT |
| 6699 |
|
</t> |
| 6700 |
|
<t>/ MIDI_INSTRUMENT_INFO |
| 6701 |
|
</t> |
| 6702 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_COUNT |
| 6703 |
|
</t> |
| 6704 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_INFO |
| 6705 |
|
</t> |
| 6706 |
|
<t>/ DB_INSTRUMENT_COUNT |
| 6707 |
|
</t> |
| 6708 |
|
<t>/ DB_INSTRUMENT_INFO |
| 6709 |
|
</t> |
| 6710 |
|
<t>/ DB_INSTRUMENTS_JOB_INFO |
| 6711 |
|
</t> |
| 6712 |
<t>/ MISCELLANEOUS |
<t>/ MISCELLANEOUS |
| 6713 |
</t> |
</t> |
| 6714 |
|
<t>/ TOTAL_STREAM_COUNT |
| 6715 |
|
</t> |
| 6716 |
<t>/ TOTAL_VOICE_COUNT |
<t>/ TOTAL_VOICE_COUNT |
| 6717 |
</t> |
</t> |
| 6718 |
|
<t>/ GLOBAL_INFO |
| 6719 |
|
</t> |
| 6720 |
</list> |
</list> |
| 6721 |
</t> |
</t> |
| 6722 |
<t>unsubscribe_event = |
<t>unsubscribe_event = |
| 6723 |
<list> |
<list> |
| 6724 |
<t>CHANNEL_COUNT |
<t>AUDIO_OUTPUT_DEVICE_COUNT |
| 6725 |
|
</t> |
| 6726 |
|
<t>/ AUDIO_OUTPUT_DEVICE_INFO |
| 6727 |
|
</t> |
| 6728 |
|
<t>/ MIDI_INPUT_DEVICE_COUNT |
| 6729 |
|
</t> |
| 6730 |
|
<t>/ MIDI_INPUT_DEVICE_INFO |
| 6731 |
|
</t> |
| 6732 |
|
<t>/ CHANNEL_COUNT |
| 6733 |
|
</t> |
| 6734 |
|
<t>/ CHANNEL_MIDI |
| 6735 |
|
</t> |
| 6736 |
|
<t>/ DEVICE_MIDI |
| 6737 |
</t> |
</t> |
| 6738 |
<t>/ VOICE_COUNT |
<t>/ VOICE_COUNT |
| 6739 |
</t> |
</t> |
| 6743 |
</t> |
</t> |
| 6744 |
<t>/ CHANNEL_INFO |
<t>/ CHANNEL_INFO |
| 6745 |
</t> |
</t> |
| 6746 |
|
<t>/ FX_SEND_COUNT |
| 6747 |
|
</t> |
| 6748 |
|
<t>/ FX_SEND_INFO |
| 6749 |
|
</t> |
| 6750 |
|
<t>/ MIDI_INSTRUMENT_MAP_COUNT |
| 6751 |
|
</t> |
| 6752 |
|
<t>/ MIDI_INSTRUMENT_MAP_INFO |
| 6753 |
|
</t> |
| 6754 |
|
<t>/ MIDI_INSTRUMENT_COUNT |
| 6755 |
|
</t> |
| 6756 |
|
<t>/ MIDI_INSTRUMENT_INFO |
| 6757 |
|
</t> |
| 6758 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_COUNT |
| 6759 |
|
</t> |
| 6760 |
|
<t>/ DB_INSTRUMENT_DIRECTORY_INFO |
| 6761 |
|
</t> |
| 6762 |
|
<t>/ DB_INSTRUMENT_COUNT |
| 6763 |
|
</t> |
| 6764 |
|
<t>/ DB_INSTRUMENT_INFO |
| 6765 |
|
</t> |
| 6766 |
|
<t>/ DB_INSTRUMENTS_JOB_INFO |
| 6767 |
|
</t> |
| 6768 |
<t>/ MISCELLANEOUS |
<t>/ MISCELLANEOUS |
| 6769 |
</t> |
</t> |
| 6770 |
|
<t>/ TOTAL_STREAM_COUNT |
| 6771 |
|
</t> |
| 6772 |
<t>/ TOTAL_VOICE_COUNT |
<t>/ TOTAL_VOICE_COUNT |
| 6773 |
</t> |
</t> |
| 6774 |
|
<t>/ GLOBAL_INFO |
| 6775 |
|
</t> |
| 6776 |
</list> |
</list> |
| 6777 |
</t> |
</t> |
| 6778 |
<t>map_instruction = |
<t>map_instruction = |
| 6779 |
<list> |
<list> |
| 6780 |
<t>MIDI_INSTRUMENT SP midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value |
<t>MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value |
| 6781 |
</t> |
</t> |
| 6782 |
<t>/ MIDI_INSTRUMENT SP midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP instr_load_mode |
<t>/ MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP instr_load_mode |
| 6783 |
</t> |
</t> |
| 6784 |
<t>/ MIDI_INSTRUMENT SP midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP entry_name |
<t>/ MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP entry_name |
| 6785 |
</t> |
</t> |
| 6786 |
<t>/ MIDI_INSTRUMENT SP midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP instr_load_mode SP entry_name |
<t>/ MIDI_INSTRUMENT SP modal_arg midi_map SP midi_bank SP midi_prog SP engine_name SP filename SP instrument_index SP volume_value SP instr_load_mode SP entry_name |
| 6787 |
</t> |
</t> |
| 6788 |
</list> |
</list> |
| 6789 |
</t> |
</t> |
| 6801 |
</t> |
</t> |
| 6802 |
<t>/ MIDI_INSTRUMENT_MAP SP ALL |
<t>/ MIDI_INSTRUMENT_MAP SP ALL |
| 6803 |
</t> |
</t> |
| 6804 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP FORCE SP db_path |
| 6805 |
|
</t> |
| 6806 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP db_path |
| 6807 |
|
</t> |
| 6808 |
|
<t>/ DB_INSTRUMENT SP db_path |
| 6809 |
|
</t> |
| 6810 |
</list> |
</list> |
| 6811 |
</t> |
</t> |
| 6812 |
<t>get_instruction = |
<t>get_instruction = |
| 6859 |
</t> |
</t> |
| 6860 |
<t>/ SERVER SP INFO |
<t>/ SERVER SP INFO |
| 6861 |
</t> |
</t> |
| 6862 |
|
<t>/ TOTAL_STREAM_COUNT |
| 6863 |
|
</t> |
| 6864 |
<t>/ TOTAL_VOICE_COUNT |
<t>/ TOTAL_VOICE_COUNT |
| 6865 |
</t> |
</t> |
| 6866 |
<t>/ TOTAL_VOICE_COUNT_MAX |
<t>/ TOTAL_VOICE_COUNT_MAX |
| 6875 |
</t> |
</t> |
| 6876 |
<t>/ MIDI_INSTRUMENT_MAP SP INFO SP midi_map |
<t>/ MIDI_INSTRUMENT_MAP SP INFO SP midi_map |
| 6877 |
</t> |
</t> |
| 6878 |
|
<t>/ FX_SENDS SP sampler_channel |
| 6879 |
|
</t> |
| 6880 |
|
<t>/ FX_SEND SP INFO SP sampler_channel SP fx_send_id |
| 6881 |
|
</t> |
| 6882 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP RECURSIVE SP db_path |
| 6883 |
|
</t> |
| 6884 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP db_path |
| 6885 |
|
</t> |
| 6886 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP INFO SP db_path |
| 6887 |
|
</t> |
| 6888 |
|
<t>/ DB_INSTRUMENTS SP RECURSIVE SP db_path |
| 6889 |
|
</t> |
| 6890 |
|
<t>/ DB_INSTRUMENTS SP db_path |
| 6891 |
|
</t> |
| 6892 |
|
<t>/ DB_INSTRUMENT SP INFO SP db_path |
| 6893 |
|
</t> |
| 6894 |
|
<t>/ DB_INSTRUMENTS_JOB SP INFO SP number |
| 6895 |
|
</t> |
| 6896 |
|
<t>/ VOLUME |
| 6897 |
|
</t> |
| 6898 |
|
<t>/ VOICES |
| 6899 |
|
</t> |
| 6900 |
|
<t>/ STREAMS |
| 6901 |
|
</t> |
| 6902 |
|
<t>/ FILE SP INSTRUMENTS SP filename |
| 6903 |
|
</t> |
| 6904 |
|
<t>/ FILE SP INSTRUMENT SP INFO SP filename SP instrument_index |
| 6905 |
|
</t> |
| 6906 |
</list> |
</list> |
| 6907 |
</t> |
</t> |
| 6908 |
<t>set_instruction = |
<t>set_instruction = |
| 6913 |
</t> |
</t> |
| 6914 |
<t>/ MIDI_INPUT_DEVICE_PARAMETER SP number SP string '=' param_val_list |
<t>/ MIDI_INPUT_DEVICE_PARAMETER SP number SP string '=' param_val_list |
| 6915 |
</t> |
</t> |
| 6916 |
|
<t>/ MIDI_INPUT_PORT_PARAMETER SP number SP number SP string '=' NONE |
| 6917 |
|
</t> |
| 6918 |
<t>/ MIDI_INPUT_PORT_PARAMETER SP number SP number SP string '=' param_val_list |
<t>/ MIDI_INPUT_PORT_PARAMETER SP number SP number SP string '=' param_val_list |
| 6919 |
</t> |
</t> |
| 6920 |
<t>/ CHANNEL SP set_chan_instruction |
<t>/ CHANNEL SP set_chan_instruction |
| 6921 |
</t> |
</t> |
| 6922 |
<t>/ MIDI_INSTRUMENT_MAP SP NAME SP midi_map SP map_name |
<t>/ MIDI_INSTRUMENT_MAP SP NAME SP midi_map SP map_name |
| 6923 |
</t> |
</t> |
| 6924 |
|
<t>/ FX_SEND SP NAME SP sampler_channel SP fx_send_id SP fx_send_name |
| 6925 |
|
</t> |
| 6926 |
|
<t>/ FX_SEND SP AUDIO_OUTPUT_CHANNEL SP sampler_channel SP fx_send_id SP audio_channel_index SP audio_channel_index |
| 6927 |
|
</t> |
| 6928 |
|
<t>/ FX_SEND SP MIDI_CONTROLLER SP sampler_channel SP fx_send_id SP midi_ctrl |
| 6929 |
|
</t> |
| 6930 |
|
<t>/ FX_SEND SP LEVEL SP sampler_channel SP fx_send_id SP volume_value |
| 6931 |
|
</t> |
| 6932 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP NAME SP db_path SP stringval_escaped |
| 6933 |
|
</t> |
| 6934 |
|
<t>/ DB_INSTRUMENT_DIRECTORY SP DESCRIPTION SP db_path SP stringval_escaped |
| 6935 |
|
</t> |
| 6936 |
|
<t>/ DB_INSTRUMENT SP NAME SP db_path SP stringval_escaped |
| 6937 |
|
</t> |
| 6938 |
|
<t>/ DB_INSTRUMENT SP DESCRIPTION SP db_path SP stringval_escaped |
| 6939 |
|
</t> |
| 6940 |
|
<t>/ DB_INSTRUMENT SP FILE_PATH SP filename SP filename |
| 6941 |
|
</t> |
| 6942 |
<t>/ ECHO SP boolean |
<t>/ ECHO SP boolean |
| 6943 |
</t> |
</t> |
| 6944 |
|
<t>/ VOLUME SP volume_value |
| 6945 |
|
</t> |
| 6946 |
|
<t>/ VOICES SP number |
| 6947 |
|
</t> |
| 6948 |
|
<t>/ STREAMS SP number |
| 6949 |
|
</t> |
| 6950 |
</list> |
</list> |
| 6951 |
</t> |
</t> |
| 6952 |
<t>create_instruction = |
<t>create_instruction = |
| 6959 |
</t> |
</t> |
| 6960 |
<t>/ MIDI_INPUT_DEVICE SP string |
<t>/ MIDI_INPUT_DEVICE SP string |
| 6961 |
</t> |
</t> |
| 6962 |
|
<t>/ FX_SEND SP sampler_channel SP midi_ctrl |
| 6963 |
|
</t> |
| 6964 |
|
<t>/ FX_SEND SP sampler_channel SP midi_ctrl SP fx_send_name |
| 6965 |
|
</t> |
| 6966 |
</list> |
</list> |
| 6967 |
</t> |
</t> |
| 6968 |
<t>reset_instruction = |
<t>reset_instruction = |
| 6979 |
</t> |
</t> |
| 6980 |
</list> |
</list> |
| 6981 |
</t> |
</t> |
| 6982 |
|
<t>find_instruction = |
| 6983 |
|
<list> |
| 6984 |
|
<t>DB_INSTRUMENTS SP NON_RECURSIVE SP db_path SP query_val_list |
| 6985 |
|
</t> |
| 6986 |
|
<t>/ DB_INSTRUMENTS SP db_path SP query_val_list |
| 6987 |
|
</t> |
| 6988 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP NON_RECURSIVE SP db_path SP query_val_list |
| 6989 |
|
</t> |
| 6990 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP db_path SP query_val_list |
| 6991 |
|
</t> |
| 6992 |
|
<t>/ LOST SP DB_INSTRUMENT_FILES |
| 6993 |
|
</t> |
| 6994 |
|
</list> |
| 6995 |
|
</t> |
| 6996 |
|
<t>move_instruction = |
| 6997 |
|
<list> |
| 6998 |
|
<t>DB_INSTRUMENT_DIRECTORY SP db_path SP db_path |
| 6999 |
|
</t> |
| 7000 |
|
<t>/ DB_INSTRUMENT SP db_path SP db_path |
| 7001 |
|
</t> |
| 7002 |
|
</list> |
| 7003 |
|
</t> |
| 7004 |
|
<t>copy_instruction = |
| 7005 |
|
<list> |
| 7006 |
|
<t>DB_INSTRUMENT_DIRECTORY SP db_path SP db_path |
| 7007 |
|
</t> |
| 7008 |
|
<t>/ DB_INSTRUMENT SP db_path SP db_path |
| 7009 |
|
</t> |
| 7010 |
|
</list> |
| 7011 |
|
</t> |
| 7012 |
<t>destroy_instruction = |
<t>destroy_instruction = |
| 7013 |
<list> |
<list> |
| 7014 |
<t>AUDIO_OUTPUT_DEVICE SP number |
<t>AUDIO_OUTPUT_DEVICE SP number |
| 7015 |
</t> |
</t> |
| 7016 |
<t>/ MIDI_INPUT_DEVICE SP number |
<t>/ MIDI_INPUT_DEVICE SP number |
| 7017 |
</t> |
</t> |
| 7018 |
|
<t>/ FX_SEND SP sampler_channel SP fx_send_id |
| 7019 |
|
</t> |
| 7020 |
</list> |
</list> |
| 7021 |
</t> |
</t> |
| 7022 |
<t>load_instruction = |
<t>load_instruction = |
| 7059 |
</t> |
</t> |
| 7060 |
</list> |
</list> |
| 7061 |
</t> |
</t> |
| 7062 |
|
<t>edit_instruction = |
| 7063 |
|
<list> |
| 7064 |
|
<t>CHANNEL SP INSTRUMENT SP sampler_channel |
| 7065 |
|
</t> |
| 7066 |
|
</list> |
| 7067 |
|
</t> |
| 7068 |
|
<t>format_instruction = |
| 7069 |
|
<list> |
| 7070 |
|
<t>INSTRUMENTS_DB |
| 7071 |
|
</t> |
| 7072 |
|
</list> |
| 7073 |
|
</t> |
| 7074 |
|
<t>modal_arg = |
| 7075 |
|
<list> |
| 7076 |
|
<t>/* epsilon (empty argument) */ |
| 7077 |
|
</t> |
| 7078 |
|
<t>/ NON_MODAL SP |
| 7079 |
|
</t> |
| 7080 |
|
</list> |
| 7081 |
|
</t> |
| 7082 |
<t>key_val_list = |
<t>key_val_list = |
| 7083 |
<list> |
<list> |
| 7084 |
<t>string '=' param_val_list |
<t>string '=' param_val_list |
| 7115 |
</t> |
</t> |
| 7116 |
<t>/ MIDI_INSTRUMENT_MAPS |
<t>/ MIDI_INSTRUMENT_MAPS |
| 7117 |
</t> |
</t> |
| 7118 |
|
<t>/ FX_SENDS SP sampler_channel |
| 7119 |
|
</t> |
| 7120 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP RECURSIVE SP db_path |
| 7121 |
|
</t> |
| 7122 |
|
<t>/ DB_INSTRUMENT_DIRECTORIES SP db_path |
| 7123 |
|
</t> |
| 7124 |
|
<t>/ DB_INSTRUMENTS SP RECURSIVE SP db_path |
| 7125 |
|
</t> |
| 7126 |
|
<t>/ DB_INSTRUMENTS SP db_path |
| 7127 |
|
</t> |
| 7128 |
|
<t>/ FILE SP INSTRUMENTS SP filename |
| 7129 |
|
</t> |
| 7130 |
|
</list> |
| 7131 |
|
</t> |
| 7132 |
|
<t>send_instruction = |
| 7133 |
|
<list> |
| 7134 |
|
<t>CHANNEL SP MIDI_DATA SP string SP sampler_channel SP number SP number |
| 7135 |
|
</t> |
| 7136 |
</list> |
</list> |
| 7137 |
</t> |
</t> |
| 7138 |
<t>load_instr_args = |
<t>load_instr_args = |
| 7215 |
</t> |
</t> |
| 7216 |
</list> |
</list> |
| 7217 |
</t> |
</t> |
| 7218 |
|
<t>midi_ctrl = |
| 7219 |
|
<list> |
| 7220 |
|
<t>number |
| 7221 |
|
</t> |
| 7222 |
|
</list> |
| 7223 |
|
</t> |
| 7224 |
<t>volume_value = |
<t>volume_value = |
| 7225 |
<list> |
<list> |
| 7226 |
<t>dotnum |
<t>dotnum |
| 7241 |
</t> |
</t> |
| 7242 |
</list> |
</list> |
| 7243 |
</t> |
</t> |
| 7244 |
|
<t>fx_send_id = |
| 7245 |
|
<list> |
| 7246 |
|
<t>number |
| 7247 |
|
</t> |
| 7248 |
|
</list> |
| 7249 |
|
</t> |
| 7250 |
<t>engine_name = |
<t>engine_name = |
| 7251 |
<list> |
<list> |
| 7252 |
<t>string |
<t>string |
| 7255 |
</t> |
</t> |
| 7256 |
<t>filename = |
<t>filename = |
| 7257 |
<list> |
<list> |
| 7258 |
<t>stringval |
<t>path |
| 7259 |
|
</t> |
| 7260 |
|
</list> |
| 7261 |
|
</t> |
| 7262 |
|
<t>db_path = |
| 7263 |
|
<list> |
| 7264 |
|
<t>path |
| 7265 |
</t> |
</t> |
| 7266 |
</list> |
</list> |
| 7267 |
</t> |
</t> |
| 7268 |
<t>map_name = |
<t>map_name = |
| 7269 |
<list> |
<list> |
| 7270 |
<t>stringval |
<t>stringval_escaped |
| 7271 |
</t> |
</t> |
| 7272 |
</list> |
</list> |
| 7273 |
</t> |
</t> |
| 7274 |
<t>entry_name = |
<t>entry_name = |
| 7275 |
<list> |
<list> |
| 7276 |
<t>stringval |
<t>stringval_escaped |
| 7277 |
|
</t> |
| 7278 |
|
</list> |
| 7279 |
|
</t> |
| 7280 |
|
<t>fx_send_name = |
| 7281 |
|
<list> |
| 7282 |
|
<t>stringval_escaped |
| 7283 |
</t> |
</t> |
| 7284 |
</list> |
</list> |
| 7285 |
</t> |
</t> |
| 7291 |
</t> |
</t> |
| 7292 |
</list> |
</list> |
| 7293 |
</t> |
</t> |
| 7294 |
|
|
| 7295 |
<t>param_val = |
<t>param_val = |
| 7296 |
<list> |
<list> |
| 7297 |
<t>string |
<t>string |
| 7304 |
</t> |
</t> |
| 7305 |
</list> |
</list> |
| 7306 |
</t> |
</t> |
| 7307 |
|
<t>query_val_list = |
| 7308 |
|
<list> |
| 7309 |
|
<t>string '=' query_val |
| 7310 |
|
</t> |
| 7311 |
|
<t>/ query_val_list SP string '=' query_val |
| 7312 |
|
</t> |
| 7313 |
|
</list> |
| 7314 |
|
</t> |
| 7315 |
|
<t>query_val = |
| 7316 |
|
<list> |
| 7317 |
|
<t>text_escaped |
| 7318 |
|
</t> |
| 7319 |
|
<t>/ stringval_escaped |
| 7320 |
|
</t> |
| 7321 |
|
</list> |
| 7322 |
|
</t> |
| 7323 |
|
<t>scan_mode = |
| 7324 |
|
<list> |
| 7325 |
|
<t>RECURSIVE |
| 7326 |
|
</t> |
| 7327 |
|
<t>/ NON_RECURSIVE |
| 7328 |
|
</t> |
| 7329 |
|
<t>/ FLAT |
| 7330 |
|
</t> |
| 7331 |
|
</list> |
| 7332 |
|
</t> |
| 7333 |
|
|
| 7334 |
<!-- GRAMMAR_BNF_END - do NOT delete or modify this line !!! --> |
<!-- GRAMMAR_BNF_END - do NOT delete or modify this line !!! --> |
| 7335 |
|
|
| 7336 |
|
<section title="Character Set and Escape Sequences" anchor="character_set"> |
| 7337 |
|
<t>Older versions of this protocol up to and including v1.1 only |
| 7338 |
|
supported the standard ASCII character set (ASCII code 0 - 127) |
| 7339 |
|
<xref target="RFC20"/>, all younger versions of this protocol |
| 7340 |
|
however support the Extended ASCII character set (ASCII code |
| 7341 |
|
0 - 255). The same group of younger protocols also support |
| 7342 |
|
escape sequences, but only for certain, explicitly declared |
| 7343 |
|
parts of the protocol. The supported escape sequences are |
| 7344 |
|
defined as follows:</t> |
| 7345 |
|
<texttable> |
| 7346 |
|
<ttcol>ASCII Character Sequence</ttcol> |
| 7347 |
|
<ttcol>Translated into (Name)</ttcol> |
| 7348 |
|
<c>\n</c> <c>new line</c> |
| 7349 |
|
<c>\r</c> <c>carriage return</c> |
| 7350 |
|
<c>\f</c> <c>form feed</c> |
| 7351 |
|
<c>\t</c> <c>horizontal tab</c> |
| 7352 |
|
<c>\v</c> <c>vertical tab</c> |
| 7353 |
|
<c>\'</c> <c>apostrophe</c> |
| 7354 |
|
<c>\"</c> <c>quotation mark</c> |
| 7355 |
|
<c>\\</c> <c>backslash</c> |
| 7356 |
|
<c>\OOO</c> <c>three digit octal ASCII code of the character</c> |
| 7357 |
|
<c>\xHH</c> <c>two digit hex ASCII code of the character</c> |
| 7358 |
|
</texttable> |
| 7359 |
|
<t>Notice: due to the transition of certain parts of the |
| 7360 |
|
protocol which now support escape sequences, a slight backward |
| 7361 |
|
incompatibility to protocols version v1.1 and younger has been |
| 7362 |
|
introduced. The only difference is that in parts of the protocol |
| 7363 |
|
where escape characters are now supported, a backslash characters |
| 7364 |
|
MUST be escaped as well (that is as double backslash), whereas |
| 7365 |
|
in the old versions a single backslash was sufficient.</t> |
| 7366 |
|
|
| 7367 |
|
<t>The following LSCP commands support escape sequences as part |
| 7368 |
|
of their filename / path based arguments and / or may contain |
| 7369 |
|
a filename / path with escape sequences in their response: |
| 7370 |
|
<list> |
| 7371 |
|
<t><xref target="LOAD INSTRUMENT">"LOAD INSTRUMENT"</xref></t> |
| 7372 |
|
<t><xref target="GET CHANNEL INFO">"GET CHANNEL INFO"</xref></t> |
| 7373 |
|
<t><xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref></t> |
| 7374 |
|
<t><xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref></t> |
| 7375 |
|
<t><xref target="ADD DB_INSTRUMENT_DIRECTORY">"ADD DB_INSTRUMENT_DIRECTORY"</xref></t> |
| 7376 |
|
<t><xref target="ADD DB_INSTRUMENTS">"ADD DB_INSTRUMENTS"</xref></t> |
| 7377 |
|
<t><xref target="REMOVE DB_INSTRUMENT_DIRECTORY">"REMOVE DB_INSTRUMENT_DIRECTORY"</xref></t> |
| 7378 |
|
<t><xref target="REMOVE DB_INSTRUMENT">"REMOVE DB_INSTRUMENT"</xref></t> |
| 7379 |
|
<t><xref target="GET DB_INSTRUMENT_DIRECTORIES">"GET DB_INSTRUMENT_DIRECTORIES"</xref></t> |
| 7380 |
|
<t><xref target="LIST DB_INSTRUMENT_DIRECTORIES">"LIST DB_INSTRUMENT_DIRECTORIES"</xref></t> |
| 7381 |
|
<t><xref target="GET DB_INSTRUMENT_DIRECTORY INFO">"GET DB_INSTRUMENT_DIRECTORY INFO"</xref></t> |
| 7382 |
|
<t><xref target="GET DB_INSTRUMENTS">"GET DB_INSTRUMENTS"</xref></t> |
| 7383 |
|
<t><xref target="LIST DB_INSTRUMENTS">"LIST DB_INSTRUMENTS"</xref></t> |
| 7384 |
|
<t><xref target="GET DB_INSTRUMENT INFO">"GET DB_INSTRUMENT INFO"</xref></t> |
| 7385 |
|
<t><xref target="SET DB_INSTRUMENT_DIRECTORY NAME">"SET DB_INSTRUMENT_DIRECTORY NAME"</xref></t> |
| 7386 |
|
<t><xref target="SET DB_INSTRUMENT_DIRECTORY DESCRIPTION">"SET DB_INSTRUMENT_DIRECTORY DESCRIPTION"</xref></t> |
| 7387 |
|
<t><xref target="SET DB_INSTRUMENT NAME">"SET DB_INSTRUMENT NAME"</xref></t> |
| 7388 |
|
<t><xref target="SET DB_INSTRUMENT DESCRIPTION">"SET DB_INSTRUMENT DESCRIPTION"</xref></t> |
| 7389 |
|
<t><xref target="FIND DB_INSTRUMENTS">"FIND DB_INSTRUMENTS"</xref></t> |
| 7390 |
|
<t><xref target="FIND DB_INSTRUMENT_DIRECTORIES">"FIND DB_INSTRUMENT_DIRECTORIES"</xref></t> |
| 7391 |
|
<t><xref target="MOVE DB_INSTRUMENT">"MOVE DB_INSTRUMENT"</xref></t> |
| 7392 |
|
<t><xref target="MOVE DB_INSTRUMENT_DIRECTORY">"MOVE DB_INSTRUMENT_DIRECTORY"</xref></t> |
| 7393 |
|
<t><xref target="COPY DB_INSTRUMENT">"COPY DB_INSTRUMENT"</xref></t> |
| 7394 |
|
<t><xref target="COPY DB_INSTRUMENT_DIRECTORY">"COPY DB_INSTRUMENT_DIRECTORY"</xref></t> |
| 7395 |
|
<t><xref target="FIND LOST DB_INSTRUMENT_FILES">"FIND LOST DB_INSTRUMENT_FILES"</xref></t> |
| 7396 |
|
<t><xref target="SET DB_INSTRUMENT FILE_PATH">"SET DB_INSTRUMENT FILE_PATH"</xref></t> |
| 7397 |
|
<t><xref target="GET FILE INSTRUMENTS">"GET FILE INSTRUMENTS"</xref></t> |
| 7398 |
|
<t><xref target="LIST FILE INSTRUMENTS">"LIST FILE INSTRUMENTS"</xref></t> |
| 7399 |
|
<t><xref target="GET FILE INSTRUMENT INFO">"GET FILE INSTRUMENT INFO"</xref></t> |
| 7400 |
|
</list> |
| 7401 |
|
Note that the forward slash character ('/') has a special meaning in |
| 7402 |
|
filename / path based arguments: it acts as separator of the nodes in |
| 7403 |
|
the path, thus if a directory- or filename includes a forward slash |
| 7404 |
|
(not intended as path node separator), you MUST escape that slash |
| 7405 |
|
either with the respective hex escape sequence ("\x2f") or with the |
| 7406 |
|
respective octal escape sequence ("\057"). |
| 7407 |
|
</t> |
| 7408 |
|
|
| 7409 |
|
<t> |
| 7410 |
|
Note for Windows: file path arguments in LSCP are expected |
| 7411 |
|
to use forward slashes as directory node separator similar |
| 7412 |
|
to Unix based operating systems. In contrast to Unix however |
| 7413 |
|
a Windows typical drive character is expected to be |
| 7414 |
|
prefixed to the path. That is an original Windows file path |
| 7415 |
|
like "D:\Sounds\My.gig" would become in LSCP: |
| 7416 |
|
"D:/Sounds/My.gig". |
| 7417 |
|
</t> |
| 7418 |
|
|
| 7419 |
|
<t> |
| 7420 |
|
The following LSCP commands even support escape sequences as |
| 7421 |
|
part of at least one of their text-based arguments (i.e. entity name, |
| 7422 |
|
description) and / or may contain escape sequences in at least one of |
| 7423 |
|
their text-based fields in their response: |
| 7424 |
|
<list> |
| 7425 |
|
<t><xref target="GET SERVER INFO">"GET SERVER INFO"</xref></t> |
| 7426 |
|
<t><xref target="GET ENGINE INFO">"GET ENGINE INFO"</xref></t> |
| 7427 |
|
<t><xref target="GET CHANNEL INFO">"GET CHANNEL INFO"</xref></t> |
| 7428 |
|
<t><xref target="CREATE FX_SEND">"CREATE FX_SEND"</xref></t> |
| 7429 |
|
<t><xref target="GET FX_SEND INFO">"GET FX_SEND INFO"</xref></t> |
| 7430 |
|
<t><xref target="SET FX_SEND NAME">"SET FX_SEND NAME"</xref></t> |
| 7431 |
|
<t><xref target="GET MIDI_INSTRUMENT INFO">"GET MIDI_INSTRUMENT INFO"</xref></t> |
| 7432 |
|
<t><xref target="GET MIDI_INSTRUMENT_MAP INFO">"GET MIDI_INSTRUMENT_MAP INFO"</xref></t> |
| 7433 |
|
<t><xref target="ADD MIDI_INSTRUMENT_MAP">"ADD MIDI_INSTRUMENT_MAP"</xref></t> |
| 7434 |
|
<t><xref target="MAP MIDI_INSTRUMENT">"MAP MIDI_INSTRUMENT"</xref></t> |
| 7435 |
|
<t><xref target="SET MIDI_INSTRUMENT_MAP NAME">"SET MIDI_INSTRUMENT_MAP NAME"</xref></t> |
| 7436 |
|
<t><xref target="GET DB_INSTRUMENT_DIRECTORY INFO">"GET DB_INSTRUMENT_DIRECTORY INFO"</xref></t> |
| 7437 |
|
<t><xref target="SET DB_INSTRUMENT_DIRECTORY NAME">"SET DB_INSTRUMENT_DIRECTORY NAME"</xref></t> |
| 7438 |
|
<t><xref target="SET DB_INSTRUMENT_DIRECTORY DESCRIPTION">"SET DB_INSTRUMENT_DIRECTORY DESCRIPTION"</xref></t> |
| 7439 |
|
<t><xref target="FIND DB_INSTRUMENT_DIRECTORIES">"FIND DB_INSTRUMENT_DIRECTORIES"</xref></t> |
| 7440 |
|
<t><xref target="GET DB_INSTRUMENT INFO">"GET DB_INSTRUMENT INFO"</xref></t> |
| 7441 |
|
<t><xref target="SET DB_INSTRUMENT NAME">"SET DB_INSTRUMENT NAME"</xref></t> |
| 7442 |
|
<t><xref target="SET DB_INSTRUMENT DESCRIPTION">"SET DB_INSTRUMENT DESCRIPTION"</xref></t> |
| 7443 |
|
<t><xref target="FIND DB_INSTRUMENTS">"FIND DB_INSTRUMENTS"</xref></t> |
| 7444 |
|
</list> |
| 7445 |
|
Please note that these lists are manually maintained. If you |
| 7446 |
|
find a command that also supports escape sequences we forgot to |
| 7447 |
|
mention here, please report it! |
| 7448 |
|
</t> |
| 7449 |
|
</section> |
| 7450 |
</section> |
</section> |
| 7451 |
|
|
| 7452 |
<section title="Events" anchor="events"> |
<section title="Events" anchor="events"> |
| 7453 |
<t>This chapter will describe all currently defined events supported by LinuxSampler.</t> |
<t>This chapter will describe all currently defined events supported by LinuxSampler.</t> |
| 7454 |
|
|
| 7455 |
<section title="Number of sampler channels changed" anchor="SUBSCRIBE CHANNEL"> |
<section title="Number of audio output devices changed" anchor="SUBSCRIBE AUDIO_OUTPUT_DEVICE_COUNT"> |
| 7456 |
|
<t>Client may want to be notified when the total number of audio output devices on the |
| 7457 |
|
back-end changes by issuing the following command:</t> |
| 7458 |
|
<t> |
| 7459 |
|
<list> |
| 7460 |
|
<t>SUBSCRIBE AUDIO_OUTPUT_DEVICE_COUNT</t> |
| 7461 |
|
</list> |
| 7462 |
|
</t> |
| 7463 |
|
<t>Server will start sending the following notification messages:</t> |
| 7464 |
|
<t> |
| 7465 |
|
<list> |
| 7466 |
|
<t>"NOTIFY:AUDIO_OUTPUT_DEVICE_COUNT:<devices>"</t> |
| 7467 |
|
</list> |
| 7468 |
|
</t> |
| 7469 |
|
<t>where <devices> will be replaced by the new number |
| 7470 |
|
of audio output devices.</t> |
| 7471 |
|
</section> |
| 7472 |
|
|
| 7473 |
|
<section title="Audio output device's settings changed" anchor="SUBSCRIBE AUDIO_OUTPUT_DEVICE_INFO"> |
| 7474 |
|
<t>Client may want to be notified when changes were made to audio output devices on the |
| 7475 |
|
back-end by issuing the following command:</t> |
| 7476 |
|
<t> |
| 7477 |
|
<list> |
| 7478 |
|
<t>SUBSCRIBE AUDIO_OUTPUT_DEVICE_INFO</t> |
| 7479 |
|
</list> |
| 7480 |
|
</t> |
| 7481 |
|
<t>Server will start sending the following notification messages:</t> |
| 7482 |
|
<t> |
| 7483 |
|
<list> |
| 7484 |
|
<t>"NOTIFY:AUDIO_OUTPUT_DEVICE_INFO:<device-id>"</t> |
| 7485 |
|
</list> |
| 7486 |
|
</t> |
| 7487 |
|
<t>where <device-id> will be replaced by the numerical ID of the audio output device, |
| 7488 |
|
which settings has been changed. The front-end will have to send |
| 7489 |
|
the respective command to actually get the audio output device info. Because these messages |
| 7490 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 7491 |
|
time events happening on the server, it is believed that an empty notification |
| 7492 |
|
message is sufficient here.</t> |
| 7493 |
|
</section> |
| 7494 |
|
|
| 7495 |
|
<section title="Number of MIDI input devices changed" anchor="SUBSCRIBE MIDI_INPUT_DEVICE_COUNT"> |
| 7496 |
|
<t>Client may want to be notified when the total number of MIDI input devices on the |
| 7497 |
|
back-end changes by issuing the following command:</t> |
| 7498 |
|
<t> |
| 7499 |
|
<list> |
| 7500 |
|
<t>SUBSCRIBE MIDI_INPUT_DEVICE_COUNT</t> |
| 7501 |
|
</list> |
| 7502 |
|
</t> |
| 7503 |
|
<t>Server will start sending the following notification messages:</t> |
| 7504 |
|
<t> |
| 7505 |
|
<list> |
| 7506 |
|
<t>"NOTIFY:MIDI_INPUT_DEVICE_COUNT:<devices>"</t> |
| 7507 |
|
</list> |
| 7508 |
|
</t> |
| 7509 |
|
<t>where <devices> will be replaced by the new number |
| 7510 |
|
of MIDI input devices.</t> |
| 7511 |
|
</section> |
| 7512 |
|
|
| 7513 |
|
<section title="MIDI input device's settings changed" anchor="SUBSCRIBE MIDI_INPUT_DEVICE_INFO"> |
| 7514 |
|
<t>Client may want to be notified when changes were made to MIDI input devices on the |
| 7515 |
|
back-end by issuing the following command:</t> |
| 7516 |
|
<t> |
| 7517 |
|
<list> |
| 7518 |
|
<t>SUBSCRIBE MIDI_INPUT_DEVICE_INFO</t> |
| 7519 |
|
</list> |
| 7520 |
|
</t> |
| 7521 |
|
<t>Server will start sending the following notification messages:</t> |
| 7522 |
|
<t> |
| 7523 |
|
<list> |
| 7524 |
|
<t>"NOTIFY:MIDI_INPUT_DEVICE_INFO:<device-id>"</t> |
| 7525 |
|
</list> |
| 7526 |
|
</t> |
| 7527 |
|
<t>where <device-id> will be replaced by the numerical ID of the MIDI input device, |
| 7528 |
|
which settings has been changed. The front-end will have to send |
| 7529 |
|
the respective command to actually get the MIDI input device info. Because these messages |
| 7530 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 7531 |
|
time events happening on the server, it is believed that an empty notification |
| 7532 |
|
message is sufficient here.</t> |
| 7533 |
|
</section> |
| 7534 |
|
|
| 7535 |
|
<section title="Number of sampler channels changed" anchor="SUBSCRIBE CHANNEL_COUNT"> |
| 7536 |
<t>Client may want to be notified when the total number of channels on the |
<t>Client may want to be notified when the total number of channels on the |
| 7537 |
back-end changes by issuing the following command:</t> |
back-end changes by issuing the following command:</t> |
| 7538 |
<t> |
<t> |
| 7550 |
of sampler channels.</t> |
of sampler channels.</t> |
| 7551 |
</section> |
</section> |
| 7552 |
|
|
| 7553 |
|
<section title="MIDI data on a sampler channel arrived" anchor="SUBSCRIBE CHANNEL_MIDI"> |
| 7554 |
|
<t>Client may want to be notified when MIDI data arrive on sampler channels on |
| 7555 |
|
back-end side, by issuing the following command:</t> |
| 7556 |
|
<t> |
| 7557 |
|
<list> |
| 7558 |
|
<t>SUBSCRIBE CHANNEL_MIDI</t> |
| 7559 |
|
</list> |
| 7560 |
|
</t> |
| 7561 |
|
<t>Server will start sending one of the the following notification messages:</t> |
| 7562 |
|
<t> |
| 7563 |
|
<list> |
| 7564 |
|
<t>"NOTIFY:CHANNEL_MIDI:<channel-id> NOTE_ON <note> <velocity>"</t> |
| 7565 |
|
<t>"NOTIFY:CHANNEL_MIDI:<channel-id> NOTE_OFF <note> <velocity>"</t> |
| 7566 |
|
</list> |
| 7567 |
|
</t> |
| 7568 |
|
<t>where <channel-id> will be replaced by the ID of the sampler channel where the MIDI |
| 7569 |
|
data arrived. <note> and <velocity> are integer values in the range between |
| 7570 |
|
0 .. 127, reflecting the analog meaning of the MIDI specification. |
| 7571 |
|
</t> |
| 7572 |
|
<t>CAUTION: no guarantee whatsoever will be made that MIDI events are actually all |
| 7573 |
|
delivered by this mechanism! With other words: events could be lost at any time! |
| 7574 |
|
This restriction was made to keep the RT-safeness of the backend's MIDI and audio |
| 7575 |
|
thread unaffected by this feature.</t> |
| 7576 |
|
</section> |
| 7577 |
|
|
| 7578 |
|
<section title="MIDI data on a MIDI input device arrived" anchor="SUBSCRIBE DEVICE_MIDI"> |
| 7579 |
|
<t>Client may want to be notified when MIDI data arrive on MIDI input devices by issuing the following command:</t> |
| 7580 |
|
<t> |
| 7581 |
|
<list> |
| 7582 |
|
<t>SUBSCRIBE DEVICE_MIDI</t> |
| 7583 |
|
</list> |
| 7584 |
|
</t> |
| 7585 |
|
<t>Server will start sending one of the the following notification messages:</t> |
| 7586 |
|
<t> |
| 7587 |
|
<list> |
| 7588 |
|
<t>"NOTIFY:DEVICE_MIDI:<device-id> <port-id> NOTE_ON <note> <velocity>"</t> |
| 7589 |
|
<t>"NOTIFY:DEVICE_MIDI:<device-id> <port-id> NOTE_OFF <note> <velocity>"</t> |
| 7590 |
|
</list> |
| 7591 |
|
</t> |
| 7592 |
|
<t>where <device-id> <port-id> will be replaced |
| 7593 |
|
by the IDs of the respective MIDI input device and the device's MIDI port where the MIDI |
| 7594 |
|
data arrived. <note> and <velocity> are integer values in the range between |
| 7595 |
|
0 .. 127, reflecting the analog meaning of the MIDI specification. |
| 7596 |
|
</t> |
| 7597 |
|
<t>CAUTION: no guarantee whatsoever will be made that MIDI events are actually all |
| 7598 |
|
delivered by this mechanism! With other words: events could be lost at any time! |
| 7599 |
|
This restriction was made to keep the RT-safeness of the backend's MIDI and audio |
| 7600 |
|
thread unaffected by this feature.</t> |
| 7601 |
|
</section> |
| 7602 |
|
|
| 7603 |
<section title="Number of active voices changed" anchor="SUBSCRIBE VOICE_COUNT"> |
<section title="Number of active voices changed" anchor="SUBSCRIBE VOICE_COUNT"> |
| 7604 |
<t>Client may want to be notified when the number of voices on the |
<t>Client may want to be notified when the number of voices on the |
| 7605 |
back-end changes by issuing the following command:</t> |
back-end changes by issuing the following command:</t> |
| 7611 |
<t>Server will start sending the following notification messages:</t> |
<t>Server will start sending the following notification messages:</t> |
| 7612 |
<t> |
<t> |
| 7613 |
<list> |
<list> |
| 7614 |
<t>"NOTIFY:VOICE_COUNT:<sampler-channel> <voices></t> |
<t>"NOTIFY:VOICE_COUNT:<sampler-channel> <voices>"</t> |
| 7615 |
</list> |
</list> |
| 7616 |
</t> |
</t> |
| 7617 |
<t>where <sampler-channel> will be replaced by the sampler channel the |
<t>where <sampler-channel> will be replaced by the sampler channel the |
| 7659 |
"GET CHANNEL BUFFER_FILL PERCENTAGE"</xref> command was issued on this channel.</t> |
"GET CHANNEL BUFFER_FILL PERCENTAGE"</xref> command was issued on this channel.</t> |
| 7660 |
</section> |
</section> |
| 7661 |
|
|
| 7662 |
<section title="Channel information changed" anchor="SUBSCRIBE INFO"> |
<section title="Channel information changed" anchor="SUBSCRIBE CHANNEL_INFO"> |
| 7663 |
<t>Client may want to be notified when changes were made to sampler channels on the |
<t>Client may want to be notified when changes were made to sampler channels on the |
| 7664 |
back-end by issuing the following command:</t> |
back-end by issuing the following command:</t> |
| 7665 |
<t> |
<t> |
| 7681 |
message is sufficient here.</t> |
message is sufficient here.</t> |
| 7682 |
</section> |
</section> |
| 7683 |
|
|
| 7684 |
|
<section title="Number of effect sends changed" anchor="SUBSCRIBE FX_SEND_COUNT"> |
| 7685 |
|
<t>Client may want to be notified when the number of effect sends on |
| 7686 |
|
a particular sampler channel is changed by issuing the following command:</t> |
| 7687 |
|
<t> |
| 7688 |
|
<list> |
| 7689 |
|
<t>SUBSCRIBE FX_SEND_COUNT</t> |
| 7690 |
|
</list> |
| 7691 |
|
</t> |
| 7692 |
|
<t>Server will start sending the following notification messages:</t> |
| 7693 |
|
<t> |
| 7694 |
|
<list> |
| 7695 |
|
<t>"NOTIFY:FX_SEND_COUNT:<channel-id> <fx-sends>"</t> |
| 7696 |
|
</list> |
| 7697 |
|
</t> |
| 7698 |
|
<t>where <channel-id> will be replaced by the numerical ID of the sampler |
| 7699 |
|
channel, on which the effect sends number is changed and <fx-sends> will |
| 7700 |
|
be replaced by the new number of effect sends on that channel.</t> |
| 7701 |
|
</section> |
| 7702 |
|
|
| 7703 |
|
<section title="Effect send information changed" anchor="SUBSCRIBE FX_SEND_INFO"> |
| 7704 |
|
<t>Client may want to be notified when changes were made to effect sends on a |
| 7705 |
|
a particular sampler channel by issuing the following command:</t> |
| 7706 |
|
<t> |
| 7707 |
|
<list> |
| 7708 |
|
<t>SUBSCRIBE FX_SEND_INFO</t> |
| 7709 |
|
</list> |
| 7710 |
|
</t> |
| 7711 |
|
<t>Server will start sending the following notification messages:</t> |
| 7712 |
|
<t> |
| 7713 |
|
<list> |
| 7714 |
|
<t>"NOTIFY:FX_SEND_INFO:<channel-id> <fx-send-id>"</t> |
| 7715 |
|
</list> |
| 7716 |
|
</t> |
| 7717 |
|
<t>where <channel-id> will be replaced by the numerical ID of the sampler |
| 7718 |
|
channel, on which an effect send entity is changed and <fx-send-id> will |
| 7719 |
|
be replaced by the numerical ID of the changed effect send.</t> |
| 7720 |
|
</section> |
| 7721 |
|
|
| 7722 |
<section title="Total number of active voices changed" anchor="SUBSCRIBE TOTAL_VOICE_COUNT"> |
<section title="Total number of active voices changed" anchor="SUBSCRIBE TOTAL_VOICE_COUNT"> |
| 7723 |
<t>Client may want to be notified when the total number of voices on the |
<t>Client may want to be notified when the total number of voices on the |
| 7724 |
back-end changes by issuing the following command:</t> |
back-end changes by issuing the following command:</t> |
| 7730 |
<t>Server will start sending the following notification messages:</t> |
<t>Server will start sending the following notification messages:</t> |
| 7731 |
<t> |
<t> |
| 7732 |
<list> |
<list> |
| 7733 |
<t>"NOTIFY:TOTAL_VOICE_COUNT:<voices></t> |
<t>"NOTIFY:TOTAL_VOICE_COUNT:<voices>"</t> |
| 7734 |
</list> |
</list> |
| 7735 |
</t> |
</t> |
| 7736 |
<t>where <voices> will be replaced by the new number of |
<t>where <voices> will be replaced by the new number of |
| 7737 |
all currently active voices.</t> |
all currently active voices.</t> |
| 7738 |
</section> |
</section> |
| 7739 |
|
|
| 7740 |
|
<section title="Total number of active disk streams changed" anchor="SUBSCRIBE TOTAL_STREAM_COUNT"> |
| 7741 |
|
<t>Client may want to be notified when the total number of disk streams on the |
| 7742 |
|
back-end changes by issuing the following command:</t> |
| 7743 |
|
<t> |
| 7744 |
|
<list> |
| 7745 |
|
<t>SUBSCRIBE TOTAL_STREAM_COUNT</t> |
| 7746 |
|
</list> |
| 7747 |
|
</t> |
| 7748 |
|
<t>Server will start sending the following notification messages:</t> |
| 7749 |
|
<t> |
| 7750 |
|
<list> |
| 7751 |
|
<t>"NOTIFY:TOTAL_STREAM_COUNT:<streams>"</t> |
| 7752 |
|
</list> |
| 7753 |
|
</t> |
| 7754 |
|
<t>where <streams> will be replaced by the new number of |
| 7755 |
|
all currently active disk streams.</t> |
| 7756 |
|
</section> |
| 7757 |
|
|
| 7758 |
|
<section title="Number of MIDI instrument maps changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_MAP_COUNT"> |
| 7759 |
|
<t>Client may want to be notified when the number of MIDI instrument maps on the |
| 7760 |
|
back-end changes by issuing the following command:</t> |
| 7761 |
|
<t> |
| 7762 |
|
<list> |
| 7763 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_MAP_COUNT</t> |
| 7764 |
|
</list> |
| 7765 |
|
</t> |
| 7766 |
|
<t>Server will start sending the following notification messages:</t> |
| 7767 |
|
<t> |
| 7768 |
|
<list> |
| 7769 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_MAP_COUNT:<maps>"</t> |
| 7770 |
|
</list> |
| 7771 |
|
</t> |
| 7772 |
|
<t>where <maps> will be replaced by the new number |
| 7773 |
|
of MIDI instrument maps.</t> |
| 7774 |
|
</section> |
| 7775 |
|
|
| 7776 |
|
<section title="MIDI instrument map information changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO"> |
| 7777 |
|
<t>Client may want to be notified when changes were made to MIDI instrument maps on the |
| 7778 |
|
back-end by issuing the following command:</t> |
| 7779 |
|
<t> |
| 7780 |
|
<list> |
| 7781 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_MAP_INFO</t> |
| 7782 |
|
</list> |
| 7783 |
|
</t> |
| 7784 |
|
<t>Server will start sending the following notification messages:</t> |
| 7785 |
|
<t> |
| 7786 |
|
<list> |
| 7787 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_MAP_INFO:<map-id>"</t> |
| 7788 |
|
</list> |
| 7789 |
|
</t> |
| 7790 |
|
<t>where <map-id> will be replaced by the numerical ID of the MIDI instrument map, |
| 7791 |
|
for which information changes occurred. The front-end will have to send |
| 7792 |
|
the respective command to actually get the MIDI instrument map info. Because these messages |
| 7793 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 7794 |
|
time events happening on the server, it is believed that an empty notification |
| 7795 |
|
message is sufficient here.</t> |
| 7796 |
|
</section> |
| 7797 |
|
|
| 7798 |
|
<section title="Number of MIDI instruments changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_COUNT"> |
| 7799 |
|
<t>Client may want to be notified when the number of MIDI instrument maps on the |
| 7800 |
|
back-end changes by issuing the following command:</t> |
| 7801 |
|
<t> |
| 7802 |
|
<list> |
| 7803 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_COUNT</t> |
| 7804 |
|
</list> |
| 7805 |
|
</t> |
| 7806 |
|
<t>Server will start sending the following notification messages:</t> |
| 7807 |
|
<t> |
| 7808 |
|
<list> |
| 7809 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_COUNT:<map-id> <instruments>"</t> |
| 7810 |
|
</list> |
| 7811 |
|
</t> |
| 7812 |
|
<t>where <map-id> is the numerical ID of the MIDI instrument map, in which |
| 7813 |
|
the nuber of instruments has changed and <instruments> will be replaced by |
| 7814 |
|
the new number of MIDI instruments in the specified map.</t> |
| 7815 |
|
</section> |
| 7816 |
|
|
| 7817 |
|
<section title="MIDI instrument information changed" anchor="SUBSCRIBE MIDI_INSTRUMENT_INFO"> |
| 7818 |
|
<t>Client may want to be notified when changes were made to MIDI instruments on the |
| 7819 |
|
back-end by issuing the following command:</t> |
| 7820 |
|
<t> |
| 7821 |
|
<list> |
| 7822 |
|
<t>SUBSCRIBE MIDI_INSTRUMENT_INFO</t> |
| 7823 |
|
</list> |
| 7824 |
|
</t> |
| 7825 |
|
<t>Server will start sending the following notification messages:</t> |
| 7826 |
|
<t> |
| 7827 |
|
<list> |
| 7828 |
|
<t>"NOTIFY:MIDI_INSTRUMENT_INFO:<map-id> <bank> <program>"</t> |
| 7829 |
|
</list> |
| 7830 |
|
</t> |
| 7831 |
|
<t>where <map-id> will be replaced by the numerical ID of the MIDI instrument map, |
| 7832 |
|
in which a MIDI instrument is changed. <bank> and <program> specifies |
| 7833 |
|
the location of the changed MIDI instrument in the map. The front-end will have to send |
| 7834 |
|
the respective command to actually get the MIDI instrument info. Because these messages |
| 7835 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 7836 |
|
time events happening on the server, it is believed that an empty notification |
| 7837 |
|
message is sufficient here.</t> |
| 7838 |
|
</section> |
| 7839 |
|
|
| 7840 |
|
<section title="Global settings changed" anchor="SUBSCRIBE GLOBAL_INFO"> |
| 7841 |
|
<t>Client may want to be notified when changes to the global settings |
| 7842 |
|
of the sampler were made by issuing the following command:</t> |
| 7843 |
|
<t> |
| 7844 |
|
<list> |
| 7845 |
|
<t>SUBSCRIBE GLOBAL_INFO</t> |
| 7846 |
|
</list> |
| 7847 |
|
</t> |
| 7848 |
|
<t>Server will start sending the following types of notification messages:</t> |
| 7849 |
|
<t> |
| 7850 |
|
<list> |
| 7851 |
|
<t>"NOTIFY:GLOBAL_INFO:VOLUME <volume>" - Notifies that the |
| 7852 |
|
golbal volume of the sampler is changed, where <volume> will be |
| 7853 |
|
replaced by the optional dotted floating point value, reflecting the |
| 7854 |
|
new global volume parameter.</t> |
| 7855 |
|
</list> |
| 7856 |
|
<list> |
| 7857 |
|
<t>"NOTIFY:GLOBAL_INFO:VOICES <max-voices>" - Notifies that the |
| 7858 |
|
golbal limit of the sampler for maximum voices is changed, where |
| 7859 |
|
<max-voices> will be an integer value, reflecting the |
| 7860 |
|
new global voice limit parameter.</t> |
| 7861 |
|
</list> |
| 7862 |
|
<list> |
| 7863 |
|
<t>"NOTIFY:GLOBAL_INFO:STREAMS <max-streams>" - Notifies that the |
| 7864 |
|
golbal limit of the sampler for maximum disk streams is changed, where |
| 7865 |
|
<max-streams> will be an integer value, reflecting the |
| 7866 |
|
new global disk streams limit parameter.</t> |
| 7867 |
|
</list> |
| 7868 |
|
</t> |
| 7869 |
|
</section> |
| 7870 |
|
|
| 7871 |
|
<section title="Number of database instrument directories changed" anchor="SUBSCRIBE DB_INSTRUMENT_DIRECTORY_COUNT"> |
| 7872 |
|
<t>Client may want to be notified when the number of instrument |
| 7873 |
|
directories in a particular directory in the instruments database |
| 7874 |
|
is changed by issuing the following command:</t> |
| 7875 |
|
<t> |
| 7876 |
|
<list> |
| 7877 |
|
<t>SUBSCRIBE DB_INSTRUMENT_DIRECTORY_COUNT</t> |
| 7878 |
|
</list> |
| 7879 |
|
</t> |
| 7880 |
|
<t>Server will start sending the following notification messages:</t> |
| 7881 |
|
<t> |
| 7882 |
|
<list> |
| 7883 |
|
<t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_COUNT:<dir-path>"</t> |
| 7884 |
|
</list> |
| 7885 |
|
</t> |
| 7886 |
|
<t>where <dir-path> will be replaced by the absolute path |
| 7887 |
|
name of the directory in the instruments database, |
| 7888 |
|
in which the number of directories is changed.</t> |
| 7889 |
|
<t>Note that when a non-empty directory is removed, this event |
| 7890 |
|
is not sent for the subdirectories in that directory.</t> |
| 7891 |
|
</section> |
| 7892 |
|
|
| 7893 |
|
<section title="Database instrument directory information changed" anchor="SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO"> |
| 7894 |
|
<t>Client may want to be notified when changes were made to directories |
| 7895 |
|
in the instruments database by issuing the following command:</t> |
| 7896 |
|
<t> |
| 7897 |
|
<list> |
| 7898 |
|
<t>SUBSCRIBE DB_INSTRUMENT_DIRECTORY_INFO</t> |
| 7899 |
|
</list> |
| 7900 |
|
</t> |
| 7901 |
|
<t>Server will start sending the following notification messages:</t> |
| 7902 |
|
<t> |
| 7903 |
|
<list> |
| 7904 |
|
<t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_INFO:<dir-path>"</t> |
| 7905 |
|
</list> |
| 7906 |
|
</t> |
| 7907 |
|
<t>where <dir-path> will be replaced by the absolute path name |
| 7908 |
|
of the directory, for which information changes occurred. The front-end will have to send |
| 7909 |
|
the respective command to actually get the updated directory info. Because these messages |
| 7910 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 7911 |
|
time events happening on the server, it is believed that an empty notification |
| 7912 |
|
message is sufficient here.</t> |
| 7913 |
|
<t> |
| 7914 |
|
<list> |
| 7915 |
|
<t>"NOTIFY:DB_INSTRUMENT_DIRECTORY_INFO:NAME <old-dir-path> <new-name>"</t> |
| 7916 |
|
</list> |
| 7917 |
|
</t> |
| 7918 |
|
<t>where <old-dir-path> is the old absolute path name of the directory |
| 7919 |
|
(encapsulated into apostrophes), which name is changes and <new-name> is |
| 7920 |
|
the new name of the directory, encapsulated into apostrophes.</t> |
| 7921 |
|
</section> |
| 7922 |
|
|
| 7923 |
|
<section title="Number of database instruments changed" anchor="SUBSCRIBE DB_INSTRUMENT_COUNT"> |
| 7924 |
|
<t>Client may want to be notified when the number of instruments |
| 7925 |
|
in a particular directory in the instruments database |
| 7926 |
|
is changed by issuing the following command:</t> |
| 7927 |
|
<t> |
| 7928 |
|
<list> |
| 7929 |
|
<t>SUBSCRIBE DB_INSTRUMENT_COUNT</t> |
| 7930 |
|
</list> |
| 7931 |
|
</t> |
| 7932 |
|
<t>Server will start sending the following notification messages:</t> |
| 7933 |
|
<t> |
| 7934 |
|
<list> |
| 7935 |
|
<t>"NOTIFY:DB_INSTRUMENT_COUNT:<dir-path>"</t> |
| 7936 |
|
</list> |
| 7937 |
|
</t> |
| 7938 |
|
<t>where <dir-path> will be replaced by the absolute path |
| 7939 |
|
name of the directory in the instruments database, |
| 7940 |
|
in which the number of instruments is changed.</t> |
| 7941 |
|
<t>Note that when a non-empty directory is removed, this event |
| 7942 |
|
is not sent for the instruments in that directory.</t> |
| 7943 |
|
</section> |
| 7944 |
|
|
| 7945 |
|
<section title="Database instrument information changed" anchor="SUBSCRIBE DB_INSTRUMENT_INFO"> |
| 7946 |
|
<t>Client may want to be notified when changes were made to instruments |
| 7947 |
|
in the instruments database by issuing the following command:</t> |
| 7948 |
|
<t> |
| 7949 |
|
<list> |
| 7950 |
|
<t>SUBSCRIBE DB_INSTRUMENT_INFO</t> |
| 7951 |
|
</list> |
| 7952 |
|
</t> |
| 7953 |
|
<t>Server will start sending the following notification messages:</t> |
| 7954 |
|
<t> |
| 7955 |
|
<list> |
| 7956 |
|
<t>"NOTIFY:DB_INSTRUMENT_INFO:<instr-path>"</t> |
| 7957 |
|
</list> |
| 7958 |
|
</t> |
| 7959 |
|
<t>where <instr-path> will be replaced by the absolute path name |
| 7960 |
|
of the instrument, which settings are changed. The front-end will have to send |
| 7961 |
|
the respective command to actually get the updated directory info. Because these messages |
| 7962 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 7963 |
|
time events happening on the server, it is believed that an empty notification |
| 7964 |
|
message is sufficient here.</t> |
| 7965 |
|
<t> |
| 7966 |
|
<list> |
| 7967 |
|
<t>"NOTIFY:DB_INSTRUMENT_INFO:NAME <old-instr-path> <new-name>"</t> |
| 7968 |
|
</list> |
| 7969 |
|
</t> |
| 7970 |
|
<t>where <old-instr-path> is the old absolute path name of the instrument |
| 7971 |
|
(encapsulated into apostrophes), which name is changes and <new-name> is |
| 7972 |
|
the new name of the instrument, encapsulated into apostrophes.</t> |
| 7973 |
|
</section> |
| 7974 |
|
|
| 7975 |
|
<section title="Database job status information changed" anchor="SUBSCRIBE DB_INSTRUMENTS_JOB_INFO"> |
| 7976 |
|
<t>Client may want to be notified when the status of particular database |
| 7977 |
|
instruments job is changed by issuing the following command:</t> |
| 7978 |
|
<t> |
| 7979 |
|
<list> |
| 7980 |
|
<t>SUBSCRIBE DB_INSTRUMENTS_JOB_INFO</t> |
| 7981 |
|
</list> |
| 7982 |
|
</t> |
| 7983 |
|
<t>Server will start sending the following notification messages:</t> |
| 7984 |
|
<t> |
| 7985 |
|
<list> |
| 7986 |
|
<t>"NOTIFY:DB_INSTRUMENTS_JOB_INFO:<job-id>"</t> |
| 7987 |
|
</list> |
| 7988 |
|
</t> |
| 7989 |
|
<t>where <job-id> will be replaced by the numerical ID of the job, |
| 7990 |
|
which status is changed. The front-end will have to send the respective |
| 7991 |
|
command to actually get the status info. Because these messages |
| 7992 |
|
will be triggered by LSCP commands issued by other clients rather than real |
| 7993 |
|
time events happening on the server, it is believed that an empty notification |
| 7994 |
|
message is sufficient here.</t> |
| 7995 |
|
</section> |
| 7996 |
|
|
| 7997 |
<section title="Miscellaneous and debugging events" anchor="SUBSCRIBE MISCELLANEOUS"> |
<section title="Miscellaneous and debugging events" anchor="SUBSCRIBE MISCELLANEOUS"> |
| 7998 |
<t>Client may want to be notified of miscellaneous and debugging events occurring at |
<t>Client may want to be notified of miscellaneous and debugging events occurring at |
| 7999 |
the server by issuing the following command:</t> |
the server by issuing the following command:</t> |
| 8072 |
</front> |
</front> |
| 8073 |
<seriesInfo name="RFC" value="2234" /> |
<seriesInfo name="RFC" value="2234" /> |
| 8074 |
</reference> |
</reference> |
| 8075 |
|
<reference anchor="RFC20"> |
| 8076 |
|
<front> |
| 8077 |
|
<title>ASCII format for Network Interchange</title> |
| 8078 |
|
<author> |
| 8079 |
|
<organization>UCLA</organization> |
| 8080 |
|
</author> |
| 8081 |
|
<date year="1969"></date> |
| 8082 |
|
</front> |
| 8083 |
|
<seriesInfo name="RFC" value="20" /> |
| 8084 |
|
</reference> |
| 8085 |
</references> |
</references> |
| 8086 |
</back> |
</back> |
| 8087 |
|
|
Parent Directory
| 
Revision Log
| 
Patch