First of all, thank you Luca and Joshua for taking the time to help me and thank you very much Joshua for that awesome explanation. I see that there is a lot to learn.
Back on topic: I checked the format context and the codec context and I only found an empty (NULL) "extradata" field in the codec context. I also checked some other fields in both structures where I thought the data could be but found nothing. Am I looking in the right place? On Tue, Jun 10, 2014 at 9:55 PM, Luca Barbato <[email protected]> wrote: > On 10/06/14 14:11, Manuel Torres wrote: > > Captured with Wireshark: > > > > v=0 > > o=- 1293840088672 1293840088672 IN IP4 192.168.2.93 > > s=Live > > t=0 0 > > m=audio 0 RTP/AVP 0 > > c=IN IP4 192.168.2.93 > > a=control:rtsp://192.168.2.93/defaultPrimary/mic0/trackID=1 > > m=video 0 RTP/AVP 96 > > c=IN IP4 192.168.2.93 > > a=control:rtsp://192.168.2.93/defaultPrimary/cam0/trackID=1 > > a=fmtp:96 packetization-mode=0; profile-level-id=42A01E; > > > sprop-parameter-sets=J01AH42NKBaHt/4AQAA21BgYGQAAAwPoAADDUOhAB08AAQcau8uNCADp4AAg41d5cE+iwA==,KO48gA== > > a=rtpmap:96 H264/90000 > > a=x-avg-params:96 source-height=1080; source-width=1920 > > m=application 0 RTP/AVP 98 > > c=IN IP4 192.168.2.93 > > a=control:rtsp://192.168.2.93/defaultPrimary/metadata/trackID=1 > > a=rtpmap:98 vnd.onvif.metadata/90000 > > > > > > And it doesn't appear as extradata as should? It is quite strange... > > lu > > _______________________________________________ > libav-api mailing list > [email protected] > https://lists.libav.org/mailman/listinfo/libav-api > _______________________________________________ libav-api mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-api
