VSE - Input Color option does not work for video files #36124

New Issue

Juan Pablo Bouza · 2013-07-12T23:46:37+02:00

Juan Pablo Bouza commented

2013-07-12 23:46:37 +02:00

%%%Ubuntu 64 here, r58187.

The input color space option for individual strips doesn't do anything if the strip is a video file. With image sequences it works well, but not with video files. It just has no effect at all.

%%%

%%%Ubuntu 64 here, r58187. The input color space option for individual strips doesn't do anything if the strip is a video file. With image sequences it works well, but not with video files. It just has no effect at all. %%%

Juan Pablo Bouza commented

2013-07-12 23:46:37 +02:00

Changed status to: 'Open'

Sergey Sharybin commented

2013-07-15 09:58:42 +02:00

%%%Fixed in svn rev58257. Thanks for the report, closing.%%%

Juan Pablo Bouza commented

2013-07-17 17:38:35 +02:00

%%%Not closed!!! :)

Now it all works fine in the viewport, but when you render, it goes back to the error. I tried it with an image and rendering works well, so I guess you missed to modify the rendering flag for videos in this issue??%%%

%%%Not closed!!! :) Now it all works fine in the viewport, but when you render, it goes back to the error. I tried it with an image and rendering works well, so I guess you missed to modify the rendering flag for videos in this issue??%%%

Sergey Sharybin commented

2013-07-17 19:00:29 +02:00

%%%Indeed. But unfortunately, issue goes deeper to how sequencer currently handles the images.

The thing is, for until image buffers stays stored in byte, they're assumed to be in a sequencer's working space. Which means input color space is actually ignoring for them. And the bug here is that sequencer preview is not actually aware of this.

But once image buffer is converted to float (using Convert Float option, or mixing it with another float image) that settings will get into account.

And the thing here is, even to make it so preview behaves same as final render, it'll imply quite a lot of changes which are not safe for the evening of release.

This is rather old issue, and leaving it for after current release.%%%

%%%Indeed. But unfortunately, issue goes deeper to how sequencer currently handles the images. The thing is, for until image buffers stays stored in byte, they're assumed to be in a sequencer's working space. Which means input color space is actually ignoring for them. And the bug here is that sequencer preview is not actually aware of this. But once image buffer is converted to float (using Convert Float option, or mixing it with another float image) that settings will get into account. And the thing here is, even to make it so preview behaves same as final render, it'll imply quite a lot of changes which are not safe for the evening of release. This is rather old issue, and leaving it for after current release.%%%

Sergey Sharybin commented

2013-09-02 15:55:15 +02:00

%%%Fixed in svn rev59734. Please give it an intense testing to see if color spaces in sequencer now behaves reliable.%%%

Sergey Sharybin commented

2013-09-02 15:55:15 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2013-09-02 15:55:15 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

VSE - Input Color option does not work for video files #36124