Connects the liveSHOW_MIDI client to the selected server | ||
Disconnects the server | ||
(connect automatically) |
If this is activated, a connection will be established automatically if a suitable server was found. For this purpose, a connection must be established manually the first time the program is started. |
|
(load last project at start) |
If this is activated, the last loaded / saved settings are automatically opened when the liveSHOW_MIDI client is started. | |
All settings can be saved in a file. The MIDI settings are closely linked to the server's project. In order to make this connection recognizable, you should always use the same file name as the project of the server. ATTENTION: If you port a server project to another computer (for example, from the office computer to the show computer, you must remember to copy the corresponding MIDI settings file to the other computer. |
||
The saved settings can be loaded from a file. | ||
Displays help for the liveSHOW_MIDI client | ||
Here the playing time of the server is displayed. In liveSHOWsoftware this is the position of the media cursor. |
Opens a selection window for CommPort devices or the virtual 'Timecode Loopback' device. | |
Delete a selected device from the list (only CommPort devices or 'Timecode Loopback' | |
Opens a settings window for a CommPort device. |
The command is executed when the specified time is transmitted. In the table of SPIT remote control objects, this is shown with MTC and the time. |
|
The command is executed when the received time corresponds to the start time of the remote control object. In the live SHOW software this is e.g. the start time of a main scene bridge in the timeline. In the table of SPIT remote control objects, this is only shown with MTC. |
Deletes all assignments to midi devices. Also to midi devices that are not listed. If not all the necessary midi devices are currently connected, you must be careful when deleting the assignments. |
When the object is playing, timecode messages are sent. The start time is the specified time. In the table of SPIT types this is shown with MTC and the time |
|
The start time is taken from the start position of the respective trigger object. In the table of SPIT types, this is only shown with MTC. |
All settings can be saved in a file. The MIDI settings are closely linked to the server's project. In order to make this connection recognizable, you should always use the same file name as the project of the server. ATTENTION: If you port a server project to another computer (for example, from the office computer to the show computer, you must remember to copy the corresponding MIDI settings file to the other computer. If you had already saved the midi settings once and a midi device is currently not connected, a message appears that there are references to unconnected midi devices. You can then decide whether you:
|
||
The saved settings can be loaded from a file. | ||
(load last project at start) |
If this is activated, the last loaded / saved settings are automatically opened when the liveSHOW_MIDI client is started. |