| Author | Thread |
|
|
09/07/2004 06:56:55 AM · #1 |
Some of the pictures I uploaded for challenges are actually heavier by a few kB once uploaded (this makes them bigger than 150k).
I am wondering why are pictures "inflating" on dpchallenge? I hope they are not decompressed on recompressed on the server side... |
|
|
|
09/07/2004 07:05:05 AM · #2 |
Originally posted by Gabriel:
Some of the pictures I uploaded for challenges are actually heavier by a few kB once uploaded (this makes them bigger than 150k).
I am wondering why are pictures "inflating" on dpchallenge? I hope they are not decompressed on recompressed on the server side... |
This should not be the case. What is the actual size (in bytes) of the file you are uploading, and what size is it when it gets to the server?
-Terry
|
|
|
|
09/07/2004 07:07:11 AM · #3 |
Originally posted by EddyG:
After the file is accepted, it is "processed". Any extraneous non-image markers in the JPEG (such as Adobe XMP data, EXIF data and color profiles that might be embedded) are removed via the 'jpegtran' utility to maximize browser compatibility. During this time, the image data is also losslessly recompressed, so it is conceivable that the JPEG file could actually get bigger by the 1-2% that we occasional see. |
Hope that helps :o)
|
|
|
|
09/07/2004 07:29:26 AM · #4 |
This is probably due to the difference in how "k" is represented. Technically, a "k" is actually 1,024 bytes. Sometimes, however, "k" is interpreted to represent 1,000 bytes. Thus, if your imaging program says your file is 147kb, where k = 1,024, this would be 150,528 actual bytes (147 X 1,024). I believe DPC would reject this file because it's beyond 150,000 bytes. The DPC limit of 150kb assumes a "k" is 1,000 bytes...
(Hopefully, my explanation isn't too convoluted...;-)
Edit: Re-read this after my morning coffee. Looks like I had it backwards, - but the "k issue" still holds, ...I think...?
Message edited by author 2004-09-07 08:51:20. |
|
|
|
09/07/2004 07:30:30 AM · #5 |
Originally posted by lenkphotos:
This is probably due to the difference in how "k" is represented. Technically, a "k" is actually 1,024 bytes. Sometimes, however, "k" is interpreted to represent 1,000 bytes. Thus, if your imaging program says your file is 147kb, where k = 1,024, this would be 150,528 actual bytes (147 X 1,024). I believe DPC would reject this file because it's beyond 150,000 bytes. The DPC limit of 150kb assumes a "k" is 1,000 bytes...
(Hopefully, my explanation isn't too convoluted...;-) |
Actually the DPC limit uses 1k=1024 bytes.
-Terry
|
|
|
|
09/07/2004 07:37:39 AM · #6 |
My submitted picture is 145 731 bytes. Once uploaded, it is 154 798 bytes.
As pictures are processed by 'jpegtran' on the server side, perhaps this program is making some pictures grow.
I hope that such 'increased' pictures are not candidates to DQ because of the size. |
|
|
|
09/07/2004 07:40:56 AM · #7 |
Originally posted by Gabriel:
I hope that such 'increased' pictures are not candidates to DQ because of the size. |
If the image gets as far as going through the uploader successfully, there's no reason for the SC to DQ it for filesize (ie anything done serverside is out of everyone's control).
|
|
|
|
09/07/2004 07:42:59 AM · #8 |
| Thank you for the clarifications. |
|
|
|
09/07/2004 07:51:37 AM · #9 |
I find I'm able to upload files as big as 152k usually and have them acceptable by the server. Must be the extra data that's stripped.
|
|
|
|
09/07/2004 08:46:09 AM · #10 |
Originally posted by jadin:
I find I'm able to upload files as big as 152k usually and have them acceptable by the server. Must be the extra data that's stripped. |
This prollly falls under the "definition of kilobyte" issue. to see the true size, right-click on the file and look at the properties. The size, in bytes, needs to be less than (or equal to) 150*1024 = 153,600 bytes. If so it will upload. this is because DPC uses the definition of kilobyte as 1024 bytes. |
|
Home -
Challenges -
Community -
League -
Photos -
Cameras -
Lenses -
Learn -
Help -
Terms of Use -
Privacy -
Top ^
DPChallenge, and website content and design, Copyright © 2001-2025 Challenging Technologies, LLC.
All digital photo copyrights belong to the photographers and may not be used without permission.
Current Server Time: 09/18/2025 08:18:52 AM EDT.
