search

jiuqiant / mediapipe_multi_hands_tracking_aar_example

MediaPipe multi-hand tracking gpu demo with MediaPipe's Android archive library
114 stars 47 forks source link

Not getting callbacks for landmarks on specific device #15

Closed ravikumar-ramamurthy closed 3 years ago

ravikumar-ramamurthy commented 3 years ago

Hi all

Thanks for great samples on mediapipe.

I am new to mediapipe and was trying multiple examples and especially hand tracking example. This example is great to start work and was able to successfully build and run on my Samsung A50 device. specs. This is arm arch processor device and the application works perfectly.

I am trying to run the same app on another device which is also arm arch processor Vuzix M400 specs and the same Android OS version. Both the devices seems to be on-par with the specs. The problem is in M400 device the landmarks call back for OUTPUT_LANDMARKS_STREAM_NAME is not consistent from FrameProcessor during startup. i.e. I launch the app, it starts with blank screen and no callbacks. Try to open multiple times and it would succeed sometimes and works. This is some strange behavior

I tried to debug this and also added additional consumer to ExternalTextureConverter to get callback for onNewFrame(TextureFrame frame). This is to check whether camera is sending the frames and mediapipe is able to receive the inputs. Even in this case the behavior is same that app launches with blank screen sometimes without callback and sometimes with proper callback.

Created another app with just preview of camera and that seems to work fine; without any mediapipe code/libraries to process the camera.

I did all the things typical developer does, but could not find any clue on this... any help is appreciated.

Thanks very much.

ravikumar-ramamurthy commented 3 years ago

I did raise this issue with mediapipe and got the answer from this issue 1508. Hence closing the issue here.