Maybe I’m being ultra-simplistic but, to me, the answer is have “standard” directories for DCP, LUT and ICC files with import routines, rather than expecting PL to cope with no matter what path. if sub-folders are required, they should be added via a management functionality for adding, removing and moving.
The key is to take control rather than letting a user place such files wherever they want.
Yes, this is what I meant earlier by allowing profiles to be placed in a known directory. Just like presets and workspace descriptions and more, a directory that PL has on its search path for relevant files. A management interface is secondary IMO, but we shouldn’t have to hack dop files to move edits between platforms or hosts, depending on what editing features have been used.
There is an “Import DCP Profile …” on Mac (the Rendering dropdown; it’s a bit different on Windows), but there is no import, it’s just selecting the absolute path that gets written to the dop.
PL could even embed profiles in dop to make it trivial for the user (at the cost of duplication; not ideal if profiles are used extensively), but the current implementation is not portable by design, despite dop being documented as a means of interchange.
Now, this is definitely wrong because it “abuses” the word Import.
Yes, that’s correct. The path-name embedded in the sidecar/.dop file is not used by PL, but PL updates it to its “current” state.
John M