anduc

7 ms·

1.
by anduc 2y ago
wow, I didn't know this was possible
2.
Show HN: Open-source image converter runs in browser, powered by LibVips WASM(github.com)
2 points by anduc 2y ago|0 comments
3.
Show HN: Open-source image converter runs in browser, powered by LibVips WASM(bannerify.co)
1 points by anduc 2y ago|0 comments
4.
Show HN: Open-source dynamic og-image to your blog / website(ogcool.vercel.app)
3 points by anduc 2y ago|1 comments
5.
by anduc 2y ago
Hi guys, thanks for your interest in my little project, I'm glad you all like it. I just spend my free time to make it much better based on your feedback - Mobile support, tested on my iPhone - GitHub README added - Added medium zoom f
6.
by anduc 2y ago
Several GBs of RAM definitely too much, I'm not aware that this consumes that much memory. I will spend more time trying to figure out how much memory is minimum necessary for this and will warn in the page.
7.
by anduc 2y ago
Can you provide more additional information for me? If you're using Linux and Chrome you probably need to pass GPU flag `--enable-unsafe-webgpu --enable-features=Vulkan`
8.
by anduc 2y ago
Sorry for the inconvenience, I've tested with Arc and can confirm this error, I didn't know why this happens. I will check further to determine the reason and report it to the upstream library (I think it's because the engine
9.
by anduc 2y ago
Someone mentioned > Looks like WEBGPU is only on nightly for FF, for now
10.
by anduc 2y ago
Hey there, sorry for the issue, does it show status "Error"? if so can you try to enable WebGPU using this flag "--enable-unsafe-webgpu --enable-features=Vulkan", if not it doesn't seems like a common error and I wi
11.
by anduc 2y ago
can you raise this issue on Github? I will take a look into this later since it's not common error. I think it's because some settings on the browser I've heard someone reported that Arc had a similar error
12.
by anduc 2y ago
Thank you, looking forward to this, if you have any feedback please let me know via x.com/duc__an
13.
by anduc 2y ago
Ah, I didn't realize that there is any product with a similar name, and in case I already know, I think I'll still pick this name since it's only an experimental open source project with WebGPU. Remove-bg is quite common IMO
14.
by anduc 2y ago
Hi there, it's because I copied the project template from my previous project, will check and try to upgrade to the React 19 soon if it'll work with the libraries
15.
by anduc 2y ago
First time I see this, by the first impression I think the output quality of this one is better than mine and my code is only based on one model In my understanding, It'll possible if the model's author build to https:/&#x2F
16.
by anduc 2y ago
Sorry for my late I missed the comment Yeah I think it's because the quanlity of the model, hopefully we will have better quanlity in near future. I will see if anything I can do with the settings
17.
by anduc 2y ago
It's nice to see it here, imagine it works like your repo but runs entirely in the user's browser, very cool, doesn't need any complicated setup
18.
by anduc 2y ago
Same here, this is the first time working with this library to me, it's really making me believe even more in the future of Transformer.js/WebGPU, it just beginning
19.
by anduc 2y ago
Haha, I didn't notice this! Yeah, only Vite will reduce the dependencies a lot, but I'm not sure which one is the biggest here to talk about Will try to the deps simpler later, after all this is about a little time of work
20.
by anduc 2y ago
Maybe it's because of how I detect the GPU and switch to another backend (to support devices that don't support WebGPU). Can you try to go https://pmndrs.github.io/detect-gpu/ and pass the result here
21.
by anduc 2y ago
Exactly this, as mentioned in the post I've used the same technology with this playground (copied lots of code from here) What I do is mostly make the UX better PS: WebGPU is the future
22.
by anduc 2y ago
I tried it on my Chrome-Mac device, but not sure how it works on other devices (assuming it works). I'll test it out later. Sorry for the inconvenience
23.
by anduc 2y ago
The error is ambiguous right now and I'll try to make it clearer (welcome for contributions) The idea is it fallbacks to not use webgpu if your browser is not supported, but it was made in 2 hours, bug is acceptable :)
24.
Show HN: Remove-bg – open-source remove background using WebGPU(bannerify.co)
286 points by anduc 2y ago|121 comments
25.
Show HN: I made og image generator and embeddable dynamic for website using SDK(ogcool.vercel.app)
1 points by anduc 2y ago|0 comments