-
Notifications
You must be signed in to change notification settings - Fork 163
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
Implementation in Video(React Native) #258
Comments
I am also having a similar issue, with webcam feed - react native |
I'm trying this with a react-native-video but it dosen't pick up as well. (not on expo) child is not renderable. Got:', null Any idea? |
@gre wonder if you could advise best way this could be fixed? I can see a gl-react-image https://github.com/gre/gl-react-image |
Related to #215 |
Is the issue that we cannot access the frame in |
i think the underlying gl.node simply dosen't support video surfaces which i think is fundamentally different from images. i 'resolved' it by showing /rendering the preview version of the video, which I have as a gif format - instead of trying to put the gl-react filter on the actual mp4 video. Then afterwards i have to ffmpeg filters to manually 'synchronize' with the gl-react filter. In any case, it would have been inefficient to try to render all the different filter options to show the user on the actual mp4 video. |
Implementation Issue
So I have been trying to implement gl-react over videos in React Native(Expo CLI). I follwed this example .
Expected behavior
Video should play with gl-react layers.
Actual behavior
However I get this error(copying the files exactly as it is):
blob:https://web.whatsapp.com/ccfde4db-5bbe-467e-a749-14dbd05dfc7d
So I tried changing the code a bit. (only index.js)
Now I get a complete black screen as the layer over the video. Video plays for sure, since audio is coming, seems like the gl layer over it comes as black only. This warning comes >> Node#138(colorify#50), uniform children: child is not renderable. Got:, null
The text was updated successfully, but these errors were encountered: