I have noticed that when shooting 3264x1836 90% quality, the JPEGs are around 2mb (as per other apps) when not using the Camera2API, but they are 11mb when using the Camera2API. There may be a reason, but the images do seem to be too large and result in much more HDD space being used for the image pixel size.
Cheers, Al
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-02-09
You cannot demand quality and whine about large images at the same time. VGA-resolution suits you better.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-03-12
It has nothing to do with whining about the file size. It's a bug that bloats the image file with unnecassary data.
So next time, if you don't have something useful to add to the conversation, just stfu please.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2018-10-24
I've got the same problem, files are 31 MB nomather what Jpeg setting i try
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What devices are these? This works okay on my devices for Camera2 API, it may be an issue with the device (not supporting/handling the quality setting when using Camera2 API).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-08-06
Hey Mark,
I'm working with a Samsung Galaxy A5 2017 (a5y17lte, Android API 28, PIE, OpenCamera v 1.48.2, Code 78), my files are about 31 MB in Size where it would be about 3MB without using Camera2 API.
Hope that helps! :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the info. Just to check, these are both JPG files?
A known issue with Samsung devices is they seem to ignore the JPEG compression setting, but that doesn't explain why there is the different for Camera2 API. This doesn't happen on my Galaxy S10e.
What resolution is this? What about other third party camera applications (e.g., Footej uses Camera2 by default, Snap Camera HDR supports both APIs)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I see the same issue, also on an a5y17lte running LineageOS 18.1. Camera2 API: 31 MB JPEG images at full 12 MP resolution in standard mode. File sizes are much smaller (2-3 MB) when I do any of the following:
- Change to original camera API
- Change output to WEBP
- Use any of the image processing modes (HDR, DRO, panorama etc.).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-03-12
Somewhere I read a fix for it and now I remembered it (lost the settings because of upgrade...):
Just enable time stamps. And if you don't like them, keep the general time stamp option enabled and disable time, date, gps and address seperately.
Now the file size is at 2-3 MB again.
So maybe it is an issue related to time stamps?
hth! :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-03-12
Great workaround, thanks! I can confirm that this works for me on the a5y17lte with Open Camera v1.49.2. This seems consistent with the other observations that the file size is reduced whenever some image processing is requested: changing output type, applying HDR etc. or in this case adding a stamp to the image. Perhaps when only the original image is requested the compression gets skipped, otherwise it's done correctly?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the info. The reason why this works is because it means the image is processed by Open Camera and then resaved as JPEG using the Android API (which respects the setting for JPEG compression/quality value). But by default, the JPEG is generated direct by the camera driver. On some devices it seems they ignore the JPEG compression setting (e.g., see https://sourceforge.net/p/opencamera/discussion/general/thread/1abb56eb/#ca68 for the issue on Samsung devices).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-02-06
Hallo,
i have same proplems on also on a5y17lte with LineageOS 18.1.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-07-17
So do I understand correctly that there is no way of fixing this directly, but work around it by trading off speed since the timestamp thing will reprocess it and therefore respect the jpeg compression?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Firstly, thanks Mark for a great app.
I have noticed that when shooting 3264x1836 90% quality, the JPEGs are around 2mb (as per other apps) when not using the Camera2API, but they are 11mb when using the Camera2API. There may be a reason, but the images do seem to be too large and result in much more HDD space being used for the image pixel size.
Cheers, Al
You cannot demand quality and whine about large images at the same time. VGA-resolution suits you better.
It has nothing to do with whining about the file size. It's a bug that bloats the image file with unnecassary data.
So next time, if you don't have something useful to add to the conversation, just stfu please.
I've got the same problem, files are 31 MB nomather what Jpeg setting i try
What devices are these? This works okay on my devices for Camera2 API, it may be an issue with the device (not supporting/handling the quality setting when using Camera2 API).
Hey Mark,
I'm working with a Samsung Galaxy A5 2017 (a5y17lte, Android API 28, PIE, OpenCamera v 1.48.2, Code 78), my files are about 31 MB in Size where it would be about 3MB without using Camera2 API.
Hope that helps! :-)
Thanks for the info. Just to check, these are both JPG files?
A known issue with Samsung devices is they seem to ignore the JPEG compression setting, but that doesn't explain why there is the different for Camera2 API. This doesn't happen on my Galaxy S10e.
What resolution is this? What about other third party camera applications (e.g., Footej uses Camera2 by default, Snap Camera HDR supports both APIs)?
I see the same issue, also on an a5y17lte running LineageOS 18.1. Camera2 API: 31 MB JPEG images at full 12 MP resolution in standard mode. File sizes are much smaller (2-3 MB) when I do any of the following:
- Change to original camera API
- Change output to WEBP
- Use any of the image processing modes (HDR, DRO, panorama etc.).
Somewhere I read a fix for it and now I remembered it (lost the settings because of upgrade...):
Just enable time stamps. And if you don't like them, keep the general time stamp option enabled and disable time, date, gps and address seperately.
Now the file size is at 2-3 MB again.
So maybe it is an issue related to time stamps?
hth! :)
Great workaround, thanks! I can confirm that this works for me on the a5y17lte with Open Camera v1.49.2. This seems consistent with the other observations that the file size is reduced whenever some image processing is requested: changing output type, applying HDR etc. or in this case adding a stamp to the image. Perhaps when only the original image is requested the compression gets skipped, otherwise it's done correctly?
Thanks for the info. The reason why this works is because it means the image is processed by Open Camera and then resaved as JPEG using the Android API (which respects the setting for JPEG compression/quality value). But by default, the JPEG is generated direct by the camera driver. On some devices it seems they ignore the JPEG compression setting (e.g., see https://sourceforge.net/p/opencamera/discussion/general/thread/1abb56eb/#ca68 for the issue on Samsung devices).
Also see https://sourceforge.net/p/opencamera/tickets/465/ .
Hallo,
i have same proplems on also on a5y17lte with LineageOS 18.1.
So do I understand correctly that there is no way of fixing this directly, but work around it by trading off speed since the timestamp thing will reprocess it and therefore respect the jpeg compression?