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
The openwebrtc-ios-sdk claims iOS7 but the iOS OWR demo apps start from iOS8.
Matrix Console starts from iOS7. Calls works fine between iOS7 OWR and FF/Chrome or other iOS7 OWR client.
But there is an interoperability issue when making calls between iOS7 vs iOS8: there is no video both side.
To answer your question stated in the title of the issue, OWR supports at least iOS 7. As @superdump says iOS 8 introduced the possibility to do HW accelerated H.264 video. If OWR is running on iOS 8 and a supported device, HW will be used, otherwise we fall back to SW coding via OpenH264.
The openwebrtc-ios-sdk claims iOS7 but the iOS OWR demo apps start from iOS8.
Matrix Console starts from iOS7. Calls works fine between iOS7 OWR and FF/Chrome or other iOS7 OWR client.
But there is an interoperability issue when making calls between iOS7 vs iOS8: there is no video both side.
Only the iOS7 logs show errors:
Assert - (kernResult == kIOReturnSuccess) - f: /SourceCache/AppleVXE380/AppleVXE380-403/Library/AppleVXE380UserLandLibrary.cpp l: 494
AppleVXE380VA ERROR: IOServiceOpen failed
Assert - (false) - f: /SourceCache/AppleVXE380/AppleVXE380-403/Library/AppleVXE380FIGwrapper.cpp l: 3106
VXE FIG: H264VideoEncoderVA_DriverCreate failed.
Assert - (pDriverInstance) - f: /SourceCache/AppleVXE380/AppleVXE380-403/Library/AppleVXE380UserLandLibrary.cpp l: 579
AppleVXE380VA ERROR: AppleVXE380VA_DriverDelete, pDriverInstance NULL.
Assert - (err == noErr) - f: /SourceCache/AppleVXE380/AppleVXE380-403/Library/AppleVXE380FIGwrapper.cpp l: 3227
VXE FIG ERROR: AppleVXE380VA_DriverDelete failed.
0:04:43.601722000 �[332m 787�[00m 0x163321b8 �[31;01mERROR �[00m �[00m vtenc vtenc.c:792:gst_vtenc_create_session:<encoder_vtenc_h264_0>�[00m VTCompressionSessionCreate() returned: -12907
The text was updated successfully, but these errors were encountered: