Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Thread

QuadTone RIP - GUI - Problem with Automated Printing (Monitor Folder)

QuadTone RIP - GUI - Problem with Automated Printing (Monitor Folder)

2005-11-27 by fjohn1963

I tried several searches of this group but came up with nothing, so 
here is my issue:

I'm having a problem with the automated printing functions in the 
QTR 
QUI application. I'm currently using v2.2.4.

I used to be able to copy more than one file to the folder that the 
GUI is monitoring, and the app would dutifully process each of them 
in 
succession. Unfortunately, starting a few versions ago, if I copy 
more 
than one image to the monitored folder, it causes the GUI app to 
hang 
and I have to shut it down in the task manager.

A specific scenario is as follows:

- Copy an image to the monitored folder (Image 1)
- QTR-GUI picks up the image and starts printing (Image 1)
- While QTR-GUI is printing, copy another image to the folder (Image 
2)
- Image 2 disappears from the monitored folder
- Image 1's spool entry builds and builds beyond the normal byte 
count.
- QTR-GUI eats up all of the system cycles and runs at 100%
- I have to kill the QTR-GUI task

It's as though, despite not being done with the first image, QTR-GUI 
sucks in the 2nd image too and everything gets clogged up.

I'm sorry, I don't remember for sure when it started doing this. I 
believe it was when I installed one of the betas, maybe about 6-9 
months ago.

I've been living with loading one image at a time and waiting until 
QTR-GUI finishes processing it, but it's really getting old.

Has anybody else encountered and fixed this problem?

Thanks.

John F.

RE: [Digital BW] QuadTone RIP - GUI - Problem with Automated Printing (Monitor Folder)

2005-11-28 by Stephen Billard

I am unable to reproduce the problem you describe on the current version of
QTRgui. The current version is 2.3.13. Please update to this version and see if
the problem still exists. 

-Stephen
 www.sbillard.org/Stephen
Show quoted textHide quoted text
> -----Original Message-----
> From: DigitalBlackandWhiteThePrint@yahoogroups.com 
> [mailto:DigitalBlackandWhiteThePrint@yahoogroups.com] On 
> Behalf Of fjohn1963
> Sent: Sunday, November 27, 2005 10:48 AM
> To: DigitalBlackandWhiteThePrint@yahoogroups.com
> Subject: [Digital BW] QuadTone RIP - GUI - Problem with 
> Automated Printing (Monitor Folder)
> 
> 
> I tried several searches of this group but came up with nothing, so 
> here is my issue:
> 
> I'm having a problem with the automated printing functions in the 
> QTR 
> QUI application. I'm currently using v2.2.4.
> 
> I used to be able to copy more than one file to the folder that the 
> GUI is monitoring, and the app would dutifully process each of them 
> in 
> succession. Unfortunately, starting a few versions ago, if I copy 
> more 
> than one image to the monitored folder, it causes the GUI app to 
> hang 
> and I have to shut it down in the task manager.
> 
> A specific scenario is as follows:
> 
> - Copy an image to the monitored folder (Image 1)
> - QTR-GUI picks up the image and starts printing (Image 1)
> - While QTR-GUI is printing, copy another image to the folder (Image 
> 2)
> - Image 2 disappears from the monitored folder
> - Image 1's spool entry builds and builds beyond the normal byte 
> count.
> - QTR-GUI eats up all of the system cycles and runs at 100%
> - I have to kill the QTR-GUI task
> 
> It's as though, despite not being done with the first image, QTR-GUI 
> sucks in the 2nd image too and everything gets clogged up.
> 
> I'm sorry, I don't remember for sure when it started doing this. I 
> believe it was when I installed one of the betas, maybe about 6-9 
> months ago.
> 
> I've been living with loading one image at a time and waiting until 
> QTR-GUI finishes processing it, but it's really getting old.
> 
> Has anybody else encountered and fixed this problem?
> 
> Thanks.
> 
> John F.
> 
>

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.