You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When using linphone with vp8 enabled, video fails to be decoded.
Describe the solution you'd like
I would like freeswitch to properly handle vp8 streams from linphone.
Describe alternatives you've considered
I have isolated the issue to vp8 partitioning. This is enabled by default in linphone but disabled by default in freeswitch. For encoding this is fine, linphone handles both cases as input. However, freeswitch only handles vp8 streams with partitioning disabled. I have modified linphone to disable vp8 partitioning which avoids the issue but the correct fix would be to support partitioning in freeswitch for ingress vp8 streams.
Additional context
Add any other context or screenshots about the feature request here.
Package version or git hash
Observed using FreeSWITCH v1.10.7 but appears to be present in latest master source as well.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When using linphone with vp8 enabled, video fails to be decoded.
Describe the solution you'd like
I would like freeswitch to properly handle vp8 streams from linphone.
Describe alternatives you've considered
I have isolated the issue to vp8 partitioning. This is enabled by default in linphone but disabled by default in freeswitch. For encoding this is fine, linphone handles both cases as input. However, freeswitch only handles vp8 streams with partitioning disabled. I have modified linphone to disable vp8 partitioning which avoids the issue but the correct fix would be to support partitioning in freeswitch for ingress vp8 streams.
Additional context
Add any other context or screenshots about the feature request here.
Package version or git hash
The text was updated successfully, but these errors were encountered: