mirror of
https://github.com/asciinema/asciinema.git
synced 2026-04-25 07:55:51 +03:00
[GH-ISSUE #201] Play ascineema recording for given time-frame. #145
Labels
No labels
bug
compatibility
feature request
fit for beginners
help wanted
hosting
idea
improvement
packaging
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asciinema#145
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dipak-pawar on GitHub (Mar 30, 2017).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/201
While editing an ASCiinema file, it would be nice to be able to stop a playback at given time.
Example:
asciinema play --start-at 12s --ends-at 34s my.rec
asciinema play --start-at 101l --ends-at 412l my.rec
So the playback will start at 12s and end with 34s.
@dipak-pawar commented on GitHub (Mar 30, 2017):
We have start-at implementaion in this #180.
I will provide implementation for ends-at if it's not done already
@ku1ik commented on GitHub (Mar 30, 2017):
I don't think this would be useful for many people, so probably not worth maintaining. Thanks for the idea anyway!
@dipak-pawar commented on GitHub (Mar 30, 2017):
@sickill Just curious, do we have any way to convert recording into different frames using timeline with the help of json file?
@ku1ik commented on GitHub (Mar 31, 2017):
I'm not sure I understand that... You mean like creating shorter recording based on the original one?
@dipak-pawar commented on GitHub (Mar 31, 2017):
yes I want to create short version of recording with time frame based on original one.
I have 10 minutes original recording. So I want to divide it in smaller one so I can embed it at different locations where it's needed in my html page
@dipak-pawar commented on GitHub (Apr 3, 2017):
@sickill Can you help in this?
@ku1ik commented on GitHub (Apr 5, 2017):
It's not as simple as it seems :) Terminals are state machines, and the recording reflects a stream of text and commands to modify that state. Because of that you can't just skip first N bytes because the following commands may be depending on the state built up so far (by the first N bytes).
To achieve what you want we would need to have a tool which would interpret the stream up to a point where you want the recording to start, and dump that state as a stream of bytes, basically establishing the "initial frame". We don't have such a tool right now unfortunatelly.
@dipak-pawar commented on GitHub (Apr 10, 2017):
Thanks @sickill