blurred image when using export snapshot

[per_bodelius]

Hi,
When I use export snapshot on IOS or Android it´s no problem.
But when using the same code in windows, (export snapshot from rect(the rect of graphic "captureimg") to file fullpictPath & "/newImage.jpg" as jpeg) I get the result you can see below (the right image)



The exported image gets blurred. Is this a specific windows problem or am I doing something wrong ?
Is there any way to control the quality of the exported image.

Best regards
Per Bodelius

[FourthWorld]

What is the jpegQuality global property set to?

[per_bodelius]

Hi,
I have set it to 100 ( like this: set the JPEGQuality to 100)

[FourthWorld]

If that hasn't improved output quality you might consider filling a bug report.

[Saman Sjr.]

have you change the Resize quality property of graphic "captureimg" object to "good" ot "best" ?

[per_bodelius]

Yes I have tried with Resize quality but i get the same result...

[[-hh]]

From dictionary: The JPEGQuality setting is used when a file is exported in JPEG

And you set it to 100. So your result shows obviously a bug on Windows. Please report to https://quality.livecode.com

[FourthWorld]

I just tested this on Win10 and was unable to reproduce it without changing the jpegQuality to a really low number (>40). Anything higher looks pretty good, and the default of 100 is nearly visually indistinguishable from the original.

Is there any resizing or other factors I'm not taking into account in my effort to reproduce this?

[per_bodelius]

The image I sent first as an example was created in LiveCode Indy 9.5 . A moment ago I tried the same stack in LC Indy 9.0.1 and the result is nearly perfect! I looks like a bug in LC 9.5 or what do you think?

[FourthWorld]

It might be, as I didn't test on v9.5. I tested in v9.5.1. Before filling a bug report it may be good to double check in v9.5.1.

9.5.1 also has some critical fixes related to memory deallocation, so it's an excellent version to work with for many reasons.

If 9.5.1 works well, and given that 9.0.1 works well, it may be worth double checking the test in 9.5. More than once I've changed a global property setting while experimenting and forgot that I did so. If that's what happened here at least you're in good company. And if not at least we know the team caught it and fixed it quickly.

[FourthWorld]

Update: I just tested in v9.5 on Win10. Good result.

Updating to v9.5.1 is a good move for other reasons, but at least you don't need to file a bug report against v9.5.

[per_bodelius]

Hi Richard,
Thanks for your engaged and fast support! I have just updated to 9.5.1 and the result is just perfect.
From now I will always try with the latest version first before start complaining on our forum ...

Regards
Per B

[FourthWorld]

No worries. The 9.0.5 and 9.5 cycles were unusual, in that some fixes went into 9.0.5 before a 9.5.x was released that included them. So you're in good company, a lot of folks continued using 9.0.5 even after 9.5 came out.

But in general, using the latest version can be very helpful. In addition to (usually) containing the latest features, when submitting a bug report the question of whether the issue is still present in the most recent build will be among the first steps in diagnosis.