You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm checking out this code to possibly use for camera frame decoding on Android but I noticed that the colorConversion example seems to be broken on any of my 4.0+ devices (4.0.3 and 4.1). It seems to be decoding the frame okay but 4.0+ devices are just showing 1 vertical line of pixels at the far right side. My gingerbread phone looks fine. I'm not sure if this is a view issue or decoding issue.
Also, I didn't have any 3.0 - 3.2 devices to try but my old 2.2 Motorala Droid just shows a black screen although the conversions seems to be running fine at ~30 FPS.
Another thing I noted is that on my old Galaxy S (2.3.3 gingerbread) device I'm getting around 40 FPS calling naGetConvertedFrame but on my newer Galaxy Nexus I'm getting 18 FPS and my tegra2 tablet is pushing around 30 FPS. Seems a little odd that the newer CPUs are processing frames slower.
Is there any simple explanation for why I see these results?
By the way, thanks for posting this informative code!
The text was updated successfully, but these errors were encountered:
Hi,
I'm checking out this code to possibly use for camera frame decoding on Android but I noticed that the colorConversion example seems to be broken on any of my 4.0+ devices (4.0.3 and 4.1). It seems to be decoding the frame okay but 4.0+ devices are just showing 1 vertical line of pixels at the far right side. My gingerbread phone looks fine. I'm not sure if this is a view issue or decoding issue.
Also, I didn't have any 3.0 - 3.2 devices to try but my old 2.2 Motorala Droid just shows a black screen although the conversions seems to be running fine at ~30 FPS.
Another thing I noted is that on my old Galaxy S (2.3.3 gingerbread) device I'm getting around 40 FPS calling naGetConvertedFrame but on my newer Galaxy Nexus I'm getting 18 FPS and my tegra2 tablet is pushing around 30 FPS. Seems a little odd that the newer CPUs are processing frames slower.
Is there any simple explanation for why I see these results?
By the way, thanks for posting this informative code!
The text was updated successfully, but these errors were encountered: