We can remove the buffer-list option and just always enable buffer-lists, IMO. The fallback option for buffer-lists does not cause any memcpy anymore and the different memory blocks on buffers is something that all elements should handle gracefully.

Created attachment 218912 [details] [review]
Use buffer lists per default

commit d38ac43a275c718a9081be5b883193ababb9f217
Author: Patricia Muscalu <patricia@axis.com>
Date:   Mon Jul 16 11:07:44 2012 +0200

    rtph264pay: use buffer lists
    
    Fixes https://bugzilla.gnome.org/show_bug.cgi?id=679994

Thanks!

There are still some memcpy in the base class when the memory is merged to change the RTP header. I will see if that can be fixed.

commit 11a494d5c966148c61929d5d887df3d0815f3021
Author: Wim Taymans <wim.taymans@collabora.co.uk>
Date:   Tue Jul 17 16:35:06 2012 +0200

    rtp: Add support for multiple memory blocks in RTP
    
    Add support RTP buffers with multiple memory blocks. We allow one block for the
    header, one for the extension data, N for data and one memory block for the
    padding.
    Remove the validate function, we validate now when we map because we need to
    parse things in order to map multiple memory blocks.