I have privately written to Barbara, apologising for the “rant”, but when you’ve got a customer waiting for a print and you’ve just spent an hour, only to find that the work you’ve done has been lost, it sort of gets to you. Then there’s the recent total lack of response from Dx0, which even applies to the beta forums before they closed them down, which makes me wonder who has said what and to whom in DxO to alienate them from communicating with us.
Further news, I have just reverted to PL6 and this problem is exactly the same there.
@Barbara-S I don’t have time to make out a report on this at the moment. After another hour in PL6, I am now even further behind and will have to use Affinity Photo to go through this all over again.
Yes, but this is a different situation. In this particular case it’s very understandable why she’s so upset. She’s doing work for a client. If she had found this bug in the normal course of things, she likely would have presented it in the same fashion as other things she’s identified in the past.
Indeed, the first time, all I did was rotate the image in PL7 before starting to re-spot but, when that failed, I then rotated it in in PL6 and immediately exported a copy so that all I had was a “virgin” image
But, see my screenshot in the previous post - the offset is clearly visible.
Is this the only image you’ve worked with that is having this problem? Could it have anything to do with the small physical size of the scanned negative or the resolution?
I wonder if this problem is Mac specific. Since I’m on Windows , if there’s anything I could do to help you out, let me know. At this point I only have PL7 installed.
I may remind you of this old post, where it was already mentioned that local adjustments are not compatible with global image transformations.
When some of the users, including me, complained that this is a big misconception, many of you who are complaining now in this post, were defending this behavior, as one could ‘just work around it’, by doing any global transformations before doing any local adjustments.
If this behavior now also happens by simply zooming, then this is of course worse, however, I think the problem should be solved from its root once and for all. Me myself I was in the same position back then and pretty annoyed that I had to redo all my local adjustments, only because I wanted to do a simple adjustment of the horizon afterwards.
The post of mine which you linked to was in regard to the order in which geometry changes and repair masks need to be applied. I believe @Joanna is well aware of that issue and the current problem she’s having is somewhat different.
If you would like to send me it, I’ll be more than happy to see if I can recreate the problem in the Windows version. Perhaps you could message me with some specific instructions regarding what you wanted to accomplish, what you did, and the specific order in which you did them. Assuming that I have the same problem you had, I will also play with it to see if there is some sort of workaround.
I already PM’ed @Joanna with my test results but wanted to share them with others. I tested this issue in the Windows version of PL 7 with Joanna’s original tiff file and was unable to recreate the issue she was having. This may be a Mac only issue. Perhaps someone else using a Mac can try to recreate the results she was getting.
