Hi,
It seems that in one of the updates to Dashboard, the Hyperdeck panel that is available here: https://www.rossvideo.com/control-sy…/example-apps/ has stopped functioning. At least on our systems with the Hyperdeck Studio.
I tried walking back the firmware on one of our Hyperdeck studios to 4.4.4, but without success.
The really weird thing is we know that they are connecting somewhat okay, it will show as connected on the Setup tab. And clicking ‘Refresh Clip List’ works fine. But telling it to record or playback anything does nothing.
Anyone got any ideas?
I noticed the same. When pressing remote, I can get play to work once or twice, and then it just plays a frame or two, then stops working all together. Going out of remote, pressing stop, then going back in works again a few times.
#DashBoard
Update: For me, I had completely forgotten about the ‘Remote’ button on the Hyperdeck. Stupid mistake. Works now.
This is what happens when between you and the place you work at, you use 4 different brands of recorders. At least that’s the excuse I’m going with…
#DashBoard
Hi,
For me the panel works the first time I connect to it but it will only get the cliplist, none of the play/stop/cue commands work.
If I try to press “comms” or “refresh clip list” more than that one time the panel goes into a loop and debugs “command to send was null” and “connection closed” over and over. Any ideas on what I am missing?
#DashBoard
Hi Tobias.
The “send command” is set to null once the clip list fetch has been started. The fact that it is constantly connecting/disconnecting without any messages coming in has me suspecting that there is an issue with the port on the Hyperdeck side. To be sure, you may want to wrap the listener code in a try { … } catch (e) { ogscript.debug('EXCEPTION: ’ + e); } to see if there is another hidden error that is being missed.
The other commands (play/stop/cue) establish a separate connection to the Hyperdeck side - if these are also failing it would again point to an issue opening a connection on that port.
Overall, I would recommend checking your Hyperdeck settings to make sure it is still listening on your configured port and accepting commands with that API. In a pinch, you could try using a program like Putty to directly-enter the desired commands to the Hyperdeck to verify that other applications are still able to connect/communicate over that port/API.
James
#DashBoard
