Re:JSMpeg – Decode It Like It's 1999
by dusted on Tuesday May 07, 2019 @05:36AM
(#19847830)
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.
[ Parent
| on HN ]
It'll use shaders if WebGL is supported and enabled: 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
> rather than a practical solution.
I have a very practical solution for you: bypassing the autoplay restriction for ads.
Ohh that's great! Terrible! But great!
This is why videos are allowed to autoplay if muted.
Otherwise sites would use GIFs or something like this, which is much less efficient.
Well, this allows to autoplay even if not muted :-P.
Re:JSMpeg – Decode It Like It's 1999
by throwaway55554 on Tuesday May 07, 2019 @07:49AM
(#19848545)
This would be very user hostile.
You mean user engagement will improve, right? :-P
Like every other form of advertising.
> 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.
Re:JSMpeg – Decode It Like It's 1999
by larvaetron on Tuesday May 07, 2019 @11:57AM
(#19850681)
> it's just a proof that it CAN be done, rather than a practical solution.
Thankfully this is Hacker News, not Practical News.
Straight 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.