Release update
Richard Jones
it's not out yet.
Unfortunately the next release has been delayed because I got distracted doing
list-item expose (as in the next-page action exposes list items in turn). It's
working, but performance is suboptimal if one (or more) of the list items
contains a table. Also there's an implementation issue which means video and
plugins are reset when each item is exposed. I'll release anyway, just noting
those caveats.
I'd like to get the timing stuff in that's been requested in the last few days
too. It won't take long at all - I should have the next release out by the
middle of next week. Hell, I might even find some time today in-between bouts
of gardening :)
Richard
Ned Batchelder
I noticed the timed-display request, and it could fit in well with my
request for a PNG-export mode. I didn't know how to automatically
advance the slides, so the patch I supplied required the user to
manually advance to each slide to get the image capture. With a timed
display mode, I could set the slides to advance after a zero-second
delay, capturing the images with no user interaction, which would be
great. I'm trying to create a fully-automated scriptable solution for
getting PNGs from a slide show.
--Ned.
http://nedbatchelder.com
Ned Batchelder, http://nedbatchelder.com
Richard Jones
1. Recording of screenshot images + timing information. I hope to
figure how to turn this into a video file.
2. Playback of a presentation using that timing information.
3. Automatic playing of a presentation with a fixed timing between pages.
2 & 3 may be run in a loop.
Richard
Richard Jones
> I've implemented three things that're checked in now:
>
> 1. Recording of screenshot images + timing information. I hope to
> figure how to turn this into a video file.
> 2. Playback of a presentation using that timing information.
> 3. Automatic playing of a presentation with a fixed timing between pages.
>
> 2 & 3 may be run in a loop.
Bugger. gmail posted this before I'd finished editing.
I believe the above satisfy your requirements using a combination of
--record and --playspeed, like so:
python run_bruce.py examples/test_image.rst --record=/tmp/images --playspeed=.5
You'll want to make sure the presentation has ".. style::
:transition.name: none" at the top
Using a speed faster than .5 is discouraged until some fine-tuning of
timing can be done.
Richard
Ned Batchelder
This works great. I have only two small problems.
1) For some reason on my slides, the second slide zips past faster than it is supposed to. With playspeed=.5, I don't get screenshot-1.png. If I change playspeed to 1, the second slide still goes past faster than the others, but now it's slower, and the .png is saved.
2) I still have to manually quit the presentation. Any ideas about exiting automatically, or is that too far off the reservation? I can use the plugin approach for this if need be.
Thanks for being so responsive!
Richard Jones
> 1) For some reason on my slides, the second slide zips past faster than it
> is supposed to. With playspeed=.5, I don't get screenshot-1.png. If I
> change playspeed to 1, the second slide still goes past faster than the
> others, but now it's slower, and the .png is saved.
That's odd. What's the slide content?
> 2) I still have to manually quit the presentation. Any ideas about exiting
> automatically, or is that too far off the reservation? I can use the plugin
> approach for this if need be.
Done. See --once.
I've also fixed --loop so it works twice ;)
Richard
Richard Jones
>> 2) I still have to manually quit the presentation. Any ideas about exiting
>> automatically, or is that too far off the reservation? I can use the plugin
>> approach for this if need be.
>
> Done. See --once.
Renamed to --autoquit. "once" was a dumb name.
Richard