Perhaps H.264 with a YUV 4:4:4 colorspace, assuming that the browser
supports both H.264 video and the profile that will allow YUV 4:4:4.
> I haven't tried recording a screencast with libvpx yet, and I wonder how
> well it would do. Any thoughts on this, or the best open source
> alternative?
You could do a screencast in VP8 but you might not be satisfied with the
quality due to chroma subsampling (same problem with Theora and typical
H.264).
> Flash screen video is an option, but I would prefer <video> over flash
> player.
It seems like screencasting is another problem that HTML5/video doesn't
really address.
-Mike M.
--
You received this message because you are subscribed to the Google Groups "WebM Discussion" group.
To post to this group, send email to webm-d...@webmproject.org.
To unsubscribe from this group, send email to webm-discuss...@webmproject.org.
For more options, visit this group at http://groups.google.com/a/webmproject.org/group/webm-discuss/?hl=en.
Theora supports 4:4:4 video. You can use that and be happy.
Monty
Thanks, I completely forgot about that. I just pulled down the 4:4:4
conformance sample from the Theora test suite.
Of course, in order to be useful in the context of the video tag, it needs
to be supported in browsers. Is it? An impromptu test indicates that
Firefox supports the 4:4:4 conformance sample while Google Chrome does
not.
--
-Mike Melanson
Have you thought about lossless vs lossy
flash screen video is lossless
H.264/Theora/WebM are lossy
H.264 dose have a lossless mode
tom_a_sparks
"It's a nerdy thing I like to do"
True, even though a Theora video might be 4:4:4 with very low
quantization, there is no warranty that it is losslessly encoded. However,
4:4:4 colorspace ideally mitigates some of the loss you would see with
screencast-type data.
H.264 does have a lossless mode. Whether that's supported by the target
browsers is yet another matter (similar to Firefox vs. Chrome in their
Theora/4:4:4 support).
--
-Mike Melanson
Chrome theora support can only barely be described as working. It falls
over with the slightest breeze. :(
E.g. Last time I checked, if the terver doesn't send
content-length? No video.
But we've gone way off topic now I fear.
4:4:4 is certainly a lot nicer for this sort of thing, and it's a
bit regrettable that webm doesn't have it. It's not obvious on all
signals, but some color combinations like red text on blue can look
pretty bad with 4:2:0.
I had some examples up, but I seemed to have lost them. But
basically for strong colors and small text 4:4:4 with fairly
non-trivial theora compression still looked better than lossless
4:2:0.
Are you dissing my Theora decoder?
http://multimedia.cx/eggs/optimizing-away-arrows/
:) It's all good.
> E.g. Last time I checked, if the terver doesn't send
> content-length? No video.
For the record, a 4:2:0 Theora video decoded in Chrome in my little
test; the 4:4:4 sample played blank.
> But we've gone way off topic now I fear.
>
> 4:4:4 is certainly a lot nicer for this sort of thing, and it's a
> bit regrettable that webm doesn't have it. It's not obvious on all
> signals, but some color combinations like red text on blue can look
> pretty bad with 4:2:0.
>
> I had some examples up, but I seemed to have lost them. But
> basically for strong colors and small text 4:4:4 with fairly
> non-trivial theora compression still looked better than lossless
> 4:2:0.
Just curious, what would be necessary to extend VP8 to cover 4:4:4?
Perhaps apply the Y coding method to each of the C planes (and upgrading
the bitstream format, of course)?
--
-Mike Melanson
http://media.basilgohar.com/samples/screencast/screencap-2010-12-18_11:47:08.webm
I originally captured it losslessly (straight to a y4m file, I think),
but I archived it as an FFV1. My encoding command line looked like this:
ffmpeg -i screencap-2010-12-18_11:47:08-ffv1.mkv -f yuv4mpegpipe -
2>/dev/null | vpxenc --output=screencap-2010-12-18_11:47:08.webm --best
--verbose --threads=4 --lag-in-frames=25 --end-usage=vbr
--target-bitrate=1000 --min-q=0 --max-q=63 --kf-max-dist=250
--auto-alt-ref=1 --tune=ssim -
Note that, because this is single pass, some of those options may not
actually have any effect.
The resulting file encoded to 423.3kbits/s with the above settings.
Thanks for posting that WebM screencast, Basil. I agree with your assessment that subsampled chroma is not necessarily a problem for screencasts. I'll have to try it out on some stock charts to see the effect with higher contrast content, but I am hopeful of the outcome.