Martin Lambers mar...@marlam.de added the comment:
I just tested again with SVN-r26207, and it now works a lot better.
Seeking generally works, but sometimes ffplay seeks to a non-key-frame,
resulting in visible artifacts.
FFplay version SVN-r26207, Copyright (c) 2003-2011 the FFmpeg
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Why?
(Moved 1024 bytes to samples/ffmpeg-bugs/roundup/issue2475)
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2475
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Sorry, but even if I installed Blender, I wouldn't know how to reproduce this.
--
status: new - closed
substatus: new - invalid
FFmpeg issue tracker
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
The problem explained in issue 1730 (that seeking before the beginning prints an
error, and later, the file restarts surprisingly) is still reproducible with
r26207.
--
status: open - closed
substatus: open -
Ronald S. Bultje rsbul...@gmail.com added the comment:
My idea for MMS is indeed to try RTSP, then HTTP/MMS (and I do prefer a
fallback to mmst, just because some old servers still use that, even
though it's not used a lot). Lack of time is the main reason that we
haven't done it yet.
The
Dennis dfrati...@hotmail.com added the comment:
Thanks,
That sounds great, right on the money.
Any thought to the ASX part?
I am sorry I am unable to contribute to the actual
programming though. I am not familiar with C or any
of the functions of FFmpeg (let alone compiling). I
am more of a
New submission from aviad rozenhek avia...@gmail.com:
when reading MPEG-TS over UDP, the stream often does not begin with a
keyframe. it can therefore take some time until video information such
as resolution and pixel format is discovered.
I noticed that some times video resolution detection
New submission from aviad rozenhek avia...@gmail.com:
when reading MPEG-TS over UDP, libav*/ffmpeg/ffplay reports a lot of
warnings during the probing stage. the warnings stem from the fact that
UDP has no seek, and from the fact that often the first frames of the
stream are not keyframes.
aviad rozenhek avia...@gmail.com added the comment:
from http://en.wikipedia.org/wiki/File_URI_scheme:
Here are two Linux examples pointing to the same /etc/fstab file:
file://localhost/etc/fstab
file:///etc/fstab
Here is the correct URI as understood by the Windows Shell API:
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
The invalid reads are still reproducible with r26207 (and they seem to cause
crashes on Windows).
FFmpeg issue tracker iss...@roundup.ffmpeg.org
scheutzo mike.scheut...@alcatel-lucent.com added the comment:
If the author of this report wants the probing code to try harder, he should use
appropriate values for -probesize, -analyzeduration and -f command line options
to ffplay.
FFmpeg issue
chaos yaint...@yahoo.com.ar added the comment:
No problem. Just download blender using the link above and the file that I
provide here. Launch blender and open the provided file, now press Alt+A, you
can stop the movie by hitting Esc. If you can't see any movie, make sure that
you are in the
New submission from Daniel Kang daniel.d.k...@gmail.com:
ffmpeg crashes on mov files with invalid time creation. gmtime will return NULL
for times it cannot convert
(http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1124.pdf p. 335). strftime
crash when NULL is passed to it. I have attached a
Daniel Kang daniel.d.k...@gmail.com added the comment:
I have uploaded a sample to
/MPlayer/incoming/invalid_mov_creation_time_issue2490
FFmpeg issue tracker iss...@roundup.ffmpeg.org
https://roundup.ffmpeg.org/issue2490
14 matches
Mail list logo
