6 ms·
This seems tremendously CPU intensive, my fan spun up after two seconds of playing video. The idea is interesting, but until it does it with GLSL shaders or som
by dusted 8y ago
This seems tremendously CPU intensive, my fan spun up after two seconds of playing video.
The idea is interesting, but until it does it with GLSL shaders or something to get that sweet hardware acceleration,it's just a proof that it CAN be done, rather than a practical solution.
- PostOnce 8y agoNot stressing my 5 year old laptop out too much.
- dschooh 8y agoIt'll use shaders if WebGL is supported and enabled: https://github.com/phoboslab/jsmpeg/blob/master/src/webgl.js https://github.com/phoboslab/jsmpeg/blob/master/src/webgl.js There is also a site to test features and their impact on performance: https://jsmpeg.com/perf.html https://jsmpeg.com/perf.html
- Crinus 8y ago> rather than a practical solution. I have a very practical solution for you: bypassing the autoplay restriction for ads.
- throwaway55554 8y agoThis would be very user hostile.
- jmkni 8y agoOhh that's great! Terrible! But great!
- aeharding 8y agoThis is why videos are allowed to autoplay if muted. Otherwise sites would use GIFs or something like this, which is much less efficient.
- Crinus 8y agoWell, this allows to autoplay even if not muted :-P. https://jsmpeg.com/perf.html https://jsmpeg.com/perf.html
- tomhoward 8y ago> it's just a proof that it CAN be done Which is a perfectly valid reason to build something. But this project is 6 years old (almost to the day, according to Github) and has over 3700 stars, so it seems to be a bit more than a mere novelty.
- speps 8y agoStraight from the minified version: > JSMpeg.Renderer.WebGL.IsSupported()?new JSMpeg.Renderer.WebGL(options):new JSMpeg.Renderer.Canvas2D(options); Not sure why you didn't check if it supported WebGL or not.
- larvaetron 8y ago> it's just a proof that it CAN be done, rather than a practical solution. Thankfully this is Hacker News, not Practical News.