- Posts: 4
- Joined: Fri Sep 20, 2013 7:29 pm
The Hyperdeck Studio sort of works.
Unfortunately the software engineers who wrote the code for the Hyperdeck studio got lazy and bypassed a few VITAL status informations.
1. STATUS BYTE 2 bit 0 - "CUE UP COMPLETE"
As the Hyperdeck always instantly cues up they have set the 'cued' status to be PERMANENTLY ON. This is wrong!
The deck is only 'cued' after it is sent the cue command and it has cued. Once moved off the cue (eg play) it is no longer 'cued'. That totally confuses the edit controller.
2. STATUS BYTE 4 bit 0 - "PREROLL OR CUE UP"
The 'Cueing' status never gets set on the Hyperdeck. When the edit controller sends a cue command the first thing it does is to check if the deck IS cueing. When it doesn't see the status it aborts its automatic process that it was trying to do.
I built a small box that I put in between the Hyperdeck and the edit controller to emulate the correct status bytes but lazy software needs to be fixed as follows...
1. Only set CUED status IF the deck has been asked to cue and then reset it if moved off the cue point.
2. Once a 'cue' command is received, SET the CUEING status for about 120mS and then clear it just so the edit controller senses its request is being carried out.
Back in the early '80's I did a lot of consultancy work for a large Japanese company who were adopting the Sony P2 rs422 protocol as they had made a dogs breakfast out of it. Then I was asked to do the same for a large (now defunct) US company to which they ended up abandoning it and went their own way; maybe that's why they don't exist anymore.
anyhow, thats my 4 cents worth.
Baz