No
Yes, it's not simpler and it's not how the DNG container was designed
it has nothing to do with DNG container - just like DNG container was not designed for ACR/LR to pickup profiles from certain folders and not from others - this design decision is about the converter, not about DNG container - note that nobody is saying that you shall not be allowed to store your profiles in DNG files if you want so... however the implementation as usual is half done by Adobe - how about removing profiles or otherwise manipulating stored profiles from/in DNG files using standard Adobe tools ? yes, exactly...
(we've found a bug) and it's not what the OP, I and other's want!
congratulations with a bug if it is a bug, I and others want to be able to (_also_) use profiles stored with the same folders where raw files are
Imagine rendered images without the ability to embed an ICC profile.
absolutely, but the purpose of "raw" files is have a flexibility in "rendering" (conversion with whatever profiles I want), purpose of "images" (all quotes intended) are exactly to disallow that uncertainty about the color profile defining the color spaces in which color coordinates are... you, as usual, trying to obfuscate.
Awful! The same is true for those of us that wish to use the DNG container as designed.
as noted DNG container design has has nothing to do from which folders/catalogs ACR/LR pickup profiles - and it is also designed to store icc profiles - so why am I not able to do this using ACR/LR... the container was designed to be store them
, was it not ?
I have to ask you, do you even use a DNG workflow?
and I have to ask you if you even understand what it is ?
Do you actually realize the raw files and the DNG camera profiles don't reside in the same location and many of us want them to do so, by having them inside the DNG?
you even realize that some people actually want to keep raw files and relevant profiles in the same place ? and that those people do not try to impose their ways on you, but as usual display your arrogance by claiming that only your way is the right one ? get yourself a mirror and take a look in it.
The facts are, some of us have multiple machines and don't want multiple DNG profiles separate from the images that require the profile or it gets substituted and that greatly and incorrectly affects it's image appearance.
fact is that LR being not an enterprise solution still relies on raw files, profiles and LR catalogs being available through a regular filesystems... and there is also ACR (which you in your usual arrogance tend to forget) - so many of us have multiple machines, do not use LR and still want profiles to be kept along with raw files when we need that (which also helps us with our backup & sharing strategies), at the same time not wishing you to change your ways... again how about stop pretending to be the only righteous guru here ?
The facts are, the DNG container should allow us to embed this important data directly into said container. It's simpler (for us at least), cuts down in possibly missing files and ensures the raw and profile stay together.
the fact are, the converters (LR/ACR) shall allow us to use profiles how users want them to use, specifically those who do not wish to use DNG files at all.
There's no logical argument other than LR6 should do what it was designed to do with respect to DNG camera profiles and embed them into the container.
there are many that it and ACR also shall allow profiles to be stored along with raw files.
PS: I want to reiterate that by no means I wish you to lose the ability to store your profiles in DNG files... however the more simple solution is to (also) allow to store profiles per catalog (even for LR users keeping everything in LR catalogs to store them there)...
