Anyone getting T+0 msec in deepstack analysis Windows?

Shap

Young grasshopper
Joined
Jul 4, 2021
Messages
37
Reaction score
22
Location
Austin,TX
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.

1629946826952.png
 

aesterling

Getting comfortable
Joined
Oct 9, 2017
Messages
352
Reaction score
346
Do you have “begin analysis with motion-leading edge” checked or unchecked? Also what is your “pre-trigger video buffer" set to?
 
Last edited:

Shap

Young grasshopper
Joined
Jul 4, 2021
Messages
37
Reaction score
22
Location
Austin,TX
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

Getting the hang of it
Joined
Aug 29, 2018
Messages
158
Reaction score
38
Location
US
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

Getting comfortable
Joined
Oct 9, 2017
Messages
352
Reaction score
346
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:

Screen Shot 2021-08-26 at 02.24.13 PM.png
Screen Shot 2021-08-26 at 02.23.46 PM.png
 

Shap

Young grasshopper
Joined
Jul 4, 2021
Messages
37
Reaction score
22
Location
Austin,TX
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

1630022702192.png
 

aesterling

Getting comfortable
Joined
Oct 9, 2017
Messages
352
Reaction score
346
Interesting. Yes, I was using hi-res jpeg. Will try DB only and see how it behaves :)
 
Top