Red Hat Bugzilla – Bug 826260
Screencast generates webm file with unknown duration
Last modified: 2013-08-01 02:35:21 EDT
Description of problem:
If you generate a webm file using Gnome Shell's screencast function, the webm file seems to have an unknown duration. You can see this when you try to play the file with Totem. The duration value keeps increasing as the video plays.
This unknown duration causes problems with the Pitivi video editor. It is unable to insert the full length of the video into the file. Instead, it inserts only a very short portion of the video.
Version-Release number of selected component (if applicable):
Happens every time.
Steps to Reproduce:
1. Generate a webm Screencast file with the Ctrl-Alt-Shift-R key combination.
2. Play the file with totem
The duration of the screencast video is incorrectly displayed in Totem.
The duration of the screencast video is correctly displayed in Totem.
I can confirm this, and all other programs can not work correctly with produced video file:
ffmpeg2theora says: WARNING: Can't get duration of media, not indexing, writing Skeleton 3 track. (and than it works very slowly with this file)
pitivi: Can extract only about 0.6 seconds from the file, any attempt to edit or freezes pitivi.
firefox+html5 video tag: plays well (just like totem) but unable to replay video.
I tried it with Kdenlive and it still happens. Do you have a quick fix :) ? Maby converting the file with another program fixes the index?
I was able to use Transmageddon to convert a webm file created by Gnome Shell as a screencast to a webm file that works in Pitivi.
I alos tried Transmageddon but it didn't work so I put VLC to play it on full screen while Kazam screencaster was recording it. I was in a big hurry and this ugly workaround fixed it :)
I'm having the same problem.
Any chance it could be related to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=869007 ?
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.