[Bug 730783] bytereader: Improve the performance to find start code for H.264 and H.265
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Tue May 27 06:01:38 PDT 2014
https://bugzilla.gnome.org/show_bug.cgi?id=730783
GStreamer | gstreamer (core) | git
--- Comment #5 from Nicolas Dufresne <nicolas.dufresne at collabora.co.uk> 2014-05-27 13:01:28 UTC ---
(In reply to comment #0)
> This patch assumes that '0x0000' is unlikely to appear and the zeros are part
> of the start code, that is, '0x010000'.
Do you mean this can have false positive, or just that this would be the worst
case ?
> Our proposed idea is based on the assumption.
> If we quickly know whether or not there exists '0x0000' in the scanning area to
> find the start code, we can skip the scanning process for the start code.
> We thus implemented the preprocessing to know whether or not there exists
> '0x0000'.
> Because the probability of zeros to appear is low, its performance dramatically
> improved.
Can you provide profiling, best case, mid case, worst case ?
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list