Closed weberbox closed 7 months ago
We've got plans to improve the quality of mouse on Netcast, but haven't had time to implement. Our solution still uses HTTP, but should work well. I'd encourage you to try the mouse for Netcast on iOS, if you can. The performance there is much better.
I don't have an iOS device to test with. If you want to see the UDP code just let me know and I will send it over.
I will use my UDP code for now and wait to see the improved HTTP version when it gets published.
I'd appreciate that. Posting a Gist would be appreciated. Or if you want to e-mail, you can send to support@connectsdk.com. Thanks!
I've tried implementing the HTTP fix and it's still pretty awful. I'm not sure if the bottleneck is Android, Apache HTTPClient, or both, but the iOS implementation is super smooth. I'll have to take a look at implementing the UDP solution for a future version.
This is actually a lot of work due to the fact that it requires the old ROAP protocol for getting a session id. Will defer this until a later date.
Moving this to 1.4 based on partner/market demand
@simongladkoskok here is the source code for the UDP packet format. https://gist.github.com/zippy-man/8899f3b3dfb22b114ae2
When using the mouse via HTTP in Netcast it is very sluggish and jumpy. Since Netcast platform supports UDP mouse control it may be a good idea to utilize it to improve the performace. I have working code that you may be able to improve and utilize if interested.