jeelizFaceFilter
three-stdlib
Our great sponsors
jeelizFaceFilter | three-stdlib | |
---|---|---|
2 | 7 | |
2,619 | 639 | |
1.0% | 2.3% | |
5.2 | 8.3 | |
3 months ago | 5 days ago | |
JavaScript | JavaScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jeelizFaceFilter
-
Adding AR Filters in a 100ms Video Call - Part 1
Ikr! That's what I was thinking when I came across Jeeliz. Now I have worked with tensorflow.js based libraries in the past but they're usually quite CPU intensive for a live video use case. Jeeliz looked promising as it's designed for this use case. So I thought why not try it out by adding some 3d AR filters to our video calls. Well! that is what we're going to do.
-
Best Web-Based Face Tracking Library?
I created a demo face filter web app using jeeliz. It has great features however, I found that the tracking performance wasn't perfect. Media pipe seems to require building out custom features manually to achieve the face filter app I need. I'm wondering if building a more custom app with mediapipe would be worth the extra effort over Jeeliz.
three-stdlib
-
Arghhh ! Three !
We have forked parts of the three core stuff to minimise breaks. drei for instance uses https://github.com/pmndrs/three-stdlib not examples/jsm. The threejs version you install can still pull the rug but pmndrs works against that with conditionals, shaders for instance are made to function despite three breaking stuff. You can generally rely on it and Fiber + eco system has semantic versioning.
-
React Three Fiber and NextJS Starter Template
React Three Fiber has been a fantastic way to quickly prototype 3D apps and games, and even efficient enough to carry them through to production. The problem? Itβs can be a lot of setup. Just from that last paragraph, you see the string of dependencies R3F uses, and it gets even more complicated from there when you familiarize yourself with the current ThreeJS ecosystem (see: three-stdlib).
-
Resources for using Three.js with Nuxt
three doesn't play well with node and node based environments. poimandres has been building out three's reach more and more, for instance https://github.com/pmndrs/three-stdlib this will all run under next/nuxt or whatever without workarounds.
-
Need help importing .gltf into a nextJS component.
three is harder to use in next because it doesn't run under node. with three-fiber we have begun to fork some parts of it: https://github.com/pmndrs/three-stdlib that will make it easier to use it under next, even if you use "vanilla" three, stdlib's GLTFLoader will run fine whereas there/jsm won't (without workarounds). is there any reason why you would not want to use react for three though? you're using it for the dom already, r3f is the exact same thing as react-dom, a renderer, it doesn't wrap three.
-
How to build 3D scenes with React Three Fiber
Same, the pmndrs folks at least pulled some of the examples stuff into https://github.com/pmndrs/three-stdlib which is ESM
-
Challenges of using Three.js and vue3+nuxt
you can use the same tools that react users use because we face the same problems. for instance, next/nuxt are running under node, which doesn't understand what "import" means, so you'll not be able to use anything from three/examples/jsm/ (loaders, controls, etc). but we have made solutions for that. for instance https://github.com/pmndrs/three-stdlib generally there is lots on the poimandres github org that is equally valid for vanilla, react, vue and anything else.
-
Render Scene inside Nextjs [Help Wanted]
don't mix three and react. take an hour to read through react-three-fiber docs and port it. you will be so much better off, 95% of that code will just vanish. poimandres also takes care of all the other parts, for instance three/examples/jsm/* is not node compatible, you can't easily use it in next. but there exists three-stdlib now and many other things that make your life easier.
What are some alternatives?
mediapipe - Cross-platform, customizable ML solutions for live and streaming media.
drei - π useful helpers for react-three-fiber [Moved to: https://github.com/pmndrs/drei]
shader-web-background - Displays GLSL fragment shaders as a website background. Supports offscreen buffers and floating point textures on almost any browser and hardware. Compatible with Shadertoy.
leva - π React-first components GUI
troika - A JavaScript framework for interactive 3D and 2D visualizations
A-Frame - :a: Web framework for building virtual reality experiences.
download-snap-memories - Script to download all memories from Snapchat
stackgl - A node.js-style module system for GLSL! :sparkles:
model-browser - model-browser is a command line tool available on npm, for browsing local 3D models via a web browser. It currently only supports GLB files.
voxel-editor - A voxel editor in the browser.
three.js - JavaScript 3D Library.
drei - π₯ useful helpers for react-three-fiber