Skip to content
Snippets Groups Projects
  1. Dec 07, 2024
  2. Dec 06, 2024
  3. Nov 26, 2024
  4. Nov 21, 2024
    • Sergio Ammirata's avatar
      Add config file support for ristsender and ristreceiver. · e43303fa
      Sergio Ammirata authored
      The file needs to be in yaml format, here is an example:
      ---
      secret: blarg
      buffer: 0
      encryption-type: 256
      profile: <simple/main/advanced>
      stats: 1000
      inputurl:
        - <URL A>
        - <URL B>
        - ...
      outputurl:
        - <URL A>
        - <URL B>
        - ...
      We used a built-in very simplistic native yaml parser and not a yaml library to not introduce a new dependency. The key-value pairs are the same ones used in the long-options of the command line (all are supported).
      e43303fa
  5. Nov 15, 2024
  6. Nov 14, 2024
  7. Nov 13, 2024
  8. Nov 11, 2024
    • Alyssa Ross's avatar
      Fix building srp_examples.c with musl · a6490097
      Alyssa Ross authored
      This fixes the immediate build failure, but it's quite a fragile fix,
      because if any other libc defines malloc, calloc, or free in a header
      that has not been included by this point in srp_examples.c, but is
      subsequently included by srp.c or srp_constants.c, the same problem
      will occur.  The ideal thing to do would be to find a way to
      accomplish the desired effect without needing to use a macro to
      override the definitions of libc functions.
  9. Nov 02, 2024
    • Sergio Ammirata's avatar
      Fix criteria for classifying rtp vs rtcp packets. · 128403eb
      Sergio Ammirata authored
      We were using payload_type < 200 and now we use a range outside 200 to 205 for the classification.
      When the marker bit of the rtp header is turned on, the payload type of the rtp packet could match the range we were looking for, thus incorrectly classifying rtp data as rtcp data. For example, STMPE-2110 uses rtp payload types 96 through 127 (224 to 255 with the marker bit on).
      With this fix, librist will also classify rtp packets with a payload type of 72-77 as rtcp. Since that range is reserved for “RTCP conflict avoidance” on the RFC4855 standard, we can leverage that to add a feature to the library (keep reading).
      Lastly, let it be documented that the library WILL only classify rtp packets as rtcp if they live in the range 200-205 or 72-77. Everything else is considered rtp data.
      If anyone wants to use custom rtcp packets not defined in the RIST specification and they want their implementation to work with librist, they must use the 72-76 range or they will be treated as rtp data and run the risk of corrupting their data stream.
      128403eb
  10. Oct 26, 2024
  11. Oct 25, 2024
Loading