I use PO for three things
a- plot to A3 laser
b - plot colour pdf
c - plot bw pdf.
Very often the same set of files.
What is best workflow to do that?
Create three different pset-files, or use one pset and apply new print style all the time?
pros and cons?
Assuming all of the sheets in the set need to be printed the same way, my recommendation would be to use variable print definitions. There is a setting in Print Organizer Preferences to enable that mode, if you're not already using it. Create three print styles, one for each printing scenario. Use the same .pset file and apply the appropriate print style before printing. This is essentially the same workflow as Batch Print, except that you can re-use the list of design files without having to maintain multiple print sets.
If your sheets need to be printed differently within the set (i.e. page-specific pen tables, print level/reference overrides, etc.) then the choice between variable and fixed print definitions isn't as clear cut. Fixed print definitions (e.g. those for which you can override individual print properties outside of the print style) become more attractive, but end up forcing you to maintain different .pset files for each printing scenario.
.
I'll have to try that - I had been using different psets with the desired printstyles - but then, I'd have to maintain all three if we added or subtracted sheets. I did like the ability to take one pset and do a save as to make the next one.
Andrew
What you say makes very much sense.
But I need to understand that 'variable print definitions' and the difference between fixed and variable mode more.
I select some/all files to print and then go TOOLS>APPLY PRINT STYLE where I see print styles from my dgnlibs.
Applying a new style to some files doesn't take to long time.
I see the EDIT>PREFERENCES>> enable variable print definitions checkbox. But what is the difference?
regards / Thomas Voghera
A variable print definitition is very lightweight object -- it stores only the name of the design file, an optional model name, and the print style (which is required). A significant difference between a variable print definition and a fixed (e.g. traditional) print definition is that a fixed print definition always represents a single page. A variable print definition represents an unknown number of pages.
A fixed print definition has no memory of a print style, and does not require use of print styles. The actions defined within a print style are applied to a fixed print definition like a keyin script. In contrast, the print style is a fundamental, mandatory property of a variable print definition. Changes to a print style will affect variable print definitions the next time they are printed/previewed.
It was a challege coming up with names for the types of print definitions. It was felt that the "one print definition equals one page" characteristic was the most important, thus "fixed" vs. "variable". "Style-based print definitions" is another way to think of variable print definitions.
The workflow for creating fixed print definitions is generally this: Print Organizer spins up its background worker process, possibly using the user and project workspaces defined in the print style or manually-specified options. The design file / model is then loaded into the worker process and much state information is obtained and stored in the print definition. This includes information about all of the views, sheets, etc. If a print style is specified and it specifies fence search criteria, the worker process scans the DGN and may return multiple fixed print definitions: one for each matching shape. Control is then returned to the Print Organizer and you can see the results of any fence seach and adjust any of the print definition properties. Since each print definition contains full state information for its DGN, you can switch views, change the paper size, etc. and see all the other print definition properties adjust correctly and immediately. When time to print or preview, Print Organizer iterates the print definitions, loading each DGN in turn into the worker process for processing. So when talking about a multi-DGN print set, the complete fixed print definition creation / printing workflow requires two separate loads for each DGN.
A variable print definition doesn't contain any state data; the worker process is not needed or used when creating variable print definitions. So the creation step finishes quickly. Appying a new print style is also a quick process -- all Print Organizer has to do is iterate the variable print definitions and replace the print style name string for each one. No DGNs are loaded and no print properties have to be recalculated. When printing or previewing, Print Organizer spins up the worker process, iterates the variable print definitions, loads each DGN in turn and applies the print style. Depending on what's in the print style, this may produce one or more temporary fixed print definitions that are then printed before moving on to the next variable print definition. Thus for a multi-DGN print set, the complete variable print definition creation / printing workflow requires only a single load for each DGN.
If using a multi-shape fence search workflow, there is no opportunity to change the order in which the fences are printed when using variable print definitions. The order may be unpredictable.
Since variable print definitions represent an unknown number of pages, and contain little information, some Print Organizer features may not be used with them. For example, design script / pen table keywords that return the total number of pages. That number isn't known until the job is complete. Also print definition expression symbols that indicate the location within the set, for the same reason. The only symbols that may be used within an output file name expressions are those that draw from what the variable print definition contains: the DGN file name and optionally the model. Plus a Sequence counter that Print Organizer increments for every actual page processed.
When working with fixed print definitions, changing the printer is a big deal. Print Organizer has to iterate all of the print definitions, recalculating all the properties in the context of the new printer. This could involve changing the paper sizes and possibly disturbing the layout and other settings that you had previously defined. This leads to the best practice of maintaining different psets for different printers.
When working with variable print definitions, changing the printer is not a big deal, either manually or within a print style. There is nothing in a variable print definition that needs to be recalculated.
So fixed and variable print definitions have their pros and cons. In general, I think that variable print definitions are a good choice if:
- All of the sheets in the print set need to be printed in the same way.
- You don't need to manually tweak or even inspect the properties of each print definition other than the DGN file name and maybe the model name. Sheet definition workflows are ideal for this.
- You don't need to know the total page count on a per-print definition basis.
- All of the DGNs in the print set share the same workspace.
- You want to keep the list of DGNs in a single PSET and switch printers as needed.
It is always possible to convert variable print definitions to fixed print definitions, but not vice versa.
We plan to offer further improvements to the printing scenarios you describe in the next major release. If you are using sheet definitions, it will be possible to define the set of sheets outside of Print Organizer. You will be able to quickly select that set (or a subset) and print using a given print style (one of your three destinations for example). The limitations regarding the page count symbols and keywords will be removed. For your needs, you'll be able to focus on print styles, and may not need pset files at all.
wow, it will take some time to digest that!
Thanks.
Seems I will want to use 'variable print definitions' and keep it checked in the preferences.