|
From: | Giacomo Furlan |
Subject: | Re: [Linphone-developers] Loading another H264 decoder profile |
Date: | Mon, 12 Oct 2015 13:40:37 +0200 |
ThanksPlease help me!AFAIK the profile-level-id is formed by three words, in this case 4D, 00, 29 (profile_idc: 0x7D, profile-iop: 0x00, level-idc: 0x29). Maybe that combination is not supported by FFMPEG? Or should I register it somewhere else?I've built the library with BUILD_X264=1, but still I only see that only msopenh264-android plugin is being registered (and not msx264)...Hello again!I've tried adding manually to submodules/linphone/coreapi/linphonecore.c a different payload type (in particular payload_type_h264 with profile-level-id=4D0029), but when the call is accepted, I still get the following error:
10-12 12:38:03.283 29515-29678/com.be_ssd.sipinterphone I/SIPManager: Found payload H264/90000 fmtp=profile-level-id=4D0029; packetization-mode=1
10-12 12:38:03.293 29515-29678/com.be_ssd.sipinterphone I/SIPManager: No match for H264/90000Giacomo FurlanSoftware developer
Software Solutions Designs2015-10-08 17:14 GMT+02:00 Giacomo Furlan <address@hidden>:Thank you.Where could I start from?Hello!I think I found the problem why I can't receive the video: the H264/90000 codec compiled with the relative submodule supports a profile level id different than 4D0029 (which is the one that is used by the other SIP client). I don't really know what this profile id is, and thus I don't know how much effort it would take to support it.Giacomo FurlanSoftware developer
Software Solutions Designs
[Prev in Thread] | Current Thread | [Next in Thread] |