If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

So the question becomes.... is this relevant? I.e., how much cpu does it take to actually decode such a video compared to, say, h264? If its similar or lower, it may be useful, but if its multiples, its useless. Current video decoders won't be able to deal with it, so it will be all up to the cpu.

So the question becomes.... is this relevant? I.e., how much cpu does it take to actually decode such a video compared to, say, h264? If its similar or lower, it may be useful, but if its multiples, its useless. Current video decoders won't be able to deal with it, so it will be all up to the cpu.

It depends entirely on the bitrate/quality level and of course the decoding functions that are off-loaded to the GPU (not necessarily the video decoder ASIC built into the GPU). HQ 4K h.265 is out of the question due to bitrate and whatnot but basic 1080P files seem to be easily decoded by CPU alone on a mid-range system.

The VLC guys make some very strange, often anti-opensource decisions. Like when they made the mobile VLC for iOS first, instead of Android, which got banned by Apple, and made me very happy, because they fully deserved that one (building it for a closed OS like iOS?! What were they thinking?).

Then they ported it to Android, but before it was even fully finished, they started asking money for the "Metro version" (what the hell? Really?).

So yeah, the VLC seem to take some very counter-intuitive decisions for an open source project.

The VLC guys make some very strange, often anti-opensource decisions. Like when they made the mobile VLC for iOS first, instead of Android, which got banned by Apple, and made me very happy, because they fully deserved that one (building it for a closed OS like iOS?! What were they thinking?).

Then they ported it to Android, but before it was even fully finished, they started asking money for the "Metro version" (what the hell? Really?).

So yeah, the VLC seem to take some very counter-intuitive decisions for an open source project.

Don't be silly. It's a few lines of code if you look at the patch, it just hooks up to x265 and that's it. You don't even know if the patch was by a core developer or someone submitted it (open source, remember)?

Also the vlc guys are great. They make one of the most used players for windows, and still work hard on being cross-platform and having support for everyone, instead of just giving in and starting to cut corners and adding lots of windows-only stuff, where probably 99.9% of their userbase is.
So I wouldn't go around accusing them of not being oss-friendly.