Page MenuHome
Create Task
Maniphest T43428

Rendering Bug in VSE with 3D scenes and imported images (skipping of current frame to the end frame during rendering)
Closed, ArchivedPublic
Actions

Description

System Information
Windows 8.1 64 bit; no dedicated GPU (Intel HD 4000)

Blender Version
Broken: (2.73)
Worked: Previous versions have had similar issues but 2.72 is working for me

Short description of error
I did a mixture of creating texts in a scene and then overlaying it to images I have in the Video Sequence Editor. Periodically I will stop the render and continue another day.

This morning when I continued, I noticed it was not rendering anything from the Sequencer, producing transparent images with just my 3D text alone. I disabled and re-enabled the Sequencer in Render > Post Processing settings. That's when Blender started to render from the end of the timeline and combined the 3D text from there to the current frame of the image imported into the VSE and produced the bad PNG sequence. I used Blender rendering engine for this but the problem occurred when I switched to Cycles rendering engime as well.

Exact steps for others to reproduce the error
Not sure if it's repeatable (but I do tend to notice after several thousands of frames for every project I've ever done, the greenbar in the timeline will begin to glitch to the end during rendering, but shifts back to the current frame after rendering is complete with no issues to the output)

  1. Create an object in the 3D view (preferably text to reproduce the problem)
  2. Import the scene into VSE
  3. Have a movie/image sequence greater than about 8000 frames being rendered into a PNG sequence (roughly here it glitches, my problem today occurred at 8307 frames)
  4. Before hitting the 8000 mark, periodically close the file and reopen it and continue rendering (don't save the file)

Event Timeline

Dav (GangstaRas) created this task.Jan 27 2015, 12:02 PM
Dav (GangstaRas) claimed this task.
Dav (GangstaRas) raised the priority of this task from to 90.
Dav (GangstaRas) updated the task description. (Show Details)
Dav (GangstaRas) added projects: BF Blender, Video Sequencer.
Dav (GangstaRas) edited a custom field.
Dav (GangstaRas) added a subscriber: Dav (GangstaRas).
Sergey Sharybin (sergey) lowered the priority of this task from 90 to 30.Jan 27 2015, 2:05 PM
Sergey Sharybin (sergey) added a subscriber: Sergey Sharybin (sergey).

It is important to have .blend file with which you're able to reproduce the issue. Otherwise it'll be unclear if there's some setting set up different from you or the issue is not really reproduceable on another machine.

Waiting 8K frames to render is also not the best usage of developers time, hence:

  • Is it Cycles rendering? if so, is it GPU or CPU rendering?
  • Did you try command line render, does it make sequence to render properly?
  • Did you try rendering in the Fullscreen mode (Display option in the Render panel)?
  • Did you try rendering with the locked interface? (the option is next to Display on the same panel)
  • Are the circumstances when failure happens faster than after 8 frames?
Dav (GangstaRas) added a comment.Jan 27 2015, 8:44 PM

As stated, it happens in both Cycles rendering and Blender engine rendering. It is however CPU rendering, I am unable to test GPU rendering. For your other pointers, I did not try those (I'm fairly new to Blender). What fixed my issue was changing my rendering output from PNG to JPG by accident. This caused the rendering to start over from the beginning (no image sequences in that format). When I changed it back to PNG now with Overwrite still unchecked in the Output menu, everything worked fine again. I immediately saved the .blend file in this condition which is why I refrained from publishing it.

I understand however that without the .blend file and a means of properly reproducing the error, it is hard for developers to help this glitch. It's the first time today Blender messed up the output because of it however, so its new to me too. It also messed it up across versions so it's to my belief that someway somehow the the .blend save got corrupted rather than something wrong with the program itself. All I can assure you is that after a prolong period of rendering, the time cursor glitches beyond the current frame as its showing the rendering process but the output is corrected to where it should be.

If the main issue happens again though, I'll be sure to make sure the .blend file stays in the "sick" state for publishing to you guys to see what's really up.

Kunda (Kunda) added a subscriber: Kunda (Kunda).Feb 2 2015, 12:29 AM
Julian Eisel (Severin) changed the task status from Unknown Status to Unknown Status.Feb 8 2015, 2:59 PM
Julian Eisel (Severin) added a subscriber: Julian Eisel (Severin).

Closed for now as it seems rather hard to reproduce the issue and the problem isn't reproducable by @Dav (GangstaRas) himself anymore. We can consider reopening if it happens again.