Re: [Freeswitch-users] h264 video call between endpoints with one end at bad resolution of 352x288
sounds like you might be doing the option to mirror resolution
On Jun 28, 2018, at 9:07 AM, antonio via FreeSWITCH-users <freeswitch-users@lists.freeswitch.org> wrote:
From: antonio <asilva@wirelessmundi.com> Subject: h264 video call between endpoints with one end at bad resolution of 352x288 Date: June 26, 2018 at 6:05:20 AM EDT To: freeswitch-users@lists.freeswitch.org
Hi,
Calling between two Grandstream GXV3275 i expected to have a video call at 1280x720, but the video that is present at destination as the resolution of 352x288 and the image as poor quality, originator is sending video at 1280×720. If i swap the devices the result is the same, the destination always get a bad resolution of 352x288 but the originator receives the video at expected resolution of 1280x720.
If i set rtp_direct between the two endpoints it work as expected.
I also tested a conference room and force the it resolution to 1280*x720 it work well, if i don't force the canvas-size i see:
2018-06-26 13:55:02.077824 [WARNING] mod_conference.c:3157 Unspecified video-canvas-size, falling back to 1280x720
And the conference is done at 1280x720.
I've open a jira where you can find a full log with this behavior:
https://freeswitch.org/jira/browse/FS-11140
I don't understand why there is transcoding and mod_av is used, the codec negotiated is the same.. i understand that the resolution is at 352x288 for the first frames sent by the phone but then it send them at 1280x720, mod_av should detected and adjust the new resolution, no?
Anyone experience this behavior?
Hi, i found the issue for this problem, it was because the fmtp parameters weren't pass to the bleg when using late-negotiation, so the other end start sending the video at lower resolution. I solve by exporting the first fmtp from the aleg to the bleg channel using the variable rtp_video_fmtp . This issue it's supposed to be fixed in https://freeswitch.org/jira/browse/FS-5958 but is present in current master and 1.8 branch. More info can be found in https://freeswitch.org/jira/browse/FS-11140. On 11/07/2018 22:06, Michael Jerris wrote:
sounds like you might be doing the option to mirror resolution
On Jun 28, 2018, at 9:07 AM, antonio via FreeSWITCH-users <freeswitch-users@lists.freeswitch.org <mailto:freeswitch-users@lists.freeswitch.org>> wrote:
*From: *antonio <asilva@wirelessmundi.com <mailto:asilva@wirelessmundi.com>> *Subject: **h264 video call between endpoints with one end at bad resolution of 352x288* *Date: *June 26, 2018 at 6:05:20 AM EDT *To: *freeswitch-users@lists.freeswitch.org <mailto:freeswitch-users@lists.freeswitch.org>
Hi,
Calling between two Grandstream GXV3275 i expected to have a video call at 1280x720, but the video that is present at destination as the resolution of 352x288 and the image as poor quality, originator is sending video at 1280×720. If i swap the devices the result is the same, the destination always get a bad resolution of 352x288 but the originator receives the video at expected resolution of 1280x720.
If i set rtp_direct between the two endpoints it work as expected.
I also tested a conference room and force the it resolution to 1280*x720 it work well, if i don't force the canvas-size i see:
2018-06-26 13:55:02.077824 [WARNING] mod_conference.c:3157 Unspecified video-canvas-size, falling back to 1280x720
And the conference is done at 1280x720.
I've open a jira where you can find a full log with this behavior:
https://freeswitch.org/jira/browse/FS-11140
I don't understand why there is transcoding and mod_av is used, the codec negotiated is the same.. i understand that the resolution is at 352x288 for the first frames sent by the phone but then it send them at 1280x720, mod_av should detected and adjust the new resolution, no?
Anyone experience this behavior?
-- Saludos / Regards / Cumprimentos António Silva
participants (2)
-
António Silva
-
Michael Jerris