Print

[mikesalway]

Hi there

I love this plugin, however i've just noticed that images I've uploaded using the plugin are compressed!

For example:
If I use the native uploader, the images are placed in the userpics/10001 directory and the 3 files are created as normal (original/normal/thumb) - with the original being the same size as in my local directory (eg: 450kb).

If I use JUpload, the images are placed in the userpics/10001/16 (album number) directory, and the 3 files are created (original/normal/thumb), however the original file is now compressed (eg: 130kb).

Is there a setting for this? I have the jpeg compression setting set to 100% in the coppermine config.

I can't use the plugin anymore unless there's a way around this, because the compression is ruining my full-size images.

Thanks

[etienne_sf]

Hum,

  What do you mean by 'ruining my full-size images' ?

Is the compression of low level ?
Is the picture smaller ?

FYI, you check the JUpload configuration page. There are enough, I guess, parameters to fullfill your needs. For instance, JUpload has a specific parameter for picture compression.

One thing I'll do, in the future, is to have JUpload use the Coppermine parameter.

Etienne

[mikesalway]

Hi Etienne

Thanks for your reply.

By ruining, I mean yes - the picture is more compressed and shows compression artifacts. As photographers, we (well, most of us I guess) go to great lengths to ensure minimal jpeg compression artifacts in our images - especially when we upload higher resolution ones to our gallery.

I set the coppermine jpeg compression config to 100% because I didn't want any EXTRA compression taking place when I upload my images. I do all my jpeg compression in photoshop when I save the image as a jpeg in the first place.

I didn't realise there was an additional config setting in JUpload to set the compression quality. It seems the default is 0.8. I've now set this to "1" in my JUpload configuration and i'll test it again now.

It would be good to have JUpload use the coppermine config values for this, as it doesn't make sense to have to configure it in 2 places.

Cheers

[mikesalway]

hmm I just tested it using a setting of '1'.

It created a LARGER file than the original. I uploaded a 454kb file and now on the server, the file is 680-odd kb.

What I really want is to just upload the file with no change. I want to control the compression.

Of course i'm only talking about the fullsize image, and not the "normal" and "thumb" versions.

[etienne_sf]

I think the good parameter for you is 'maxNonTransformedPictureSize'.

  With it big enough, you can avoid any transformation by the applet before upload.

Etienne

[MarkRH]

You might also make sure that pictureTransmitMetadata is set to true so that it will not do anything with the image before uploading it.  With it set to false it was re-compressing my images and removing the Exif information they had at the same time.

[etienne_sf]

Oups !!   


  If the users explain to me how to use !!!!!


Thanks for the (right) comment.

Etienne

[mikesalway]

Thanks - I have set "maxNonTransformedPictureSize" to 4000 (? is this a good value?) and "pictureTransmitMetadata" to TRUE.

I'll do a test and let you know the result.

[mikesalway]

Ok, this is now solved as far as I'm concerned.

I just uploaded a 471kb image and it was 471kb on the server.

Thanks!