Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Media Selection

66 views
Skip to first unread message

Jan

unread,
Oct 22, 2024, 4:41:51 AM10/22/24
to XMPie Interest Group
Hello,

I'm trying to get Media selection (just static in this case) to work with our Canon Varioprint digital press but I'm not getting anywhere.
I need to assign a different media to each spread. I'm exporting as pdf/vt-1. The printer has a PRISMAsync controller. But after I send the pdf to the printer (via Prisma remote controller) it switches to default paper.
Does anyone have experience with how to correctly identify the media for presses running PRISMAsync? 

Jan

unread,
Oct 22, 2024, 4:44:45 AM10/22/24
to XMPie Interest Group
Alternatively, I could do the same via jdf ticket, but my jdf tickets that work fine for regular pdfs, again don't work for pdf/vt-1 (everything is switched to default media). Any tips on what needs to be changed in the tickets?

couch

unread,
Oct 22, 2024, 9:54:46 PM10/22/24
to XMPie Interest Group
I don't have any experience with the Canon Varioprint, but there are some different examples shown here: https://help.xmpie.com/KBA/index.htm#t=0019%2F0019_Advanced_RIP-specific_features_with_XMPie.htm

In general, you need to find out if the rip works with:
* "named" media - where you define a media name in a library on the rip, and need to set the same name in the output file,
* specific media "attributes" like type/color/weight - where you need to define one or more of the attributes in the output file, or
* totally custom media calls like some old Fiery rips.

There are examples of all three in the KB article.

west-digital.fr

unread,
Oct 23, 2024, 11:25:05 AM10/23/24
to XMPie Interest Group
Believe me or not but the local representatives for this printer manufacturer recently advised that, when it turns to send a JDF and a related PDF to this very Front End, then the only solution was to merge both files into a single file, then submit.
So, we had to develop some automation for our customer.
Obviously, it's then impossible to view the resulting file in Acrobat Reader or another PDF Viewer application - as they think that the file has been corrupted, due to the unexpected XML/JDF header.
But based on our experience, the Front End and the printer then follow the JDF directions and print the PDF accordingly.
Unfortunately, the above only concerns regular (Adobe) PDF documents - we did not experiment PDF/VT, as in your case.

Jan

unread,
Oct 24, 2024, 2:37:55 AM10/24/24
to XMPie Interest Group
west-digital.fr, I don't know about your situation, but for me, hotfolders with jdf tickets are working without any issues with normal PDF documents. It is when I switch to PDF/VT that I run into problems.
Reply all
Reply to author
Forward
0 new messages