https://wiki.blender.jp/index.php?action=history&feed=atom&title=%E5%88%A9%E7%94%A8%E8%80%85%3AAlexK%2FGsoc2013%2Fvse 2026-08-01T03:24:10Z このウィキのこのページに関する変更履歴 MediaWiki 1.31.0 https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:AlexK/Gsoc2013/vse&diff=143033&oldid=prev 2018-06-28T20:57:02Z

<p>1版 をインポートしました</p> <table class="diff diff-contentalign-left" data-mw="interface"> <tr class="diff-title" lang="ja"> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">← 古い版</td> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">2018年6月28日 (木) 20:57時点における版</td> </tr><tr><td colspan="2" class="diff-notice" lang="ja"><div class="mw-diff-empty">(相違点なし)</div> </td></tr></table>

Yamyam https://wiki.blender.jp/index.php?title=%E5%88%A9%E7%94%A8%E8%80%85:AlexK/Gsoc2013/vse&diff=143032&oldid=prev 2013-07-14T06:26:35Z

<p></p> <p><b>新規ページ</b></p><div>==Scheduling==<br /> * We will use OpenCL kernels and cpu threads<br /> ** So, there is cpu and gpu platform memory space<br /> *** So, we can share images between gpu-s in the same platform<br /> *** We would have queue for each memory space.<br /> ** A bucket is the list of instruction which is assign to a single device<br /> *** A bucket is dependent on outputs of other buckets<br /> *** Later we can extend the bucket system to work on tiles instead of whole images<br /> *** By making tiles smaller, we can have fewer frames in processing == more interactive<br /> * Frame ID<br /> ** When we update a strip parameter, we drop the frame associated with it (if we have time)<br /> ** The composition starts all over again<br /> * Scene Strips<br /> ** For now we would make a copy to avoid time jumping problems (we would process them in main thread anyway)<br /> <br /> <br /> ==Sequencer==<br /> * Images of a strip are stored as cache 2<br /> ** They are associated with clip ad stored in array liked structures<br /> ** We can prefect frames in advanced (videos)<br /> * We make a copy of a scene to avoid update conflicts<br /> * coping is also done for OpenGL preview rendering<br /> * Later, we can make not full copies, and cut corners for faster performance<br /> <br /> ==Plugins==<br /> * Plugins will be in OpenCL <br /> ** With python api<br /> ** It can be used for sound<br /> * Using python for math can be too slow<br /> * for C we don't have compiler, plus we need to handle sigsegv<br /> <br /> ==Strips==<br /> * Size<br /> ** Each strip will have position, scaling, rotation <br /> *** Internally, they are all modifiers <br /> *** Moreover, users will be able to manipulate the position in a view<br /> *** Selecting a strip by selecting an object in the view should be possible, but it is not a priority<br /> * The cache is used for storing the images. The level 2 cache is associated and is stored in a strip. A image in cache will have have &quot;in use&quot; flag.<br /> * Strip will have offset time<br /> * the current implementation of movie clips is fine<br /> ** closer integration can be possible later<br /> <br /> ==Effects==<br /> * Effects<br /> ** One input effects<br /> *** These effects can be used as modifiers for a strips<br /> *** For current modifiers, they can be used as effects strips<br /> *** The effects won't be restricted to original clip (for this we will have modifiers)<br /> *** Also, effects will have a (default) option for a sequence below as an input <br /> ** Other effects<br /> *** Are mainly blends<br /> *** They all can be used as blend mode for a strip<br /> ** Internally, modifiers/effects/blends will be handled the same way by engine<br /> <br /> ==Views==<br /> * By design, the engine will support multiple views<br /> * The engine will calculate the target resolution for outputs <br /> * The outputs can be different types: original strip, left/right, waveform, histogram<br /> * The engine will have the list of all target outputs for optimization<br /> <br /> ==Quality==<br /> * The quality level can be selected<br /> ** filters can be turned off, or put to the draft quality<br /> * For draft, we will first pre-scale the images to the target output size .<br /> * Each kernel will be compiled as char, half (gpu only), float. The quality settings are applied to the whole sequencer.<br /> * The whole track can be muted (audio and video)<br /> <br /> ==Colorspaces==<br /> * Blender will convert images into rgb type color space with OCIO<br /> * All operations will be done in internal color space<br /> * The output image will be converted to display colorspace with OCIO<br /> <br /> ==DNA==<br /> * Pretty much will stay the same<br /> * Will be extended for new modifiers/effects<br /> * Position/size might be move to modifier stack</div>

wiki>AlexK