Thread: Avisynth+
View Single Post
Old 6th July 2016, 19:17   #2020  |  Link
ultim
AVS+ Dev
 
ultim's Avatar
 
Join Date: Aug 2013
Posts: 359
Quote:
Originally Posted by Wilbert View Post
feature requests:

1) ConvertToYUV400 (same naming as ConvertYUV444, instead of ConvertToY16/32),
2a) PRGB colorformats (for the new bit-depths)
2b) ConvertToPRGB (planar RGB: PRGB <-> YUV420/YUV422 via in between format YUV444),
3) script functions which give the bit-depth.
1) There is already ConvertToY() (without bit depth specification), but ConvertToYUV400() can be added as an alias for consistency with the other functions.
2) There are multiple RGB and multiple YUV color spaces, so at least >1 need to be supported to give correct results in most cases, if one wants to convert RGB<->YUV. When and if at all this will be done is better asked to pinterf, unless someone else steps up to implement it.
3) Sure.

EDIT:
Quote:
Originally Posted by Wilbert View Post
Question: what happens when doing for example ConvertToYV12(available options) on a 16/32 bit YUV source? Is that implemented already?
IMHO those functions with exact bit depth specification should stay true to their name. For me it would be weird and unexpected if ConvertToYV24() produces float pixels at one point, since that is not YV24. So my stand on this is that ConvertToYV24() should be a shortcut for ConvertToYUV444().ConvertTo8Bits() (and similarly for other old functions).
__________________
AviSynth+

Last edited by ultim; 6th July 2016 at 19:24.
ultim is offline