RSATom / WebChimera.js

[ABANDONED] libvlc binding for Electron
GNU Lesser General Public License v2.1
661 stars 105 forks source link

[announce] WebChimera.js will dead after VLC 3.0 release #110

Closed RSATom closed 3 years ago

RSATom commented 8 years ago

https://forum.videolan.org/viewtopic.php?f=32&t=135545

It looks like since VLC 3.0 vmem will be even more broken. So if you still use WebChimera.js I would recommend you start search some alternative solution.

Sorry.

jaruba commented 8 years ago

200

romaincointepas commented 7 years ago

@RSATom Any plans on supporting VLC 2.2.5 and maintaining it (making releases for new node versions)?

RSATom commented 7 years ago

@romaincointepas, since WebChimera.js buld is automated, it will be pretty easy maintain any VLC 2.2.x versions.

jbkempf commented 7 years ago

@RSATom there are work-arounds and we will get a solution. And seeing the additions in 3.0, I doubt it's a good idea to stay on 2.2.x.

jaruba commented 7 years ago

i did not expect JB to ever find this thread.. it's a christmas miracle..

1439916660-haabt

jbkempf commented 7 years ago

@jaruba I don't really like github, but since we (the VLC community) must do more around the JS ecosystem, and WC.js is the most advanced one around VLC, I doubt I have a choice :)

RSATom commented 7 years ago

I doubt it's a good idea to stay on 2.2.x.

It's not about stay on 2.2.x, it's more about abandon WebChimera.js completely. And tbh it's almost happened already.

jbkempf commented 7 years ago

@RSATom ah, ok. Any special reason why?

RSATom commented 7 years ago

@jbkempf, just because we can't get good results with VLC 3.0 atm, and as you've mentioned, it's bad idea stay on outdated 2.x

But if there will be any reasonable solution - it's not a big deal to resurrect project. I just don't have time to search reasonable solution for VLC 3.0, and don't sure I can.

jbkempf commented 7 years ago

@RSATom 3.0 is not finished yet. So dropping because there might be a big problem seems a bit weird.

Also, I'd argue you should use OpenGLES2 output mapped to webgl, because that would be way way faster.

RSATom commented 7 years ago

I just have to warn users, to give them time to switch to some other technology, since it could cost big amount of money for some of them.

RSATom commented 7 years ago

Also, I'd argue you should use OpenGLES2 output mapped to webgl, because that would be way way faster.

Could you please explain what do you mean by "OpenGLES2 output mapped to webgl"?

jbkempf commented 7 years ago

You should be able to use the OpenGLES2 output of VLC and map it directly to a webgl context from CEF. I don't know yet how though.

RSATom commented 7 years ago

Understand. But unfortunately Node.js addons don't have access to low level OpenGL context used by WebGL. At least it was so about year ago. Maybe something was changed, don't know.

And yes, I'm agree, it would be much better approach than current (with vmem).

thers commented 7 years ago

So if we'll pass WebGLRenderingContext from within JS code to native node module there is no way to use it?

jbkempf commented 7 years ago

I need to check, but there are ways, like emscripten is doing: https://kripken.github.io/emscripten-site/docs/porting/multimedia_and_graphics/EGL-Support-in-Emscripten.html

thers commented 7 years ago

It'll be really good if you keep working on this one-and-only lib :) You know, there are no alternatives.

jbkempf commented 7 years ago

Well, as soon we add torrents to VLC, it'll be even better :)

jaruba commented 7 years ago

@jbkempf never thought u guys will make that step

Ivshti commented 7 years ago

@jbkempf "use the OpenGLES2 output of VLC and map it directly to a webgl context from CEF" - can you please elaborate on that?

jbkempf commented 7 years ago

@Ivshti sure. I'll do that on the other ticket.

ghost commented 7 years ago

just found this project, sadpanda about vmem :( and while there isn't any real alternative right now, we are likely to have a client-side vlc.js at some point through emscripten

Either way great project you got going here, even if release 3.0 changes might kill it :/

right now though this looks like the best shot at getting the convenience of VLC in the browser. atm im streaming my library with a simple webserver and using VLC's network feature to watch videos, and playing a video is as clunky as it sounds. used to use Plex but ive been wanting to implement something like this project in a simpler lightweight interface of my own, to which this looks like it'll do the job (thank you!). today its server-side tomorrow hopefully we'll have a client-side alternative as well.

RSATom commented 7 years ago

As I know libvlc team finally solved problem with vmem in VLC 3.0. But I'm still don't sure I should resurrect this project. Just because this solution could not get well enough performance even with FullHD, say nothing of 4k..

gamelaster commented 7 years ago

This project is awesome, there is not any alternatives, please keep it up

RSATom commented 7 years ago

I was wrong, it looks like we will not have solution with vmem in the near future: https://patches.videolan.org/patch/17206/

So I will keep WebChimera.js in suspended state... sorry.

itshaadi commented 7 years ago

i had to install windows 7 on virtual box and then install all the requirements for compiling WebChimera. and now it's suspended !

giphy

ghost commented 7 years ago

nah, I see your point here with this after reading the discussion on the patch. And yeah it does indeed struggle with HD content (of which all my shit is exactly that, no 4k atm but still). fair call here.

jbkempf commented 7 years ago

We're still looking for a good way to find a fast solution. PPAPI is one, but not a long term one.

RSATom commented 3 years ago

It's already dead.