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
TFLite Multipose model input error for android #66564
Comments
Hi @Raaed-Ilham , I will replicate the issue and i will get back to you . |
Hi @Raaed-Ilham , Did you check out this . This example |
y
Yes that was what I initially tried but I cant build the sample app due to a gradle build issue which is a whole other issue will look into it a bit more then but it uses the same model so it shouldnt be an issue I have compared the code as well. |
I have been trying to work with the movenet multipose lightning model. The model gives the following error
java.lang.IllegalArgumentException: Cannot copy to a TensorFlowLite tensor (serving_default_input:0) with 3 bytes from a Java Buffer with 122880 bytes.
The model, downloaded from the official tfhub/kaggle page ,
requests inputs of (1,1,1,3) of Datatype.UINT8
However in the documentation on the model page it asks for inputs in the form of 1HW*3 where h and w are multiples of 32
ideally 160,256 for example.
I have opened this issue on recommendation from @sushreebarsa after viewing another user with a similar issue given here:
#53127
Currently if 1,1 are given as H and W it results in a bunch of random points on the left hand side of the phone screen which do not seem to move with the user. Any changes to the input size of the image and model only change the latter java buffer size, the tensor image size always remains at 3 bytes in the error messages.
Please let me know if its possible to resolve this issue or if theres something wrong with the model itself. If it is an error with the model could converting the the original model to tflite version with different input parameters be possible somehow.
Relevant code given below
The text was updated successfully, but these errors were encountered: