-
Notifications
You must be signed in to change notification settings - Fork 6
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
"VFX Avi player" #4
Comments
While this looks like an actual bug in the detection of the decoder, I doubt AVI videos will play in the browser. Of course, IE might be an exception—but keep in mind that Webvs works in Chrome only. Apart from that I'm not sure how video could work in Webvs at all. It will not work locally, since JavaScript cannot access your local file system. Uploading a video to a server isn't exactly practicable. Anyway, I suggest you commit a bug fix for the decoder. As for Webvs, video is one of the features that will likely not get implemented. |
Hi, |
also, before the question comes up: texer images are added as base64 encoded strings |
I can comment a bit on video in Webvs. It is technically quite simple to get videos into Webvs. Webgl lets you map html5 video elements or even video from the webcam (this'd be a fun thing to try) onto textures (http://stemkoski.github.io/Three.js/Video.html). So its basically a question of codec support in the browser and how we can retrieve the file resources. The video can be streamed from external url, but as @idleberg mentioned it is not quite practical and unless we come up with some really clever stuff i dont think js can handle reasonably big videos encoded as strings in json. |
This might help: |
damn this is absolutely difirent version that distributed here http://goebish.free.fr/vfx/ this one is more cool :D https://github.com/goebish/VfxAviPlayer/releases/tag/1.0.7 👍 👍 |
i use in my presets "VFX Avi player" from http://goebish.free.fr/vfx
Decoder find it as
{
"type": "AVIPlayer",
"filePath": "video_file.avi",
"enabled": false
}
actually element was enabled and there was much more settings :)
The text was updated successfully, but these errors were encountered: