Bug 75346

Summary:	[SLIDESHOW] Images scaled down poorly, resulting in aliasing/moire patterns
Product:	LibreOffice	Reporter:	Mike Doherty <mike>
Component:	Impress	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED INSUFFICIENTDATA
Severity:	normal	CC:	ilmari.lauhakangas, jbfaure
Priority:	medium
Version:	4.1.3.2 release
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	103610, 104238
Attachments:	Editing view - no moire pattern Presentation view - severe moire pattern

Description Mike Doherty 2014-02-22 03:40:39 UTC

I have a presentation with a very large image. In editing view, it gets scaled down nicely, and there's very little in the way of aliasing or moire pattern visible. When I run the presentation, the image is scaled poorly, and severe moire patterning is visible. The same thing happens if I remove the background and instead insert the image as a normal image object in the slide itself.

I have both hardware acceleration and antialiasing enabled in Options > View > Graphics output.

The best workaround is to:
  - scale the image to the right size and resolution yourself outside Impress, or
  - insert the image as an image object within the slide, and then right-click on it, and select "Compress graphic" to scale it down to size

Either of these will permanently change the image in your presentation, so you might end up changing the image for each different output device.

Instead, Impress should scale the image down better.

I'll attach screenshots showing the effect shortly.

Comment 1 Mike Doherty 2014-02-22 03:41:34 UTC

Created attachment 94548 [details]
Editing view - no moire pattern

Comment 2 Mike Doherty 2014-02-22 03:42:28 UTC

Created attachment 94549 [details]
Presentation view - severe moire pattern

Comment 3 Jean-Baptiste Faure 2014-04-21 20:12:14 UTC

Please could you attach a presentation document showing the problem?

Note: we do not need your photo and your cv, the part of the cloth showing the moire effect.

Best regards. JBF

Comment 4 QA Administrators 2014-11-02 16:46:31 UTC Comment hidden (obsolete)

Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

Comment 5 Mike Doherty 2014-11-02 18:00:44 UTC

I've uploaded a presentation with just the one problematic slide to Dropbox, because it's too large to be uploaded here: https://db.tt/pOAmrtYc

Comment 6 Buovjaga 2014-11-16 17:37:20 UTC

(In reply to Mike Doherty from comment #5)
> I've uploaded a presentation with just the one problematic slide to Dropbox,
> because it's too large to be uploaded here: https://db.tt/pOAmrtYc

Moire reproduced on Ubuntu and not reproduced on Windows.

Win 7 64-bit Version: 4.4.0.0.alpha2+
Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827
TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08

Ubuntu 14.10 64-bit Version: 4.4.0.0.alpha2+
Build ID: 3cf226622a3d8c09d655034dbcc81695f1662b87
TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-11-15_23:24:22

Comment 7 QA Administrators 2015-12-20 16:15:42 UTC Comment hidden (obsolete)

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later)
https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:

1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug

3. Leave a comment with your results.

4a. If the bug was present with 3.3 - set version to "inherited from OOo";

4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-12-20

Comment 8 QA Administrators 2017-01-03 19:49:18 UTC Comment hidden (obsolete)

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice
(5.1.6 or 5.2.3 https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and
your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to "inherited from OOo";
4b. If the bug was not present in 3.3 - add "regression" to keyword

Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug-20170103

Comment 9 Buovjaga 2019-01-11 11:29:24 UTC

The Dropbox link is now 404. Our upload limit is currently 30MB. Mike: please attach the presentation. Well, re-test before uploading.

Comment 10 QA Administrators 2019-07-11 02:55:35 UTC Comment hidden (obsolete)

Dear Mike Doherty,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

Comment 11 QA Administrators 2019-08-19 07:07:30 UTC

Dear Mike Doherty,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp