Proxies are for input strips, the scopes are drawn based on the render result (at preview size, if preview is enabled).<br>But each space area displaying a scope will analyse all pixel of this render result to draw the scope. Drawing a scope by analysing only a part of the pixels will speed things up. <br>
<br>Note that from what I read the subsampled image is 16 lines with the same x resolution (for example if your project is 1920x1080 pixels, then the subsampled image used for drawing the scopes is 1920x16 pixels) but I suppose other kind of sumbsamplig (or quick scale) can do the work too.<br>
<br>Xavier<br><br><div class="gmail_quote">2009/1/26 Roger Wickes <span dir="ltr"><<a href="mailto:rogerwickes@yahoo.com">rogerwickes@yahoo.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="font-family: tahoma,new york,times,serif; font-size: 10pt;"><div></div>
<div>proxies come to mind, which are say 25%, but perhaps another proxy could be computed. 1/16 is like 4%<br> </div>----------------<br>Sent by Roger Wickes for intended recipient. If you are not the intended recipient, please delete this message and contact Mr. Wickes immediately.
<div><br></div>
<div style="font-size: 10pt; font-family: tahoma,new york,times,serif;"><br>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;"><font face="Tahoma" size="2">
<hr size="1">
<b><span style="font-weight: bold;">From:</span></b> Xavier Thomas <<a href="mailto:xavier.thomas.1980@gmail.com" target="_blank">xavier.thomas.1980@gmail.com</a>><br><b><span style="font-weight: bold;">To:</span></b> bf-blender developers <<a href="mailto:bf-committers@blender.org" target="_blank">bf-committers@blender.org</a>><br>
<b><span style="font-weight: bold;">Sent:</span></b> Monday, January 26, 2009 5:36:17 AM<br><b><span style="font-weight: bold;">Subject:</span></b> [Bf-committers] Speeding up sequencer scopes drawing<br></font><div><div>
</div><div class="Wj3C7c"><br>Hello,<br><br>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)<br>
<br>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.<br>
<br>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. <br><br>I will make fiew tests to investigate this, but please (Peter) tell me what you think.<br>
<br>Xavier<br><br><br><br><br></div></div></div></div></div><br>
</div><br>_______________________________________________<br>
Bf-committers mailing list<br>
<a href="mailto:Bf-committers@blender.org">Bf-committers@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-committers" target="_blank">http://lists.blender.org/mailman/listinfo/bf-committers</a><br>
<br></blockquote></div><br>