Originally Posted by Soulnight
For point 2, Anna thinks she found the issue. Somehow we did not see the issue in our own testing earlier.
So please try the attached version V2.8 of our madmeasure dynamic clipping tool.
Skipping files seems to be fixed in 2.8, thanks!
I'd like to keep using my batch file for now as it supports various folders plus it seems it's the only way to both get a progress of the measurements and to get a copy of MadVR's output file. Apart from its content (which is in your log), I found this useful to have in a separate file, at least for debugging, because it gives me a timestamp of the original measurements. That way when/if something goes wrong, I know if the measurements file is the original or one of yours.
So I have a few requests, namely to support the following command line arguments (these are examples, of course use whatever you prefer):
1) path to the folder to scan
2) /measure for automatic start of measurements scan, of the saved folder or of the folder specified in the command line when present
3) /delete to delete all the measurements files (including your _details.txt)
4) /restore to restore the original measurements and delete the original folder
5) auto-exit when the measurements/delete/restore are finished if launched that way (with parameters in the command line)
At the moment I'm calling your utility at the end of my batch file, I'd like to call it with the following arguments after each share scan instead:
madMeasureDynamicClipping.exe U:/@MadMeasureHDR /measure
It's fine if it only supports one path in the command line, but I guess it could support more than one switch as long as /measure is always done last.
I assume this should be easier to implement than multi-paths support within the utility itself and it would be more powerful/flexible for power users
Also please could you:
6) When MadMeasureDynamicClipping.exe is defined as the default app to open .measurements files, open the file that called it when double clicking on it. At the moment double-clicking on a .measurements file opens the utility but does nothing.
7) store the settings in a separate file or in the registry, so that when we update the utility we don't have to re-specify all the settings (path to MadVR, folder to scan, algo to use, etc)? That will make updating easier/faster and will limit the risk of errors. I often start scanning files with the manual/default algo after an update...