Roger, I am glad that I was able to bring some light to the subject. I'll try to shed some more. On Fri, Feb 20, 2015 at 1:06 AM, Roger Breton <graxx@videotron.ca> wrote: First, thank’s for the suggestion to change the *.dmxf to *.xml, to allow
opening the file under a browser. Sadly, that does not help change the presentation of the data (the nature of XML). Call me sentimental but I hate having to scroll the file up and down to find the data I am looking for? CIE XYZ values are stored at the beginning of the file while their corresponding RGB device values are at the end of the file. With PatchTool, I get the two served up under the same friendly graphic display. That’s an important value to me, Mark, since my time on earth is limited... I admit I have not looked at the CxF3 specs yet but, in order to decipher the DMXF format, for display measurements, at least, so far, one has to do a fair amount of “reverse-engineering”? Like, I find that “Measurement41” encapsulates the CIE XYZ for the monitor calibrated white point. But, if I search for the corresponding device RGB values, which should be RGB=255,255,255, nothing turns up readily? It’s not stored in the following piece of data but in a completely separate section, at the end of the file, in the “Target” section, as I said above. After I reasoned that the number “41” was the key to my search, it was a cinch to find the “Target41” entry and I was home free. There is a logic to the way the data is coded, no question, but it’s not for the faint of heart.
As the data is in the proposed ISO standard CxF3 format I would think that it would, or should, be accessible to a multitude of applications and in a 'digestible' form. I don't think it is intended as a working file in this 'raw' state. The fact that Danny's app already does this shows that he is, naturally, ahead of the game. The bottom line is it is NOT a proprietary format and therefore, no mystery. I have the documents from X-Rite detailing the spec if you would like some good bed-time reading. I believe they on X-Rite's website but haven't confirmed this.
The …/i1 Profiler/Display Measurements subdirectory does exist on my system, but it’s empty? I have not checked to see whether it was empty *before* calibrating my monitor but it sure remained empty *after* calibrating, with the exception, of course, for the file “sample-i1Pro.dmxf which is placed there by the installer. So, I am still not sure whether i1Profiler actually saves a copy of display measurements anywhere on the system other than in the resulting display profile? One has to drag and drop the profile onto the measurement icon, in i1Profiler, as Ethan pointed out yesterday, to actually force the software to serve up the data.
Profiler only saves the data if you tell it to. If you want your data to go into the appropriate folder, in this case, the Measurements folder, you just use the Load/Save option at whatever stage of the process you are at. Once I had located the folder through the i1 Profiler Load/Save dialogue it remembered the location. You can also drag and drop your saved data file (Measurement, Settings, Patch Sets...) into, or out of, the appropriate folder(s) where they can readily accessed by Profiler. As it was said earlier, you can 'export' file by simply choosing another location to save it to. If anyone can shed light on the Compare Profiles option at the end of the process it would be greatly appreciated. This was a great teaching tool in Profilemaker 5 and I thought I had used it successfully in Profiler. Some bugs have reportedly crept in as a result of updates so I'm not sure if it is a result of cerebral neurone atrophy or Profiler. Regards, Mark