03:08
<robman>
afternoon all 8) does anyone know if you can get an ImageData directly from an HTMLVideoElement in some way? or is the only solution to do a 2dcontext.drawImage(video) -> 2dcontext.getImageData(...) pipeline?
03:09
<annevk>
it's the only way
03:09
<robman>
boo
03:09
<robman>
very innefficient
03:09
<robman>
thanks annevk
04:26
<jwalden>
robman: not necessarily inefficient; I could imagine the former call living entirely in GPU memory in the right circumstances, and with good enough implementations
04:26
<jwalden>
whether any of that is the case, I couldn't say, tho
04:28
<zewt>
jwalden: vanishingly unlikely
04:28
<jwalden>
yeah, we're probably not there yet
04:28
<zewt>
well, no--unlikely for both calls
04:29
<zewt>
the first call, perhaps eventually
04:30
<jwalden>
sure, the second basically never will, don't disagree there
04:30
<jwalden>
never said anything about the second :-)
04:31
<zewt>
of course, having the first be on the GPU would mean the second call would be even slower :)
04:32
<zewt>
(if it has to make a GPU to RAM transfer, instead of RAM to RAM, or even better a copy-on-write of the original)
09:37
<annevk>
Ms2ger, congrats on getting all those patches landed
09:37
<annevk>
guess isWhiteSpace should be LATER/WONTFIX
09:37
<Ms2ger>
Mm
10:13
<robman>
zewt / jwalden - wondered what your thoughts on drawImage(video)/getImageData(...) on a hidden canvas context were - does that add any performance improvements or is it effectively just the same
10:16
<robman>
or if anyone else has a view on that too 8)
14:46
<sanxiyn>
Hi!
14:46
<sanxiyn>
This may be of your interest: https://github.com/sanxiyn/csstty
14:46
<sanxiyn>
Started today.
15:02
<sanxiyn>
Hi
15:44
<zewt>
robman: don't have to even put the canvas in a document
21:23
<zewt>
must resist the urge to reply "what about triggering standards mode?"
23:57
<robman>
zewt - thanks for the tip about the DOM-less canvas - will that save much overhead?
23:57
<zewt>
compared to it being hidden? probably not (but you'd have to try it)