I’ll create a brand new DOP later this evening and put that up. That will let us know if it was Mike’s DOP or a general fault
Hopefully you can set the button to toggle. Otherwise it will be very hard to hold in 2 buttons when needed.
I will call Nikon tomorrow and ask. I doubt this can be done, but hopefully their tech support people will know for sure, and if so, how to configure it.
My guess is I need to program the two buttons, one for action spot metering, and the other for center weighted metering.
No, starting FilmPack only starts the standalone version for those who are not using PhotoLab.
As long as you have activated FilmPack in PhotoLab it will work fine. You obviously have because you can see the + on the Contrast palette.
Being out over the weekend I’m trying to ‘catch up’ now …
Activate the Local Adjustments to see the list of corrections – in this case starting with Control points.
The next 2 screenshots show a Control line with settings for the background.
normal view → note the position of the picker
mask view → note the Chrominance & Luminance adjustments
Different to other tools, Control points and Control lines allow to choose how much Chrominance (colour range) and Luminance (lightness range) to include in the selection (mask) → Mask selectivity.
- Control points pick up the chrominance & luminance values from underneath the CP’s position
- Control lines pick them up from wherever you position the picker
- and both can be corrected w/ CPs and CLs …
The next screenshot shows a reversed Control point to (better) control the light fall off.
mask view → w/ Chrominance & Luminance set to “0” – the CP acts as a ‘pure’ radial gradient
I suggest to make a Virtual Copy of the version you want to check, activate the Local Adjustments globally, deactivate all of them in the list and re-activate them one by one to see the effect / to play with the settings.
have fun, Wolfgang
about help & tutorials …
- PL 5 – User Guide
- Control line - TuTo DxO
-
DxO Webinar: Editing Skies Using Control Points & Control Lines
( from DxO Webinars by @PhotoJoseph | PhotoJoseph.com ) -
DxO Webinar: Sculpting the light using U point with Dan Hughes - YouTube
( about the former version/s w/o Chroma & Luma settings – easy to understand the basics)
3 Likes
Thanks, Joanna - actually, this is the way I’ve been doing it for ages - it is the only way I know how to do it. Using a function-button sounded like an even easier way to switch back and forth between the two metering modes, but the standard way is adequate.
For me, it means lowering the camera, finding the button on top, and selecting what I want. I guess that’s just a habit I’ve developed. Knowing where this button is, is just about as useful as using a programmed function button.
If I remember correctly, I set the function button to an “artificial horizon” years ago, then forgot about it. This video explains how I learned most of my settings that I configured on my D750, including the function buttons:
Useful settings for D750
Thanks for the reminder.
I closed PhotoLab.
With Finder, I went to the folder for this image, and deleted my .dop file.
I downloaded your new .dop file to my downloads folder.
I moved it into the image folder.
For reasons I don’t understand, it got renamed to "MM2_0295 | 2022-04-15.nef-2.dop
So, I deleted the file from the folder (moved to trash), then emptied my trash.
As expected, it downloaded with the correct name, no “-2”.
I copied the file, and pasted it into the image folder, and it did not get renamed with the “-2”.
As a test, I deleted the .nef file from my image folder, emptied my trash, then dragged the file from my downloads folder to my image folder. Again, it was moved properly, without being renamed.
I am lost as to why this happened, as it seems like having the old file in the trash somehow might have caused the replacement file to be renamed with a “-2” the first time I tried this today. I don’t know why this happened, but from now on, I’ll be careful to verify that the file name doesn’t get changed when I move your file into my image folder.
I re-opened PL5, went to this image, and only saw what looks like my original edited image, completely with my watermark. When I click on the comparison window, it says “no virtual copy” and it shows the two versions I had saved.
So, I closed PL5 and deleted my two images from the PL5 Exports file. All I have left are my original image and your new .dop file.
Restart PL5, and I see my edited image with my watermark, which can’t be from your .dop file as the watermark should be gone.
So, I close PL5, and delete the .dop file, and empty the trash, which I’m sure I don’t need to do. I then re-open PL5, and as far as I know, there is no more .dop file for this image in the folder, so I should see an un-edited version of my image.
Nope, it shows my edited version. At the top of the PL5 page it shows:
It has a (M) at the end, meaning this should be a Master image, meaning there might be a virtual image somewhere?
OK, I moved the .dop file to the trash, closed PL5, and re-opened PL5. Of course, it still shows my original edited image with the (M) and my watermark.
How can I “reset” this image in PL5, so all it shows is the original image, with no editing? Until I can do that, I’m just spinning my wheels. Is there a button I can select to force PL5 to go back and show the original?
As a test, I copied the image to a different folder, and renamed it with an “x” at the end of the file name, then moved this renamed file back into the original image folder. PL5 should see it as a brand new image it doesn’t know about. That worked. Presumably, I can rename Joanna’s .dop file using the same “x”, and PL5 would open my new image using Joanna’s settings, but right now I’m more interested in fixing what’s broken in PL5 - why does my original image show up with my old corrections, when there is no .dop file ??
You will need to delete the database files for PL5, otherwise, everything gets mixed up.
Oops, what database files am I supposed to delete? Maybe I should just write this image for as “lost”, and delete it. I have my new copy with the “x” added at the end. I think that is better than getting involved in the database.
If you agree, does PL5 have a tool for me to delete the original file from within PL5, so its database will know the file has been removed?
This sounds like a big problem with PL5. I have no idea as to how it got confused, but apparently that might even be why the “.dop” file developed the problem people have found?
If I open the original file in PL5, as I just did, and turn off “watermarking”, my watermark goes away. Is there a setting within PL5 to “reset” the image to its original settings as imported, with no changes from PL5?
…I did it the hard way, turning off every correction I made. I then made a virtual copy, which looks identical to my test photo from the original file, with the “x” added to the file name. So, if I close PL5 and copy your .dop file into the folder, maybe my VC, or the original, will recognize your changes?
Assuming you don’t use either projects or history in PL5, these three…
If you are not happy deleting the database, in theory 
if you copy the RAW and DOP files to somewhere else, go into PL and delete the original files from there, then close PL, replace the files and restart PL, all should/might be well.
I wish I lived in Theory, everything seems to work there 
1 Like
In theory, there is no difference between theory and practice, but in practice there is. 
3 Likes
I guess I’m not really into theory, or practice, and I’m certainly not happy deleting a database, so I cheated. I went to the file, and created a VC. It seems like I can edit that VC if I wish to, maybe all I need is one nice photo of these non-mountains, and while I intend to tone it down a little, I’m pleased with this one too:
https://forum.dxo.com/uploads/default/original/3X/d/f/df825f2ee9b733da16e67bc35d02a6ccb679a53f.jpeg
I find it difficult to accept that I never got a good photo of the mountains with snow on top. I’ll go through my images once more, for the whole trip, but I think it’s time for me to move on.
I neither use them, nor know what they are or do.
There are databases and there are databases. In this case, DxO’s database is primarily used as a cache to speed up certain processes like searching.
The problem is that it is also used as a duplicate storage for everything that is found in the DOP files and this is where problems have been occurring for quite some time now.
If you move stuff outside of PL5, the database can get out of sync with the DOP files and PL attempts, very badly, to reconcile those differences.
The database is only relevant as a long term storage mechanism if you work with Projects, which allow you to assemble links to your photos about a particular topic or theme. Essentially the same as the idea of Albums in Apple’s Photos app.
If you delete the database, PL will reconstruct it from the information held in your DOP files and you will have lost nothing, apart from the problems you have been encountering.
There are several of us in these forums who regularly delete the database - one even has a script that does it automatically every time they open PL. You have chosen to automatically generate and read DOP files and that is all you need - but, at present, the database has gotten confused and is now starting to corrupt some of your DOP files - simply delete it and normality should be restored.
1 Like
Sigh… The only thing I want to use PhotoLab for, is an image editor. If I ever want those other functions, I will use Photo Mechanic. So, as I now understand it, to be able to do other things with my images, PhotoLab’s database is fragile. Instead of storing the information about my photos in the .dop files, as I have come to expect, it is ALSO storing that same information in a database that I have no need for.
If you point me at the directions on how to safely delete the database, I guess that’s my best option. However, from what you’ve written, PhotoLab ought to have a setting about whether or not to maintain the database, where I could de-select it.
(I started with PL3, then upgraded to PL4, and then to PL5. Lots of time for PhotoLab’s database to create errors. …and it might be because I copied the folders with my Colorado photos from my MacBook Pro to my desktop Mac Mini. Who knows if that was safe to do, but I didn’t know any other way, and it “should have” been safe, right? 
)
The problem seems to be that some folks swear by the database, other just swear at it 
1 Like
Don’t forget some people who would like to work with a database – as soon as it is close to reliable instead being a way of trying to hurt nobody, going for sidecars, editing sidecars and a weak database on top of it. I think, DxO should just cancel the options for projects, they cause more anger and troubles than they ease up life.
I have created a VC for the specific file we are dealing with, and I’ve done some deleting. Maybe I can simply ignore this for now. I made a VC from the original file, and if I need to, I can re-edit it, using what I’ve learned here.
I have no interest or curiosity as to what “Projects” is, or was, or does. I plan to just use PL5 for editing, and also for discussions in the PL Forums. I think I can just forget this whole incident, pretending it was all just a bad dream. I eventually plan to use Photo Mechanic to keep track of my files, but I haven’t even started to investigate that yet. I don’t do much with Albums in Apple Photos either.
I’ve got another potential issue or problem - when I travel, I take my laptop. My current plans are to copy those photos to my Mac Mini.