Project

General

Profile

Actions
Copy link

Bug #593

closed

Lossy jpeg compression result changes since 3.6.0 stable.

Added by Jan Schlamelcher over 11 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Jan Schlamelcher
Category:
Library
Target version:
3.6.1+
Start date:
2014-03-21
Due date:
% Done:

0%

Estimated time:
Module:
dcmjpeg
Operating System:
Compiler:

Description

While testing the dcmjpeg-warning commit (8ed8c53851531150c1e5102e5eb23c6aa5254004), I came across some files whose compression-behaviour changed since the stable release 3.6.0:

 /share/dicom/images/cabinet/cabinf01.dio
 /share/dicom/images/cabinet/cabinf02.dio
 /share/dicom/images/cabinet/cabinf07.dio
 /share/dicom/images/cabinet/cabinf08.dio

This is probably not a problem, since dcmcjpeg still creates valid files. However it seems that these changes are not intended and therefore should be investigated further.

Actions
Copy link
 #1

Updated by Jörg Riesmeier over 11 years ago

  • Priority changed from Low to Immediate
Actions
Copy link
 #2

Updated by Jörg Riesmeier over 11 years ago

  • Priority changed from Immediate to Normal
Actions
Copy link
 #3

Updated by Jan Schlamelcher over 8 years ago

  • Status changed from New to Closed

Could not reproduce the problem with a freshly compiled DCMTK 3.6.0 vs. #8ed8c5385. It was most likely a problem with how testing was performend or due to different compilers producing different output.

Actions
Copy link

Also available in: Atom PDF