Page MenuHome

AVI Raw index corrupted
Confirmed, NormalPublic

Description

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: rB0330d1af29c0
Worked: Never

Short description of error
Rendering AVI RAW file will create file with invalid or corrupted index. This seems to happen only with 3840x2160 resolution.

Exact steps for others to reproduce the error

  1. Open file
  2. Render animation
  3. Open rendered file in VLC

Related Objects

Event Timeline

This video only consists of glossy letters on a black background. Using ANY other format for video output, played at 3840 x 2160, creates horrific white splotches all over the background. AVI Raw is the only format that will generate an output file that displays cleanly at full screen resolution, 3840 x 2160.

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Wed, Sep 9, 6:54 AM

AVI Raw is the only format that will generate an output file that displays cleanly at full screen resolution, 3840 x 2160.

Are you talking about video compression? because there should be more options for lossless output like MPNG, FF#1 or huffYUV.

Can you upload .blend file separately, so we can render only cube to examine the issue? I assume the bug will be still there in such case and even in lower resolution?

Also can you link to existing report?

The .blend file is already included in the .ZIP file attached to this report. "Link to existing report" ... not sure what you mean, you're already here. But here is the link....

https://developer.blender.org/T80482#1012225

(Sorry for so many edits) ... I have set compression to 0 to avoid any potential lossy compression. It did not help. You have the .blend file; you'll see.

I meant

The .blend file is already included in the .ZIP file attached to this report.

Yes, I just didn't want to download 300M file just for .blend file. Nevermind, I will download the whole thing.

"Link to existing report" ... not sure what you mean, you're already here. But here is the link....

I meant "This has been reported before and was lowered from 90 to 30 in priority for some reason; the person reporting it never followed up so it was never addressed."

Okay maybe just be a little more specific that you just want the .blend file to avoid the download.

The prior report came up on Google but of course now I can't remember the exact search terms I used.

I'm really not trying to be a disrespectful smart a** but it just isn't that complicated. Just download what I uploaded. Load the blend file and press ctrl+F12. That's it. Let it generate the output and the bug is duplicated. Already more time has been wasted parsing details redundantly and trying to avoid download time than would ever have been required to have you examining the index on that completed AVI output file. I set everything up specifically so all you have to do is load the .blend file and press ctrl+f12. I was very careful about making things as easy as I can. I have been an assembly language developer since 1984 and I've been programming since 1976. I have a sense of how to make debugging easy and complete for the devs.

Richard Antalik (ISS) renamed this task from AVI Raw Corruption to AVI Raw index corrupted.Fri, Sep 11, 3:35 AM
Richard Antalik (ISS) changed the task status from Needs Information from User to Confirmed.
Richard Antalik (ISS) updated the task description. (Show Details)

Using this site’s search function, ‘AVI Raw’ returns T60091 as the second result, which fits the description of the prior report.

This has been reported before and was lowered from 90 to 30 in priority for some reason;

@Chris Malcheski (CMalcheski) these numbers are the result of the re-organization of the bug tracker that was done last December. Unfortunately, there was an issue (the details of which I don’t know) that didn’t allow the old priorities and statuses to keep their names. 90 was ‘Needs Triage’ and 30 was ‘Needs Information from User’ if I recall correctly. Hope that clarifies that bit at least.