Avatar for Username

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

Is it possible to disable VP8 error concealment for WebRTC?

  • 2 odpowiedzi
  • 1 osoba ma ten problem
  • 18 wyświetleń
  • Ostatnia odpowiedź od Robert Kirnum

Robert Kirnum
Robert Kirnum
more options

Chrome appears to disable VP8 error concealment when rtcp-fb nack is negotiated when setting up a connection (SIP / SDP). I have not been able to get Firefox to disable error concealment. I am also unable get Firefox to enable rtcp-fb nack though I am not certain this will disable VP8 error concealment as on Chrome.

Chrome appears to disable VP8 error concealment when rtcp-fb nack is negotiated when setting up a connection (SIP / SDP). I have not been able to get Firefox to disable error concealment. I am also unable get Firefox to enable rtcp-fb nack though I am not certain this will disable VP8 error concealment as on Chrome.

Wybrane rozwiązanie

From http://www.ietf.org/rfc/rfc2327.txt SDP: Session Description Protocol

6. SDP Specification

… 

  Text records such as the session name and information are bytes
  strings which may contain any byte with the exceptions of 0x00 (Nul),
  0x0a (ASCII newline) and 0x0d (ASCII carriage return).  The sequence
  CRLF (0x0d0a) is used to end a record, although parsers should be
  tolerant and also accept records terminated with a single newline
  character.  By default these byte strings contain ISO-10646
  characters in UTF-8 encoding, but this default may be changed using
  the `charset' attribute.

Looks like the Firefox SDP parser requires a carriage return ('\r'), it is unable to process attributes ending in just a newline ('\n'). I guess the RFC does indicate SHOULD as opposed to SHALL.

Przeczytaj tę odpowiedź w całym kontekście 👍 1

Wszystkie odpowiedzi (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Maybe check out the Firefox source code about rtcp-fb nack.

Zmodyfikowany przez cor-el w dniu

Robert Kirnum
Robert Kirnum Zadający pytanie
more options

Wybrane rozwiązanie

From http://www.ietf.org/rfc/rfc2327.txt SDP: Session Description Protocol

6. SDP Specification

… 

  Text records such as the session name and information are bytes
  strings which may contain any byte with the exceptions of 0x00 (Nul),
  0x0a (ASCII newline) and 0x0d (ASCII carriage return).  The sequence
  CRLF (0x0d0a) is used to end a record, although parsers should be
  tolerant and also accept records terminated with a single newline
  character.  By default these byte strings contain ISO-10646
  characters in UTF-8 encoding, but this default may be changed using
  the `charset' attribute.

Looks like the Firefox SDP parser requires a carriage return ('\r'), it is unable to process attributes ending in just a newline ('\n'). I guess the RFC does indicate SHOULD as opposed to SHALL.