By disabling the proxy in Windows, the Videohub Control software can finally reach the videohub. We guess that the software uses the Qt interface QNetworkProxyFactory with default parameters and therefore no exception list are considered for the proxy. Initially everything seemed to be solved but now we faced a new problem: if a proxy is configured on Windows to reach the Internet, the switch remains controllable via telnet but not via Videohub Control software.īy analyzing this aspect, we learned that the windows executable VideohubControl.exe checks if a company network proxy is configured on the pc and tries to use it when it starts, ignoring the exception list set for local addresses. At this point something has changed and we finally managed to reach the machine both via telnet and via Videohub Control.Īt this point we changed the ip to insert again the video hub on our LAN with private addressing (10.102.214.*). We changed the IP of the videohub bringing it back to the 192.168.10.x network default and relaunched the setup for the umpteenth time. Finally we made one last attempt which proved to be decisive. We coudn't take remote control either via telnet or via IP with Blackmagic Videohub Control software. The problem has been partially solved and the causes identified.įor your information, we send you the details of the troubleshooting performed.Īt first we tried unsuccessfully to reach the videohub from multiple PCs with windows 10 enterprise, even connecting the videohub directly to the PC to avoid possible problems due to the network switch. Has anybody haved a similar issue? Do you have any suggestion? ![]() Or can we force a new software/firmware installation, even if the latest version is (formaly) already installed? Is it possibile to force a harware factoy reset ? If so, how? Right now we only can switch video input and output from its frontal panel, but without software we cannot change signal labels, we cannot see the signal routing, nor control the device remotely, so it is a very unhandy and uncompleted workflow for us. We are not able to upgrade nor downgrade the software, so we are stuck at this point. No firewall is active neither our PC, nor on our LAN. ![]() It looks like the switch has its IP ports closed (except for ping requests). 7.0.1 and 6.4.4, but this is not possibile, because the updater shows up the error "incompatible software version" and stops the installation, since the latest version is already installed.Įven the VideoHub Setup software cannot find the switch on the network, only on USB. We then tried to downgrade the software to v. It responds to ping requests, but it doesn't respond to VideoHub Control Software request (it keeps searching for the switch forever). Since then, we cannot control anymore the switch on the network. We updated the Switch software to version 7.0.3 with no errors. We properly set the switch IP address, mask and gateway. Video payload identification ancillary data as per SMPTE 352M.We recently bought a Smart Videohub CleanSwitch 12x12 and installed its VideoHub Control software. ![]() ![]() REC 601, REC 709, REC 2020 SDI Auto SwitchingĪutomatically selects between 270Mb SD‑SDI, 1.5G HD‑SDI, 3G level A and level B HD-SDI, 6G HD‑SDI, 12G‑SDI and DVB‑ASI on each input so that each input can be running a different television standard. SMPTE 259M, SMPTE 292M, SMPTE 296M, SMPTE 372M, SMPTE 424M, SMPTE 425M level A and B Video payload identification ancillary data as per SMPTE 352M. SDI Color SpaceĪutomatically selects between 270Mb SD‑SDI, 1.5G HD‑SDI, 3G level A and level B HD‑SDI, 6G HD‑SDI, 12G‑SDI and DVB‑ASI on each input so that each input can be running a different television standard. YUV 4:2:2 and RGB 4:4:4 SDI Color Precisionġ0, 12‑bit RGB 4:4:4 in all HD and 2K modes, Ultra HD modes up to 2160p30 and 4K modes up to 4Kp30 DCI. Television standard sample rate of 48kHz and 24-bit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |