search

okamibl / xy-vsfilter

Automatically exported from code.google.com/p/xy-vsfilter
0 stars 0 forks source link

What Color Space xy-vsfilter Outputs by Default? #51

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Official VSFilter 2.39 always rendered subtitles in RGB and did a RGB -> YUV 
conversion when outputting YUV formats 

x264 always outputs Videos to YV12 by default so
I set xy-vsfilter > Colors > Preferences Order > moved up YV12 to Top
then in Dynamic Change i selected YV12 & clicked [Change]
this setting will make vsfilter to output to YV12 right?
i think YV12 is faster than YUY/YUV/RGB
i don't see YUV in the list except IYUV
i moved p010/p016 down since madvr doesn't support my GPU
will this setting alright?
What does xy-vsfilter output to by default?
there's no info on home page

Original issue reported on code.google.com by ved_k...@ymail.com on 8 Nov 2011 at 9:04

GoogleCodeExporter commented 8 years ago 
YUV formats supported by VSFilter = YV12, YUY2, I420, IYUV, P010, P016

As far as I can tell, the Preference Order, Dynamic Change, and Force RGB 
settings were broken in Official VSFilter 2.39, which means they are also 
broken in xy-VSFilter. Making any changes in that section probably doesn't 
affect anything, or at least I've never seen it affect anything. I'd recommend 
you don't change anything on the VSFilter Color tab. The default settings 
should be fine for everyone.

xy-VSFilter always defaults to outputting the same format as the input format. 
If something doesn't support the same format as the input, xy-VSFilter will 
attempt to do a color conversion. So yes, if your decoder outputs YV12 to 
xy-VSFilter, then xy-VSFilter will also output YV12 (if supported) to the video 
renderer or other filter. This behavior is identical to Official VSFilter 2.39.

The current exceptions are P010 and P016, which no color conversions ever 
occur. If xy-VSFilter has P010 or P016 input from the decoder, but you are not 
using madVR, xy-VSFilter fail and be unloaded. This is why you need to disable 
P010 and P016 output in your decoder (not VSFilter), if you aren't using madVR. 
This will be fixed at some point.

Original comment by cyber.sp...@gmail.com on 8 Nov 2011 at 4:27

GoogleCodeExporter commented 8 years ago 
Dynamic Change, and Force RGB settings were broken in Official VSFilter 2.39, 
which means they are also broken in xy-VSFilter. 

any chances it will be fixed in future release?

Original comment by ved_k...@ymail.com on 8 Nov 2011 at 6:12

GoogleCodeExporter commented 8 years ago 
You'll need to wait for the xy-VSFilter developer to return (unknown 
time-frame, but I expect he'll return in a month or so) to comment on that, but 
considering this isn't a regression from VSFilter 2.39 it would be very low 
priority.

Original comment by cyber.sp...@gmail.com on 9 Nov 2011 at 5:38

GoogleCodeExporter commented 8 years ago

Original comment by cyber.sp...@gmail.com on 10 Nov 2011 at 11:24