YAAW - Yet Another Argyll Wrapper

[riclin]

Your points are totally understandable. It's no big thing to add some more placeholders to your script or to create some configs as starting points to experiment. At the moment I'm looking to find the best settings for the targets. More does not naturally mean substantially better.

That said, do let me know if you derive any additional target layouts that work for you without scaling adjustments and I'll update yaaw accordingly.

 

[rjanowsky]

Did some experiments with the target layouts. Short result: Normal users should be happy using the 440, 880 and so on layouts. Nothing special to obey, everything works as expected.

But for the enthusiast/perfectionist user it is possible to make a layout with 504 patches per page. Caveats: One have to use -L (no extra margin for the clip).

Measuring the target is easily possible (no scaled down patch fields), only the clip to hold the paper can't be used. Could be activated manually by the user in the config or automagically in the background by the script. No big deal to realize, but obviously quite exotic. See attached a json-config file.

 

[rjanowsky]

Just for info:

On macOS there are no man pages for Argyll (direct download from homepage or installed via Homebrew) available. One has to grab an Argyll package from a Linux distribution and unpack them from there into the man pages directory structure.

 

[riclin]

Just for info:

On macOS there are no man pages for Argyll (direct download from homepage or installed via Homebrew) available. One has to grab an Argyll package from a Linux distribution and unpack them from there into the man pages directory structure.

Interesting - I didn't expect that. I'll give it some thought ..... tx.

r/

 

[riclin]

Interesting - I didn't expect that. I'll give it some thought ..... tx.

r/

The manpage issue extends beyond just macOS - newer ArgyllCMS releases no longer include manpage helpfiles and Graeme has replaced them with html files instead. This means that they are no longer available via the *nix standard "man" command - and that their location is also uncertain since there is no assurance regarding the location that the Argyll download is unpacked.

Instead of relying on default repository locations and/or paths, YAAW now attempts to locate the ArgyllCMS download directory on startup:

• Use the complete Argyll toolset already on $PATH, when available.
• Otherwise perform a bounded search in likely locations, including:
  • ~/Argyll/Argyll_V*/bin
  • ~/Argyll_V*/bin
  • ~/bin
  • ~/.local
  • /opt
  • /usr/local
• Prefer the newest matching Argyll_Vx.x.x installation when several exist.
• Add the discovered bin directory to YAAW’s own process PATH.
• Retain the sibling doc directory, such as:
  ~/Argyll/Argyll_V3.5.0/doc
  
  The documentation buttons now follow this order:​
• Installed Linux manpage, verified with man -w.
• HTML documentation associated with the startup-discovered Argyll installation.
• Standard repository-style HTML locations.
• Official online documentation—but only after asking permission

Hopefully that fixes things. This update is beginning to stray a little further from KISS than I had hoped but in view of the Argyll distribution changes I'm unable to see an alternative. Any cleverness from others appreciated.

Link to modified version below:

https://drive.google.com/file/d/1SFqR6m1gtqR-TnVtydjk4b7NhyHiRaPR/view?usp=sharing

r/

 

[riclin]

YAAW Code Freeze

After a rolling set of fixes and updates, I am freezing YAAW for the moment and have set the current version at 3.40.0. This release includes all patches previously posted, and also provides modest improvements to the gamut viewing tool. I do not intend making significant changes to this in the immediate future unless a catastrophic bug is identified or suggestions regarding sensible improvements are received.

YAAW V3.40.0 currently resides at:

https://drive.google.com/file/d/1ztEu5FKSY9WmKexr1pI17UYLEjfGnw3L/view?usp=sharing

I will consider relocating it to github once it is known to be stable. In the meantime, feedback and comments are received with interest.

riclin

 

[rjanowsky]

• The documentation buttons now follow this order:​
• Installed Linux manpage, verified with man -w.
• HTML documentation associated with the startup-discovered Argyll installation.

Works for me on macOS. First test with manually installed man pages displays the man page for the command/tool. After deleting the man pages from the system the locally available html docs were displayed.

 

[rjanowsky]

Hi Richard, just out of curiosity. Why are you running colprof with Table resolution High (-q h), but not also the Low quality B2A table generation (-b) with high resolution. The default in colprof is low. Does it not matter or needs to much time or ...?

 

[riclin]

Works for me on macOS. First test with manually installed man pages displays the man page for the command/tool. After deleting the man pages from the system the locally available html docs were displayed.

Good. Probably best to not rely on the man pages even though I personally prefer that approach - but since they were abandoned at an earlier version, there's no certainty that they'll remain current with newer versions of Argyll. BTW - which Argyll version are you running Ron?

r/