Multiple Exports
Hey guys, when i export two sets of jpegs from the one job, at the same time, one at 250 DPI - 20 inches and one at 72DPI at 20 inches. The last export, 72DPI, changes the first export from 250 DPI to 72DPI. so i end up with two folders with 72DPI images, not one folder of 250 and one folder of 72. Hope that makes sense. It works in reverse also, what ever the last export DPI is changes the first exports DPI.
thanks in advance
thanks in advance
0
-
[quote="NNN634353534813473752" wrote:
Hope that makes sense.
No, it doesn't, not to me anyway.
Are you saying that exporting an image, say image_1234 to image_1234.jpg and then changing the dpi and exporting once more, then C1 overwrites image_1234.jpg? If yes, I think you may have inspected the same file twice, the second export should go to a different file, say image_1234_1.jpg0 -
yes exactly, but not into the same folder, two separate folders with different names.
so if i export, 1000 files at 250 DPI in folder called HIGHRES and then start a second export at 72 DPI into a folder called LOWRES, as soon as the second export starts the first folders files become 72dpi. so i end up with two folders at 72 DPI (in this example)0 -
That is strange. How are you checking the dpi value for the processed images?
C1 does not overwrite files on output - you cannot even ask it to. Given that you report that the dpi value for the previous export changes for all images as soon as you start the second it makes me wonder what could make that change so quickly and hence my question about how you are checking the value.0 -
[quote="NNN634353534813473752" wrote:
yes exactly, but not into the same folder, two separate folders with different names.
The way I read your post, you claimed that C1 changed the first exported image file. Knowing that C1 does not overwrite image files, that did not make sense to me.
Further, if your observation is correct, the first export and the second export that overwrote the existing file, did happen in one directory. That is why I did not bother with your different directories, they seemed irrelevant for the problem at hand.
I think you should answer IanL's question: How are you checking the dpi value for the processed images?0 -
[quote="NNN634353534813473752" wrote:
yes exactly, but not into the same folder, two separate folders with different names.
so if i export, 1000 files at 250 DPI in folder called HIGHRES and then start a second export at 72 DPI into a folder called LOWRES,as soon as the second export starts
the first folders files become 72dpi. so i end up with two folders at 72 DPI (in this example)
Please explain this "as soon as the second export starts" part.
Are you processing twice or are you selecting two recipes and processing them simultaneously?0 -
DPI (Dots Per Inch) is a printer term not part of file an output specification. 0 -
[quote="SFA" wrote:
DPI (Dots Per Inch) is a printer term not part of file an output specification.
Very true but there is a resolution field on the Basic Tab:
https://www.azuloxworkshops.com/educati ... exporting/
I took that to be where the value was set on output.
Of course setting that value doesn't really *do* anything so if that is the only change the OP is making between the two processing runs then they are not getting any actual difference between the two images.0 -
[quote="IanL" wrote:
[quote="SFA" wrote:
DPI (Dots Per Inch) is a printer term not part of file an output specification.
Very true but there is a resolution field on the Basic Tab:
https://www.azuloxworkshops.com/educati ... exporting/
I took that to be where the value was set on output.
Of course setting that value doesn't really *do* anything so if that is the only change the OP is making between the two processing runs then they are not getting any actual difference between the two images.
That's PPI (Or PPC or PPM).
The number of pixels that are expected to be used to create 1 inch of display, (or 1CM or 1 MM)
The pixels available depend on
[list=]The size of the original image file.
How the crop relates to that if a crop has been applied for any reason including lens correction adjustments in some cases.
Whether the process recipe (or Export) is to be allowed to scale up during the process. (I.E. Enlarge the image in Film Photography language and by how much).
[/list]
Knowing the target for Pixels Per [Whatever measure] allows C1 to advise the user how large the final output might be when presented as full (100%) export file size on, different screen sizes at their native resolutions, for different printers at their native resolutions, projectors at their native resolutions, etc.
If you need something smaller you may well simply allow the printer, projector or a computer's internal image presentation routines to shrink the image to fit at the device's regular resolution.
It that would be too small you might change the target PPI setting to see how far it would need to change (e.g. smaller PPI value) in order to give the size (via "Enlargement") required.
Which is basically what this section of the above quoted link is saying.
https://www.azuloxworkshops.com/educati ... rstandings
So one of the main useful uses would be to see what PPI (or DPI if you prefer but mainly for screens and projectors or referencing difference to a printer's native published DPI reference value) you would be working with if you export your processed and cropped image to a specific size (Dimensions of the required viewing medium).
Here's a link to a tool (one of many) and a supporting article that discusses this subject for both scanning and printing.
https://www.scantips.com/calc.html
One thing it seems to miss and that can be found in other tools, is to consider viewing distance and thus the additional question of optical acuity available to the person viewing.
One can find a number of such calculators available for mobile phones, etc.
HTH.
Grant0 -
ok so i should mention this happens across two different computers, i'm attaching a screen shot showing the moment the second export commences. (sorry i'm trying to find out how to attach this screen shot)
I'm checking the DPI in PS.
its like this,
one job - two exports (one at 250 DPI and one at 72 DPI to two different folders) When the second export starts the files in both folders become the same DPI, either 250 or 72 depending on what started first.
I can only export on job at a time. If i try export two jobs at the same DPI no problems, as soon as one job has a differnt DPI it change the DPI for all files/jobs.0 -
[quote="NNN634353534813473752" wrote:
ok so i should mention this happens across two different computers, i'm attaching a screen shot showing the moment the second export commences. (sorry i'm trying to find out how to attach this screen shot)
I don't know if "across two different computers" is significant or not, but then I am not sure I understand what you are saying. Do you mean that you confirm the issue on independent runs on two installations of Capture One, on two computers that has no shared image storage?
It is not possible to attach images to forum posts, you need to store images somewhere else and include a link in your postings.[quote="NNN634353534813473752" wrote:
I'm checking the DPI in PS.
its like this,
one job - two exports (one at 250 DPI and one at 72 DPI to two different folders)
I may be confused by "export". Where do you activate the job that exports twice? I ask because I wonder if you use Output (cogwheel icon), tick two recipes and click Process, or if you actually use Export (which is also a C1 function)[quote="NNN634353534813473752" wrote:
When the second export starts the files in both folders become the same DPI, either 250 or 72 depending on what started first.
How do you know that the exported files had one dpi value after the first export and that the export file was overwritten to have a different dpi value once the second export started? The C1-overwrites-an-existing-image-file does not make sense to me. You also export different dpi to separate folders. Not only does C1 write the second export to the wrong folder (the first), it also overwrites existing files in that folder.
C1 may have a bug. I think you should collect as much facts as possible in a report to the support team.
I can think of a bug that could cause a similar scenario as yours, but it does not fit your description "When the second export starts the files in both folders become the same DPI". That implies, to me, that the files had one dpi before the second export overwrote the files with a different dpi.
If, I say if, C1 has a bug that causes Processing to only pick up the dpi from one recipe in a chain of selected recipes, then all exported files will get that same dpi value. But then there is no overwriting, the first files does not change ("become a different dpi") once the second export starts, they are initially written with the wrong dpi value. And, all but one export dpi-folders would likely be empty. No, my guesswork does not fit your description.0
Post ist für Kommentare geschlossen.
Kommentare
10 Kommentare