1. 09 Feb, 2017 2 commits
    • Martin Storsjö's avatar
      aarch64: vp9itxfm: Make the larger core transforms standalone functions · 11547601
      Martin Storsjö authored
      This work is sponsored by, and copyright, Google.
      
      This reduces the code size of libavcodec/aarch64/vp9itxfm_neon.o from
      19496 to 14740 bytes.
      
      This gives a small slowdown of a couple of tens of cycles, but makes
      it more feasible to add more optimized versions of these transforms.
      
      Before:
      vp9_inv_dct_dct_16x16_sub4_add_neon:    1036.7
      vp9_inv_dct_dct_16x16_sub16_add_neon:   1372.2
      vp9_inv_dct_dct_32x32_sub4_add_neon:    5180.0
      vp9_inv_dct_dct_32x32_sub32_add_neon:   8095.7
      
      After:
      vp9_inv_dct_dct_16x16_sub4_add_neon:    1051.0
      vp9_inv_dct_dct_16x16_sub16_add_neon:   1390.1
      vp9_inv_dct_dct_32x32_sub4_add_neon:    5199.9
      vp9_inv_dct_dct_32x32_sub32_add_neon:   8125.8
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      11547601
    • Martin Storsjö's avatar
      arm: vp9itxfm: Make the larger core transforms standalone functions · 0331c3f5
      Martin Storsjö authored
      This work is sponsored by, and copyright, Google.
      
      This reduces the code size of libavcodec/arm/vp9itxfm_neon.o from
      15324 to 12388 bytes.
      
      This gives a small slowdown of a couple tens of cycles, up to around
      150 cycles for the full case of the largest transform, but makes
      it more feasible to add more optimized versions of these transforms.
      
      Before:                              Cortex A7       A8       A9      A53
      vp9_inv_dct_dct_16x16_sub4_add_neon:    2063.4   1516.0   1719.5   1245.1
      vp9_inv_dct_dct_16x16_sub16_add_neon:   3279.3   2454.5   2525.2   1982.3
      vp9_inv_dct_dct_32x32_sub4_add_neon:   10750.0   7955.4   8525.6   6754.2
      vp9_inv_dct_dct_32x32_sub32_add_neon:  18574.0  17108.4  14216.7  12010.2
      
      After:
      vp9_inv_dct_dct_16x16_sub4_add_neon:    2060.8   1608.5   1735.7   1262.0
      vp9_inv_dct_dct_16x16_sub16_add_neon:   3211.2   2443.5   2546.1   1999.5
      vp9_inv_dct_dct_32x32_sub4_add_neon:   10682.0   8043.8   8581.3   6810.1
      vp9_inv_dct_dct_32x32_sub32_add_neon:  18522.4  17277.4  14286.7  12087.9
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      0331c3f5
  2. 08 Feb, 2017 2 commits
  3. 07 Feb, 2017 3 commits
  4. 06 Feb, 2017 3 commits
  5. 05 Feb, 2017 2 commits
  6. 04 Feb, 2017 1 commit
  7. 03 Feb, 2017 4 commits
    • Diego Biurrun's avatar
      7abdd026
    • Diego Biurrun's avatar
      build: Ignore generated .version files · 740b0bf0
      Diego Biurrun authored
      740b0bf0
    • Martin Storsjö's avatar
      rtmp: Correctly handle the Window Acknowledgement Size packets · 15a92e0c
      Martin Storsjö authored
      This swaps which field is set when the Window Acknowledgement Size
      and Set Peer BW packets are received, renames the fields in
      order to clarify their role further and adds verbose comments
      explaining their respective roles and how well the code currently
      does what it is supposed to.
      
      The Set Peer BW packet tells the receiver of the packet (which
      can be either client or server) that it should not send more data
      if it already has sent more data than the specified number of bytes,
      without receiving acknowledgement for them. Actually checking this
      limit is currently not implemented.
      
      In order to be able to check that properly, one can send the
      Window Acknowledgement Size packet, which tells the receiver of the
      packet that it needs to send Acknowledgement packets
      (RTMP_PT_BYTES_READ) at least after receiving a given number of bytes
      since the last Acknowledgement.
      
      Therefore, when we receive a Window Acknowledgement Size packet,
      this sets the maximum number of bytes we can receive without sending
      an Acknowledgement; therefore when handling this packet we should set
      the receive_report_size field (previously client_report_size).
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      15a92e0c
    • Martin Storsjö's avatar
      rtmp: Rename packet types to closer match the spec · a1a143ad
      Martin Storsjö authored
      Also rename comments and log messages accordingly,
      and add clarifying comments for some hardcoded values.
      
      The previous names were taken from older, reverse engineered
      references.
      
      These names match the official public rtmp specification, and
      matches the names used by wirecast in annotating captured
      streams. These names also avoid hardcoding the roles of server
      and client, since the handling of them is irrelevant of whether
      we act as server or client.
      
      The RTMP_PT_PING type maps to RTMP_PT_USER_CONTROL.
      
      The SERVER_BW and CLIENT_BW types are a bit more intertwined;
      RTMP_PT_SERVER_BW maps to RTMP_PT_WINDOW_ACK_SIZE and
      RTMP_PT_CLIENT_BW maps to RTMP_PT_SET_PEER_BW.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      a1a143ad
  8. 02 Feb, 2017 8 commits
  9. 01 Feb, 2017 4 commits
  10. 31 Jan, 2017 11 commits