Blackmagic Forum

When I set a POI in Resolve it never matches the exact time set of the POI.
There's also a little stopwatch icon changing from 1-12 seconds sometimes 1-6 seconds.
My guess is that the growing file gets polled/updated from time to time. It also seems that the Hyperdeck sends segments for about 6 seconds each.

Does anyone know if and how this delay can bet shorten to make it actually work and usable for a broadcast?

There is not much documentation around and support seems also not know alot about it.
In the Resolve manual there is another manual mentioned (on page 508 Please see the dedicated DaVinci Resolve Replay Editor Instruction Manual for more information) but that documentations does not seem to be available yet.

Same for me. Just got the keyboard but no documentation found. Also, when plugging in to USB-C no signal/led that it works at all...

ItsCool.Media wrote:Same for me. Just got the keyboard but no documentation found. Also, when plugging in to USB-C no signal/led that it works at all...

I am in exactly the same situation. I currently have a lovely looking paperweight.

Update: When speaking to BMD during IBC in Amsterdam the solution was simple...Upgrade to DR19. Obvious perhaps...but not documented. Well, it worked like a charm. The Replay Editor runs without hickups now but I could not get to test Replay since after a few hours DR became sluggish to the point that it is not usable anymore. Quite a few other are suffering as well seeing the posts on other forums. So this ticket is closed for me for now so I can focus on getting DR to work again....

My initial post was made up on the latest DR19 and also the fixed version that arrived a few days later.
Still trying to get it work as ment to.
I looked in the manual that has finally been released but found no solution yet as they are always involving a Atem and a notebook.

But I'm working with just some Hyperdecks (daiys chained for Timecode), Decklink card (also for input to get timecode into DR) and a fast PC with the very latest DR19 on it.

When I set a POI in Resolve it never matches the exact time set of the POI.
There's also a little stopwatch icon changing from 1-12 seconds sometimes 1-6 seconds.
My guess is that the growing file gets polled/updated from time to time. It also seems that the Hyperdeck sends segments for about 6 seconds each.

Does anyone know if and how this delay can bet shorten to make it actually work and usable for a broadcast?

The manual is now online https://documents.blackmagicdesign.com/ ... Editor.pdf

coyutbm wrote:My initial post was made up on the latest DR19 and also the fixed version that arrived a few days later.
Still trying to get it work as ment to.
I looked in the manual that has finally been released but found no solution yet as they are always involving a Atem and a notebook.

But I'm working with just some Hyperdecks (daiys chained for Timecode), Decklink card (also for input to get timecode into DR) and a fast PC with the very latest DR19 on it.

When I set a POI in Resolve it never matches the exact time set of the POI.
There's also a little stopwatch icon changing from 1-12 seconds sometimes 1-6 seconds.
My guess is that the growing file gets polled/updated from time to time. It also seems that the Hyperdeck sends segments for about 6 seconds each.

Does anyone know if and how this delay can bet shorten to make it actually work and usable for a broadcast?

What codec are you using on your Hyperdecks to record? An Intra codec like one of the ProRes or DNX variants will potentially be a better choice than a LongGOP codec like h.264/265 for replay purposes. If you're using h.264/265 then try switching to ProRes or DNX?

Stephen, we're having the same problem. lag switching from setting a POI to going into playback. 10-20 sec delay is killing us in replay for basketball. Did you ever find a solution?

It’s 50/50 h264/265 will put more stress on the processor Prores/DNX will put more stress on the network. I’d advise testing both to see which codec yields the least latency.
Good Luck

We're on an ATEM ISO extreme, so limited options for recording. only h264. have you had any success reducing the delay?

We did a lot of trial and error yet. (Hyperdeck to NAS to Resolve Live)
Here's what we found yet:

First tries in a 1G Network with h264 and ProRes variants

Synology NAS
Recordings do not get recognized by Resolve as growning files as it uses the wrong files system. We did not reformat the NAS with exFAT 128kb and stoped that trial

Bought a Blackmagic Cloud Pod to do further tests
We first tried with a Samsung T7 ssd, which was not recognized by the cloud pod. Got it working after a firmware update on the T7 ssd trough Samung Magician. But the T7 uses some buffer that will not really work well with single, large recording files. So Hyperdeck had troubles writing the files and made a lot multiple files. Resolve Live does not support a watch folder so you will need to import each new created file again after the initial one crashes... (BM please program a watchfolder function).
Furter testst with old Samsung T3 and T5 ssd's. They were working much better and Hyperdeck could keep writing a single file. But adding more than 1 camera source would make the system slow (around constant 10sec delay before you got both camera sources synced to use for replay)
So we bought a fast M2 ssd and put it in a usb-c enclosure. But that did not solve the long delay before 2 camera sources were matched and available. 10 seconds is much too long to get a usefull live replay on a live event.

10G Network

We then went ahaead and put all devices and DR in a 10G network.
This brought the delay down to about 5 seconds refresh rate. Which is still very slow and we only used 2 camera sources yet. Our target is at least 4 sources. h264 or ProRes did not really make a big difference in delay, even the amount of data was much greater with ProRes as expected.

We still wait on a cloud store max to arrive since a while. We will need it to test the system as we initially planed it. Fingers crosses this will get a additional boost. Otherwise the system would not be really usefull for live replay in a live event enviroment.
Hopefully this will bring the delay furtehr down.

5-7 seconds is pretty normal for this system. For reference this is an almost free way to run something that you normally only find on a EVS or tri-play system costing ten to 100 of thousands of euro's...

It is called Replay but it aint a full size EVS clone system.

We found a way to reduce the delay to around 1-2 seconds.

On our Hyperdeck 4k recorders we build in some optional ssd cache.
It seems Hyperdeck writes the file first to the internal ssd cache and rolls them out to the external recording after a couple of seconds. So its not parallel external recording and caching.
Thankfully you can disable the internal ssd cache in the menu. When doing so the files are available almost instantly in Resolve Replay. But you add the risk of a faulty recording if there are any network problems while recording.

Our current test setup:

- Up to date Win11 resolve system with 4070 Super Ti graphic card, 64GB memory and currently 2.5GB network
- 10G Switch
- Cloud Store Max 24TB
- 5 Hyperdeck recording 1080p/50fps Prores LT

When going with full ProRes the 2.5GB network card in the edit system goes into a bottle neck.
So we might add a 10G card to that system as well.

coyutbm wrote:Thankfully you can disable the internal ssd cache in the menu.

How do you do this? What menu?

In the menu of the hyperdeck. But only if you actually did build a m2 cache in the hyperdeck by your self.