Closed wanderingcode closed 6 months ago
Could you retry this with one of the latest SDK releases and see if it still reproduces, maybe best would be 1.8.1?
This has been over a year now. A lot has changed. I can confirm it still crashes on 1.7.4 We have not implemented the new async api yet so it will take some time before we can test this on the latest versions. I'll try to make some time to fit it into our schedule.
Honestly, for what its worth sorry for the delay. We only started working on this SDK end of last year, wasn't sure about state of these old untouched issues so they just kind of lingered. I will see that someone in the team takes a look at this. Not sure if this is fixed at all, so we will try to reproduce it and come back with info.
I appreciate that. Thanks
Ok looking through the Objc part of the SDK I think I found the issue. We will confirm fix and then work to backport it ASAP.
Excellent!!
No problemo, I will update once release is made. I would definitely suggest moving to the new Async API as soon as possible. It is much more stable and overall just more better.
Understood. It's on our list, just not our top priority right now. We will re-evaluate.
Thank you!
In order to process a video frame I created a MCIosVideoRenderer class and override didReceive. In that function if I call frameType() on the provided video frame the app crashes with the following error:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[MCVideoFrameImpl frameType]: unrecognized selector sent to instance
I would expect a MCVideoType to be returned so I can verify the correct pixel format and process accordingly. Any help is appreciated.