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

the additional window has no image #100

Open
Ishihara-Masabumi opened this issue Jul 21, 2023 · 2 comments
Open

the additional window has no image #100

Ishihara-Masabumi opened this issue Jul 21, 2023 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@Ishihara-Masabumi
Copy link

When I run the following command, the additional window has no image as below.
./MocapNET2LiveWebcamDemo --from /dev/video0 --live

Screenshot from 2023-07-21 17-37-37

@Ishihara-Masabumi
Copy link
Author

Moreover, the video Almost doesn't move.

@AmmarkoV AmmarkoV self-assigned this Jul 25, 2023
@AmmarkoV AmmarkoV added the question Further information is requested label Jul 25, 2023
@AmmarkoV
Copy link
Collaborator

AmmarkoV commented Jul 25, 2023

The 3D points output window gets created here however depending on the visibility of the person there are a lot of "if" statements that might make it not appear.

Please remember that this repository currently hosts a body pose estimation method (in the master branch) and a body+hands body pose estimation method ( in the mnet3 branch) and your input image just shows a head, so this is the reason why it does not output something since there is no view of the body.

In regards to the framerate, to achieve the maximum framerate the demo in this repository is programmed to use the GPU for 2D joint estimation and the CPU for 3D (possibly in a multithreaded configuration) so this combination utilizes system resources in the best way possible. If your framerate is low this is most probably caused by having a CPU-only tensorflow library that handles all of the processing in CPU and using the heavier "--openpose" 2D joint estimator.

Trying with the --forth 2D joint estimator :
./MocapNET2LiveWebcamDemo --from /dev/video0 --forth

will work with a decent framerate (albeit with lower quality 2D input that will result in lower quality 3D output) even when all of the computations are conducted on the CPU.

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

No branches or pull requests

2 participants