Open headupinclouds opened 6 years ago
I see that this one relates to my case.
When I searched for the size within the ImageFormat.YUV_420_888, I could work with the resolution (W: 4128; H: 2322). It's true that it's smaller than the resolution above. Anyway, it could have been that some other image format from the case above used different number of channels, perhaps, and that the resolution per se isn't the bottleneck.
From https://github.com/elucideye/drishti/issues/711
Attempting to run at "4144 x 2332" seems to crash the application.
Need to better understand root cause.
If there are resource limitations, the error should be handled and reported in a more user friendly way (at least). Ideally, such resolutions can be made to work. The operating pipeline resolution for a given detection range should not change memory allocation significantly, so it should be doable.
May relate to more general issues: https://github.com/elucideye/drishti/issues/265 https://github.com/elucideye/drishti/issues/181