- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In IPP 6.1.5 UIC samples, when Encoding or Decoding a JPeg2000 image, the param struct must be filled in.
One member is "precision", with values J2K_16 and J2K_32; for example "param_jpeg2k.precision = J2K_16".
I miss documentation for this parameter. What is it for, and what are the requirements and/or effects of using it?
One member is "precision", with values J2K_16 and J2K_32; for example "param_jpeg2k.precision = J2K_16".
I miss documentation for this parameter. What is it for, and what are the requirements and/or effects of using it?
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, for 8u images it is allowed and sufficient to use 16-bit precision for internal computations. For 16-bit images it is required to use 32-bit precision in internal computations.
Link Copied
7 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
this parameter control arithmetic precision of internal computatations. When it is J2K_32 it mean 32-bit internal computations will be used and when it is J2K_16 then 16-bit computations will be used where it appropriate. 16-bit computation path allow to reduce a little bit internal memory buffers size.
Regards,
Vladimir
this parameter control arithmetic precision of internal computatations. When it is J2K_32 it mean 32-bit internal computations will be used and when it is J2K_16 then 16-bit computations will be used where it appropriate. 16-bit computation path allow to reduce a little bit internal memory buffers size.
Regards,
Vladimir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, but I was looking for an answer as I wrote in my question; Since J2K_16 indeed is faster, and since it uses less memory, can I always use that, also for 16u images, without problems?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No. For 16-bit input data internal computations have to use higher precision to avoid artifacts. IPP JPEG2000 codec will ignore that parameter and force 32-bit computations in that case.
Vladimir
Vladimir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So, to conclude:
- For 16u images, is it a requirement to use J2K_32?
- For 8u images, is it sufficient to use J2K_16?
- For 8u images, is it allowed to use J2K_16?
This information is not available in the IPP samples.
- For 16u images, is it a requirement to use J2K_32?
- For 8u images, is it sufficient to use J2K_16?
- For 8u images, is it allowed to use J2K_16?
This information is not available in the IPP samples.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, for 8u images it is allowed and sufficient to use 16-bit precision for internal computations. For 16-bit images it is required to use 32-bit precision in internal computations.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks.
You could pass this on to your IPP Sample documentation collegues.
You could pass this on to your IPP Sample documentation collegues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sure. Unfortunately it is too late for IPP 7.0 release but weconstantly work onimprovement ofdocumentation.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page