DCN-NG is set-up in a multi-PC environment, all required licenses are installed. When trying to connect to the server from the secondary PC, the Operator Application takes a long time to start and once it does, the screen is simply blank and the server icon mouse-over shows the application is disconnected. When pinging the server from the secondary PC, the ping goes through without issues.
System setup with multiple cameras and a supported multiviewer:
Orange: Ethernet connections, red: audio or video connections, blue: HD-SDI
Follow the manuals for the multi-viewers. They can be found at their manufacturer’s websites:
TvOne Corio Matrix Mini User Manual
Kramer MV 6 User Manual
Make sure that to get this setup to work, both the multi-viewer and the CCS1000D Control Unit should be in the same VLAN/subnet. Also, use the correct port to connect to the multiviewer:
TvOne Corio Matrix Mini; port 10001, example: http://192.168.1.2:100001
Kramer MV 6; port 5000, example: http://192.168.1.2:5000
The RESTful API of the CCS1000D is used in order to get a clear view of the state of the discussion devices’ microphones (amongst other things). However, when a Priority call is made, the other speakers still show as active even though they are muted in reality.
This is actually as it' supposed to work. The reason the speakers still show as active is because they remain in the speaker list while the priority call comes through (in this case, the chairperson making an announcement overruling all other parties) is that in the system there’s a difference between speakers being muted and speakers being removed from the speaker list.
In this case, after the priority call ends, the speakers are unmuted and can resume the discussion.
It’s also possible to configure the system to stop all speakers and remove all waiting participants from the request list. If the system is setup in this way and the chairperson starts speaking, the system will indeed erase all other speakers and waiting speakers.
The API can be used to create a custom interface. This means that logic can be added so the preferred outcome is created. In this case it means that the custom interface needs to poll for the speakers list but also needs to take in account that when a priority call comes through (also pollable) this means the others are muted. Using these two givens can then be used to for example change the icons of the speakers to a ‘muted’ state in the custom interface.
In order to change the layout, the StyleSheet needs to be changed. Default it is located in C:\ProgramData\Bosch\DICENTIS\VotingResult.xslt, this file can be opened in any text editor, Notepad++ is recommended as it is very versatile.
When using a fixed IP addresses in a multi-subnet Dicentis system, certain settings need to be made for the system to function well. If the settings are not made correctly, the system can stop functioning & disconnect from the server.
The APS in question was running on v1.12 and needed to be upgraded to v2.60 and any firmware updates would continually fail (even other intermediate versions). The below procedure is not specific to this update and can also be used for updating from other older versions.
Dicentis can run on a server with multiple network cards, but adding a variable that points to the network card that connects to the APS and other Dicentis equipment is required for it to work correctly.
Trouble mixing and matching older & newer Dicentis cable assemblies, cables and connectors. The problem is usually that the cables and connectors do not fit together correctly or it's very hard to put them together.
When trying to open the API demonstrator it will not open the demonstrator.
In version 3.11 it works but in 3.20 it will not.
Run the DCNM setup again and make sure that the option ‘(Default) Bosch DICENTIS API’ is also enabled.
Complete the installation and restart the PC.
Connection between DCN server and operator client will disconnect. This is occuring when using windows 10 PC's with SSD-disks.
After restart of the DCN services it will work for a while.
Also windows 10 has the 'fast startup' option enabled. This option will store settings and running services to have a fast startup. Because of this our services will start to fast and are not properly connected to the other services.
And the use of SSD-disk in the server PC can cause a start up that is to fast for the services.
In windows 10 there is the option enabled to store some services when the system has been shut down and start up again. This can cause problems with our services:
1: disable fast start-up option in the win 10 PC:
go to the control panel of windows
then go to 'power options'
then click on 'choose what the power buttons do'
then click on 'Change settings that are currently unavailable'
then disable 'Turn on fast startup'
Also the use of an SSD disk in the server PC can cause some startup problems with our DCN-NG software. You can fix this by doing the following:
go to the services
right-click on 'DCN-SW Server'
click on 'Properties'
Change startup type to 'Automatic (Delayed start)'
Now restart the PC and test with these settings.