|
|
| plamen |
| Posted: May 4 2011, 04:00 PM |
 |
|
Advanced Member
Group: Members
Posts: 47
Member No.: 23938
Joined: 26-July 08
|
| QUOTE (jpsdr @ May 4 2011, 07:36 AM) | | QUOTE (plamen @ May 3 2011, 01:44 PM) | | Where to place the content of this archive? In "Plugins" folder? |
Yes, just put the .vdf file in the "plugins" folder.
Choose the one according your CPU and configuration. |
Thank you, but what to do with the .dll file? |
|
| -vdub- |
| Posted: May 4 2011, 09:59 PM |
|
|
Advanced Member
Group: Members
Posts: 613
Member No.: 27087
Joined: 24-February 10
|
Maybe the .dll is an avisynth plugin filter ! |
|
| jpsdr |
| Posted: May 5 2011, 08:46 AM |
|
|
Advanced Member
Group: Members
Posts: 335
Member No.: 20490
Joined: 23-December 06
|
Yes, the .dll is an avisynth plugin, so, don't care about it for VDub.
About detecting source color space : As far as i know, this information is not avaible in VDub, and would nevertheless has to be put by the user.
So, when you select and configure filter, color space settings are default values. |
|
| -vdub- |
| Posted: May 5 2011, 02:46 PM |
|
|
Advanced Member
Group: Members
Posts: 613
Member No.: 27087
Joined: 24-February 10
|
Really need to know some software for could get it correct info from source video for decompression. As with what ale5000 was talking about above for virtualdub, so far found no such software, guessing they will be somewhere.
| QUOTE (ale5000 @ May 2 2011, 12:07 PM) | Go on Video => Color Depth
Select in "Decompression format" inside "Other..." the format+color matrix of your input video (or Autoselect that may works fine but not always).
Then select the destination format+color matrix in "Output format to compressor/display" inside "Other...". |
|
|
| jpsdr |
| Posted: May 6 2011, 08:54 AM |
|
|
Advanced Member
Group: Members
Posts: 335
Member No.: 20490
Joined: 23-December 06
|
For what i know, the only avaible information for filters is the following :
| CODE |
namespace nsVDXPixmap {
enum VDXPixmapFormat {
kPixFormat_Null = 0,
kPixFormat_XRGB1555 = 5,
kPixFormat_RGB565 = 6,
kPixFormat_RGB888 = 7,
kPixFormat_XRGB8888 = 8,
kPixFormat_Y8 = 9,
kPixFormat_YUV422_UYVY = 10,
kPixFormat_YUV422_YUYV = 11,
kPixFormat_YUV444_Planar = 13,
kPixFormat_YUV422_Planar = 14,
kPixFormat_YUV420_Planar = 15,
kPixFormat_YUV411_Planar = 16,
kPixFormat_YUV410_Planar = 17
};
};
|
|
|
| -vdub- |
| Posted: May 6 2011, 02:09 PM |
|
|
Advanced Member
Group: Members
Posts: 613
Member No.: 27087
Joined: 24-February 10
|
Virtualdub Select:
Video > Video Color Depth > Other
|
|
| phaeron |
| Posted: May 7 2011, 10:00 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
All of the YCbCr formats in the list that jpsdr posted are Rec. 601 formats. The latest versions of VirtualDub support Rec. 709 as well, but the format constants aren't documented in the Plugin SDK yet.
Use the "alias format" filter to swap interpretation from one color space to another. The filter chain will then convert from Rec. 709 to Rec. 601 or RGB as needed. Note that VirtualDub will not let you masquerade Rec. 709 as YUY2 or YV12 to a codec; you will need to alias it back to Rec. 601 if your codec uses that particular little lie. You can, however, send it out directly as HDYC if the codec supports it, which is a Rec. 709 format.
|
|
| jpsdr |
| Posted: May 16 2011, 02:19 PM |
|
|
Advanced Member
Group: Members
Posts: 335
Member No.: 20490
Joined: 23-December 06
|
Can i replace by the following in the vdplugin.h of SDK 1.1 without risk ? (Found in 1.10.0 source code)
| CODE |
namespace nsVDXPixmap {
enum VDXPixmapFormat {
kPixFormat_Null = 0,
kPixFormat_XRGB1555 = 5,
kPixFormat_RGB565 = 6,
kPixFormat_RGB888 = 7,
kPixFormat_XRGB8888 = 8,
kPixFormat_Y8 = 9,
kPixFormat_YUV422_UYVY = 10,
kPixFormat_YUV422_YUYV = 11,
kPixFormat_YUV444_Planar = 13,
kPixFormat_YUV422_Planar = 14,
kPixFormat_YUV420_Planar = 15,
kPixFormat_YUV411_Planar = 16,
kPixFormat_YUV410_Planar = 17,
kPixFormat_YUV422_UYVY_709 = 22,
kPixFormat_Y8_FR = 24,
kPixFormat_YUV422_YUYV_709 = 25,
kPixFormat_YUV444_Planar_709 = 26,
kPixFormat_YUV422_Planar_709 = 27,
kPixFormat_YUV420_Planar_709 = 28,
kPixFormat_YUV411_Planar_709 = 29,
kPixFormat_YUV410_Planar_709 = 30,
kPixFormat_YUV422_UYVY_FR = 31,
kPixFormat_YUV422_YUYV_FR = 32,
kPixFormat_YUV444_Planar_FR = 33,
kPixFormat_YUV422_Planar_FR = 34,
kPixFormat_YUV420_Planar_FR = 35,
kPixFormat_YUV411_Planar_FR = 36,
kPixFormat_YUV410_Planar_FR = 37,
kPixFormat_YUV422_UYVY_709_FR = 38,
kPixFormat_YUV422_YUYV_709_FR = 39,
kPixFormat_YUV444_Planar_709_FR = 40,
kPixFormat_YUV422_Planar_709_FR = 41,
kPixFormat_YUV420_Planar_709_FR = 42,
kPixFormat_YUV411_Planar_709_FR = 43,
kPixFormat_YUV410_Planar_709_FR = 44,
kPixFormat_YUV420i_Planar = 45,
kPixFormat_YUV420i_Planar_FR = 46,
kPixFormat_YUV420i_Planar_709 = 47,
kPixFormat_YUV420i_Planar_709_FR = 48,
kPixFormat_YUV420it_Planar = 49,
kPixFormat_YUV420it_Planar_FR = 50,
kPixFormat_YUV420it_Planar_709 = 51,
kPixFormat_YUV420it_Planar_709_FR = 52,
kPixFormat_YUV420ib_Planar = 53,
kPixFormat_YUV420ib_Planar_FR = 54,
kPixFormat_YUV420ib_Planar_709 = 55,
kPixFormat_YUV420ib_Planar_709_FR = 56,
kPixFormat_VDXA_RGB = 0x10001,
kPixFormat_VDXA_YUV = 0x10002
};
};
|
Is FR full range ?
i it ib .. what does it mean ?
VD 1.10.1 (latest test version).
Is it normal to have YUV444 video if i select YUV420 interlaced in input ?
Wich finaly render some of these variables useless (kPixFormat_YUV420i_Planar for exemple) for filters, if video is converted. |
|
| phaeron |
| Posted: May 18 2011, 05:02 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
These constants have been in place for a while, so yes, you can consider them stable. They will be documented in the next version of the plugin SDK.
The "i" stands for interlaced. Very few of the built-in filters will take this format, so right now you'll get a conversion to 4:4:4 most of the time. The "null transform" filter is an example of one that doesn't force such a conversion.
The "it" and "ib" formats stand for interlaced top field and interlaced bottom field. They are the result of extracting even or odd fields from the interlaced formats. Although the filter system knows about these formats, the filters generally don't use them yet; the display system does when displaying interlaced video.
FR does indeed stand for full range: 0-255 in both luma and chroma. The 601-FR formats match the color space used by JPEG JFIF. The Y8_FR format is a simple grayscale ramp and is mapped to BMP as an 8-bit grayscale palette.
The VDXA formats are for 3D acceleration. You should not use or accept them unless your filter actually supports the RunAccel() entry point.
|
|
| jpsdr |
| Posted: May 18 2011, 07:44 AM |
|
|
Advanced Member
Group: Members
Posts: 335
Member No.: 20490
Joined: 23-December 06
|
Thanks for your answer.
| QUOTE (phaeron @ May 18 2011, 05:02 AM) | The "i" stands for interlaced. Very few of the built-in filters will take this format, so right now you'll get a conversion to 4:4:4 most of the time. The "null transform" filter is an example of one that doesn't force such a conversion.
|
That's strange.
If i'm doing the following :
Select color depth YCbCr 4:2:0 Limited interlaced for both input and output.
Create a video test RGB color cube TFF (or BFF).
Add the "null transform" filter : It shows me 4:4:4 for both input and output...
This means color space input could be detected, assuming user put the exact selection in input...
My choice in my filters is (and will be) to leave the options to the user. |
|
| phaeron |
| Posted: May 21 2011, 08:10 PM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
Oops, sorry... this works in my dev tree. It doesn't work in 1.10.0.
|
|
| jpsdr |
| Posted: May 22 2011, 09:39 AM |
|
|
Advanced Member
Group: Members
Posts: 335
Member No.: 20490
Joined: 23-December 06
|
Ok.
Just to say, i'm using 1.10.1-test7, not 1.10.0, but, maybe it's in the same situation. |
|
| jpsdr |
| Posted: May 29 2011, 07:50 AM |
|
|
Advanced Member
Group: Members
Posts: 335
Member No.: 20490
Joined: 23-December 06
|
| QUOTE (phaeron @ May 21 2011, 08:10 PM) | | Oops, sorry... this works in my dev tree. It doesn't work in 1.10.0. |
What about the last 1.10.1-test8 you just posted ? |
|
