[quote name='Vieux loup' timestamp='1285500336' post='3245']Please someone show me the way from having the pics without any PP on my harddisc to being able to show my pictures efficiently and be part of the real world.
[/quote]
Ok. We skip the postprocessing itself since PP can mean anything from next to nothing to hours and hours of work. If you just want to show an image (that you have as tif/jpg-file on your harddisk) on the internet, there is not very much to do .. obviously, the keyfactor for both the uploader (you) and the downloader/viewer (me for instance) is the size of the imagefile that is created for this purpose.
The original file from your camera might have a pixelsize of 4500x3000 pixels (just to have some numbers) and the file on disk might (as a jpg-file) have a filesize of 4Mb up to 7Mb. ... obviously, you dont need a file that large (in pixels) to have a nice display on the internet. I usually limit filesize to what a normal display can show ... so I select 1200x800 pixels. This alone wil limit the resulting size in something below 1MB. The next thing is "jpg-quality" ... For the original file, you want this quality very high, but for a file to be displayed, a lower quality can be selected (you usually select this quality when storing an image in jpg-format) ... typical quality numebrs count from 0% bad to 100% good (or from 0 to 10 or 12) depending on the program you are working with. Selecting a quality of 92% rather than 98% can half the filesize of a jpg-file at times.
Reducing filesize by reducing the pixelsize and selecting a lower jpg-quality (which means a higher data-compression) leads to a certain loss in sharpness ... therefore I do a slight resharpening after the reduction in pixelsize. Then my final workflow to convert a file for display is like this:
- reduce number of pixels (but keep aspect ratio)
- resharpen a bit
- store as jpg with a reduced jpg-quality
By this I usually end up with filesizes around 200Kb which can even be transferred over a modem line in a relatively moderate time.
Just a last reminder for this workflow: ALWAYS WORK ON A COPY ... NEVER ON THE ORIGINAL.
In principle, every program that allows image manipulation is likely able to execute the tasks mentioned above ... I typically use IrfanView for this ... it is free, it does all I need, It has a nice batch-processor if I need the work done on a lot of files.
Hope this helps a bit ... Rainer
[/quote]
Ok. We skip the postprocessing itself since PP can mean anything from next to nothing to hours and hours of work. If you just want to show an image (that you have as tif/jpg-file on your harddisk) on the internet, there is not very much to do .. obviously, the keyfactor for both the uploader (you) and the downloader/viewer (me for instance) is the size of the imagefile that is created for this purpose.
The original file from your camera might have a pixelsize of 4500x3000 pixels (just to have some numbers) and the file on disk might (as a jpg-file) have a filesize of 4Mb up to 7Mb. ... obviously, you dont need a file that large (in pixels) to have a nice display on the internet. I usually limit filesize to what a normal display can show ... so I select 1200x800 pixels. This alone wil limit the resulting size in something below 1MB. The next thing is "jpg-quality" ... For the original file, you want this quality very high, but for a file to be displayed, a lower quality can be selected (you usually select this quality when storing an image in jpg-format) ... typical quality numebrs count from 0% bad to 100% good (or from 0 to 10 or 12) depending on the program you are working with. Selecting a quality of 92% rather than 98% can half the filesize of a jpg-file at times.
Reducing filesize by reducing the pixelsize and selecting a lower jpg-quality (which means a higher data-compression) leads to a certain loss in sharpness ... therefore I do a slight resharpening after the reduction in pixelsize. Then my final workflow to convert a file for display is like this:
- reduce number of pixels (but keep aspect ratio)
- resharpen a bit
- store as jpg with a reduced jpg-quality
By this I usually end up with filesizes around 200Kb which can even be transferred over a modem line in a relatively moderate time.
Just a last reminder for this workflow: ALWAYS WORK ON A COPY ... NEVER ON THE ORIGINAL.
In principle, every program that allows image manipulation is likely able to execute the tasks mentioned above ... I typically use IrfanView for this ... it is free, it does all I need, It has a nice batch-processor if I need the work done on a lot of files.
Hope this helps a bit ... Rainer