Ayase Minori
Ayase Minori
I don't know if there's a way to fix this, honestly, this seems to be an upstream bug within google/mediapipe.
You will need to lower the resolution input for Mediapipe, if you put it anything above 640x480, tracking slows down to a crawling halt.
Have you tried performing a benchmark against native mediapipe to see if the speed is comparable? There's nothing I can do mostly about if it's an upstream problem.
Hi, thanks for reporting. Unfortunately, even I am lost on what's going on here, hence we announced back in Discord we're rewriting it because I couldn't figure out what's wrong...
I don't know if I can help you yet other than suggesting to downgrade to 0.8.x for now, because 0.9.x kept failing at packet validation.
The solutions class were removed around 0.9.x, downgrade to 0.8.x or you can contribute the solutions class back if you're able to, I'd do it but I do not have...
Right now that's not possible, its primarily designed right now to be on par with kalidokit at some degree but mostly to provide a more human readable way to parse...
The solutions class were introduced back in [0.8.9](https://github.com/cosyneco/MediaPipe.NET/tree/0.8.9), you can start there.
Almost forgot to say, there's more info around #56 too if you want more context.
I think its fine in its own way. GPLv3 is *strict copyleft*. In a legal standpoint, this allows to maintain copyright of the author, then again, *this* is just a...