I've been prototyping and testing strip-wise rendering. In case anyone
wants to know what the state of the work is right now:
http://monochrome.sutic.nu/2010/11/15/sequence-rendering.html
The short version: Just prototyping right now. Image stabilization etc.
works great. Working on getting e
Hi Leo,
> I've read through the plugin proposal you wrote way back, and I find no
> real issue with it. Why wasn't it implemented? Was it just lack of
> resources, or am I missing something?
lack of resources and some unresolved issues with IPOs. The problem was,
that I thought it was a good ide
Peter,
I've read through the plugin proposal you wrote way back, and I find no
real issue with it. Why wasn't it implemented? Was it just lack of
resources, or am I missing something?
(Also, I am prototyping a strip-wise renderer, but that's another story.)
/LS
On 2010-10-05 23:18, Dan Eicher w
On Tue, Oct 5, 2010 at 1:45 AM, Peter Schlaile wrote:
> Hi Dan,
>
> > It has {application,plugin,libplugin} version control and symbol
> > dependencies (as I understand them)
>
> after reading again through the documentation, I don't think so. There is
> no thought put into negotation between the
Hi Dan,
> It has {application,plugin,libplugin} version control and symbol
> dependencies (as I understand them)
after reading again through the documentation, I don't think so. There is
no thought put into negotation between the application and the plugin,
what API version should be used for a
On Fri, Oct 1, 2010 at 3:03 PM, Leo Sutic wrote:
>
> Libplugin assumes that the application has extension points where
> plugins can be added. Each extension point can have, if I understand the
> docs and illustrations right, *one* plugin; since the function pointer
> that is the extension point
On 2010-10-01 23:41, Dan Eicher wrote:
> On Fri, Oct 1, 2010 at 3:19 AM, Peter Schlaile wrote:
>
>> Hi,
>>
>>> I have libplugin (http://libplugin.sourceforge.net/intro.html) working
>> in
>>> blender. Well, extensions and join-points at least, still haven't ported
>>> over the (semi-)current plug
On Fri, Oct 1, 2010 at 3:19 AM, Peter Schlaile wrote:
> Hi,
>
> > I have libplugin (http://libplugin.sourceforge.net/intro.html) working
> in
> > blender. Well, extensions and join-points at least, still haven't ported
> > over the (semi-)current plugin systems to use it. When I say 'working' I
>
Hi,
> I have libplugin (http://libplugin.sourceforge.net/intro.html) working in
> blender. Well, extensions and join-points at least, still haven't ported
> over the (semi-)current plugin systems to use it. When I say 'working' I
> mean on linux building with cmake BTW, probably be a chore to get
On Wed, Sep 29, 2010 at 3:51 PM, Leo Sutic wrote:
> Hi Peter,
>
> thanks for the link to the plugin proposal. Any other pointers to work
> already done would be greatly appreciated.
>
> I'll drop back to working on bugs in the 2.5 beta for now.
>
> /LS
I have libplugin (http://libplugin.sourcef
Hi Peter,
thanks for the link to the plugin proposal. Any other pointers to work
already done would be greatly appreciated.
I'll drop back to working on bugs in the 2.5 beta for now.
/LS
___
Bf-committers mailing list
Bf-committers@blender.org
http://l
Hi Leo,
> 1. Render A10-A15
> 2. Render B10-B15
> 3. Render Final 10-Final 15
> 4. Render A16-A20
> 5. Render B16-B20
> 6. Render Final 16-Final 20
>
> Of course, we could use a chunk size of 1 and then we'd be back to the
> way things work today, but having larger chunk sizes allows us to
> amort
Hi Peter,
On 2010-09-28 20:39, Peter Schlaile wrote:
> Hi Leo,
>
>> Looking at the code for the VSE it appears solid, but not very modular,
>> nor suitable for effects that need access to more than the current
>> frame. Since the tools I have fall into that category ? the anti-shake,
>> for examp
On Tue, Sep 28, 2010 at 11:39 AM, Peter Schlaile wrote:
> Anti-Shake or motion tracking sound like tools, that should run within a
> seperate background rendering process. We could add something to the
> interface, that enables an effect track to have a custom render/bake run.
> Like: please rende
Hi Leo,
> Looking at the code for the VSE it appears solid, but not very modular,
> nor suitable for effects that need access to more than the current
> frame. Since the tools I have fall into that category ? the anti-shake,
> for example, needs to compute the optical flow for each pair of frames
Dear All,
right now we are working toward a 2.5 release, and I am very aware of
the fact that we have to get things out the door. "Real artists ship"
and all that. I just want to share some thoughts on the future of the
VSE, post-2.5. I apologize if these thoughts have been brought up
earlier and
16 matches
Mail list logo
