August2007

 

 

SUPPORTUPDATE: Rendering issues seen on Windows 2003 Server/other Windows OS's

For sometime we have seen images render through the ROES Server as if they arenegatives, mostly on Windows 2003 Server.  Finally, we were able to findthe cause and duplicate it on Windows Vista and 2003 Server.  The issueappears to be caused by the Windows display settings being in High Color/Medium(16 bit) - changing these to True Color/Highest (32 bit) mode allows theseimages to render properly.  In Display Properties - Settings tab, justchanging from Medium (16 bit) to Highest (32 bit) and re-starting the serverwill resolve this.

 

 

NewServer Available

The newROES Server is in use at several labs and offers several new features andfunctions:

 

NewAttribute - autoenqueue - The autoenqueue attribute canbe added on products within a catalog to allow them to automatically be sent tothe rendering printer in the ROES Server (leave the checkbox empty in theOptions tab for Auto-enqueue order items). This is ideal for single image prints and non-corrected workflow queues in theserver.  To add the new attribute quickly, be sure to highlight a numberof products in the catalog (or all of them), right-click and select DistributeAttribute, then enter autoenqueue for the attribute and true for the value,then click OK.

 

NewFuji PIC Pro Render Direct printer type - Ideal fornon-corrected/ready-to-print workflows, it will render the products first andthen feed as simple units into PIC Pro.

 

New Output File Naming for rendered items - The default naming for therendered files and the checkbox for 'Use image names..." haschanged/been removed.  Report or self-defined macros can now be usedto generate the file names of any rendered order item in the OutputFile Name: field.  Examples:

 

Basicmacro use:

[UNIT_INDEX(04)]_[UNIT_PRODUCT_DESCRIPTION]_QTY[UNIT_QUANTITY]

Setspadded 4 character index, followed by the description and quantity needed ofthe item being rendered.

 

Self definedmacro (very long, but end result is 0001_firstimagename.jpg):

[UNIT_INDEX(04)]_[SET_MACRO(UNIT_FIRST_IMAGE, "undefined")][BEGIN_UNIT_NODE_LIST][BEGIN_IF(("<UNIT_NODE_INPUT_TYPE>" == "image") &&("<UNIT_FIRST_IMAGE>" == "undefined") )][SET_MACRO( UNIT_FIRST_IMAGE,"<UNIT_NODE_IMAGE_PATH>")][END_IF][END_UNIT_NODE_LIST][GET_FILENAME_SANS_EXTENSION(<UNIT_FIRST_IMAGE>)]

Thismacro works well in all rendering printers, as the padded index keeps the itemsin order, especially in PIC Pro.  For proofing orders where the index willnot be needed (not likely 2 of the same image rendered), the [UNIT_INDEX]_ canbe removed to just get the image submitted via ROES.

 

BackprintingValues Using Report Macros - Report macros can be combined for backprinting values:

 

BackprintLine 1, for instance, could use [LAB_ORDER_ID]_[CUSTOMER_NUMBER]

This willgive the server generated order number and then the customer account number orstudio name.

 

BackprintLine 2 could use [SET_MACRO( UNIT_FIRST_IMAGE, "undefined")][BEGIN_UNIT_NODE_LIST][BEGIN_IF(("<UNIT_NODE_INPUT_TYPE>" == "image") &&("<UNIT_FIRST_IMAGE>" == "undefined") )][SET_MACRO(UNIT_FIRST_IMAGE, "<UNIT_NODE_IMAGE_PATH>")][END_IF][END_UNIT_NODE_LIST][GET_FILENAME_SANS_EXTENSION(<UNIT_FIRST_IMAGE>)]

This willgive just the image name submitted through ROES (or first image if acomposite). 

 

Report AbilitiesIt is now possible to embed squarebrackets in a text or HTML report using the escaped character set - for aleft bracket use &lb; and for right bracket use &rb; in the report, forexample &lb;BEGIN_ORDER&rb; for an order header.

 

 

NewErrors Area     in Messages tab - Available via the View Logdropdown list, any order that fails to process initially through the serverwill be listed to provide data on the order.  The order canbe cut/pasted from the Done/Finished Orders folder into Incoming Orders to tryto re-process or the ROESServer log file in Working Files can be searched forthe order number to find the error that occurred.

  

 

RE-ORDERSTHROUGH ROES/ROES Commentator

The ROESCommentator is a Java application that adds original order data(comments) into an image file's header so that the image can be used forre-ordering.  DP2 labs have a built-in utility from Kodak that allowscreation of lower resolution proxy images, where we added a script to add theorder and image file name to the proxy for use in re-ordering throughROES.  When these images are used, the ROES Client reads the originalorder values in the header and does not pull the proxy image into the order,keeping the re-order files small.  Once the ROES Server receives theorder, it will use the original image back at the lab based on the data inthe order file, ensuring that the same retouched/corrected image is used in creatingthe job/order item. 

 

Fornon-DP2 labs the workflow is the same on the client side, where 'commented'images will allow the studios to reorder images from a single or multipleoriginal orders, and mix in new images if desired.  To create the imagesneeded for re-ordering use, you will need to decide on whether to use theoriginal images or generate lower-res proxies first, and maintain the sameorder number folder and image file names.  Then open the ROES Commentator(http://www.softworksroes.com/ROES/Commentator/launch.jnlp)and drag/drop the entire order images folder onto the Commentator window. This will add the order number and image name as Comments into the imageheader.  This folder of images or proxies can then be sent back to thestudio on CD or downloaded as a zip file.  The folder would then beavailable to be selected in the thumbnail area of the ROES Client to be used incropping into products, and upon completion only the header comments will beadded to the order information, not the image/proxy, speeding ordertransmission time and reducing storage needs.