Loading ...
Loading ...
Loading ...
Timecode syntax
Timecodes are expressed as non-drop-frame timecode in the format:
HH:MM:SS:FF
Handling of deck "remote" state
The “remote” command may be used to enable or disable the remote control of the deck. Any attempt to
change the deck state over ethernet while remote access is disabled will generate an error:
111 remote control disabled↵
To enable or disable remote control:
remote: enable: {“true”, “false”} ↵
The current remote control state may be overridden allowing remote access over ethernet irrespective of
the current remote control state:
remote: override: {“true”, “false”} ↵
The override state is only valid for the currently connected ethernet client and only while the connection
remains open.
The “remote” command may be used to query the remote control state of the deck by specifying no
parameters:
remote↵
The deck will return the current remote control state:
210 remote info:↵
enabled: {“true”, “false”}↵
override: {“true”, “false”}↵
↵
Asynchronous remote control information change notification is disabled by default and may be
configured with the “notify” command. When enabled, changes in remote state will generate a “510 remote
info:”asynchronous message with the same parameters as the “210 remote info:” message.
Closing connection
The "quit" command instructs the server to cleanly shut down the connection:
quit↵
Checking connection status
The "ping" command has no function other than to determine if the server is responding:
ping↵
Getting help
The "help" or "?" commands return human readable help text describing all available commands and
parameters:
help↵
Or:
?↵
The server will respond with a list of all supported commands:
201 help:↵
{Help Te x t}↵
{Help Te x t}↵
↵
131
DeveloperInformation
Loading ...
Loading ...
Loading ...