This message was deleted.
# helpdesk
s
This message was deleted.
d
Thanks for the report Maxime! Do you mind filling an issue on Github (client-sdk-swift) to make it easier to track? This seems like a bug somewhere in the stack.
b
@jolly-airport-6235 Hi I'll investigate this one. filed an issue here https://github.com/livekit/client-sdk-swift/issues/148
Hi I think I fixed this issue in https://github.com/livekit/client-sdk-swift/commit/fee3d76e82fdabc30c3aadb3096a71c077a5ba08 Looks like it was the camera capturer side issue , not rendering side. To publish in 60FPS: • Create a camera track with 60FPS (defaults to 30) • Publish video track with 60FPS option. set
VideoView.debugMode = true
to see FPS in VideoView.
🔥 1
🙌 1
j
Hi Hiroshi, I should have added that we were using a
LocalVideoTrack.createBufferTrack
not the
CameraCapturer
so the format was already good on our side. However, rendering on iOS is still not true 60fps after your patch (webrtc is reporting 60fps stream but rendering is not). The only way to make it work at 60fps as far as I know is to do something like this in VideoView:
Copy code
self.nativeRenderer?.asMetalView?.preferredFramesPerSecond = 60
👀 1
b
Hey thanks for the info, that’s pretty interesting. I suppose Metal layer needs tweaking.
I made changes https://github.com/livekit/client-sdk-swift/commit/d7b3d66a726d8ae9c074da93e4905aeb3da2cb07 but I'm not sure it's actually rendering in 60 FPS. do you have a method to verify this ?