Page MenuHome
Create Task
Maniphest T25024

Image Scopes w/o Interlace
Closed, ArchivedPublic
Actions

Description

It seems to me that the scopes are computed without taking care of the interlace options. Which makes a lot of spikes in them.

Event Timeline

francoisgfx (francoistarlier) edited a custom field.Dec 3 2010, 1:10 PM
francoisgfx (francoistarlier) attached 1 file(s): F13871: scopes.JPG.
Ton Roosendaal (ton) added a comment.Dec 3 2010, 1:17 PM

Right, there's no de-interlace in Blender available for this. The node system has no interlace support at all even, sequencer does though.

I'm not sure if we want interlace support in our compositor even... it makes the pipeline even more complicated. Is being evaluated if that's worth the complexity.

Ton Roosendaal (ton) changed the task status from Unknown Status to Archived.Dec 3 2010, 1:17 PM
francoisgfx (francoistarlier) added a comment.Dec 3 2010, 3:24 PM

then the workflow is this ?
- import the interlace footage in NLE
- export to tga as progressive
- import new sequence in Compositor

o_O

Ton Roosendaal (ton) added a comment.Dec 3 2010, 4:41 PM

You could try...
issue is mainly that we first focus on having a decent 3D creation pipeline, with compositor meant to use directly images from the rendering system. Blender isn't really a video editor... but the sequencer still supports it.