Opcode PatchTalk User Guide - House of Synth

More documents

Recommendations

Info

Send Opcode YourModules!Opcode will periodically release additional Galaxy modules. We hopethat eventually MIDI manufacturers will write them before theyrelease new devices but, in the meantime, if you want to share yourwork with other Galaxy users, send us your modules. We’ll be collectingthem for possible inclusion with future versions of Galaxy.PatchTalk HelpA summary of PatchTalk is available as on-line help. To open a helpwindow, choose PatchTalk from the System 7 Help menu.(Figure 6: System 7 help menu icon appears on upper right of Macintoshscreen.PatchTalk CommandsCommands are the instructions you write in PatchTalk scripts. Theyinstruct Galaxy to perform very specific functions. When a script isrun, each command in the script is executed in sequence. Rememberthat while Galaxy tries to do as much for you as possible, when it’srunning a script, it can only do exactly what is stated.The following list of commands describes both how to use them in ascript and what they do when run by Galaxy. The format of the commandis given first, then a description of what the command does,followed by some examples. Keep these points in mind when lookingat the format lines:• Words in boldface, such as Receive, are typed just as they appear.• Words in italics are replaced by one or more words that are appropriate,for example ListOfValues may be replaced by 3 + 4.• Groups of words in braces, such as {into | after} are choices separatedby the vertical bar. You can choose one of the options.• Any text after two dashes (‘- -’) is a comment. Galaxy will ignorewhatever is there through the end of the line. A long dash will alsowork (“—”, typed as Option-Shift-dash).• Some parts of a command are optional. This is noted in a comment.Note that if you include optional parts you must write them in theorder they appear in the format line.• Upper and lower case letters make no difference: put, Put, andPUT are all the same.Opcode Publication 1950906 - 12 - PatchTalk Guide
• While some formats are shown on several lines for clarity,PatchTalk commands are written one line per command. (See“PatchTalk Notes” for a way to get around this limitation.)SendSend ListOfValuesThis transmits the data in the ListOfValues to the MIDI device. Anydata may be sent: system exclusive commands, note commands, patchdata. It’s up to you to ensure that valid MIDI messages are sent andthat any device IDs or channel assignments get encoded into the data(see the second example).Send $F7 send an end-of-system-exclusivemessageSend ($C : DeviceID) $7F send a patch change to patch127. Note the use of adding theDevice ID variable to send theprogram change on the rightchannel.SendBulkReceiveSendBulkThis sends the contents of a bulk window to the MIDI device. Use theReceiveBulk command to get the data. Use this only with patch typesthat have their Patch Size set to Bulk.Receive MaximumSize { into | after } Destinationrequire ExactSize bytes --optionaltimeout after Time {seconds | milliseconds } --optionalwait UserMessage --optionalThis gets one system exclusive message over MIDI and places it into orafter the Destination. Any additional data beyond the number stated,MaximumSize, are lost.The optional require clause specifies the exact number of MIDI bytesrequired. If a different number of bytes is received (too many or toofew), then the operation fails and the user will get a message. Use thiswhenever you know exactly how many bytes the MIDI device shouldsend to you.The optional timeout clause specifies the amount of time to wait for amessage. If this time is exceeded, the receive command will fail andthe user will get a time out message. Note that s and sec are acceptableabbreviations for seconds, as are ms and msec for milliseconds. If notimeout is specified, a default timeout will be used.Opcode Publication 1950906 - 13 - PatchTalk Guide
Page 1: O P C O D EPUBLICATIONPatchTalk Gui
Page 5: Patch NumberingDevice ID RangeHands
Page 8 and 9: Select the device type and click th
Page 10 and 11: Typical format for a Get Patch scri
Page 14 and 15: The optional wait clause puts a tex
Page 16 and 17: NOTE: “After” can only be used
Page 18 and 19: RepeatRepeatCommandsUntil Condition
Page 20 and 21: PatchNumThe number of the patch who
Page 22 and 23: NumbersAnywhere a numeric value is
Page 24 and 25: Lists of ValuesSome commands, notab
Page 26 and 27: Define CustomPatch TypeEdit Help Me
Page 28 and 29: • Examine the contents of bank or
Page 30 and 31: Also beware of strange things like
Page 32 and 33: PatchTalk TipsPutting Empty into aV
Page 34 and 35: Sending OtherMIDI MessagesRemember
Page 36 and 37: ** Data fields are of this type: */

Opcode PatchTalk User Guide - House of Synth

Create successful ePaper yourself

Delete template?

Save as template?