Thank You to Those Who Helped with My Milky Way Image

Processing Play Raw
1

I want to thank those who took time out of their busy days and helped me by editing my Milky Way image.
@priort / @gigaturbo / @Thomas_Do / @martin.scharnke / @Jean-Marc_Digne / @Popanz / @age / @dqpcoxeas
Apologies if I missed someone who provided an answer.

I’ve been trying to find a way to “capture” the information from the XMP files, or from DT interface itself to follow the workflow/settings you provided. From this post, Direct reading of an XMP file, I learned the numerical settings within each module are coded as hexidecimals in blobs.

  • I tried decoding/converting the hex numbers but this proved futile.
  • I attempted catalouging screenshots of each module in DT. But this was also futile when graphs, instead of sliders, were used in modules.Ex: color zones and tone curve.
    :confused:

I code using Splunk to find fraudulent transactions for a living, plus I have somewhat of a background in progamming (SQL & XML), though not to the exent of the sharp developers here. I tried to create a macro in NotePad++ for listing out the modules used in an XMP file, however, I am unable to find the macro on my PC and post here.
Therefore, here are the steps, and maybe a dev here can create and importable/editable macro for NotePad++. If you notice I have missed a step, please let me know.

  1. Start NotePad++.
  2. Open the XMP file you want to copy the history stack.
  3. Open a new file.
  4. Go back to the XMP file.
  5. Place cursor at top of XMP file.
  6. Click Search / Find (or CTRL+F).
  7. Enter .+darktable:num= in Find what: text box.
  8. Click Find All in Current Document button.
  9. Click in the Find Results panel.
  10. Right mouse click and Select all results (or CTRL+A).
  11. Use SHIFT+right arrow to remove file name and line from the highlighted text to copy.
  12. Copy CTRL+C.
  13. Click tab new file from step 3.
  14. Paste CRTL+V.
  15. Click tab for your original XMP file.
  16. Right mouse click the Find Results panel and select Clear All.
  17. Click Search / Find (or CTRL+F).
  18. Enter darktable:history in Find what: text box.
  19. Enter .+darktable:operation= in Find what: text box.
  20. Click Find All in Current Document button.
  21. Click in the Find Results panel.
  22. Right mouse click and Select all results (or CTRL+A).
  23. Use SHIFT+right arrow to remove file name and line from the highlighted text to copy.
  24. Copy CTRL+C.
  25. Click tab new file from step 3.
  26. If needed, add a line after your last paste press Enter
  27. Paste CRTL+V.
  28. Right mouse click the Find Results panel and select Clear All.
  29. Click in the top panel (where you have been pasting).
  30. Click Edit / Line Operations / Sort Lines Lexicographically Ascending.
  31. Click Search / Replace (or CTRL+H).
  32. Enter \tLine \d+:\s{7} Find what: text box.
  33. Click Replace All button.

BTW, the numbers in your final list, darktable:num= , are offset by negative one.
Ex.: darktable:num=“0”
** darktable:operation=“mask_manager”**
Is listed as 1 in the history stack .

Thanks and God bless,
Genesius :pray: :camera_flash:

4 Likes
2

Maybe this will help…

The author I believe is @criadoperez

1 Like
3

@dqpcoxeas
Is there an English translation available? My Espanol is not what it once was (40 years ago). :rofl:
Thanks and God bless,
Genesius :pray: :camera_flash:

4

If you hover on the modules in the history stack you get a popup that shows there values. Maybe the code that provides that data could be leveraged for your purposes…

1 Like
5

Thanks @priort
I tried some of it is very hyroglyphic and difficult (but not impossible) to capture as screenshots. Especially, when a mask is involved.
God bless,
Genesius :pray: :camera_flash:

6

I would just walk up through the active modules from bottom to top and look at each one. You can either disable a certain module or reset it and then use ctrl z to bring it back to see what the user settings are doing. Many edits won’t even transfer well to another image so really it’s best to just see what tools were used and what general impact they had on the overall edit. There is rarely a magic setting of 22 percent of some slider in some module that is a key to another edit but rather what sliders were used and relative proportions maybe to impart a desired change…

2 Likes