Re: [webrtc-pc] RTCRtpSynchronizationSource.audioLevel algorithmic equality

@jan-ivar I find it a bit confusing. I read @fluffy's comment as disagreeing with the prose in the case of synchronization sources (@fluffy please feel free to correct me). Currently, if the audiolevel is missing on the receiver side, it is computed. There is no way to tell if the audio level is computed or if it comes from the header. So if they aren't allegorically equivalent, what assumptions can one make about the quality of the value?

I guess my confusion stems from the dual life of this Dictionary, which looks like an RTP construct, but quacks like a media construct.  The timestamp is play out time, and the without the header you have to decode the media.

-- 
GitHub Notification of comment by na-g
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1760#issuecomment-371370926 using your GitHub account

Received on Thursday, 8 March 2018 03:56:14 UTC