[FFmpeg-trac] #2215(undetermined:closed): Frodo 12 does not play live matroska stream
FFmpeg
trac at avcodec.org
Thu Jan 31 12:38:50 CET 2013
#2215: Frodo 12 does not play live matroska stream
-------------------------------------+-------------------------------------
Reporter: wargand | Owner:
Type: defect | Status: closed
Priority: normal | Component:
Version: unspecified | undetermined
Keywords: | Resolution: invalid
Blocking: | Blocked By:
Analyzed by developer: 0 | Reproduced by developer: 0
-------------------------------------+-------------------------------------
Comment (by cehoyos):
Replying to [comment:4 wargand]:
> Problem is, I am currently on a somewhat tight schedule
Allow me to say that I consider this sentence (contrary to your earlier
message) quite offensive.
[...]
> I am not accusing you, the only thing, which really surprised me and
annoyed me a little bit, was how fast the rejection came.
So it would have been friendlier if I waited longer? That does not sound
very convincing to me...
> Not a single question. Just: Not our problem.
What I should have written is "not enough information" but the very little
information you provided indicates a (possible) bug in xbmc.
Please understand that I am *not* claiming there is no bug in FFmpeg, I am
just claiming there is no (no in the sense of: not even the tiniest)
possibility that this can be fixed - even if by some miracle the bug would
be fixed in FFmpeg (I have no idea how given that there is no way to test
and no hint what triggers the problem) how would this fix get into xbmc?
> Maybe it is not your problem. I am sorry, if I sounded a bit harsh.
Don't worry - see above!
> Maybe the XBMC guys patched the bug in themselves.
Allow me to repeat that I do not claim this.
(But did you check if xbmc is using the lavf matroska demuxer at all? I
don't know.)
> And definitely I did not provide an even remotely usable bug report.
Thank you for clarifying!
> Also sorry here, but FFMpeg or XBMC are not the most simple and smallest
projects. Building up enough knowledge to actually help is tough. See my
report as some kind of head start.
Imo, this start should happen on the mailing list.
> If it is something in your libs, enough commercial products use directly
or indirectly FFMpeg, you probably will get proper reports soon enough.
I do not easily remember a (both useful or useless) bug report from a
commercial product...
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2215#comment:5>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list