-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with wasm file #124
Comments
Sorry for the inconvenience. We encountered issues with providing the data files via npm due to Package Size limitation of NPM. Therefore, now we have decided to make the data downloadable as one package via the CDN See #127. Additionally, I agree with preload. The better version to preload is to just run the background removal once with a empty image. As soon as there is some time we'll fix this. |
I suggest making the repository compatible with huggingface or tensorflowjs: I have implemented mediapipe and transformer in my web application and it was very quick to do. |
I encountered a challenging error with version 1.5.2. Does anyone have any suggestions?
It seems the issue is related to the WASM file or its configuration. Since these files are not available on GitHub, I can't track down the exact problem. However, version 1.5.1 works correctly.
I also encountered issues when downloading the asset files and had to create a script to download them myself.
Additionally, some documentation is only available on npm:
Additionally, preload does not function correctly as it requests all 100 files at once, which can cause client failures when downloading the files, especially on mobile devices. The best approach is to download them one by one and cache them in the service worker before calling the backgroundRemove function.
In addition, hash URLs do not have an extension, all URLs, unless they are dynamic, must have an extension and the extension specifies the type of content.
Good luck fixing 1.5.2
The text was updated successfully, but these errors were encountered: