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

Replace onFrameAvailabe by onImageAvailable #318

Open
smits opened this issue Jun 19, 2017 · 3 comments
Open

Replace onFrameAvailabe by onImageAvailable #318

smits opened this issue Jun 19, 2017 · 3 comments
Assignees

Comments

@smits
Copy link
Contributor

smits commented Jun 19, 2017

Might solve #314.

@PerrineAguiar
Copy link

PerrineAguiar commented Aug 1, 2017

Issues encountered:

  • Calling TangoService_connectOnImageAvailable returns with the error Cannot register onImageAvailable callback when onFrameAvailable already registered!, even after commenting the code which register onFrameAvailable.
    Issue reported here, but no answered yet.
    UPDATE: Ignoring the error code seems to work.
    Solution: Make a simple app to isolate the problem, test it on Lenovo and Asus and report it to Tango team.

  • Cannot register the color camera with both onFrameAvailable and onImageAvailable (but no error code in this case...), while we still need to use onFrameAvailable because the new struct TangoImage is not compatible with the tango 3d reconstruction API and tango support.
    UPDATE: The new release m21 containing the update for the tango 3d reconstruction API to work with TangoImage should come at the end of the week.

@PerrineAguiar
Copy link

Test results:

  • TangoService_connectOnFrameAvailable with camera id TANGO_CAMERA_FISHEYE throws an error on the Asus phone. The callback is not triggered.
    The error message is:
    Cannot register onFrameAvailable callback when onImageAvailable already registered!

  • TangoService_connectOnImageAvailable with camera id TANGO_CAMERA_COLOR (only the color camera is supported for onImageAvailable according to the documentation), throws an error on both the Asus and Lenovo phone. The callback is still triggered.
    The error message is:
    Cannot register onImageAvailable callback when onFrameAvailable already registered!

@PerrineAguiar
Copy link

This is not solving #314. The reason of #314 and its fix is in #371.

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

No branches or pull requests

2 participants