It is explained here: https://www.voukoder.org/forum/thread/352
TL;DR: Staxrip, Hybrid & Co. are not combined with an NLE that has to render each frame first.
It is explained here: https://www.voukoder.org/forum/thread/352
TL;DR: Staxrip, Hybrid & Co. are not combined with an NLE that has to render each frame first.
Today is VEGAS day. With the latest updates of the connectors I added a "Audio only" template.
Working on it.
Edit: Please try out the latest VEGAS connectors.
Changes:
- Alpha channel templates (VEGAS 18 and 19)
- Speed improvements
Voukoder currently gets the frame data as I420 or P010 from VEGAS only (which does not have alpha channel). I would have to use A410 for this.
Unfortunately I don't have the necessary information to implement this. This is not documented in the DVR SDK.
Please provide a voukoder log file.
Yes.
Copy the directory C:\Program Files\VEGAS\VEGAS Pro 18.0\FileIO Plug-Ins\voukoderplug and the file Voukoder-x64.fio2007-config to:
C:\Program Files\VEGAS\VEGAS Pro 19.0\FileIO Plug-Ins\voukoderplug
Not in FFmpeg:
Encoder hevc_nvenc [NVIDIA NVENC hevc encoder]:
General capabilities: dr1 delay hardware
Threading capabilities: none
Supported hardware devices: cuda cuda d3d11va d3d11va
Supported pixel formats: yuv420p nv12 p010le yuv444p p016le yuv444p16le bgr0 rgb0 cuda d3d11
The thing is: It doesn't really make sense to have alpha in this kind of lossy codecs. You use h264/h265 as the final output format of your project.
When creating i.e. an overlay in AfterEffects to import this in Premiere again you would use ProRes or other lossless(y) intermediate formats. Esp. with alpha information you dont want to have any encoding artifacts.
What is your use case?
Thanks for the Piwo ![]()
To your question:
According to https://developer.nvidia.com/nvidia-video-c…k#NVENCFeatures the size limit for h264 is 4096x4096 and 8192x8192 for h265.
Yes, the format might support this but the libx265 encoder does not accept input formats with alpha channels (yuva):
Encoder libx265 [libx265 H.265 / HEVC]:
General capabilities: delay threads
Threading capabilities: other
Supported pixel formats: yuv420p yuvj420p yuv422p yuvj422p yuv444p yuvj444p gbrp yuv420p10le yuv422p10le yuv444p10le gbrp10le yuv420p12le yuv422p12le yuv444p12le gbrp12le gray gray10le gray12le
VP9 does:
So when you select "AMD H264" and you click OK it changes back to "libx264"? That sounds strange.
btw: Not every encoder has presets. Presets are usually supplied by the community.
I just noticed the alpha channel is ignored for 8 bit video in the premiere connector. not sure x265 supports alpha channel. vp9 should support it AFAIK. I'll look at it in more detail soon.
If the codec is listed in the dropdown box it is also available for encoding. Voukoder tests all possible encoders on startup.
This line:
[17:37:40] Display #0 on: Intel(R) HD Graphics 4600
means only your monitor is connected to on-board GPU and not to the AMD GPU.
Well, you'd need to use side data to set CLL and Master Display values (HDR10).
Once I have some time I'll work on a new premiere connector as this requries the 2022 SDK.
I fully agree.
(Biplanar or semi-planar means the pixel data is stored in two planes - The first contains the Y data and the second contains the interleaved UV data).
Normally you just use "bitrate" based settings if you aim for a specific file size (i.e. the file has to fit on a DVD or USB drive). If you don't care about the file size (like you want to upload the file to YouTube or similar) you are using quantizer (~ quality) based rate control mechanisms like CRF or CQ(P).
Just noticed adobe released the 2022 SDK with a bunch of new pixel formats:
PrPixelFormat_YUV_420_MPEG4_FIELD_PICTURE_BIPLANAR_10u_as16u_709 = MAKE_PIXEL_FORMAT_FOURCC('p', '0', 'i', '0'),
PrPixelFormat_YUV_420_MPEG4_FRAME_PICTURE_BIPLANAR_10u_as16u_709 = MAKE_PIXEL_FORMAT_FOURCC('p', '0', '1', '0'),
PrPixelFormat_YUV_420_MPEG4_FIELD_PICTURE_BIPLANAR_10u_as16u_709_FullRange = MAKE_PIXEL_FORMAT_FOURCC('p', '0', 'i', 'f'),
PrPixelFormat_YUV_420_MPEG4_FRAME_PICTURE_BIPLANAR_10u_as16u_709_FullRange = MAKE_PIXEL_FORMAT_FOURCC('p', '0', '1', 'f'),
PrPixelFormat_YUV_420_MPEG4_FIELD_PICTURE_BIPLANAR_10u_as16u_2020 = MAKE_PIXEL_FORMAT_FOURCC('P', '0', 'i', '0'),
PrPixelFormat_YUV_420_MPEG4_FRAME_PICTURE_BIPLANAR_10u_as16u_2020 = MAKE_PIXEL_FORMAT_FOURCC('P', '0', '1', '0'),
PrPixelFormat_YUV_420_MPEG4_FIELD_PICTURE_BIPLANAR_10u_as16u_2020_FullRange = MAKE_PIXEL_FORMAT_FOURCC('P', '0', 'i', 'f'),
PrPixelFormat_YUV_420_MPEG4_FRAME_PICTURE_BIPLANAR_10u_as16u_2020_FullRange = MAKE_PIXEL_FORMAT_FOURCC('P', '0', '1', 'f'),
PrPixelFormat_YUV_420_MPEG4_FIELD_PICTURE_BIPLANAR_10u_as16u_2020_HDR = MAKE_PIXEL_FORMAT_FOURCC('P', 'O', 'i', '0'),
PrPixelFormat_YUV_420_MPEG4_FRAME_PICTURE_BIPLANAR_10u_as16u_2020_HDR = MAKE_PIXEL_FORMAT_FOURCC('P', 'O', '1', '0'),
PrPixelFormat_YUV_420_MPEG4_FIELD_PICTURE_BIPLANAR_10u_as16u_2020_HDR_FullRange = MAKE_PIXEL_FORMAT_FOURCC('P', 'O', 'i', 'f'),
PrPixelFormat_YUV_420_MPEG4_FRAME_PICTURE_BIPLANAR_10u_as16u_2020_HDR_FullRange = MAKE_PIXEL_FORMAT_FOURCC('P', 'O', '1', 'f'),
PrPixelFormat_YUV_420_MPEG4_FIELD_PICTURE_BIPLANAR_10u_as16u_2020_HDR_HLG = MAKE_PIXEL_FORMAT_FOURCC('P', 'h', 'l', '0'),
PrPixelFormat_YUV_420_MPEG4_FRAME_PICTURE_BIPLANAR_10u_as16u_2020_HDR_HLG = MAKE_PIXEL_FORMAT_FOURCC('P', 'H', 'L', '0'),
PrPixelFormat_YUV_420_MPEG4_FIELD_PICTURE_BIPLANAR_10u_as16u_2020_HDR_HLG_FullRange = MAKE_PIXEL_FORMAT_FOURCC('P', 'h', 'l', 'f'),
PrPixelFormat_YUV_420_MPEG4_FRAME_PICTURE_BIPLANAR_10u_as16u_2020_HDR_HLG_FullRange = MAKE_PIXEL_FORMAT_FOURCC('P', 'H', 'L', 'f'),
Although the renderer returned an error when I tried to use the HLG format.
From what I've read these formats only work with effects, not with output plugins.