Search results

Basti - you may wish to look at how YAAW now addresses presets and runtime records - the current version is now pretty capable I think and hopefully also fairly well behaved (although nowhere as pretty as ChromIQ ;) ). It now incorporates: configuration presets per-project logging; JSON...

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.

Thanks Ron. Pleased to read your comments. The profcheck error improvements with the preconditioned profile are actually quite sigfnificant. Yaaw might not be beautiful, but it's simple to use and seems to work quite well. r/

Thanks for the suggestions regarding the higher density targets - very useful information. Don't be offended if I don't incorporate them per se into the current release - an unstated part of the "ethos" behind yaaw is that it provide a standard working framework (recent glitches notwithstanding)...

OK - the error was mine - I had misunderstood the difference between how targen processes no "-c" field vs "-c none". Having gone back to RTFM: with no -c option, targen uses its default device-space model; -c <profile> uses an ICC/MPP profile for preconditioning; -c none explicitly turns off...

Very interesting! Good find Ron. On reflection, I must admit that I found issues that I thought may have been related to the "-c none" switch too and in earlier versions of yaaw inserted a test that masked out the -c switch if no preconditioning profile had been selected. In a more recent code...

As I mentioned, the -S switch just reduces warning and error messages - it shouldn't actually impact the quality of the read per se. You might want to have a play with the most current version to which I have some default settings for i1 and 3p instruments - they generate useful looking targets...

20% IPA looks too much for long term exposure. I'd swap the IPA/PG ratios - i.e. 0 75% Aq / 20%PG / 5%IPA - or even leave the IPA out altogether: 80% Aq / 20% PG

-H - high res mode - chartread should use it if available for instrument else ignore it - switchable on the Config page - turn it off there -c - useful if you need to explicitly select the device - but that wasn't an issue for you was it? Harmless. -S - suppress warnings meaning there's reduced...

Yep - agree with your thoughts and observations. Although I'm reluctant to use the chartread -S switch - if a profile is going bad then I think I'd rather know about rather than being lulled into a false sense of security. YMMV. ;) Thanks for your comments. ChromIQ is looking good! r/

I have uploaded an update to YAAW which attends to several observations: 3.39.18 - Added wider, more readable YAAW confirmation/warning dialogs. - Added instrument-aware filename/profile naming: <printer>_<paper>_<ink>-Argyll_<instrument>_<patchcount> - Added editable Paper Size field with...

I should have noticed that you are using an i1Pro and not a Colormunki - sorry about that. As mentioned in my recent covering post, YAAW has been extensively tested with the CM - but until now, only a CM. You are breaking new ground ;) The issue here can only be the arguments being passed to...

Hi Ronald - welcome to ArgyllCMS ;) None of these are YAAW error messages or diagnostics - they come from ArgyllCMS. Something appears to be going wrong with your target generation. I suggest that you try again using the default settings. For testing purposes, use a single page 210 patch A4...

Hi Wim - I have prepared a zipfile containing 3 examples of profiles that were prepared using Turboprint, ArgyllCMS and my YAAW profiling wrapper. The zipfile also includes the runtime logs etc for each mediatype so you can explore them further. You can download it at...

OK - this REALLY is the last tweak for now ..... https://drive.google.com/file/d/1nw_oDuhwrpZWu9Klvw7Xk99bSBLYDz8t/view?usp=sharing riclin

Isn't it interesting/aggravating how many bug fixes and improvements appear the day after actually exposing software to the world? This is a jump to v3.39.12. It further attends to macOS idiosyncrasies by comparison with Linux. It also adds a dropdown selection box for the "Load Configuration"...

YAAW is updated to v3.39.6. Changes include - better compatibility with macOS environments - save / load config buttons moved to upper RH corner - Load Config now displays a list of available json files for selection - Argyll inconsistency in instrument selection corrected (p3 vs 3p)...

Hi Ronald - I expect that YAAW will deliver exactly the same profile as ChromIQ - assuming that both front ends pass the same arguments to the Argyll tools. And there's no doubt that ChromIQ looks more refined - if that works well for you, then YAAW will offer no benefit other than perhaps...

Thanks for the useful feedback Ronald. YAAW hasn't been previously tested under macOS so I'm encouraged that that was the only glitch so far. It resulted because macOS doesn't call terminal modes in the same way as *nix - something that surprised me as a non-Apple user. There was no macOS...

YAAW has received many major enhancements over the past few months, so I thought it may be useful to make the current version available to others. It does not in any way compete with the very excellent work undertaken by itsab1989 and his splendid ChromIQ. Rather, YAAW takes an alternate...