dual_sport_dork 🐧🗡️

Progenitor of the Weird Knife Wednesday feature column. Is “column” the right word?

I make knives now, too. Why not buy one at flightlessforge.com?

  • 67 Posts
  • 1.09K Comments
Joined 3 years ago
cake
Cake day: July 20th, 2023

help-circle

  • Correct. Just having the .icc file in hand doesn’t do anything for you, nor does the act of generating it with your calibrator tool. (Probably, anyway. Its software may allow you to apply it to your Windows color settings, i.e. in a manner that’ll affect the display of literally everything on your computer monitor. If so, don’t do that.) You need to load it in your image editing/viewing software so it can apply those corrections to your display output.

    One other thing to note here. ICM/ICC/whatever can simulate what an output device will produce (a printer or a press) or what an input device will give you (a camera or more likely a scanner) but only if your display is capable of producing a wider color gamut than your output device. It won’t do much for you the other way around.

    You’ll also have the fun of playing around with rendering intents once you have your ICC profile loaded. This is one of those things that fries everyone’s brain. It still kind of sends me for a loop.

    You’re probably going to want to start with a relative colorimetric intent to start with. Try that, and see if the output from your printer makes sense to you relative to what’s on the screen. If not, you can try switching to absolute colorimetric. For your application, perceptual will probably continue to produce out-of-whack looking results. I only use that for photographs.

    Bear in mind that your output in print will also be impacted by your choice of paper. “White” consumer paper is not actually optically white. Using your profiling tool and either of the colorimetric rendering intents you should be able to compensate for the whiteness or lack thereof of your paper also, but remember that any time you switch papers you’ll need to do another test print and create another output profile.

    In light of all of the above it’s no wonder normal people just declare the heck with it, use their editors inbuilt CYMK simulation profile, and console themselves with that being good enough.


  • Ah. Yes. Welcome to part of my world.

    This is a persistent, but more or less solved problem in the fields of professional graphic design and press, but home users are going to have a tougher time of it.

    TL;DR: You’re on the right track, here. There is a system for this called ICM — Image Color Matching. You need an ICM or ICC profile for your printer, which professional-ish image editing software will be able to load and use to tweak its display output in order to more or less match its appearance on your screen to the final output from your printer. This will come in the form of a .icc file.

    If you have a decent printer the manufacturer may have been kind enough to provide this for you as part of its software and driver package. If you have a professional class printer, they definitely did. If you have a cheap consumer printer, probably not.

    My considerably less than professional but not quite entirely dinkum Canon ImageClass laser printer did, and if I’m doing anything heavy duty enough that I really care about what its output looks like in print, I can use it in Corel to give myself a good preview and adjust my image edits accordingly. This process isn’t 100% perfect, but it’s a damn sight better than nothing. Having your monitor calibrated to begin with certainly helps, but your monitor’s calibration doesn’t actually have anything to do with the relationship between the colors it’s outputting to the colors your printer will output. Just, if your monitor is out of whack you’ll be chasing additional phantoms around and driving yourself nuts, because you’ll be layering one inaccuracy on top of another.

    If your printer doesn’t have an ICM/ICC profile available for it, your best bet is to hope that some dedicated nerd on the internet has produced one for it with a color profiling tool and made it available for you to download. Otherwise, you’ll have to buy or build your own color profiling tool to generate your own off of a test print. (I believe you said you had one.) A better cheap-as-free solution would be to use the ICM profile from a different similar printer of the same process (inkjet, laser, whatever) and resign yourself to the conclusion that it’ll have to be better than nothing.

    Part of your problem is probably your software. Whatever you or she is using to design and print has to support color profiles, and you’ll have to learn how to use them with that particular piece of software. I use the Corel suite and it makes it pretty easy for me, but that’s an expensive license that I didn’t personally have to pay for, so I kind of made out there. You actually can apply an .icc profile system-wide in Windows as a brute force approach, but this probably isn’t a good idea if you’re going to use that computer for everything else. Content that’s had its colors remapped to match a particular print device’s output are only going to look right in that particular context and will be out of whack compared to everything else. You probably don’t want to apply your printer’s ICC profile to your entire machine’s user interface and all webpages, for instance.

    Or maybe you do. I don’t know.


  • Yes, and the form controls included do not support mouse wheel inputs either unless you manually capture the events in your own code using the Windows API. This includes e.g. multiline text boxes in within VBA applications even as late as in Office 2016 which is monumentally irritating.

    But VB itself was certainly among the first modern IDEs. It wasn’t the first IDE in general, though. I think that was probably Turbo Pascal back in the DOS days which had its editor, compiler, and debugger (such as it was) all in one lump.




  • As much as we love to hate on bad old M$, Visual Basic had a rather feature complete IDE for 1991, including syntax highlighting. At minimum by the 5.0 release (1997) it also had function syntax hints and certainly built in documentation. You could even customize the editor window colors.

    Of course it had absolutely no code repository or version control capability whatsoever. It was designed with a one dude, one computer, one project paradigm in mind for sure.