[Bf-python] Sequencer py api

[Campbell Barton]

Ken Hughes wrote:
> Stephen Swaney wrote:
>> On Wed, Dec 27, 2006 at 02:02:40PM +1100, Campbell Barton wrote:
>>> almost finished a Python Sequence module for accessing a scene 
>>> sequencer data- nested, metastrips as an iterator, strip data 
>>> (images, sound, scene and referenced ipo)
>>>
>>> Its mostly read only at the moment, but you can move clips around and 
>>> change their flags.
>>>
>>> Just wondering if a Python API is acceptable at the moment, any 
>>> reasons not to include it?
>>> Maybe we could just add in the documentation that the API may change 
>>> in the next release.
>>
>> Since we are in the phase of doing release candidate builds - BCon-3,
>> I would hold off on committing anything new until after the next release.
> 
> I have to agree.  I've got a refactor of the Curve module that I'm going 
> to hold off on committing, although I've found a few bugs that I'll fix 
> in any case.  On the other hand, I'd be really interested in using a Bpy 
> Sequence API, so do post it to the tracker in the interim.
> 
> Ken
> _______________________________________________
> Bf-python mailing list
> Bf-python at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-python
> 

Good point,
Heres what Iv done so far, needs cleanup, but have you can probably get 
an idea from looking at it how things work.

Theres 2 pypypes,
PySceneSeq: is a sequence object that links to the Scene. it can iterate 
on the scenes sequences and access the current metastrip (if your 
editing inside one) as well as the active strip.


PySequence: wraps the sequence directly, you can loop through nested 
metastrips..

Currently no support for effects or HDAudio
The files are here. for now you can use Blender.Sequence.Get() to get 
the current sequence for the active, This will be removed when Scene.c 
is modified.

http://members.optusnet.com.au/cjbarton/seq/

Only need to modify Blender.c