As the title says: I am running into a "Range check error" when printing to file.

Details:
I am using QU 2017.127 on a W10 X64 machine, Windows version 1703 (OS build 15063.332)
The printjob consists of one A4 sheet wit a centered 120 x 120 mm B&W image.
I send the file to my desktop, all other settings default, filename 'test' (without the quotation marks).
When I change the file format to TIFF I don't see the error message.

I did not print it to paper yet, so I don't know what is going to happen when I do that.
That is something for later tonight, I will amend this post then.

I attach a screenshot so you can see what is happening.

When you need more details please say so.

[edit]
I got no error message when printing to paper.
[/edit]

Thank you Fred for confirming there is 'something' weird going on.


Same thing as before, the same Range check error message.
But... are we doing the same thing?
Your saying right click on Properties to go to Print to file makes me wonder.

In order to print to file I just set the Job properties under the Printers and Settings tab > Printer/Media to Print to File (see attached screenshot).
Frankly I am not aware of a right click somewhere which would lead to Print to file (still learning after all these years......  )

So what I did now in reply to your message:
- recalled the "Print to file" job that gave me the error first time, the job that made me start this topic
- Clicked Edit > preferences > Units > Imperial
- Clicked the Printer icon
- The same Range check error pops up

A new error appears, right clicking the Properties to toggle between print to paper and print to file I now get an access violation message, see screenshot.

My sequence...
set up print in metric format 120mm x 120mm.  047
Change to Imperial. See size in inches. 048
Show cursor ready to right click Properies button. 049
Show Print to file screen open with no error. 050

Fred

As it is now, after forced exit of QU, reboot of the machine, reconfiguring of QU, I can't get it to produce the error message again.

I tried it several times, both with setting up fresh jobs and recalling existing ones.

Beats me.

I am prepared to believe there is something wrong with my PC, either hardware- or software wise which caused this.
But how come Fred had something similar? Not exactly the same thing, but it seemed related?

Perhaps it is time (at least over here in Europe....) to get some sleep and see what happens tomorrow.
It is 22:30 over here, maybe things clear up after some sleep.

Hi Fred,

Thank you for your patience.
I am really glad Mike found something, although you guys were not able te reproduce the error I had here.

I just tried the whole sequence I used last night, and which produced the "Range check" error, again.
Guess what... no problem, things work as usual.
I can reproduce the "Out of system resources" error you saw by switching from Metric to Imperial just before right clicking properties.
Mind you, I saw that error last night as well, but in a slightly different sequence of actions.

In retrospection, I was processing some images last night using three different programs: my DAM (IMatch), my preferred raw converter (DxO) and QU. I don't recall if I had DxO open when the error first showed up.
I do know though that things went back to normal when I closed all programs and rebooted the machine.
I have also observed (as reported in this topic) that QU would not close down normally (clicking the X in the top right corner of the QU window), throwing all kinds of errors at me when I clicked that X, until I forcibly ended it via the Windows task manager.

It may have been a one-time memory leak issue caused by one of the programs and a specific sequence of events.
If it occurs again I will report back.

In the mean time I am looking forward to v128.

Thank you again for your time, your help and your patience!

Herman.