Author: rigo_ls
Description:
When I transcode .mts files to WEBM, I get a video that shows the first frame for 2 seconds(static image) and at the 3rd second it starts playing normally.
This happens on every .mts file I have used and any WEBM settings.
Version: unspecified
Severity: normal
jgerber wrote:
can you provide a sample .mts file, so i can have a look what is causing it.
rigo_ls wrote:
(In reply to comment #1)
can you provide a sample .mts file, so i can have a look what is causing it.
can you tell me how to provide you the .mts file? a video of 1 minute is approximately 150MB(cannot be attached on e-mail)
jgerber wrote:
upload it to megaupload or another one click hoster and send me the link.
rigo_ls wrote:
interesting!, I sent the file to j, and got the following message in february:
Hi,
got the file but had not time to look at it,
will get back to you once i had a closer look.
the file has an initial offset, possibly audio/video do not start at the
same time. in that case f2t would repeat the first frame until audio
starts...
j
do you need another file?
mdale wrote:
That was not part of the bug thread ;) ...
We can leave it open if you want, but I imagine the bug is really an upstream issue with ffmpeg. Is that correct Jan?
jgerber wrote:
yes its an issue in ffmpeg, will test with the file once i get around to update the version of ffmpeg used in Firefogg or report issue with ffmpeg, if you want to test now, checkout current ffmpeg from git and try to encode it to see if the issue is still present.
(In reply to comment #8)
Is the problem still there if you tried to encode with the latest version of ffmpeg?
Firefogg is no longer supported/developed under the Wikimedia umbrella, hence closing this ticket as WONTFIX for the scope of Wikimedia.
In the Wikimedia software architecture, Firefogg has been mostly superseded by http://www.mediawiki.org/wiki/Extension:TimedMediaHandler .
If the problem reported here is still reproducible in Firefogg, please feel free to file a report under https://bugs.launchpad.net/firefogg where current Firefogg development is located.
I am sorry for the inconvenience and that this report was not investigated in a timely manner back when it was filed. Thanks for your understanding.