Capturing Using remote Communications

Once the clients and servers are connected in the Communication window, capture commands can be initiated through the Capture window or the Communication window. Open the Capture window to view or set up the necessary buttons in the Capture toolbar.

There are two capture remote communication buttons in the Capture window, Communicate and Communicate Only. These buttons are not a part of the default of the toolbar set and must be added by customizing the capture window toolbar, (see the capture window section on customizing the toolbar to add these buttons to the capture window.)

Fig 66dThe Communicate capture button will initiate a quickstart capture locally (server) and remotely on the connected clients with the initiate recording option checked. All the capture functions in the local capture window: stop, pause and resume will work both on the local (server) capture and the remote (client) captures.

Fig 66cThe Communicate Only capture button will only send capture commands to the clients and will not initiate the local capture. The captured files will be found in the preferred quickstart capture folder. They will be named using a date stamp according to the system date. To set the Quickstart capture folder choose Capture > Quickstart set folder from the main menu bar along the top of the screen.

Remote Communications Coding

The most powerful and simple feature of remote communications is the ability to send button push commands from a server’s code window to a client’s code window. This means that multiple people can be coding on different computers, all feeding information to each other’s timeline or into a single timeline over a network. Using the Internet, capture and coding processes can literally be done across the globe.

The button push commands are sent from server computers to client computers automatically when code mode is activated in a code window. There are no configuration settings in the preferences for this feature of remote communications. The only things that are required are a connection to a client and the identical code windows on each computer.

There are a few items to note.

  • Use identical code windows on each server and client. Remote button pushing is when a server code window sends the push command to the matching client code window. The client computer locates the button to be pushed down and pushes it down. If the same code window is not open on the client computer, no buttons will be pushed down, so no codes will be created in the timeline of the client computer.
  • Multiple windows can be open at one time. It is a good practice to break down a single large code window into multiple smaller ones. This can make the coding process focused and accurate for the people coding.
  • Do not set the same hotkeys for multiple windows. When multiple code windows are open, the hotkeys may push down the wrong buttons if the same ones are set in the buttons of the windows.
  • Capturing does have to occur locally on a server computer. Connect to a capturing client with the same code window open, open the same code window on the server and activate code mode. The button pushes will start on the client even though the server is not capturing.

Imagine 20 or more people could be viewing the same event, coding on separate computers in different geographical location while all the data is being pushed into one capturing client. The possibilities for this feature are endless.



Fatal error: Call to undefined function get_top_parent_page_id() in /home/sporthelp/public_html/wp-content/themes/tropixel/footer-nav.php on line 27