[Bf-committers] blendercasts reloaded...

Gaia gaia.clary at machinimatrix.org
Sat Nov 23 16:44:05 CET 2013

On 23.11.2013 15:30, Brecht Van Lommel wrote:
> For me the reasons not to do this are:
> * It shifts work from tutorial makers to developers, and it's the
> developers that are already the bottleneck at the moment, we have many
> people making tutorials. So developer time seems a more rare resource
> at the moment.
I am not sure why this would shift work from tutorial makers to developers.
Or do you mean "creating this tool would need developer resources" ?
Otherwise why would tutorial makers not use such a tool ? Its not so 
to use compared to creating screen casts ...
> * I have never seen such a system done well in other applications, the
> few times I've come across it, it's always been pretty frustrating.
What made these tools frustrating ? Is this a bad concept or did you 
only step
into tools which had it badly implemented ?
> I'm not sure why, maybe it's just a coincidence and there are
> applications (of Blender's complexity) out there that do this very
> well.
This actually keeps me on track :) Actually this is a good argument for
continue thinking about how it could be done better :)
> Brecht.
> On Fri, Nov 22, 2013 at 4:53 PM, Gaia <gaia.clary at machinimatrix.org> wrote:
> blendercasting:
> - Similar as with screencast i start a session recorder
> - Mouse movements are tracked and recorded.
> - The recorder tracks what functions i have clicked at what time
>     and where on the screen.
> - optionally it also records audio in parallel.
> - maybe i can add the audio later when i playback the cast..
> All is actually pretty similar to a screencast, except that blender
> records what goes on instead of creating 25 screenshots per second.
> Now what can a user do with that after the cast is loaded:
> - pause the cast at any time
> - scrub along the cast timeline forward backward
> - make inspections right in blender, make changes, ...
> - save the current blendercast status as regular blendfile
>     for later reuse.
> - However, when user scrubs the blendercast timeline
>     or resumes the session,then all user changes get reverted
>     and the blender cast continues exactly at the current location
>     in the timeline.
> Actually the user can make snapshots of a tutorial at any time
> by:
> - pausing the tutorial
> - save as .blend
> - resume the tutorial
> The blendercaster (tutorial maker) can do a bit more:
> - scrub to any point in the timeline and "delete the future"
>     this is for redoing something that went wrong the first time.
> - similar: store the session as a blendercast. either
>     the entire cast, or optionally "from start up to now"
> - load an existing blendercastand
>     add more to the end of the cast (continue a cast)
> "blendercast" would be a nice present for Christmas 2014 :)

More information about the Bf-committers mailing list