dcmpsprt(1)
π dcmpsprt(1) β the OFFIS DCMTK girlies' guide to print jobs π
okay so bestie, welcome to dcmpsprt β it lives in the OFFIS DCMTK family and honestly? she's a whole vibe. she takes your DICOM images plus presentation states and turns them into an actual print job. iconic behaviour, no cap.
β¨ NAME β¨
dcmpsprt β read DICOM images and presentation states and render print job π¨οΈπ¦
πΈ SYNOPSIS πΈ
dcmpsprt [options] dcmfile-in...
π DESCRIPTION π
so the dcmpsprt utility literally reads one or more DICOM images and presentation states and creates a print job out of them. main character energy, truly.
the print job it makes is made of one Stored Print object plus one or more Hardcopy Grayscale images, and it gets written to the database that's specified in the config file. periodt. π
and if you want, the print job can optionally be spooled to the printer β in which case dcmpsprt calls the dcmprscu application, which is the one that actually handles the communication with the printer. so dcmpsprt is more like the manager, and dcmprscu does the talking. iykyk π«Ά
π§ PARAMETERS π§
dcmfile-inβ the DICOM image file(s) that are going to be printed. pass-if you want stdin, because sometimes that's just the move β¨
π₯ OPTIONS π₯
π general options π
-h,--helpβ print this help text and exit (the classic)--versionβ print version information and exit--argumentsβ print the expanded command line arguments-q,--quietβ quiet mode: print no warnings and errors. basically "don't talk to me" mode π-v,--verboseβ verbose mode: print processing details. she's telling you everything π-d,--debugβ debug mode: print debug information-ll,--log-level[l]evel: string constant β use levellfor the logger. the valid levels are(fatal, error, warn, info, debug, trace)-lc,--log-config[f]ilename: string β use config fileffor the logger
π¦ processing options π¦
+p,--pstate[p]state file: string β render the following image with presentation statep. heads up: this option can be specified multiple times (fr fr, stack 'em) π-c,--config[f]ilename: string β process using settings from configuration filef-p,--printer[n]ame: string (default: 1st printer in cfg file) β select the printer with identifiernfrom the cfg file. if you don't pick one, you get the 1st printer in the cfg file. defaults, slay π
π¨οΈ spooling options π¨οΈ
-s,--spoolβ spool the print job to the DICOM printer--nospoolβ do not spool the print job to the DICOM printer. this is the default, bestie π
πΈ film orientation options πΈ
--portraitβ set portrait orientation--landscapeβ set landscape orientation--default-orientationβ use the printer default. this is the default β¨
π trim (border) options π
--trimβ set trim on--no-trimβ set trim off--default-trimβ use the printer default. this is the default β¨
π¦ requested decimate/crop behavior options π¦
--request-decimateβ request decimate--request-cropβ request crop--request-failβ request failure--default-requestβ use the printer default. this is the default β¨
π print presentation LUT options π
--default-plutβ do not create presentation LUT. this is the default β¨--identityβ setIDENTITYpresentation LUT shape--plut[l]ut identifier: string β add LUTlto the print job--inverse-plutβ render the inverse presentation LUT into the bitmap of the hardcopy grayscale image--illumination[v]alue: integer (0..65535) β set illumination tov(incd/m^2)--reflection[v]alue: integer (0..65535) β set reflected ambient light tov(incd/m^2)
π basic film session options (only with --spool) π
β okay so these ones only work if you're spooling. just --spool things, bestie.
--copies[v]alue: integer (1..100, default: 1) β set the number of copies tov--medium-type[v]alue: string β set medium type tov--destination[v]alue: string β set film destination tov--label[v]alue: string β set film session label tov--priority[v]alue: string β set print priority tov--owner[v]alue: string β set film session owner ID tov
π annotation options π
--no-annotationβ do not create annotation. this is the default β¨-a,--annotation[t]ext: string β create annotation with textt+pd,--print-dateβ prepend date/time to the annotation. this is the default β¨-pd,--print-no-dateβ do not prepend date/time to the annotation+pn,--print-nameβ prepend the printer name to the annotation. this is the default β¨-pn,--print-no-nameβ do not prepend the printer name to the annotation+pl,--print-lightingβ prepend illumination to the annotation. this is the default β¨-pl,--print-no-lightingβ do not prepend illumination to the annotation
π«Ά overlay options π«Ά
+O,--overlay[f]ilename: string, [x] [y]: integer β load overlay data from PBM filefand display it at position(x,y)+Og,--ovl-graylevel[v]alue: integer (0..4095) β use overlay gray levelv. the default is4095= white π€
β other print options β
-l,--layout[c]olumns [r]ows: integer (default: 1 1) β use theSTANDARD\c,rimage display format--filmsize[v]alue: string β set film size ID tov--magnification[v]alue: string β set magnification type tov--smoothing[v]alue: string β set smoothing type tov--configinfo[v]alue: string β set configuration information tov--resolution[v]alue: string β set requested resolution ID tov--border[v]alue: string β set border density tov--empty-image[v]alue: string β set empty image density tov--max-density[v]alue: string β set max density tov--min-density[v]alue: string β set min density tov--img-polarity[v]alue: string β set image box polarity tov(NORMALorREVERSE)--img-request-size[v]alue: string β set requested image size tov(width in mm)--img-magnification[v]alue: string β set image box magnification type tov--img-smoothing[v]alue: string β set image box smoothing type tov--img-configinfo[v]alue: string β set image box configuration information tov
π LOGGING π
okay so the level of logging output β across all the command line tools and the underlying libraries β is something you get to specify. you're in charge, queen π
by default, only errors and warnings get written to the standard error stream. if you use option --verbose, you also get informational messages like processing details reported. option --debug gets you more details on the internal activity, e.g. for debugging purposes. other logging levels can be picked with option --log-level. in --quiet mode only fatal errors are reported β and in those very severe error events the application will usually terminate. π for more deets on the different logging levels, see the documentation of the module "oflog".
and if you want the logging output written to a file (optionally with logfile rotation), to syslog (Unix) or to the event log (Windows), option --log-config is your girl. that configuration file also lets you direct only certain messages to a particular output stream, and filter certain messages based on the module or application that generated them. an example config file is provided in <etcdir>/logger.cfg. π
π COMMAND LINE π
all the command line tools use this notation for parameters: square brackets enclose optional values (0-1), three trailing dots mean multiple values are allowed (1-n), and a combination of both means 0 to n values. easy.
command line options are told apart from parameters by a leading + or - sign, respectively. usually the order and position of command line options are arbitrary (i.e. they can appear anywhere). however, if options are mutually exclusive, the rightmost appearance is used. this behavior conforms to the standard evaluation rules of common Unix shells. so like, the last one wins β main character gets the crown π
plus, one or more command files can be specified using an @ sign as a prefix to the filename (e.g. @command.txt). such a command argument is replaced by the content of the corresponding text file (multiple whitespaces are treated as a single separator unless they appear between two quotation marks) prior to any further evaluation. quick note though: a command file cannot contain another command file. no inception, sorry π this simple but effective approach lets you summarize common combinations of options/parameters and avoids longish and confusing command lines β an example is provided in file <datadir>/dumppat.txt. obsessed.
π ENVIRONMENT π
the dcmpsprt utility will attempt to load DICOM data dictionaries specified in the DCMDICTPATH environment variable. by default β i.e. if the DCMDICTPATH environment variable is not set β the file <datadir>/dicom.dic will be loaded, unless the dictionary is built into the application (which is the default for Windows).
the default behavior should be preferred, and the DCMDICTPATH environment variable should only be used when alternative data dictionaries are required. DCMDICTPATH has the same format as the Unix shell PATH variable, in that a colon (":") separates entries. on Windows systems, a semicolon (";") is used as a separator. the data dictionary code will attempt to load each file specified in the DCMDICTPATH environment variable. it is an error if no data dictionary can be loaded. β οΈ
π§ FILES π§
<etcdir>/dcmpstat.cfg,<etcdir>/printers.cfgβ sample configuration files
π SEE ALSO π
dcmprscu(1)β the one who actually talks to the printer, bestie π«Ά
π COPYRIGHT π
Copyright (C) 1999-2026 by OFFIS e.V., Escherweg 2, 26121 Oldenburg, Germany.
and that's the whole page, bestie π this was Version 3.7.1, dated Sat Oct 17 2026 09:34:01 β go forth and print things, you absolute icon πβ¨π¦
π¦ where this page comes from
- arch rolling: dcmtk 3.7.1-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms