On 18 Apr 2014, at 23:30, Vittorio Giovara <[email protected]> wrote:
> On Fri, Apr 18, 2014 at 4:07 PM, Tim Walker <[email protected]> wrote: >> On 16 Apr 2014, at 02:50, Ben Avison <[email protected]> wrote: >> >>> This permits re-use with parsers for codecs which use similar start codes. >>> --- >>> libavcodec/Makefile | 2 +- >>> libavcodec/arm/Makefile | 2 +- >>> libavcodec/arm/h264dsp_armv6.S | 253 >>> ------------------------------------- >>> libavcodec/arm/h264dsp_init_arm.c | 4 +- >>> libavcodec/arm/startcode_armv6.S | 253 >>> +++++++++++++++++++++++++++++++++++++ >>> libavcodec/h264dsp.c | 31 +----- >>> libavcodec/startcode.c | 57 +++++++++ >>> libavcodec/startcode.h | 35 +++++ >>> 8 files changed, 351 insertions(+), 286 deletions(-) >>> delete mode 100644 libavcodec/arm/h264dsp_armv6.S >>> create mode 100644 libavcodec/arm/startcode_armv6.S >>> create mode 100644 libavcodec/startcode.c >>> create mode 100644 libavcodec/startcode.h >> >> Note: some code in libavformat looks for startcodes too (e.g. for Annex B -> >> MP4 conversion). Would it make sens to factor this out to libavutil? > > This might be a good idea. > Which one would be the best place, lavcodec or lavutil? > -- > Vittorio Did anything come of this? I'd like to know the answer to this question too. Tim _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
