On Thu, Jun 19, 2014 at 1:06 PM, Todd McIntosh <[email protected]> wrote:
>
> Hi Campbell,
>
> I'm not sure that would work with separate instances. The idea with a 
> cinematic timelapse is that you have one window where you do your modeling 
> work as per normal. Then in a second window, you have a camera viewport of a 
> camera that is animated in rotation around your model.
>
> Normally you would use an external screencasting app to record the display of 
> the second window. I was thinking it would be great to do it all with Blender 
> since the basic features are there. We're just missing the window launch call 
> and window targeting for the screencast call.
>
> Would your separate instance open work for the above scenario?

Nope, not if you want them to display the same data.

But suggest using external screen-casting program (python can call it),

Blender's screen-casting is fairly weak, and probably should be removed.
Theres no sound, resizing the window causes problems and the mouse is
faked. Really you'll get better result if you use a 3rd party screen
recording application.

>
>
> Thanks,
>
>
> Todd McIntosh
> Resonance Media + Design
> Phone: (905) 471-5048
> Email: [email protected]
>
>
>
> Campbell Barton
> 18 June, 2014 11:00 PM
>
> Is it necessary to be in the same Blender instance?
>
> subprocess.Popen([bpy.app.binary_path, "--window-geometry", "100",
> "100", "800", "600"])
>
> If you wanted you could pass in the current file and some script to
> start a screencast, eg:
>
> subprocess.Popen([
> # current file
> bpy.app.binary_path,
> "--window-geometry", "100", "100", "800", "600",
> bpy.data.filepath,
> # execute a script
> "--python", "start_screencast.py",
> ])
> Todd McIntosh
> 16 June, 2014 12:58 PM
> Hi Campbell, thanks for the feedback.
>
> I'm thinking about addons that can take a task or process that someone might 
> setup in Blender and automate it.
>
> For example, the procedure of setting up a Cinematic Time-lapse could be 
> easily automated if we were able to launch a new window, size it, and then 
> call the screencast command and target only that new window. However we can't 
> currently launch and size a window, or target one window with the screencast 
> call.
>
> If I wanted to submit a patch to trunk that added these features, would there 
> be a philosophical reason to oppose it?
>
>
> Campbell Barton
> 16 June, 2014 10:38 AM
> So far we didnt expose window management functions to Python, and
> probably wont expose them - though if there is a very good reason we
> can I suppose.
>
> In Blender you generally don't need to create new windows, normally a
> popup dialog is fine.
>
>
>
> Todd McIntosh
> 15 June, 2014 9:32 PM
> Maybe Campbell or another dev could answer this:
>
> What's the rationale for not being able to launch and size custom windows 
> with Python? Is this intentionally restricted or is just low priority in the 
> c++ codebase?
>
> Would there be opposition to a patch that would allow python access to launch 
> a new window?
> _______________________________________________
> Bf-python mailing list
> [email protected]
> http://lists.blender.org/mailman/listinfo/bf-python




-- 
- Campbell
_______________________________________________
Bf-python mailing list
[email protected]
http://lists.blender.org/mailman/listinfo/bf-python

Reply via email to