Anyone getting T+0 msec in deepstack analysis Windows?

[Shap]

Hello guys,

using latest BI+DS.

Can anyone confirm if they are getting T+0 in the deepstack analysis window?

I am constantly getting T+50 up to T+100 msec. So the image sent to DS and motion rectangle is a bit off.

 

[aesterling]

Do you have “begin analysis with motion-leading edge” checked or unchecked? Also what is your “pre-trigger video buffer" set to?

 

[Shap]

I have "begin analysis with motion-leading edge” unchecked (tried with check as well). Pre trigger buffer is 5 sec. FPS ratio is 1.0

Sent from my KB2005 using Tapatalk

 

[lcam]

I only get T+0 and have "begin analysis with motion-leading edge” unchecked and Pre-trigger video buffer is set to 3 sec.

 

[aesterling]

I don't remember what determines it. For comparison, my settings are

• Pre-trigger video buffer of 1.5 sec,
• Analyze one every 500ms
• Begin analysis with motion-leading edge checked

and I get these results:

 

[sebastiantombs]

I get "T+0" with a 3 second buffer and all other settings the same.

 

[Shap]

I don't remember what determines it. For comparison, my settings are

• Pre-trigger video buffer of 1.5 sec,
• Analyze one every 500ms
• Begin analysis with motion-leading edge checked

and I get these results:

View attachment 99812
View attachment 99811

You have the same problem I had - not only you do not get T+0, you also have a duplicate frame sent to DS: (T+598).
This also probably causes you to have many false-negative responses from DS.

I bet you have this option set to "Hi res JPEG" - set it to DB Only and it will fix the problem

 

[aesterling]

Interesting. Yes, I was using hi-res jpeg. Will try DB only and see how it behaves