db&w documentation wiki

finest software | finest docs

Site Tools


framed2018:introduction

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
private:framed2017:introduction [2017/06/19 12:48] – created lightwolfframed2018:introduction [2017/12/27 10:40] (current) – ↷ Links adapted because of a move operation lightwolf
Line 1: Line 1:
 ====== Introduction ====== ====== Introduction ======
  
-frameD is a plugin for LightWave3D to create, load and manage image sequences defined by text files((Gratuitous footnote. We'll try to make the following ones more informative. ;) ))+frameD is a plugin for LightWave3D to create, load and manage image sequences defined by text files((Gratuitous footnote. We'll try to make the following ones more informative. ;) )).
  
-The main usage scenarios are image sequences that contain duplicate images (such as mouth shapes mapped on a character's face) as well as backplates used for reference(( We know – actually we expect – that many of you will come up with uses that we certainly never thought of. ))+The main usage scenarios are image sequences that contain duplicate images (such as mouth shapes mapped on a character's face) as well as backplates used for reference(( We know – actually we expect – that many of you will come up with uses that we certainly never thought of. )).
  
 These text files are treated by LightWave3D as animation files. However, they point to individual images which are loaded as frames of the “virtual” animation. These text files are treated by LightWave3D as animation files. However, they point to individual images which are loaded as frames of the “virtual” animation.
  
-Since the individual images are loaded through the frameD plugin, it can perform additional processing or even not load from disk at all. This is leveraged by providing the option to load proxy images (which are created automatically) and by using available memory to cache images.+Since the individual images are loaded through the frameD plugin, it can perform additional processing or even not load from disk at all. This is leveraged by providing the option to **load proxy images** (which are created automatically) and by using available memory to **cache images**.
  
 frameD supports both standard “IFL” based sequences as well as its own proprietary “XFD” format. The latter is XML based and allows for more attributes to be saved than simple IFL files allow for. frameD supports both standard “IFL” based sequences as well as its own proprietary “XFD” format. The latter is XML based and allows for more attributes to be saved than simple IFL files allow for.
  
 +===== Basic Workflow =====
 +
 +Single frames or image sequences are assembled in the [[framed2018:framed_editor|frameD Editor]] to a sequence that can be loaded into LightWave 3D by the animation loader((Please note, the editor does not use the cache. However, when loading an image for the first time, a thumbnail will be created and saved to disk. On subsequent loads, only the thumbnail will be loaded.)).
 +
 +One loaded by the animation loader in LightWave 3D, the images of the sequence will be cached and the timing can be manipulated using various looping options as well as a re-timing curve in the [[framed2018:master_plugin]]. Images shared by multiple sequences will only be loaded once.
 ===== Features ===== ===== Features =====
  
Line 26: Line 31:
 ===== Compatibility ===== ===== Compatibility =====
  
-frameD is compatible with LightWave3D 2017+frameD is compatible with LightWave3D 2018
 It currently runs with the Windows and MacOS versions of LightWave.  It currently runs with the Windows and MacOS versions of LightWave. 
  
 Please visit http://framed.db-w.com for more up to date information. Please visit http://framed.db-w.com for more up to date information.
  
-<-^|^|^->+<-acknowledgements| ^|^setting_up|->
framed2018/introduction.1497869334.txt.gz · Last modified: 2017/06/19 12:48 by lightwolf