I can do most of those types of things on a folder by folder basis. I don’t need to do it while importing and I would certainly not want to have an import as a requirement like LightRoom. If it was an option rather then a requirement I might support it , but I would be unlikely to ever use it.
Mark
It’s not a requirement in Lightroom either. You can copy photos to a folder and sync the folder later. Everyone has a different process.
Exactly. One of the (original) reasons I started with PL is that it does NOT require an import process.
John M
Yes, but this is so sluggish to use it’s unusable. My Laptop is not an old one either (Core i7, SSD etc), everything else is pretty speedy.
I will definitely skip the update to PhotoLab 6. Even if it costs 1 euro.
What would make me upgrade to PhotoLab 7 in a year could be:
The principle “what I see on the screen is the exported file” is a red line. If it is broken PhotoLab becomes useless to me.
You mean that the color profile isn’t set correctly in exported images on the Mac version? That has been fixed about a month
Core i7 itself doesn’t say that much, as there are 13 generations of Intel Core i7 processors. Heat often is a problem with laptops which results in throttling. But PL6 indeed is quite heavy on resources
You’re right of course, and it’s not the latest but I didn’t want to get into too much spec talk.* Most of PL5 & 6 operations are pretty quick when I’m using it and others are a bit slow but satisfactory, but I tried the “rotate while cropping” and it was the last time I will ever try that! I can’t see how anyone could think it useable. I was genuinely surprised at the way it worked.
* 10th Generation Core i7-10875H (16MB Cache, 5.1 GHz, 8 cores), GeForce RTX 2060 6GB GDDR6 + Max-Q
sRGB profile is still not attached when selecting sRGB in the export menu. Last tested on photolab 5.5 and Windows. I am specifically referring to the sRGB!
when I noticed (that is quite some time ago now – long before PL6 !) I exported with the custom profile
to overcome
while in PL6.0.1 Build 33 it is
@migo33 I also like DxPL for not having an explicit import function, having played with software that does while testing DxPL’s keyword handling in particular. But it does have an “implicit” import function which is used whenever a user navigates to a directory which is new (to DxPL) or contains new elements.
But the only edit template that can be applied is the one and only template defined in the ‘Preferences’ and that contains image editing functions only, i.e. no metadata handling whatsoever.
So now I understand what DAM functions you are referring to or rather what element of DAM functions you are referring to!
For those of us who value the “simplicity” and “freedom” of the implicit import process what is currently on offer is fine and we can select images to apply metadata updates to at our leisure, albeit the metadata ‘Templates’ on offer in Photo Mechanics are nowhere to be seen! The best that is possible is to make changes to an image and then copy it to other images, as appropriate!?
I don’t know if it will be possible for DxPL to ever have the assignment of metadata to an image on import because implicit import on discovery and explicit import with rules applied are difficult to reconcile.
But it would be possible to “not” import on the “discovery” of a new (to DxPL) directory and prompt for import or not, this would address the issue raised by some users of wasting space by adding a directory to the database every time a directory is “discovered”!
To that simple prompt could then be added an “import” function where an edit preset and a metadata template (preset), the metadata preset is arguably required anyway but doesn’t currently exist, could be added @Musashi at a (slightly) later stage!?
I don’t think that DxO envisaged DxPL to be a competitor for software with more advanced DAM functions, and definitely not a competitor for those that are “just” a DAM, but rather a product that could co-exist with those products.
However, adding metadata templates to a system that already handles edit presets is not “rocket” science, allowing the current discovery process to be interrupted to
Prevent database “clutter”, except someone (me) would suggest that they want the ability to wander around a directory without automatically importing the data and then suggest that they might want to be able to selectively import data as and when the “mood” took them!
To provide the ability to assign an edit template to the discovery (“import”) process from the introduction of that facility (the current process is useful but totally inadequate)
To add the ability to assign a metadata template to the discovery process, when they have been added to the product, for general use, in the same way as edit presets!
PS:-
Rather than changing the flow for all users add an option to enable the current automatic discovery (the default) or allow for selective discovery (maintain the existing options but allow for the introduction of new facilities/work flow etc…)
Implicit import has one major drawback in combination with DPL’s eagerness to instantly start calculating previews. This sucks up resources and DPL is quite a slug then… Most other apps handle import and preview rendering more intelligently.
The absence of reference to the sRGB profile in the exports is neither a bug nor a lack: it is the normal behavior, in accordance with the original standard (W3C/ICC).
The sRGB profile being the basic profile, any software capable of displaying an image must have this profile internally and use it… if it does not find any indication of another profile.
Whether the file to be displayed is tagged sRGB or there is nothing, it will always be displayed with sRGB. There is absolutely nothing to fear!
I use this way from PhotoLab2. But it is not good for new users who don’t have enough knowledge of color management. Judging by the forum posts few people understand color management.
Which sRGB profile? Nikon, Canon or Adobe? The truth is that no one is doing things right with regard to sRGB, because the “mistake” is small and unnoticeable. Now that you have a wide working color space, the poor color management in photolab starts to become visible. But instead of realizing first-class color management in PhotoLab, patches are still being made…
sRGB as such does not exist!
Do not mix PhotoLab’s color management (its working color space) and the colorimetric profiles that are assigned to a file for output.
When exporting an image, PhotoLab “translates” the colors from its workspace to the color profile requested for the output. It can be any of the ICC profiles listed by PhotoLab (common Adobe RGB, ProPhoto… etc. profiles), or any imported ICC profile (which assumes that you have the file for this profile).
The basic ICC profile (initially there was only this one) is sRGB IEC61966-2.1. Any software/hardware capable of displaying a color image will use this profile until it is told to use another one. It doesn’t matter whether the IEC61966-2.1 sRGB ICC profile is mentioned in the image metadata or not.
Note that there may be other ICC profiles that start with sRGB, such as Nikon sRGB 4.0.0.3001, etc. These are not standard sRGB profiles, and you will then have to import the corresponding ICC file into PhotoLab if you wish to export with such a profile (which is not of much interest, except in very specific cases).
Afterwards, I don’t follow you at all on your interpretation of “poor color management” in PhotoLab, but that’s just my point of view.
I just wish for crop and rotate it would stop going out of the original frame and giving me black borders if I shrink the crop size first and THEN try to rotate. Drives me nuts.
Welcome Jason
What you describe here is the result of a preset, standard or that you can customize.
The functions called by “1- DxO Standard” are, for the most part, corrections adapted to each of your photos.
Pascal
And why is the Adobe RGB profile embedded when the Adobe RGB option is selected in the export menu?
And for the whole color management in photolab - it’s mediocre! Whether you like it or not!
The conversion from one color space to another is done with what rendering intent? With black point compensation or without? Do you have control over this?
So much from me! I’m tired of explaining the obvious! Be happy!
I think this will be my last post on the subject…
Once again :
when exporting an image with the IEC61966-2.1 sRGB profile, it does not have to embed this profile in the metadata of this file, in accordance with the standard!
An extract from the CIPA standard for Exif:
"B. - Tags Relating to ColorSpace
– ColorSpace
The color space information tag (ColorSpace) is always recorded as the color space specifier. Normally sRGB (=1) is used to define the color space based on the PC monitor conditions and environment. If a color space other than sRGB is used, Uncalibrated (=FFFF.H) is set"
In the ColorSpace exifs (tag A001), any image file tagged “1” has an sRGB profile. There is no need to embed this profile in the metadata: it is sRGB calibrated!.
For all other color profiles:
In the ColorSpace exifs (tag A001), any image file tagged “uncalibrated” in the ColorSpace exifs is not sRGB calibrated. The profile must then be embedded in a metadata section “ICC Profile”
Extract metadata from a PhotoLab 6 output file (jpeg for example) read by Photoshop:
1 - With an sRGB profile:
<exif:ColorSpace>1</exif:ColorSpace>
Photoshop says:
<photoshop:ICCProfile>sRGB IEC61966-2.1</photoshop:ICCProfile>
There is no “ICC profile” section in the metadata! And there’s no need for it, Photoshop wouldn’t even read it).
2 - With a profile other than sRGB, Adobe RGB for example:
<exif:ColorSpace>65535</exif:ColorSpace> (65535 = uncalibrated)
Since there is an “ICC Profile” section in the metadata, Photoshop says:
<photoshop:ICCProfile>Adobe RGB (1998)</photoshop:ICCProfile>
And Photoshop will use the profile embedded in the Exif to correctly display the image.
(I won’t get into the color management discussion as the functionality isn’t fully complete. I do note, however, that the [perceptual/relative] rendering intent is already present.)
Wesh list
A réal rotating tool !!! Like LR
Can edit mask (erase part of mask) like LR
A powerfull and automatic sélection object (Sky, background, eyes, skin, legs, etc….like LR
For thé upoint, not only circle tool but ellipse. Like LR
A stiching tool for panorama. Like LR !!!
AND MORE NEW STUFF IN EACH VERSION. Not on l’y 3 or 4… like LR