1000128900 2015-11-17T08:52:27-05:00 Aspen, Beech family of printheads from Memjet. Navigator supports multiple printheads on a press. 1000220978 false Aspen Documentation 4 2016-09-16T10:44:57-04:00 1 1 2015-11-17T14:43:55-05:00 0 0 General documentation on the Navigator Aspen system is attached below. Updates and supplements are available on this site in this directory. The manual for the RIP and for the workflow Server are here. Some videos to help you with basic Navigator usage are here. <p>General documentation on the Navigator Aspen system is attached below.</p> <p>Updates and supplements are available on this site in <a href="http://help.xitron.com/solution/folders/1000220978" target="" style="line-height: 16px;">this directory.</a></p> <p>The manual for the RIP and for the workflow Server <a href="http://help.xitron.com/solution/articles/1000216352-navigator-rip-and-workflow-documentation" target="_blank" style="line-height: 16px;">are here.</a></p> <p>Some videos to help you with basic Navigator usage <a href="http://help.xitron.com/solution/folders/1000218906" target="">are here</a>.</p> 1000220978 69 1000216346 2015-11-17T15:00:35-05:00 1003593276 1 2 0 0 Aspen Documentation 2016-12-02T10:08:07-05:00 1003593276 1 2016-09-22T11:26:39-04:00 0 0 Requirements:  Memjet r10.2 and Xitron r8. It is possible to achieve super dense blacks by printing the black channel with two black printing blades. Once you configure the system correctly, it is automatic. Configure your print engine with CMYKK inks (See Memjet documentation for any ordering requirements).  Make sure both black blades register themselves with the same name: "Black". When this happens the Xitron system will notice.  We will then deliver the black channel to both Black blades.  It will be ripped once and duplicated on both blades. This method can be used to double print any CMYK ink.  As long as there are two ink blades registering themselves with the same name then the Xitron RIP will deliver that ink channel to both of those print blades. <div dir="ltr"> <div dir="ltr"> <p>Requirements:  Memjet r10.2 and Xitron r8.</p> <p><br></p> <p>It is possible to achieve super dense blacks by printing the black channel with two black printing blades.</p> <p>Once you configure the system correctly, it is automatic.</p> <p><br></p> <p>Configure your print engine with CMYKK inks (See Memjet documentation for any ordering requirements).  Make sure both black blades register themselves with the same name: "Black".</p> <p>When this happens the Xitron system will notice.  We will then deliver the black channel to both Black blades.  It will be ripped once and duplicated on both blades.</p> <p><br></p> <p>This method can be used to double print any CMYK ink.  As long as there are two ink blades registering themselves with the same name then the Xitron RIP will deliver that ink channel to both of those print blades.</p> </div> </div> 1000220978 17 1000238876 2016-10-13T10:38:25-04:00 1003593276 2 2 0 0 Achieving double black in the Aspen system 2016-12-02T10:08:07-05:00 1003593276 1 2016-12-02T10:02:04-05:00 0 0 Centering has moved to the Page Setup so that it can be invoked or not in individual workflows, rather than globally. See below for the three step process to find the control. 1.  Open the Page Setup Manager and choose "Edit" for your Page Setup. 2. Cick "Configure Device". 3. Check or uncheck center <div dir="ltr"> <p></p> <p><br></p> <p>Centering has moved to the Page Setup so that it can be invoked or not in individual workflows, rather than globally.</p> <p><br></p> <p>See below for the three step process to find the control.</p> <p><br></p> <p><br></p> <p>1.  Open the Page Setup Manager and choose "Edit" for your Page Setup.</p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/1047640799/original/DHwAZteZdO6Txz7Mx4GCIT-ti2ilS-kVRw.PNG?1480690761" class="inline-image" data-id="1047640799" alt="DHwAZteZdO6Txz7Mx4GCIT-ti2ilS-kVRw.PNG" title="DHwAZteZdO6Txz7Mx4GCIT-ti2ilS-kVRw.PNG"></p> <p><br></p> <p><br></p> <p>2. Cick "Configure Device".</p> <p></p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/1047640802/original/xMLmMtUrv-gQj9GaOMG2Yah-EcvMmyYpKA.PNG?1480690770" class="inline-image" data-id="1047640802" alt="xMLmMtUrv-gQj9GaOMG2Yah-EcvMmyYpKA.PNG" title="xMLmMtUrv-gQj9GaOMG2Yah-EcvMmyYpKA.PNG"></p> <p><br></p> <p>3. Check or uncheck center</p> <p></p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/1047640808/original/x80mRH0-jsG0WslBz0WqO2LPVAzG4BZlYw.PNG?1480690780" class="inline-image" data-id="1047640808" alt="x80mRH0-jsG0WslBz0WqO2LPVAzG4BZlYw.PNG" title="x80mRH0-jsG0WslBz0WqO2LPVAzG4BZlYw.PNG"></p> <br><p></p> <br><p></p> <br><p></p> </div> 1000220978 12 1000242177 2016-12-02T10:02:04-05:00 1003593276 3 2 0 0 Centering on media - r8 and later 2016-12-02T10:08:07-05:00 1003593276 1 2016-11-10T11:34:31-05:00 0 1 There are several PDF documents related to the r8 release. Aspen R8 Release Notes lists the updates included in the release. Aspen R8 quick start gives a general overview of how to configure an R8 system.  It describes a multiple RIP installation. Aspen troubleshooting R8 lists common questions or challenges and potential solutions. Aspen CMYKS R8 describes how to configure this special case mode of the Aspen system.  There is more CMYKS information here Aspen v2 R8 quick start describes how to configure the Aspen v2 output plugin.  It is necessary for stitching 2 engines together to create a 17" print area. Aspen R8 Test environment Installation Instructions is only of interest to OEM engineers and support staff.  It describes how to configure a stitched-press test system with no stitched printer connected. <div dir="ltr"> <p>There are several PDF documents related to the r8 release.</p> <p><br></p> <p><i><b>A</b><b>spen R8 Release Notes</b></i> lists the updates included in the release.</p> <p><b><i>Aspen R8 quick start</i> </b>gives a general overview of how to configure an R8 system.  It describes a multiple RIP installation.</p> <p><i><b>Aspen troubleshooting R8</b></i> lists common questions or challenges and potential solutions.</p> <p><i><b>Aspen CMYKS R8</b></i> describes how to configure this special case mode of the Aspen system.  <span>There is more CMYKS information </span><a href="http://help.xitron.com/solution/articles/1000237652-aspen-release-notes-for-cmyks-6318" target="" style="background-color: rgb(255, 255, 255);">here</a></p> <p><i><b>Aspen v2 R8 quick start</b></i> describes how to configure the Aspen v2 output plugin.  It is necessary for stitching 2 engines together to create a 17" print area.</p> <p><b><i>Aspen R8 Test environment Installation Instructions</i></b> is only of interest to OEM engineers and support staff.  It describes how to configure a stitched-press test system with no stitched <img id="cursor" width="0" height="0" rel="cursor" src="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw==" style="display: none;">printer connected.</p> <p><br></p> </div> 1000220978 14 1000241242 2016-11-10T13:02:16-05:00 1003593276 4 2 0 1 Aspen r8 2016-12-02T10:08:07-05:00 1003593276 1 2017-01-12T15:11:10-05:00 0 0 To switch the default width of an Aspen engine in a RIP from 8.64" to 8.72", read the instructions below. In the Aspen.ini file at %appdata%/xitron/plugsins/aspen.ini/ you need to add a new preference "DeviceWidthPixels", which allows you to set the device width. This ini file is read by the plugin during startup and used to configure the device. In the absence of any entry in the aspen.ini file the aspen plugin will default to 8.64" or 13824 pixels.  If you desire to change to 8.72" you must set this value to 13952 pixels. Explanation of the pixel to inch conversion: (inches * pixels per inch resolution) = device width in pixels.  e.g. (8.72*1600)=13952 If you start with the larger of the two requested values (13952) and reduce the value to (13824) between RIP sessions this seems to work properly but if you go the other way the smaller value remains valid.  In other words, a RIP set up for 8.64" will not easily move to 8.72", but moving from 8.72" to 8.64" does work easily.   What does "easily" mean in this case? To switch from 8.64 to 8.72 you must delete the Aspen device and the associated Page Setups in the RIP, shut the RIP down, make the change and restart the RIP. Then you must recreate the Aspen device (device manager) and the Page Setups (page setup manager).  For this reason it is expected that only a knowledgable technical person will attempt this in the field.   --------------------  The entry in the INI file looks like this:   [Aspen]   DeviceWidthPixels=13952 To switch the default width of an Aspen engine in a RIP from 8.64" to 8.72", read the instructions below.<p><br></p><br>In the Aspen.ini file at %appdata%/xitron/plugsins/aspen.ini/ you need to add a new preference "DeviceWidthPixels", which allows you to set the device width.<p><br></p>This ini file is read by the plugin during startup and used to configure the device.<p><br></p><br>In the absence of any entry in the aspen.ini file the aspen plugin will default to 8.64" or 13824 pixels.  If you desire to change to 8.72" you must set this value to 13952 pixels.<p><br></p><em>Explanation of the pixel to inch conversion: (inches * pixels per inch resolution) = device width in pixels.  e.g. (8.72*1600)=13952</em><br><br>If you start with the larger of the two requested values (13952) and reduce the value to (13824) between RIP sessions this seems to work properly but if you go the other way the smaller value remains valid.  In other words, a RIP set up for 8.64" will not easily move to 8.72", but moving from 8.72" to 8.64" does work easily.  <p><br></p><br>What does "easily" mean in this case?<p><br></p><br>To switch from 8.64 to 8.72 you must delete the Aspen device and the associated Page Setups in the RIP, shut the RIP down, make the change and restart the RIP. Then you must recreate the Aspen device (device manager) and the Page Setups (page setup manager). <p><br></p>For this reason it is expected that only a knowledgable technical person will attempt this in the field.  <p><br></p>-------------------- <p><br></p>The entry in the INI file looks like this: <p><br></p><p><br></p> [Aspen]  <p><br></p>DeviceWidthPixels=13952<p><br></p> 1000220978 3 1000243773 2017-01-12T15:11:10-05:00 1003593276 5 2 0 0 Switch default width to 8.72 inches 2017-01-12T15:13:20-05:00 1003593276 1 2016-08-31T14:33:52-04:00 0 0 CMYKS is a special Aspen RIP mode. You can print spot colors with the standard Aspen system.  CMYKS mode is used to mix CMYK inks into a spot ink to create a new color mixture.  Some changes were made to that system in release 6318.  Read the PDF for more detail. <div dir="ltr"> <div dir="ltr"> <p>CMYKS is a special Aspen RIP mode.</p> <p>You can print spot colors with the standard Aspen system.  CMYKS mode is used to mix CMYK inks into a spot ink to create a new color mixture. </p> <p>Some changes were made to that system in release 6318. </p> <p>Read the PDF for more detail.</p> </div> </div> 1000220978 9 1000237652 2016-09-16T10:48:06-04:00 1003593276 6 2 0 0 Aspen release notes for CMYKS 6318 2017-01-12T15:13:20-05:00 1003593276 1 2015-11-17T11:53:14-05:00 0 0 The attached document talks about PDF creation settings for high speed digital presses. <p>The attached document talks about PDF creation settings for high speed digital presses.</p> 1000220978 65 1000216309 2015-11-17T11:53:14-05:00 7 2 0 0 Exporting PDFs for use with High Speed Digital Presses 2017-01-12T15:13:20-05:00 1003593276 1 2015-11-17T10:15:59-05:00 0 0 Collation described In printing, the term Collate refers to the arranging of individual sheets into a pre-determined sequence.   For example, a perfect bound book needs its pages to be collated in numerical order before it can be bound.  If you have a 3 page job and want to print 3 copies of that job there are two basic ways to do this: collated and uncollated. (You can skip to the diagram below) As shown below, a collated job will print the entire job in numerical order until all pages of that job are complete, and then start the next copy over from page 1 again.  An uncollated job will print the requested number of copies of the first page, and then move on to the next page. Calculating the number of pages you can collate. The Aspen system architecture has the RIP delivering pages in RAM to the Durango spooler.  The Durango spooler fills it's Page Pool (RAM buffer) and, from there, delivers it to the printhead controller system. Collated jobs need to fit entirely within the Durango Page Pool. On a 1-Aspen system it is straightforward to calculate because there will only be one computer.   On a multiple Aspen system you need to figure total RAM across all the RIP computers in order to calculate how many pages your system is capable of collating.  At 1375x1600 dpi resolution Aspen pages fit ten (10) A4 or Letter pages per gigabyte of RAM.   Each RIP computer needs 8gb of its own RAM for the RIP, the OS, etc. You can configure the Durango Page Pool to use the remainder of the RAM available on a computer.   The calculation to figure number of Letter-size pages your system can collate is [ ((RAM in GB) - 8) x (# of RIPcomputers)  x 10 ] Therefore a 1-Aspen configuration with 16gb of RAM can collate (16-8)x1x10 = 80 pages. Therefore a 4-Aspen configuration (as of Nov., 2015, configured with 4 computers) with 16gb of RAM can collate (16-8)x4x10 = 320 pages. To collate more pages, add RAM and configure the Durango Page Pool accordingly. Converting for other page dimensions What about a different size page?  For example, if you want to print short run paperback books. The calculation is easily alterable for physical dimensions.  It scales up and down linearly. For example, mass market paperbacks measuring 110×178 mm or 4.4" x 7" or alternate sized "B-format" paperbacks measuring 130mm×198mm or 5.12"×7.8" will fit about 20 pages per gigabyte.  They are about half of a letter page so twice as many will fit in RAM. The calculation for paperback books is therefore: [ ((RAM in GB) - 8) x (# of RIPcomputers)  x 20 ] Converting for other resolutions page size resolution pages / GB 8.5"x11" or A4 1375x1600 10 8.5"x11" or A4 1135x1600 12 8.5"x11" or A4 725x1600 19 8.5"x11" or A4 555x1600 25 Changing the Durango Page Pool In the Durango spooler application, click "configure" That will bring up a window like this: You have to stop the spooler in order to change the Page Pool size.  The Page Pool is measured in MB. 4096MB is 4GB.  The current setting of 4096 will give us a collate count of 40 Letter or A4 pages.   When the spooler is stopped you can edit the Page Pool size. The new setting will take place after you click "start spooler".  8192MB/8GB will give us a collate count of 80 A4 or Letter pages. Configuring the system to collate more pages As of this writing, our computers ship with 16GB of RAM. 32GB of additional RAM will allow you to collate 400 Letter sized pages. You would have 48GB of RAM in the computer and could allocate 40Gb to the Durango Page Pool. On a 1-Aspen system that would allow you to collate jobs of 400 pages. On a 4-Aspen system that would allow you to collate jobs of 1600 pages. 64GB of additional RAM will allow you to collate 720 Letter sized pages. You would have 80GB of RAM in the computer and could allocate 72Gb to the Durango Page Pool. On a 1-Aspen system that would allow you to collate jobs of 720 pages. On a 4-Aspen system that would allow you to collate jobs of 2880 pages. While we have never done this, in theory you can install 128GB of total RAM in each computer. This would allow a current theoretical maximum collation of 1200 Letter sized pages on a 1-Aspen press and 4800 pages on a 4-Aspen press. The computers we ship as of Nov., 2015 come with 16GB RAM and are capable of holding 128GB of RAM.  Check with Xitron if you suspect our computer specification has changed.  November 17, 2015. Appendix.  "Old" Collate Warning.  Not recommended for anyone other than press manufacturers. Before we moved the collate system into RAM, collate worked like this: We used postscript commands to repeat the job over and over again until the requested copy count had been satisfied. This means that there was no page count limitation at all.  However, it also means that we ripped the job over and over again and risked not being able to keep up with the speed of the press, causing job underrun errors.  For comparision: Old Collate: RIPs each job one time for every copy count requested, going through each job from start to finish again and again.  No limitation on pages, but a possibility for job underrun errors. Collate:  RIPs each job one time only and stores it in RAM, sending it to the printhead as many times as the copy count requires.  The page count is limited to what can fit in RAM.  There is no possibility for underrun errors.   If you know how to edit the Navigator Server .ini file you can enable "old collate". This setting controls whether or not we manage the collate option by repeating to RIP using PS or whether we handle it in RAM.  To manage the collate option with postscript commands, set CollateInPS value to 1, otherwise leave it as zero or delete the option to collate in RAM.  In the Server .ini file [Aspen] CollateInPS=1 <p><b><u>Collation described</u></b></p> <p style="color: rgb(77, 77, 77); font-family: Tahoma, Geneva, sans-serif, arial; font-size: 14px;">In printing, the term <i>Collate </i>refers to the arranging of individual sheets into a pre-determined sequence.  </p> <p style="color: rgb(77, 77, 77); font-family: Tahoma, Geneva, sans-serif, arial; font-size: 14px;"><span>For example, a perfect bound book needs its pages to be collated in numerical order before it can be bound. </span></p> <p style="color: rgb(77, 77, 77); font-family: Tahoma, Geneva, sans-serif, arial; font-size: 14px;"><span><br></span></p> <p style="color: rgb(77, 77, 77); font-family: Tahoma, Geneva, sans-serif, arial; font-size: 14px;">If you have a 3 page job and want to print 3 copies of that job there are two basic ways to do this: <i>collated </i>and <i>uncollated</i>.</p> <p style="color: rgb(77, 77, 77); font-family: Tahoma, Geneva, sans-serif, arial; font-size: 14px;">(You can skip to the diagram below)</p> <p style="color: rgb(77, 77, 77); font-family: Tahoma, Geneva, sans-serif, arial; font-size: 14px;">As shown below, a collated job will print the entire job in numerical order until all pages of that job are complete, and then start the next copy over from page 1 again.  An uncollated job will print the requested number of copies of the first page, and then move on to the next page.</p> <p style="color: rgb(77, 77, 77); font-family: Tahoma, Geneva, sans-serif, arial; font-size: 14px;"><br></p> <p><img src="http://www.mgxcopy.com/blog/wp-content/uploads/2014/09/collation-424d3eca5b58b0f4dc2eeb2fa91ab629.png" data-height="302" style="width: 302px; height: 302px;"></p> <p><br></p> <p><b><u>Calculating the number of pages you can collate.</u></b></p> <p>The Aspen system architecture has the RIP delivering pages in RAM to the Durango spooler.  The Durango spooler fills it's <i>Page Pool</i> (RAM buffer) and, from there, delivers it to the printhead controller system.</p> <p><span>Collated jobs need to fit entirely within the Durango Page Pool. </span><span>On a 1-Aspen system it is straightforward to calculate because there will only be one computer.   On a multiple Aspen system you need to figure total RAM across all the RIP computers in order to calculate how many pages your system is capable of collating.</span><span> </span><br></p> <p><span><br></span></p> <p>At 1375x1600 dpi resolution Aspen pages fit ten (10) <i>A4</i> or <i>Letter</i> pages per gigabyte of RAM.  </p> <p><span>Each RIP computer needs 8gb of its own RAM for the RIP, the OS, etc. You can configure the Durango Page Pool to use the remainder of the RAM available on a computer.  </span></p> <p><span><br></span></p> <p>The calculation to figure number of Letter-size pages your system can collate is [ ((RAM in GB) - 8) <b>x</b> (# of RIPcomputers)  <b>x </b>10 ]</p> <p>Therefore a 1-Aspen configuration with 16gb of RAM can collate (16-8)x1x10 = 80 pages.</p> <p>Therefore a 4-Aspen configuration (as of Nov., 2015, configured with 4 computers) with 16gb of RAM can collate (16-8)x4x10 = 320 pages.</p> <p>To collate more pages, add RAM and configure the Durango Page Pool accordingly.</p> <p><br></p> <p><b><u>Converting for other page dimensions</u></b></p> <p>What about a different size page?  For example, if you want to print short run <a href="https://en.wikipedia.org/wiki/Paperback#Types" target="_blank" style="line-height: 16px;">paperback books</a>.<a href="https://en.wikipedia.org/wiki/Paperback#Types" target="_blank" style="background-color: rgb(255, 255, 255);"></a></p> <p><br></p> <p>The calculation is easily alterable for <span style="font-family: Arial;">physical </span>dimensions.  It scales up and down linearly.</p> <p>For example, mass market paperbacks measuring <span style="font-family: Arial; font-size: small;"><span style="color: rgb(37, 37, 37);">110×178 mm or 4.4" x 7" or alternate sized "B-format" paperbacks measuring </span><span style="color: rgb(37, 37, 37);">130mm×198mm or </span><span style="color: rgb(37, 37, 37);">5.12"×7.8" will fit about 20 pages per gigabyte.  They are about half of a letter page so twice as many will fit in RAM.</span></span></p> <p><span>The calculation for paperback books is therefore:</span></p> <p><span>[ ((RAM in GB) - 8) </span><b>x</b><span> (# of RIPcomputers)  </span><b>x </b><span>20 ]</span></p> <p><span><br></span></p> <p><span><b><u>Converting for other resolutions</u></b></span></p> <p><br></p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <table border="0" cellpadding="0" cellspacing="0" width="240"><tbody> <tr> <td width="94">page size</td> <td width="75">resolution</td> <td width="71">pages / GB</td> </tr> <tr> <td>8.5"x11" or A4</td> <td>1375x1600</td> <td style="text-align: right;">10</td> </tr> <tr> <td>8.5"x11" or A4</td> <td>1135x1600</td> <td style="text-align: right;">12</td> </tr> <tr> <td>8.5"x11" or A4</td> <td>725x1600</td> <td style="text-align: right;">19</td> </tr> <tr> <td>8.5"x11" or A4</td> <td>555x1600</td> <td style="text-align: right;">25</td> </tr> </tbody></table> <p></p> <p><br></p> <p><br></p> <p><b><u>Changing the Durango Page Pool</u></b></p> <p><br><span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 13px; font-weight: normal;">In the Durango spooler application, click "configure"</span></p> <p></p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/1034446035/original/blob1447770950678.jpeg?1447770953" class="inline-image" data-id="1034446035"></p> <p><br></p> <p><br></p> <p>That will bring up a window like this:</p> <p></p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/1034446168/original/blob1447771039737.jpeg?1447771039" class="inline-image" data-id="1034446168"></p>You have to stop the spooler in order to change the Page Pool size.  The Page Pool is measured in MB. 4096MB is 4GB.  The current setting of 4096 will give us a collate count of 40 Letter or A4 pages.  <p><br></p> <p><span>When the spooler is stopped you can edit the Page Pool size.</span></p> <p><br><span></span></p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/1034447713/original/blob1447771915630.jpeg?1447771918" class="inline-image" data-id="1034447713"></p> <p></p> <p>The new setting will take place after you click "start spooler".  8192MB/8GB will give us a collate count of 80 A4 or Letter pages.</p> <p><br></p> <p><b><u>Configuring the system to collate more pages</u></b></p> <p>As of this writing, our computers ship with 16GB of RAM.</p> <p><br></p> <p>32GB of additional RAM will allow you to collate 400 Letter sized pages.</p> <p>You would have 48GB of RAM in the computer and could allocate 40Gb to the Durango Page Pool.</p> <p>On a 1-Aspen system that would allow you to collate jobs of 400 pages.</p> <p>On a 4-Aspen system that would allow you to collate jobs of 1600 pages.</p> <p><br></p> <p></p> <p>64GB of additional RAM will allow you to collate 720 <span>Letter sized</span><span> pages.</span></p> <p>You would have 80GB of RAM in the computer and could allocate 72Gb to the Durango Page Pool.</p> <p>On a 1-Aspen system that would allow you to collate jobs of 720 pages.</p> <p>On a 4-Aspen system that would allow you to collate jobs of 2880 pages.</p> <p><br></p> <p>While we have never done this, in theory you can install 128GB of total RAM in each computer.</p> <p>This would allow a current theoretical maximum collation of 1200 <span>Letter sized </span><span>pages on a 1-Aspen press and 4800 pages on a 4-Aspen press.</span></p> <p><br></p> <p>The computers we ship as of Nov., 2015 come with 16GB RAM and are capable of holding 128GB of RAM.  Check with Xitron if you suspect our computer specification has changed.</p> <p><br></p> <p><br></p> <p> November 17, 2015.</p> <p><br></p> <p><br></p> <p><br></p> <p><br></p> <p><br></p> <p><br></p> <p><br></p> <p><b><u>Appendix.  "Old" Collate</u></b></p> <p>Warning.  Not recommended for anyone other than press manufacturers.</p> <p><br></p> <p>Before we moved the collate system into RAM, collate worked like this:</p> <p>We used postscript commands to repeat the job over and over again until the requested copy count had been satisfied.</p> <p>This means that there was no page count limitation at all.  However, it also means that we ripped the job over and over again and risked not being able to keep up with the speed of the press, causing job underrun errors. </p> <p>For comparision:</p> <p><i>Old Collate</i>: RIPs each job one time for every copy count requested, going through each job from start to finish again and again.  No limitation on pages, but a possibility for job underrun errors.</p> <p><i>Collate</i>:  RIPs each job one time only and stores it in RAM, sending it to the printhead as many times as the copy count requires.  The page count is limited to what can fit in RAM.  There is no possibility for underrun errors.  </p> <p><br></p> <p>If you know how to edit the Navigator Server .ini file you can enable "old collate".</p> <p>This setting controls whether or not we manage the collate option by repeating to RIP using PS or whether we <span>handle it in RAM.  To manage the collate option with postscript commands, set CollateInPS value to 1, otherwise leave it as zero or delete the option to collate in RAM</span><span>. </span></p> <p>In the Server .ini file </p> <p><br></p> <p>[Aspen] </p> <p>CollateInPS=1</p> 1000220978 50 1000216262 2015-11-20T16:50:44-05:00 1003593276 8 2 0 0 Collate 2017-01-12T15:13:20-05:00 1003593276 1 2016-12-02T10:07:18-05:00 0 0 <div dir="ltr"> <p></p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/1047641076/original/kBM_o4O4kuIMmV1N5F5M5ttqyzDApsAtdg.JPG?1480691178" class="inline-image" data-id="1047641076" alt="kBM_o4O4kuIMmV1N5F5M5ttqyzDApsAtdg.JPG" title="kBM_o4O4kuIMmV1N5F5M5ttqyzDApsAtdg.JPG" height="999px" data-height="999" style="width: 1084px;"></p> <p><br></p> <p></p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/1047641087/original/hwzzb6tTNWnQA4QohYkYE0sT2ZTOp7YB9Q.JPG?1480691193" class="inline-image" data-id="1047641087" alt="hwzzb6tTNWnQA4QohYkYE0sT2ZTOp7YB9Q.JPG" title="hwzzb6tTNWnQA4QohYkYE0sT2ZTOp7YB9Q.JPG"></p> <br><p></p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/1047641107/original/H8m9qi8m3TAckV4bHN_JJ9h2udGZD-VAxA.JPG?1480691210" class="inline-image" data-id="1047641107" alt="H8m9qi8m3TAckV4bHN_JJ9h2udGZD-VAxA.JPG" title="H8m9qi8m3TAckV4bHN_JJ9h2udGZD-VAxA.JPG"></p> <br><p></p> </div> 1000220978 5 1000242178 2016-12-02T10:07:18-05:00 1003593276 9 2 0 0 Centering on Media - r7 and earlier 2017-01-12T15:13:20-05:00 1003593276 1 2016-05-26T11:02:58-04:00 0 0 Release notes for Aspen r7 <div dir="ltr"> <div> <p dir="ltr"></p> <p><br></p>Release notes for Aspen r7<p></p> </div> </div> 1000220978 9 1000232045 2016-09-16T10:47:03-04:00 1003593276 10 2 0 0 Aspen r7 release notes 2017-01-12T15:13:20-05:00 1003593276 1 2016-05-27T11:26:30-04:00 0 0 Installation guide Aspen v2 quick start (for stitching) Aspen troubleshooting <div> <p dir="ltr"></p> <p><br></p>Installation guide<p></p> <p dir="ltr">Aspen v2 quick start (for stitching)</p> <p dir="ltr">Aspen troubleshooting</p> </div> 1000220978 6 1000232114 2016-05-27T11:26:30-04:00 1003593276 11 2 0 0 r7 update documents 2017-01-12T15:13:20-05:00 1003593276 1 2016-03-22T13:39:47-04:00 0 1 Introduction:  Color management engines will often "contaminate" a pure black with other colors in an attempt to get the black hue of the printer to match the black hue of the target CMYK color space.  This is usually desirable.  It can lead to darker blacks and it is generally one of the points of color management.  However, this can cause problems with text or hairline rules.  These objects can look hazy or fuzzy due to slight misregistrations between colors.  Some of the under colors can leak out and cause the edges to be less defined. A built in partial solution: Navigator has a toggle to "preserve 100% black" or "print 100% black with only black ink". This stops the color management engine from adding other colorants to the black when that black is 100%.  For offset printers using color management for proofing this is an adequate amount of control. The problem defined: On a digital press with color management "preserve 100% black" may not be enough control. We have encountered a category of jobs which have grey scale text. (e.g. A bank statement from a particular bank has the entire back page of most sheets as screened black text.)  These jobs print with the text as a 4 color mixture due to the color management engine. It varies from average quality to unreadable within a print run. Any job with this exact problem which is entirely black you could just print with color management off.  When the color management engine is required for other elements in the job it becomes more complicated. Solution: We have created three page features (enabled in a RIP Page Setup) that will address this problem in three different ways.  Each of the page features acts only on channels which are presented to the color management engine as pure grey or black. 1. "Pure Grey+Black".  Bypasses color management for text and line art between 0% - 100% black. 2. "Pure Grey+Black text".  Bypasses color management for text between 0% - 100% black. 3. "Pure Grey+Black lineart".  Bypasses color management for line art between 0% - 100% black To install a page feature just drop the file into the folder inside the Navigator RIP folder at sw/page features/. How to decide which page feature to use: If you are uncertain about which way to proceed, there is a test file included in the delivery (attached to this article) called "preserve black test.pdf" which will help you to see the effect each page feature will have. You can use these page features in conjunction with the "preserve 100% black" checkbox to achieve different effects. For example: If you wish to print all grey or black text and 100% black line art only on the black channel, check "preserve 100% black" and use the "Pure Grey+Black text" page feature. Warning and suggestions:   Should you use this?  If you are trying to fix a problem caused by improper file design, we suggest you encourage file designers to do their job properly.  Turning off color management for one color may have undesirable side effects. The "pure grey+black" effect could also be achieved using the "pure primaries" feature of an ICC profiling application.  This requires the use of device link profiles which should be studied for applicability to your situation. <div dir="ltr"> <p><br></p> <p><b>Introduction:</b>  Color management engines will often "contaminate" a pure black with other colors in an attempt to get the black hue of the printer to match the black hue of the target CMYK color space.  This is usually desirable.  It can lead to darker blacks and it is generally one of the points of color management.  However, this can cause problems with text or hairline rules.  These objects can look hazy or fuzzy due to slight misregistrations between colors.  Some of the under colors can leak out and cause the edges to be less defined.</p> <p><br></p> <p><b>A built in partial solution:</b> Navigator has a toggle to "preserve 100% black" or "print 100% black with only black ink". This stops the color management engine from adding other colorants to the black when that black is 100%. </p> <p><span>For offset printers using color management for proofing this is an adequate amount of control.</span></p> <p><b><br></b></p> <p><b>The problem defined:</b></p> <p>On a digital press with color management "preserve 100% black" may not be enough control.</p> <p><br></p> <p>We have encountered a category of jobs which have grey scale text. (e.g. A bank statement from a particular bank has the entire back page of most sheets as screened black text.)  These jobs print with the text as a 4 color mixture due to the color management engine. It varies from average quality to unreadable within a print run.</p> <p>Any job with this exact problem which is entirely black you could just print with color management off. </p> <p>When the color management engine is required for other elements in the job it becomes more complicated. </p> <p><br></p> <p><b>Solution:</b></p> <p>We have created three page features (enabled in a RIP Page Setup) that will address this problem in three different ways.  Each of the page features acts only on channels which are presented to the color management engine as pure grey or black.</p> <p><br></p> <p>1. "Pure Grey+Black".  Bypasses color management for text and line art between <span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;">0% - 100% black.</span></p> <p>2. "Pure Grey+Black text".  Bypasses color management for text <span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;">between </span><span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;">0% - 100% black.</span></p> <p><span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;">3.</span><span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;"> "Pure Grey+Black lineart".  </span><span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;">Bypasses color management for line art between </span><span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;">0% - 100% black</span></p> <p><br></p> <p><span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;">To install a page feature just drop the file into the folder inside the Navigator RIP folder at sw/page features/.</span></p> <p><span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;"><br></span></p> <p><font face="Helvetica Neue, Helvetica, Arial, sans-serif, Helvetica Neue, Helvetica, Arial, sans-serif, Helvetica Neue, Helvetica, Arial, sans-serif, Helvetica Neue, Helvetica, Arial, sans-serif, Helvetica Neue, Helvetica, Arial, sans-serif"><b>How to decide which page feature to use:</b></font></p> <p><span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;">If you are uncertain about which way to proceed, there is a test file included in the delivery (attached to this article) called "preserve black test.pdf" which will help you to see the effect each page feature will have.</span></p> <p><br></p> <p style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;"><span style="font-size: 13px; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;">You can use these page features in conjunction with the "preserve 100% black" checkbox to achieve different effects.</span></p> <p style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;"><span style="font-size: 13px; font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif, 'Helvetica Neue', Helvetica, Arial, sans-serif;">For example: If you wish to print all grey or black text and 100% black line art only on the black channel, check "preserve 100% black" and use the "Pure Grey+Black text" page feature.</span></p> <p><br></p> <p><b>Warning and suggestions</b>:  </p> <p>Should you use this?  If you are trying to fix a problem caused by improper file design, we suggest you encourage file designers to do their job properly.  Turning off color management for one color may have undesirable side effects.</p> <p>The "pure grey+black" effect could also be achieved using the "pure primaries" feature of an ICC profiling application.  This requires the use of device link profiles which should be studied for applicability to your situation.</p> <p><br></p> <p><br></p> </div> 1000220978 70 1000227811 2016-12-01T11:47:26-05:00 1003593276 12 preserve black How to print pure black in a color managed workflow. 2 0 1 Printing pure black in a color managed workflow 2017-01-12T15:13:20-05:00 1003593276 1 2015-11-17T14:02:29-05:00 0 0 A guide for installing multiple RIP systems to drive an Aspen print engine. <p>A guide for installing multiple RIP systems to drive an Aspen print engine.</p> 1000220978 44 1000216337 2015-11-17T14:02:29-05:00 1003593276 13 2 0 0 Aspen Quick Start guide for multi-RIP installations 2017-01-12T15:13:20-05:00 1003593276 1 2016-04-18T13:52:49-04:00 0 0 This document details the different ways you can configure an Aspen CMYKS system to generate separations. It should be read after the CMYKS Quick Start guide. <p>This document details the different ways you can configure an Aspen CMYKS system to generate separations.</p> <p>It should be read after the CMYKS Quick Start guide.</p> 1000220978 16 1000229543 2016-04-18T13:52:49-04:00 14 2 0 0 CMYKS advanced separations guide 2017-01-12T15:13:20-05:00 1003593276 1 2015-11-17T14:29:54-05:00 0 0 A guide for the CMYKS special mode in Navigator Aspen. This special mode allows for a spot color channel to be edited with CMYK and Spot. <p>A guide for the CMYKS special mode in Navigator Aspen.</p> <p>This special mode allows for a spot color channel to be edited with CMYK and Spot.</p> 1000220978 28 1000216340 2015-11-17T14:29:54-05:00 1003593276 15 2 0 0 CMYKS quick start 2017-01-12T15:13:20-05:00 1003593276 1 2015-11-17T14:47:05-05:00 0 0 If you cannot connect Navigator Server to a remote RIP on a multiple RIP, multiple computer system, then this document is for you. <p>If you cannot connect Navigator Server to a remote RIP on a multiple RIP, multiple computer system, then this document is for you.</p> 1000220978 46 1000216348 2015-11-17T14:47:05-05:00 1003593276 16 2 0 0 Troubleshooting - connect to a remote RIP 2017-01-12T15:13:20-05:00 1003593276 1 2015-11-17T14:35:31-05:00 0 0 Some notes on configuration and use of the r6 release. Topics covered:  Page Setup configuration that may be different in Aspen r6 than in previous versions. separation setups some known issues with job chaining at the new resolutions <p>Some notes on configuration and use of the r6 release.</p> <p><br></p> <p>Topics covered: </p> <p></p> <ul> <li> <span>Page Setup configuration that may be different in Aspen r6 than in previous versions.</span><br> </li> <li>separation setups</li> <li>some known issues with job chaining at the new resolutions</li> </ul> <p><br></p> 1000220978 30 1000216343 2015-11-17T14:35:31-05:00 1003593276 17 2 0 0 Navigator for Aspen r6 configuration notes 2017-01-12T15:13:20-05:00 1003593276 1 2015-11-17T13:55:49-05:00 0 0 Oct 15, 2015  Software versions included: Server & Client 6.1.23 RIP 10.0r1 (x64) Aspen Output plugin 2.1.1.1 Durango Spooler 2.0.1.9 MultiRIP Config Tool 0.8 XiRemote 1.0.2.3     New resolution modes The system supports several new resolution modes. The lower resolutions will render faster.  The lower resolutions may support higher paper path speeds.  The supported resolutions are: 1600x1375 1600x1135 1600x725 1600x555 Whether your printer supports each of these modes is a separate question. You should separately determine which resolutions are appropriate for your press. Spot color support Spot color support has been added to the standard Aspen plug-in.  This allows for the rendering and delivery of spot colors to a 5th blade equipped with a spot color.  This is distinct from CMYKS mode which is a special case. Spot color may be supported by sending files appropriately containing 1 or more spot colors.  If there are more spot colors than one in a job, the user may need to use the ink remapping tool to set up the job properly.  To configure your RIP to output spot color, you will need a separation style in the Page Setup Manager that allows for the spot color to be printed, rather than converted to process. Separation style that will convert spot colors to a CMYK mixture:   A separation style that will send down the spot colors in the job to the press:   CMYKS mode There is a new device inside the Aspen plugin, available only through a special license. This device allow for mixing spot and cmyk inks to alter the spot color channel in a print job. It is a special case mode and is not necessary for the support of a fifth color blade.   Changes and additions; new and rolled up from previous versions.   New Workflow version 6123 =================== Disable a socket call at boot time that was locking up the system at a customer site. Change back the Thumbnail licensing. Improve capture of output plugin errors that happen at the end of jobs.     Aspen output plugin 2111 =========================== Remove unsupported resolution pairs   Rolled up from previous versions. Aspen output plugin 2109 =========================== Improve capture of output plugin errors that happen at the end of jobs. Add the optional CMYKS mode.   From Aspen R5.1: - Support the swatch sheet for Spot color remapping on a multi-head press. - Include the Remora resolution modes. - Support for SetGold on the multi-head press - Better support for single page jobs on a single head press. In R5, the job could not be re-queued from inside the Press workflow, or if it went first through the Prep workflow it would be padded up to the number of RIPs in use. - Handle jobnames (group lists, actually) that start with multibyte (e.g. Japanese or Chinese) chars. From Aspen R5.2: - Add double book mode to the Page Filter Action. - Aspen output plugin (and Durango Spooler) v2019. Add the ability to change the device width through the .ini file. From Aspen CMYKS: - Aspen CMYKS mode, a new device (inside the RIP output plugin), and a new way of adjusting spot colors. - Output all the CMYKS swatch sheet pages in one job. - Disable a call at boot time that was locking up the system at a customer site. - Revert bit 11 to be Thumbnail Action again, CMYKS on the server is simply enabled through an .ini setting. - Attempt to catch Aspen plugin output errors and report them in the client. <div dir="ltr"> <h1><br></h1> <p>Oct 15, 2015 </p> <h2> </h2> <h2>Software versions included:</h2> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <table border="1" cellspacing="0" cellpadding="0" style="margin-left: 35.75pt;"> <tbody> <tr> <td width="160" style="border-width: 1pt; border-color: windowtext; padding: 0in 5.4pt;"> <p>Server &amp; Client</p> <p> </p> </td> <td width="107" style="border-width: 1pt; border-color: windowtext; padding: 0in 5.4pt;"> <p>6.1.23</p> <p> </p> </td> </tr> <tr> <td width="160" style="border-width: 1pt; border-color: windowtext; padding: 0in 5.4pt;"> <p>RIP</p> <p> </p> </td> <td width="107" style="padding: 0in 5.4pt;"> <p>10.0r1 (x64)</p> <p> </p> </td> </tr> <tr> <td width="160" style="border-width: 1pt; border-color: windowtext; padding: 0in 5.4pt;"> <p>Aspen Output plugin</p> <p> </p> </td> <td width="107" style="padding: 0in 5.4pt;"> <p>2.1.1.1</p> <p> </p> </td> </tr> <tr> <td width="160" style="border-width: 1pt; border-color: windowtext; padding: 0in 5.4pt;"> <p>Durango Spooler</p> <p> </p> </td> <td width="107" style="padding: 0in 5.4pt;"> <p>2.0.1.9</p> <p> </p> </td> </tr> <tr> <td width="160" style="border-width: 1pt; border-color: windowtext; padding: 0in 5.4pt;"> <p>MultiRIP Config Tool</p> <p> </p> </td> <td width="107" style="padding: 0in 5.4pt;"> <p>0.8</p> <p> </p> </td> </tr> <tr> <td width="160" style="border-width: 1pt; border-color: windowtext; padding: 0in 5.4pt;"> <p>XiRemote</p> <p> </p> </td> <td width="107" style="padding: 0in 5.4pt;"> <p>1.0.2.3</p> <p> </p> </td> </tr> </tbody> </table> <p><span style="font-size: 12px; font-family: Cambria, serif; color: rgb(36, 63, 96);"> </span></p> <p><span style="font-size: 12px; font-family: Cambria, serif; color: rgb(36, 63, 96);"> </span></p> <h2>New resolution modes</h2> <p>The system supports several new resolution modes. The lower resolutions will render faster.  The lower resolutions may support higher paper path speeds.  </p> <p>The supported resolutions are:</p> <p>1600x1375</p> <p>1600x1135</p> <p>1600x725</p> <p>1600x555</p> <p> </p> <p>Whether your printer supports each of these modes is a separate question. You should separately determine which resolutions are appropriate for your press.</p> <p> </p> <p> </p> <h2>Spot color support</h2> <p>Spot color support has been added to the standard Aspen plug-in.  This allows for the rendering and delivery of spot colors to a 5<sup>th</sup> blade equipped with a spot color.  This is distinct from CMYKS mode which is a special case. </p> <p>Spot color may be supported by sending files appropriately containing 1 or more spot colors.  If there are more spot colors than one in a job, the user may need to use the ink remapping tool to set up the job properly.  To configure your RIP to output spot color, you will need a separation style in the Page Setup Manager that allows for the spot color to be printed, rather than converted to process.</p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p>Separation style that will convert spot colors to a CMYK mixture: </p> <p><br></p> <p></p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/1034467930/original/blob1447785115953.jpeg?1447785116" class="inline-image" data-id="1034467930" data-height="393" style="height: 393px; width: 573.538px;"></p> <p><br></p> <p><span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 13px; font-weight: normal;"> </span><span style="font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif; font-size: 13px; font-weight: normal;">A separation style that will send down the spot colors in the job to the press:</span></p> <p><span></span></p> <p><img src="https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/1034467955/original/blob1447785144945.jpeg?1447785145" class="inline-image" data-id="1034467955" data-height="394" style="height: 394px;"></p> <br><p></p> <br><p> </p> <p><span style="font-size: 12px; font-family: Cambria, serif; color: rgb(36, 63, 96);"> </span></p> <h2>CMYKS mode</h2> <p>There is a new device inside the Aspen plugin, available only through a special license.</p> <p>This device allow for mixing spot and cmyk inks to alter the spot color channel in a print job. It is a special case mode and is not necessary for the support of a fifth color blade.</p> <p><span style="font-size: 12px; font-family: Cambria, serif; color: rgb(36, 63, 96);"> </span></p> <h2>Changes and additions; new and rolled up from previous versions.</h2> <p><b><span style="color: rgb(0, 0, 0);"> </span></b></p> <p><b><span style="color: rgb(0, 0, 0);">New</span></b></p> <p><span style="color: rgb(0, 0, 0);">Workflow version 6123</span></p> <p><span style="color: rgb(0, 0, 0);">===================</span></p> <p><span style="color: rgb(0, 0, 0);">Disable a socket call at boot time that was locking up the system at a customer site.</span></p> <p><span style="color: rgb(0, 0, 0);">Change back the Thumbnail licensing.</span></p> <p><span style="color: rgb(0, 0, 0);">Improve capture of output plugin errors that happen at the end of jobs.</span></p> <p><span style="color: rgb(0, 0, 0);"> </span></p> <p><span style="color: rgb(0, 0, 0);"> </span></p> <p><span style="color: rgb(0, 0, 0);">Aspen output plugin 2111</span></p> <p><span style="color: rgb(0, 0, 0);">===========================</span></p> <h2><span style="font-size: 12px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">Remove unsupported resolution pairs</span></h2> <p><b> </b></p> <p><b>Rolled up from previous versions.</b></p> <p><span style="color: rgb(0, 0, 0);">Aspen output plugin 2109</span></p> <p><span style="color: rgb(0, 0, 0);">===========================</span></p> <p><span style="color: rgb(0, 0, 0);">Improve capture of output plugin errors that happen at the end of jobs.</span></p> <h2><span style="font-size: 12px; font-family: Calibri, sans-serif; color: rgb(0, 0, 0);">Add the optional CMYKS mode.</span></h2> <p><b> </b></p> <p>From Aspen R5.1:<br> - Support the swatch sheet for Spot color remapping on a multi-head press.<br> - Include the Remora resolution modes.<br> - Support for SetGold on the multi-head press</p> <p> - Better support for single page jobs on a single head press. In R5, the job could not be re-queued from inside the Press workflow, or if it went first through the Prep workflow it would be padded up to the number of RIPs in use.<br> - Handle jobnames (group lists, actually) that start with multibyte (e.g. Japanese or Chinese) chars.<br> <b><br> </b>From Aspen R5.2:<br> <b> </b>- Add double book mode to the Page Filter Action. <br> - Aspen output plugin (<i>and Durango Spooler)</i> v2019. Add the ability to change the device width through the .ini file. <br> <br> From Aspen CMYKS:<br> - Aspen CMYKS mode, a new device (inside the RIP output plugin), and a new way of adjusting spot colors.<br> - Output all the CMYKS swatch sheet pages in one job.<br> - Disable a call at boot time that was locking up the system at a customer site.<br> - Revert bit 11 to be Thumbnail Action again, CMYKS on the server is simply enabled through an .ini setting.<br> - Attempt to catch Aspen plugin output errors and report them in the client.<i><br></i></p> </div> 1000220978 51 1000216336 2016-09-16T10:46:41-04:00 1003593276 18 2 0 0 Aspen r6 release notes 2017-01-12T15:13:20-05:00 1003593276 1 2016-05-26T11:33:33-04:00 0 0 Aspen r5 release notes <div dir="ltr"> <div> <p dir="ltr">Aspen r5 release notes</p> </div> </div> 1000220978 5 1000232050 2016-09-16T10:47:20-04:00 1003593276 19 2 0 0 Aspen r5 release notes 2017-01-12T15:13:20-05:00 1003593276