[GH-ISSUE #98] [CLI] See duration of recording #688

New issue

Closed

opened 2026-03-15 08:52:12 +03:00 by kerem · 3 comments

kerem commented

2026-03-15 08:52:12 +03:00

Owner

Originally created by @vvv on GitHub (May 8, 2015).
Original GitHub issue: https://github.com/asciinema/asciinema/issues/98

I'd like to know the duration a recording written to JSON file.

ttytime utility (part of ttyrec) provides this information:

TTYTIME(1)                                                    TTYTIME(1)

NAME
       ttytime  -  print  the  time  of  the  recorded  session  data by
       ttyrec(1)

SYNOPSIS
       ttytime file...

DESCRIPTION
       Ttytime tells you the time of  recorded  data  in  seconds.   For
       example:

              % ttytime *.tty
                  173 foo.tty
                 1832 bar.tty

SEE ALSO
       script(1), ttyrec(1), ttyplay(1)

                                                              TTYTIME(1)

Originally created by @vvv on GitHub (May 8, 2015). Original GitHub issue: https://github.com/asciinema/asciinema/issues/98 I'd like to know the duration a recording written to JSON file. `ttytime` utility (part of [ttyrec](http://0xcc.net/ttyrec/index.html.en)) provides this information: ``` TTYTIME(1) TTYTIME(1) NAME ttytime - print the time of the recorded session data by ttyrec(1) SYNOPSIS ttytime file... DESCRIPTION Ttytime tells you the time of recorded data in seconds. For example: % ttytime *.tty 173 foo.tty 1832 bar.tty SEE ALSO script(1), ttyrec(1), ttyplay(1) TTYTIME(1) ```

kerem closed this issue

2026-03-15 08:52:17 +03:00

kerem commented

2026-03-15 08:52:23 +03:00

Author

Owner

@vvv commented on GitHub (May 8, 2015):

Poor man's calculator:

#!/bin/sh
set -e

asciinema_time() {
    awk '/^ +[0-9]+\.[0-9]+,/ { t += $1 } END { print int(t) }'
}

if date --version >&/dev/null; then
    REL='-d@' # GNU
else
    REL='-r'  # BSD
fi

for f in "$@"; do
    date ${REL}$(cat "$f" | asciinema_time) -u +%H:%M:%S | tr \\n \\t
    echo $f
done

@vvv commented on GitHub (May 8, 2015): Poor man's calculator: ``` sh #!/bin/sh set -e asciinema_time() { awk '/^ +[0-9]+\.[0-9]+,/ { t += $1 } END { print int(t) }' } if date --version >&/dev/null; then REL='-d@' # GNU else REL='-r' # BSD fi for f in "$@"; do date ${REL}$(cat "$f" | asciinema_time) -u +%H:%M:%S | tr \\n \\t echo $f done ```

kerem commented

2026-03-15 08:52:28 +03:00

Author

Owner

@ku1ik commented on GitHub (May 8, 2015):

asciinema is not planning to mirror all ttyrec/ttytime/tty* features. Anyway, why not opening recording file (since asciinema 1.0 it's a simple JSON file) and looking at duration attribute? It's total duration in seconds.

@ku1ik commented on GitHub (May 8, 2015): asciinema is not planning to mirror all `ttyrec/ttytime/tty*` features. Anyway, why not opening recording file (since asciinema 1.0 it's a simple JSON file) and looking at `duration` attribute? It's total duration in seconds.

kerem commented

2026-03-15 08:52:33 +03:00

Author

Owner

@vvv commented on GitHub (May 8, 2015):

Gosh, indeed.
Please excuse my inattention.

@vvv commented on GitHub (May 8, 2015): Gosh, indeed. Please excuse my inattention.

kerem referenced this issue

2026-03-15 11:09:36 +03:00

[GH-ISSUE #688] asciinema stream + ZSH with OMZ within tmux session shows additional characters #965