Skip to main content

Deciphering yet another mystery parameter - camera picture quality

I don't know much about photography and much less about image formats. The little I know comes mostly from web development. There I use images as semi-static assets, and I know how to work around the potential problems. 


That experience was of limited use when I worked on end-user-created images on a React Native app I'm working on. I needed a crash course into JPEGs. 


We use react-native-camera to take photos. Snapping one has an elusive option called photo quality. It is an integer in a range between zero and one, and in the example code, it was set to 0.5. Zero point five. What does that mean? Is that good? 0.5 does not feel that good. To me, a modern iPhone is more than 0.5? The default value is 1 though, is that better? I wanted to find out what turning that mystery knob entails.


Spoiler alert: the JPEG quality is clearly explained in the JPEG Wikipedia article, but obviously, I needed to jump through some hoops to understand that. I want to go through some generic thoughts on how to approach these kinds of voodoo configuration parameters. Perhaps it is a suitable default, but who knows, right? Taking photos is a core feature, so I want to set the quality properly.


Initially, without knowing anything about JPEG compression and quantization tables, numerous things were puzzling:


  • As said, the default is 1, but the example code sets it to 0.5
  • Quality 0.5 intuitively seems low to me? Is it something that was added to the example years ago and is now outdated? Is that a good-for-all or a not-worst-case-for-all type of default?
  • What happens if I change that. Is that platform-specific? Will it affect performance? Indeed it will affect the file sizes
  • If I set it too low, the photos look terrible, but we save on our cloud costs. If I set it too high, the photos look great but are slow to load, and we need to pay more to the cloud provider. 
  • Do I need to do some A/B testing with the mystery knob?
  • How can I explain to the next developer that the mystery knob should be set to a specific value?


Figuring out that 0.5 is indeed a perfectly acceptable value for the app was awkward. It involved watching a YouTube video about JPEG, Intense googling about quantization tables, glancing through a whitepaper, reading some Android documentation, extracting JPEG quantization tables from a couple of test images, and finally, reading the Wikipedia article, which would have been the obvious step to start with.


Although the example code works for us, I think the default is an unfortunate choice, and the example code works only for applications not requiring a decent image quality. I'll settle that my lumpish exercise was not in vain. Once again, a lesson in the dangers of copy-pasting code from GitHub (although it's fine for 90% of the time 😉). 


PS: If you want to produce a "good enough" JPEG, use a quality value between 50-100. Q=50, which is the standard, is considered nowadays low.


djpeg can be used to extract the quantization tables. The above one is for the color, the below for luminance.


djpeg -verbose -verbose -verbose image.jpg > /dev/null 

This is the "standard" compression (Q=50)

I pulled a random image from Instagram and looks like it had less compression which is expected from applications where the images are a core feature

I assume IG does something clever, but this looks something like Q=75

Labels:

Comments

Post a Comment

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro
Post a Comment
Read more

Extracting object properties from an IFC file with IfcOpenShell

Besides the object geometry information, IFC files may contain properties for the IFC objects. The properties can be, for example, some predefined dimension information such as an object volume or a choice of material. Some of the properties are predefined in the IFC standards, but custom ones can be added. IFC files can be massive and resource-intensive to process, so in some cases, it helps to separate the object properties from the geometry data. IfcOpenShell  is a toolset for processing IFC files. It is written mostly in C++ but also provides a Python interface. To read an IFC file >>> ifc_file = ifcopenshell.open("model.ifc") Fetch all objects of type IfcSlab >>> slab = ifc_file.by_type("IfcSlab")[1] Get the list of properties >>> slab.IsDefinedBy (#145075=IfcRelDefinesByType('2_fok0__fAcBZmMlQcYwie',#1,$,$,(#27,#59),#145074), #145140=IfcRelDefinesByProperties('3U2LyORgXC2f_hWf6I16C1',#1,$,$,(#27,#59),#145141), #145142
Post a Comment
Read more

Hubristic developer

Almost half of any Finnish generation goes through a shared experience: the conscript army. An integral part of that experience is learning military slang, a set way people in the army talk. The stories told with said jargon often spread outside of the barracks. It is not uncommon to hear strangers bonding together over beers reminiscing and feeling nostalgic about freezing cold nights spent in tents. There is a similar phenomenon detectable among us coders. To be part of the coder tribe, there is at least one type of story that one must master. That is - of course - ranting about legacy codebases. "Can you believe how much of a mess the previous coders left? Hear, hear!" There is no better way to onboard a new team member than to blame some previous B-team for all the murky parts of the system at hand. This can be seen as harmless, a subject for a good  meme . Rarely do we hold real grudges against "the legacy folk" and can be the best of friends in a social gather
Post a Comment
Read more