Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No detection and tracking in the video #11

Closed
Teezq opened this issue Jul 26, 2021 · 7 comments
Closed

No detection and tracking in the video #11

Teezq opened this issue Jul 26, 2021 · 7 comments

Comments

@Teezq
Copy link

Teezq commented Jul 26, 2021

Hi @emasterclassacademy , I have ran into a problem where there is no detection or bounding box at my output video. I have manually printed out the boxs, scores and classes, but these parameters only return values on the first frame while other remaining frames just remains an empty list. Does anyone here encounter such issue? Or did anyone manage to solve it? I am aware that I only generated the 3 files when converting yolo to tensorflow: checkpoint, yolov3.tf.data-00000-of-00001, yolov3.tf.index. Could this be the problem? If yes, does anyone has experience with this?

@Teezq
Copy link
Author

Teezq commented Jul 27, 2021

Any hint guys? So I have confirmed that the yolo detection runs on the first frame, deepsort tracking doesnt since there is no update. When begining from second frame, both just stop running and return empty values.

@Teezq
Copy link
Author

Teezq commented Jul 27, 2021

image

@Teezq Teezq closed this as completed Jul 27, 2021
@kenca5ey
Copy link

Hi @Teezq - Did you manage to find a solution to this issue? I am experiencing the exact same issue as you were, where the first frame has a detection but all of the arrays for detections are zeros thereafter

@kenca5ey
Copy link

Hi @emasterclassacademy - Great work! Would really appreciate any insights on why yolo.predict runs correctly on the first call to the function but on subsequent calls to yolo.predict only empty arrays are returned. Any idea why this might be?

@acschristoph
Copy link

Hey guys I have same issue did u resolve it ?

@kenca5ey
Copy link

Hi @acschristoph - I am not sure what changed to cause this issue so I didn't end up sticking with this. But as a workaround, calling the model itself yolo() will likely work on subsequent iteration calls.

@vini-c-costa
Copy link

Hey guys, @Teezq @kenca5ey @acschristoph

Have you solved this issue? I'm having the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants