Hi - this is great. It seems we are talking about different points. I am just noting what happens if you use “Send to” from PL to FP using “as shot”. In this case, you do end up with Wide Gamut.
When you said:
I thought you were talking about sending from PL8 direct to FP7. My bad.
… as elaborated from FP7 standalone (= exporting to application … or directly).
PL behaves correctly in this regard. It happens the moment you click Save, and the “original” PL export is overwritten by the (in this case, faulty) standalone version of FP7.
Let’s hope DxO fixes this bug. 
I think by "
you mean the process of going from PL to FP by clicking the “Send to” button?
If so. And IF we are talking about the use case I describe where the source image is RAW and is possibly tagged as AdobeRGB then FP behaves correctly. The source image does not have a profile, other than the DXO Wide Gamut and so this is the one used for the final export (Save As) from FP
This is not a bug. What other profile could it use in this case? Surely you aren’t suggesting it should use the AdobeRGB tag from the EXIF in the RAW file? (This may not even be here and is not a colour profile - just a memo saying that this was the setting on the camera when the shot was made, there purely for informational purposes). Maybe, you could argue it should just say “I don’t know and the user didn’t tell me anything so I’ll try sRGB”. IF you were to read some of my posts above you would see my comment about the message in the logs which suggests that DXO may have been thinking of that.
In summary.
RAW image opened in PL
Send to FP7 with “As shot” chosen (see screenshot)
Save As from FP (screenshot)
Resultant file has DXO Wide Gamut.
This is not a bug. It is a logical and reasonable choice. (Some posters seem not to fully grasp that Wide Gamut is just another space/profile even if it is primarily intended for working).
However - while it is a logical choice because of the message in the logs one can wonder if there wasn’t an intent in such as case to default to sRGB (which is what the logs say) and you could argue, I guess, that that would be a better choice.
So; the above flow is not a bug. But, I don’t really understand what you are saying. It seems to me that you may be talking about a different flow - and a bug you have discovered in that. But, I don’t really understand.
After reading your post several times, I have now edited my reply for clarity.
Your assumption
" … where the source image is RAW and is possibly tagged as AdobeRGB then FP behaves correctly. The source image does not have a profile, other than the DXO Wide Gamut … "
is misleading.
Most cameras can save their images in the AdobeRGB or sRGB color space. While this applies to the JPEG format, the OOC RAW file doesn’t have a color space.
PL’s internal working color space, neither “DxO Wide Gamut” nor “Classic (Legacy),” is also not adopted. – If this were the case, the “Classic (Legacy)” option would result in “AdobeRGB” according to this logic …
What you see is the RAW file in the (color-managed) representation for your monitor, based on the PL settings but without a color profile.
.
You can develop the RAW file in PL, apply a rendering from the FP 7 PlugIn,
then “Export to disk” and specify one of the available color spaces for your RGB output → as shown. And the color space is retained.
.
Unfortunately that’s not the case with “Export to Application” (used here for the sake of testing). You specify one of the available color spaces for your RGB output and then apply a rendering from FP 7 Standalone, which overwrites the specified color space and saves the final RGB output as “DxO WideGamut RGB” without asking (and any other option).
– That is not only completely wrong, but also causes additional work if you have to convert to a different color space again. –
To make it visible, rename the FP7 Standalone output before saving → as shown. Otherwise it happens in the background without noticing.
.
And when you open a supported raw file (or a RGB) file directly in FP 7 Standalone to apply a rendering, the same BS happens. FP 7 saves (or overwrites) the output as “DxO WideGamut RGB”.
.
In contrast, the predecessors FP 6 and 5 do not touch the specified color space and profile.
greetings, Wolfgang
