From: "Thompson, David" <dthompson2@worcester.edu>
To: Jack Hill <jackhill@jackhill.us>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: [EXT] Use Chickadee to render animation to file?
Date: Fri, 27 May 2022 16:10:07 -0400 [thread overview]
Message-ID: <CAJ=RwfbQoG6QvU+9k=wAzG9xND3rHuhLqEqW948dz1VL4G+K6w@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2205271222170.11587@marsh.hcoop.net>
Hi Jack,
This is an interesting use case! It's certainly possible, but would require
some work. It would probably look something like this: Render the scene to
a framebuffer texture, copy the pixel data from the GPU, and pipe it to a
video encoder. Chickadee's texture API doesn't yet provide any procedures
that allow you to access the raw pixel data, so that would need to be added
first. It would be a little clunky because you'd have to wait for the
animation to finish in real time since it's not a real animation tool but
it would work. Feel free to give it a shot and let us know how it goes!
- Dave
On Fri, May 27, 2022 at 12:39 PM Jack Hill <jackhill@jackhill.us> wrote:
> Hi Guilers!
>
> I've been experimenting with David Thompson's Chickadee⁰. I'm really
> enjoying using agendas and scripts to create animations. My problem is (at
> least right now) I don't want to create an interactive game-like thing.
> Instead, I'm creating a deterministic animation. I'd like to start out
> with some Guile code and end up with a video file.
>
> What I hope to do is to program the animation using all the nice features
> of Chickadee, but instead of displaying it on a screen, output the frames
> that would be drawn to files. Does this seem possible? How would I go
> about it?
>
> 0: https://dthompson.us/projects/chickadee.html
>
> Best,
> Jack
>
next prev parent reply other threads:[~2022-05-27 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 16:38 Use Chickadee to render animation to file? Jack Hill
2022-05-27 20:10 ` Thompson, David [this message]
2022-05-27 21:02 ` [EXT] " Jack Hill
2022-06-01 5:53 ` Dr. Arne Babenhauserheide
2022-06-01 12:48 ` [EXT] " Thompson, David
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ=RwfbQoG6QvU+9k=wAzG9xND3rHuhLqEqW948dz1VL4G+K6w@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=guile-user@gnu.org \
--cc=jackhill@jackhill.us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).