[Bf-committers] Speeding up sequencer scopes drawing

Roger Wickes rogerwickes at yahoo.com
Mon Jan 26 16:53:15 CET 2009

proxies come to mind, which are say 25%, but perhaps another proxy could be computed. 1/16 is like 4%
Sent by Roger Wickes for intended recipient. If you are not the intended recipient, please delete this message and contact Mr. Wickes immediately. 

From: Xavier Thomas <xavier.thomas.1980 at gmail.com>
To: bf-blender developers <bf-committers at blender.org>
Sent: Monday, January 26, 2009 5:36:17 AM
Subject: [Bf-committers] Speeding up sequencer scopes drawing


I use a lot the scope views in the sequencer, and having 4 of them opened at the same time (histogram, vectorscope, waveform and separated channels waveform) really slow down "time navigation". (each time we change the current frame the scopes need a lot of time to actualize)

I read somewhere (don't remember where) that some commercial NLE programs use a subsampled version of the image (16 entire lines evenly distributed of the original image) to create the scopes. The trick in blender would be to make each scope view use the same subsampled image (if each view recalculate his own subsampled image the preformance gain won't be the same). Maybe adding a scope view that show all the scopes in the same view is a simpler solution.

Further, maybe the subsample fct (or an other fct) can convert all float image to int so the scope drawing functions for float image can be dropped to keep the code base smaller. 

I will make fiew tests to investigate this, but please (Peter) tell me what you think.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-committers/attachments/20090126/39f6f156/attachment.htm 

More information about the Bf-committers mailing list