Project

General

Profile

Actions

Bug #71825

closed

image rendering results in very hight file size

Added by Christian von Holten almost 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2015-11-25
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Hello,

I noticed a very strange behavior of image rendering. The file size of a compressed jpg, which is rendered by graphicsmagick is as much as bmp, but you can see some artefacts as well.

If I change the resulting format to png or gif, the file size is much less than the jpg.

I have done a workaround, but this only helps to fight the symptoms, not knowing the reason.

10 = FILES
10 {
  references {
    table = pages
    fieldName = media
  }

  renderObj = IMAGE
  renderObj {
    file {
      quality = 80
      import.data = register:imageURL
      maxW = 150
      ext = jpg
    } 
  }
}

This results in bad image quality and very high file size

10 = FILES
10 {
  references {
    table = pages
    fieldName = media
  }

  renderObj = COA
  renderObj {
    10 = LOAD_REGISTER
    10.imageURL.data = file:current:publicUrl

    20 = IMAGE
    20 {
      file = GIFBUILDER
      file {
        XY = [10.w],[10.h]
        format = jpg
        quality = 80
        10 = IMAGE
        10 {
          file {
            import.data = register:imageURL
            maxW = 150
          }
        }
      }
    }
  }
}

This ist my workaround.

Can anybody comprehend this behaviour?


Files

Actions #1

Updated by Mathias Schreiber almost 9 years ago

  • Status changed from New to Needs Feedback
  • Assignee set to Mathias Schreiber

What's the problem with PNG?
We're kind of stuck to what graphicsmagick renders.

Actions #2

Updated by Oliver Hader almost 9 years ago

Can you please attach one of those faulty big JPG images here?

Actions #4

Updated by Xavier Perseguers almost 9 years ago

Found: big file contains many XMP metadata.

Actions #5

Updated by Xavier Perseguers almost 9 years ago

Please check options [GFX][im_useStripProfileByDefault] and [GFX][im_stripProfileCommand] in Install Tool. What do you have? Are you currently stripping metadata?

Actions #6

Updated by Christian von Holten almost 9 years ago

I am using GM. Her are my settings from install tool:

[GFX][im_useStripProfileByDefault] = 1
[GFX][im_stripProfileCommand] = -set colorspace RGB

Actions #7

Updated by Christian von Holten almost 9 years ago

How can I remove all XMP metadata?

Actions #8

Updated by Xavier Perseguers almost 9 years ago

According to the help info, please try to change the stripProfileCommand so that it contains -strip as well.

Actions #9

Updated by Xavier Perseguers almost 9 years ago

@Christian, did it help?

Actions #10

Updated by Alexander Opitz over 8 years ago

  • Status changed from Needs Feedback to Closed
  • Assignee deleted (Mathias Schreiber)

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF