I could run a test for you on a Windows machine and let you know the processing time if that would help, so you can compare to what you are currently doing. I'd need some information to try to duplicate the type of job we are comparing. Just pick a typical job that you can (re)time: you can use print preview so you don't actually use paper since we are only interested in the processing time. I'd need to know:
- Type of printer
- Page size you are using (displayed above the live view)
- Resolution setting in Qimage One (600, 720, etc.)
- Typical resolution of the images you are printing (6000x4000 for example)
- Type of images (TIFF, JPEG, PSD, etc.)
- The size and number of prints in the job (four 30x20, six 13x19, and two 8x10 as an example)
If I have that info, I can run it and see how long it takes. Since the Windows version is multithreaded, I've found that it can print almost as fast as the spooler can accept data. I've considered the idea of adding a feature that just records the spool file so it can be sent again without the processing time, but I'm not convinced it would be a lot faster and you lose a lot of features such as the ability to change paper type, use a new printer profile, substitute new images, and so on. It would be an interesting comparison particularly since given the price of many RIPs, it'd be cheaper to buy a high end PC... or wait until we get the multithreading optimization in the Mac version.