> On Mar 11, 2022, at 6:07 AM, Weber, Patrick <[email protected]> > wrote: > > >>> What is the ?codec ID?? > > While I was hoping you'd know, I rather expected this response. Let me ask > the customer which RFC/standard he's referring to & I'll get back with you. I > suspect he's looking for a media description with codec name & ID; here's his > question to me: > > "When working with the video stream, the codec for the data stream is > reported as "Data: none". This is easily seen with the FFMPEG tool (ffprobe > rtsp://192.168.0.40/Primary). Generally when working with KLV data streams > the codec should be set to KLV (id: 100356). When you create the stream is > this something that you can specify?"
This doesn’t seem to have anything to do with the RTP stream (as defined, in this case, by RFC 6597 - which describes the RTP payload format for carrying this KLV data). RFC 6597 doesn’t mention “codec” at all. I suspect that the FFMPEG tool that your customer is using (“ffprobe”) just happens to not recognize this RTP payload format (“application/smpte336m”). And then your customer is getting confused, and thinking that there’s a problem with the KLV data in the stream, when there isn’t. His ‘problem’ is likely just with “ffprobe”. Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
