Closed GoogleCodeExporter closed 9 years ago
A longer analyzeduration ensures that everything is properly detected in some
"broken" or badly-formed files. So generally lowering it may not be a good
option.
However, it might be possible to check if we're dealing with a stream and/or a
network protocol, and then lower the value for improved streaming behaviour,
because on files its really quite different.
I'll look into it.
Original comment by h.lepp...@gmail.com
on 25 Jun 2013 at 1:24
Thats a good idea!
Looking forward to your test versions :-)
Original comment by Tobias.D...@gmail.com
on 25 Jun 2013 at 1:48
I went with 1s probe duration for now, which is already much better than the 5s
before, but i'm thinking about making the two values (or at least the one for
the network streams) configurable, so the user can configure if he wants faster
playback or more reliable stream detection.
Original comment by h.lepp...@gmail.com
on 30 Jun 2013 at 12:58
Thank you for this change.
I also think making it configurable is an good solution.
Like in my test version 500ms works very good for MPEG2TS multicast streams.
Tobias
Original comment by Tobias.D...@gmail.com
on 1 Jul 2013 at 6:17
This issue was closed by revision 2ad572ed12a6.
Original comment by h.lepp...@gmail.com
on 3 Jul 2013 at 6:17
Original issue reported on code.google.com by
Tobias.D...@gmail.com
on 25 Jun 2013 at 1:16Attachments: