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
We have been using 1080p30 for a while with no trouble but on recent iOS versions (16.4+) notice this issue much more frequently. The encoder dies and the only way to detect it is to check the stats and see local send framerate goes to 0. Republishing the track can fix it but will fail again in under a minute.
Twilio video is in need of a higher resolution hardware accelerated codec which could be solved by allowing for a higher level profile. VP8 and VP9 being software encoded is prohibitively expensive, results in hot phones and throttling when sending more than one stream even on the latest hardware.
I'm happy to take the compatibility hit, we target higher end devices and would much prefer higher resolution.
The text was updated successfully, but these errors were encountered:
Any plans to resolve [ISDK-1590]?
We have been using 1080p30 for a while with no trouble but on recent iOS versions (16.4+) notice this issue much more frequently. The encoder dies and the only way to detect it is to check the stats and see local send framerate goes to 0. Republishing the track can fix it but will fail again in under a minute.
Twilio video is in need of a higher resolution hardware accelerated codec which could be solved by allowing for a higher level profile. VP8 and VP9 being software encoded is prohibitively expensive, results in hot phones and throttling when sending more than one stream even on the latest hardware.
I'm happy to take the compatibility hit, we target higher end devices and would much prefer higher resolution.
The text was updated successfully, but these errors were encountered: