VSE displaying png metadata/artifacts #86686

New Issue

Georg K · 2021-03-18T04:59:15+01:00

Georg K commented

2021-03-18 04:59:15 +01:00

System Information
Operating system: Linux-5.11.2-1-MANJARO-x86_64-with-glibc2.33 64 Bits
Graphics card: AMD VERDE (DRM 2.50.0, 5.11.2-1-MANJARO, LLVM 11.1.0) AMD 4.5 (Core Profile) Mesa 20.3.4

Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-03-17 12:51, hash: 4de7dc42c9
Worked: 2.91, 2.92

Short description of error
After loading a png created with inkscape, some hidden metadata of that png file (that I could not see using image viewers but only if I open the png in a text editor: line 4 "tEXtSoftware www.inkscape.org") www.inkscape.org is displayed below the image together with artifacts.

Exact steps for others to reproduce the error
export something from inkscape to png
in the VSE, load that png using Add Image/Sequence
text/artifacts appear below the image

png:

result:

**System Information** Operating system: Linux-5.11.2-1-MANJARO-x86_64-with-glibc2.33 64 Bits Graphics card: AMD VERDE (DRM 2.50.0, 5.11.2-1-MANJARO, LLVM 11.1.0) AMD 4.5 (Core Profile) Mesa 20.3.4 **Blender Version** Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-03-17 12:51, hash: `4de7dc42c9` Worked: 2.91, 2.92 **Short description of error** After loading a png created with inkscape, some hidden metadata of that png file (that I could not see using image viewers but only if I open the png in a text editor: line 4 "tEXtSoftware www.inkscape.org") www.inkscape.org is displayed below the image together with artifacts. **Exact steps for others to reproduce the error** export something from inkscape to png in the VSE, load that png using Add Image/Sequence text/artifacts appear below the image png: ![Inkscape export.png](https://archive.blender.org/developer/F9897374/Inkscape_export.png) result: ![Blender bug - VSE inkscape metadata.jpg](https://archive.blender.org/developer/F9897371/Blender_bug_-_VSE_inkscape_metadata.jpg)

Georg K commented

2021-03-18 04:59:15 +01:00

Added subscriber: @georgK

Philipp Oeser commented

2021-03-18 09:30:03 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-03-18 09:30:03 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Philipp Oeser commented

2021-03-18 09:30:03 +01:00

Cannot confirm the artifacts, do you have a chance to test this on a different computer (newer GPU, possibly not using Mesa)?

You can toggle the display of metadata here:

Cannot confirm the artifacts, do you have a chance to test this on a different computer (newer GPU, possibly not using Mesa)? You can toggle the display of metadata here: ![image.png](https://archive.blender.org/developer/F9897591/image.png)

Georg K commented

2021-03-18 16:09:15 +01:00

Okay, I begin to understand that this is not about metadata from photo cameras (Nikon/Canon photo metadata is not displayed), but about metadata blender exports with it's frames using tEXt tags that are also used by inkscape, so this text is displayed. While the metadata display toggle has already been present in 2.92 it is only working in 2.93.

Testing on intel integrated HD graphics (also mesa), there were no artifacts, so those seem to be a "feature" of my Radeon + mesa setup.

Okay, I begin to understand that this is not about metadata from photo cameras (Nikon/Canon photo metadata is not displayed), but about metadata blender exports with it's frames using tEXt tags that are also used by inkscape, so this text is displayed. While the metadata display toggle has already been present in 2.92 it is only working in 2.93. Testing on intel integrated HD graphics (also mesa), there were no artifacts, so those seem to be a "feature" of my Radeon + mesa setup.

Philipp Oeser commented

2021-03-18 16:39:11 +01:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Philipp Oeser commented

2022-01-20 11:43:37 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Philipp Oeser commented

2022-01-20 11:43:37 +01:00

Sorry this has been lying around.

@georgK: could you do me a favor and check if this is still an issue in fresh builds from https://builder.blender.org/download/daily/?
Iirc, AMD VERDE has been put on the list for driver workarounds since.

I assume you have tested starting blender with --debug-gpu-force-workarounds?

Sorry this has been lying around. @georgK: could you do me a favor and check if this is still an issue in fresh builds from https://builder.blender.org/download/daily/? Iirc, AMD VERDE has been put on the list for driver workarounds since. I assume you have tested starting blender with `--debug-gpu-force-workarounds`?

Georg K commented

2022-01-20 18:23:38 +01:00

Thanks for coming back to this issue.

debug-gpu-force-workarounds does not mitigate the problem.

in Blender 3.0.0:

in Blender 3.1.0 Alpha, branch: master, commit date: 2022-01-20 11:55, hash: 969a571e0f
AMD VERDE (DRM 2.50.0, 5.15.12-1-MANJARO, LLVM 13.0.0) AMD 4.5 (Core Profile) Mesa 21.3.2

Seems like the issue moved, but is still present.
Also, it is unclear if the metadata handling has been adjusted or if it is not displayed due to graphics issues. Setting the video sequencer preview background color to white shows nothing in the metadata area with any kind of image I tested. For comparison, there also was no metadata shown on an older 3.1.0 Alpha from this month on a machine with intel HD Graphics (same mesa version).

Thanks for coming back to this issue. - debug-gpu-force-workarounds does not mitigate the problem. in Blender 3.0.0: ![3.0.0 --debug-gpu-force-workarounds.jpg](https://archive.blender.org/developer/F12812959/3.0.0_--debug-gpu-force-workarounds.jpg) in Blender 3.1.0 Alpha, branch: master, commit date: 2022-01-20 11:55, hash: `969a571e0f` AMD VERDE (DRM 2.50.0, 5.15.12-1-MANJARO, LLVM 13.0.0) AMD 4.5 (Core Profile) Mesa 21.3.2 ![latest 3.1.0 --debug-gpu-force-workarounds.jpg](https://archive.blender.org/developer/F12812717/latest_3.1.0_--debug-gpu-force-workarounds.jpg) Seems like the issue moved, but is still present. Also, it is unclear if the metadata handling has been adjusted or if it is not displayed due to graphics issues. Setting the video sequencer preview background color to white shows nothing in the metadata area with any kind of image I tested. For comparison, there also was no metadata shown on an older 3.1.0 Alpha from this month on a machine with intel HD Graphics (same mesa version).

Philipp Oeser commented

2022-02-04 08:57:17 +01:00

Added subscriber: @Jeroen-Bakker

Philipp Oeser commented

2022-02-04 08:57:17 +01:00

I still cannot reproduce artifacts, this is what it looks like here:

@Jeroen-Bakker : can you reproduce?

Other than that, I will set this to "Unconfirmed" with the following consequences:

The issue reported can't be reproduced so far, and has been moved to the *BF Blender: Unconfirmed* project.
If 2 other people aren't able to redo the bug after 2 weeks, it will be closed.

We appreciate the effort that goes into making bug reports, but to be able to fix bugs we have to be able to redo them.
If there is anything you can provide to help others to reproduce the problem, be sure to include it.

I still cannot reproduce artifacts, this is what it looks like here: ![image.png](https://archive.blender.org/developer/F12845274/image.png) @Jeroen-Bakker : can you reproduce? Other than that, I will set this to "Unconfirmed" with the following consequences: ``` The issue reported can't be reproduced so far, and has been moved to the *BF Blender: Unconfirmed* project. If 2 other people aren't able to redo the bug after 2 weeks, it will be closed. We appreciate the effort that goes into making bug reports, but to be able to fix bugs we have to be able to redo them. If there is anything you can provide to help others to reproduce the problem, be sure to include it. ```

Georg K commented

2022-02-15 20:43:42 +01:00

Out of the blue, the artifacts are gone in 3.2. They are still present in 2.93.0 and 3.0.1, so it seems to be due to a change in Blender, not to an OS upgrade.
With a buildbot build from the same date as my previous test, in most sessions the VSE artifacts are still there, but in some sessions, they are not.

In any case, the metadata is still not displayed anymore (it was in 3.0.1). It seems like metadata handling has been changed since the metadata area in the N-panel is also empty in contrast to 2.93/3.0.1 where it showed the same info as the Preview.

Just noticed Pablo having artifacts in the VSE as well, although only when scaling: https://youtu.be/TPRhIS4NOt0?t=2488 (at 41:30).

Out of the blue, the artifacts are gone in 3.2. They are still present in 2.93.0 and 3.0.1, so it seems to be due to a change in Blender, not to an OS upgrade. With a [buildbot build from the same date as my previous test](https://builder.blender.org/download/daily/archive/blender-3.1.0-alpha+master.eb3ff1d6f9ca-linux.x86_64-release.tar.xz), in most sessions the VSE artifacts are still there, but in some sessions, they are not. In any case, the metadata is still not displayed anymore (it was in 3.0.1). It seems like metadata handling has been changed since the metadata area in the N-panel is also empty in contrast to 2.93/3.0.1 where it showed the same info as the Preview. Just noticed Pablo having artifacts in the VSE as well, although only when scaling: https://youtu.be/TPRhIS4NOt0?t=2488 (at 41:30).

Philipp Oeser commented

2022-03-24 14:10:45 +01:00

Added subscriber: @pablovazquez

Philipp Oeser commented

2022-03-24 14:10:45 +01:00

Metadata is still (and always was) diplaying for me:

@pablovazquez : doe you have the issue reported here (missing metadata) as well?

Metadata is still (and always was) diplaying for me: ![image.png](https://archive.blender.org/developer/F12942652/image.png) @pablovazquez : doe you have the issue reported here (missing metadata) as well?

Philipp Oeser commented

2022-04-05 10:44:21 +02:00

OK, ringing the bell for the last week of keeping this report (since it still could not be reproduced elsewhere)

Philipp Oeser commented

2022-04-26 08:59:56 +02:00

Changed status from 'Needs User Info' to: 'Archived'

Philipp Oeser closed this issue

2022-04-26 08:59:56 +02:00

Philipp Oeser commented

2022-04-26 08:59:56 +02:00

In #86686#1335633, @lichtwerk wrote:
OK, ringing the bell for the last week of keeping this report (since it still could not be reproduced elsewhere)

Think we should close this now.

> In #86686#1335633, @lichtwerk wrote: > OK, ringing the bell for the last week of keeping this report (since it still could not be reproduced elsewhere) Think we should close this now.

Omar Emara commented

2022-06-20 08:37:27 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-06-20 08:37:27 +02:00

Changed status from 'Archived' to: 'Needs Developer To Reproduce'

Omar Emara reopened this issue

2022-06-20 08:37:27 +02:00

Omar Emara commented

2022-06-20 08:37:27 +02:00

I can replicate this, it is exactly the same as the issue in #98620 but with older AMD GPUs. Those GPUs are no longer supported, so not sure if will handle this.
--debug-gpu-force-workarounds doesn't work because the workaround was accidentally left out of the force workaround list when it was added.

I can replicate this, it is exactly the same as the issue in #98620 but with older AMD GPUs. Those GPUs are no longer supported, so not sure if will handle this. `--debug-gpu-force-workarounds` doesn't work because the workaround was accidentally left out of the force workaround list when it was added.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

VSE displaying png metadata/artifacts #86686