About that missing documentation... #2945
valzargaming
started this conversation in
Feedback & Suggestions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
JDA/src/main/java/net/dv8tion/jda/internal/audio/AudioPacket.java
Line 44 in 726ef9d
I've figured out what
0x78is supposed to be. 0b0111 and 1000. The first 0 is the marker and the payload type 1111000 (or 0x78 & 0x7F = 120, with 0x7F being a bitmask that keeps the lower 7 bits and clears the top (marker) bit).Per RFC 3551:
Tables 4 and 5 define this profile's static payload type values for the PT field of the RTP data header. In addition, payload type values in the range 96-127 MAY be defined dynamically through a conference control protocol, which is beyond the scope of this document....and per opusrtp docs:
tl;dr:
0x78has a marker bit of0and a payload type of120. Because we know Discord uses Opus per the docs I think we can say it's safe to assume that's what these bytes represent.Beta Was this translation helpful? Give feedback.
All reactions