Support Forum Project Downloads FAQ Documentation About Demo Tutorials Blog Plugins
November 21, 2009, 06:00:34 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Private messages disabled
Caused by the massive abuse of the PM system in the past, the sending of personal messages has been disabled for all regular users on the Coppermine forum.
[more]
   Home   Help Search Board rules Login Register  
Pages: [1]   Go Down
  Send this topic  |  Print  
Author Topic: Uploading Big Photos in Large Quantities  (Read 480 times)
0 Members and 1 Guest are viewing this topic.
emperoradz Topic starter
Coppermine newbie

United States United States

Posts: 2


« on: October 09, 2009, 12:05:33 am »

We are running Coppermine + JUpload (latest version) on our Yearbook Server.

Here are our settings:
Max size for uploaded files (KB): 10000000000000
Max width or height for uploaded pictures/videos (pixels): 2048000
maxChunkSize: 2000
maxFileSize: 50000
maxNonTransformedPictureSize: 50000
pictureCompressionQuality: 1

We upload all kinds of photos (7MP, 8MP, 12MP, etc). The largest we usually upload is 12MP (7000-10000KB).
We want NO resizing and modification. Just plain uploads.

Now when we try to upload 100 or so 12MP files, it's fine. But when we try uploading 500 or so, after 127 it starts complaining that the files are too big, and we need to click OK repeatedly for the 400 remaining files.

Any way to turn off ALL warnings, turn of resizing of any kind, and let any picture through unblemished.

Also, when is metadata preservation coming....
Logged
Joachim Müller
Administrator
*****
Gender: Male
Germany Germany

Posts: 45051


aka "GauGau"


WWW
« Reply #1 on: October 09, 2009, 06:52:25 am »

We are running Coppermine + JUpload (latest version) on our Yearbook Server.
JUpload is a plugin that is not part of coppermine itself. It only get's supported within the very sub-board "cpg1.4 JUpload by etienne_sf"

Max size for uploaded files (KB): 10000000000000
Use settings that make sense: 10,000 TB is just plain stupid and might cause issues.
Max width or height for uploaded pictures/videos (pixels): 2048000
That's of course silly as well.
maxChunkSize: 2000
maxFileSize: 50000
maxNonTransformedPictureSize: 50000
pictureCompressionQuality: 1
Those are JUpload settings. I have no idea of their impact.

We want NO resizing and modification. Just plain uploads.
You don't even want thumbnails to be created? OK, that's an unusual setup.

Now when we try to upload 100 or so 12MP files, it's fine. But when we try uploading 500 or so, after 127 it starts complaining that the files are too big, and we need to click OK repeatedly for the 400 remaining files.
Happens when? Using JUpload or using coppermine's batch-add?

Any way to turn off ALL warnings
What warnings? Batch-add is an admin only feature. The admin should be able to live with some warnings.
turn of resizing of any kind
Sure: set the max pixel size for thumbnails and intermediates to the same value you have set your max resolution to.

Also, when is metadata preservation coming....
As far as Coppermine is concerned: as soon as the image libraries that Coppermine can use (GD or ImageMagick) will support meta tag preservation we'll add that feature to coppermine as well. We can't add features to coppermine that the underlying architecture don't have.

We have a strict "one question per thread" policy that you agreed to respect when signing up. Another policy says that it's absolutely mandatory to post a link to your gallery in each thread. And yet another policy says that you must have read the docs before being allowed to post on the support board. If you have issues with uploading (and as far as I am concerned batch-add is an uploading method just as well), do exactly as suggested in the docs, section "asking for support on upload issues".

If you have posted this in error on the upload sub-board and where looking for JUpload support only, say so in your reply, so a moderator can move your thread accordingly. Most of the recommendations posted above apply nevertheless though, as JUpload is using the server-side of coppermine.
Logged
emperoradz Topic starter
Coppermine newbie

United States United States

Posts: 2


« Reply #2 on: October 13, 2009, 09:41:30 pm »

Ah looks like I posted it in the wrong place. Can you please move this to JUpload?

Quote
Use settings that make sense: 10,000 TB is just plain stupid and might cause issues.That's of course silly as well.Those are JUpload settings. I have no idea of their impact.
Meant to be no limit, wasn't sure how to do it so just put 10 PB

Quote
You don't even want thumbnails to be created? OK, that's an unusual setup.
We do, we just don't want the original file to be edited.

Quote
Happens when? Using JUpload or using coppermine's batch-add?
JUpload, we only use JUpload

Quote
What warnings? Batch-add is an admin only feature. The admin should be able to live with some warnings.Sure: set the max pixel size for thumbnails and intermediates to the same value you have set your max resolution to.
Says size is too big so it won't be resized (JUpload warning)

Quote
We have a strict "one question per thread" policy that you agreed to respect when signing up. Another policy says that it's absolutely mandatory to post a link to your gallery in each thread. And yet another policy says that you must have read the docs before being allowed to post on the support board. If you have issues with uploading (and as far as I am concerned batch-add is an uploading method just as well), do exactly as suggested in the docs, section "asking for support on upload issues".
It's being a private network

Quote
If you have posted this in error on the upload sub-board and where looking for JUpload support only, say so in your reply, so a moderator can move your thread accordingly. Most of the recommendations posted above apply nevertheless though, as JUpload is using the server-side of coppermine.
yup sorry. Please move it to JUpload board
Logged
Joachim Müller
Administrator
*****
Gender: Male
Germany Germany

Posts: 45051


aka "GauGau"


WWW
« Reply #3 on: October 14, 2009, 07:27:16 am »

It's being a private network
Then there can only be generic advice: make sure that regular http uploads work as expected first before uploading with JUpload. Can't help you with JUpload issues, as I don't know/understand/use it, so I'm out of this thread. Bye.

It's being a private network
Then there can only be generic yup sorry. Please move it to JUpload board[/quote]Phill did as you suggested.
Logged
etienne_sf
Moderator
****
Gender: Male
France France

Posts: 798


WWW
« Reply #4 on: October 16, 2009, 03:37:57 pm »

Hi,

  I missed this message as I (apparently) get no alarm in my mail box, when a message is moved. Sorry for that.

Here are my answer, about JUpload :

We are running Coppermine + JUpload (latest version) on our Yearbook Server.

Here are our settings:
Max size for uploaded files (KB): 10000000000000
Max width or height for uploaded pictures/videos (pixels): 2048000
maxChunkSize: 2000
maxFileSize: 50000
maxNonTransformedPictureSize: 50000
pictureCompressionQuality: 1

We upload all kinds of photos (7MP, 8MP, 12MP, etc). The largest we usually upload is 12MP (7000-10000KB).
We want NO resizing and modification. Just plain uploads.

Now when we try to upload 100 or so 12MP files, it's fine. But when we try uploading 500 or so, after 127 it starts complaining that the files are too big, and we need to click OK repeatedly for the 400 remaining files.

Can you put here the JUpload debug output ?

 I never managed so many such big files...

Any way to turn off ALL warnings, turn of resizing of any kind, and let any picture through unblemished.

I don't know exactly about he Warnings.

To turn off resizing:
- Keep the parameter you've choosen
- Put in maxFileSize a bigger value, like you did for 'Max size for uploaded file'


Also, when is metadata preservation coming....

  You can preserve metadata. Go to the JUpload configuration page (parameter pictureTransmitMetadata). But you'll have to test if it's ok, with your configuration. With (apparently) recent camera, preserving leads to 'strange' colors. See one of the three head messages in this list (and vote for its correction ! see explanation there).


Etienne

Logged
Pages: [1]   Go Up
  Send this topic  |  Print  
 
Jump to:  

Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC
Page created in 0.085 seconds with 17 queries.