The PC input source to the HDX CODEC must be designated either ―People‖ or
―Content‖. People images are transmitted on the main video channel while Content
images are transmitted on the second H.239 video channel. When presentation
(Content) material is transmitted or received the system maintains the main (People)
channel resolution despite the reduction in bandwidth allocated to that channel. If it
is desired to allocate all the call bandwidth to the Content to maximise image
quality, then the Content (PC) signal may be connected to the main channel.
Network connection of a PC to the CODEC is also possible by loading the software
application ―People + Content™ IP‖ onto the PC or laptop, but this is limited to
visual material only as sound is not transmitted.
An H.239 (dual video) conference is initiated and terminated by pressing the ―Send
Computer‖ button on the remote control panel. The camera occupies the first
channel and the PC image source the second channel. The two signals are then sent
to the remote site for simultaneous display on two picture monitors. Both channels
can deliver high resolution high frame rate images.
Successful H.239 conferences were established in both directions between HDX
systems and with other manufacturers‘ CODECs for both high and ordinary
definition conferences. The HDX 4500 CODEC supports remote camera control.
The system takes just over two minutes to boot up from cold, when not in a call the
system automatically reverts to sleep mode after a user definable period. An
incoming call or remote control panel button press will return the system to active
mode.
Some problems were experienced after re-booting the system. Several user system
settings had returned to the default from their original user selection, these included:
Camera white balance and second monitor screen resolution. This could cause
problems for casual users as it occurred after a power off and/or a reboot.
At times some areas of the menu were ―greyed out‖ (i.e. could not be selected)
suggesting that the CODEC was in a call, when in fact it was not. The problem
could only be cleared by re-booting the system.
To Next Page
Loading...
