If your Vegas output is 25p, then why even mention interlacing? Why would Voukoder care what format your raw footage was? All it sees is the Vegas output.
I don't understand what you mean (my project/sources are 50i), anyway I wanna use Voukoder - FFMPEG - deinterlacing algos not Vegas ones.
Most hardware encoders won't accept interlaced Vegas output.
...that I don't need: I have interlaced INPUT and need progressive output.
Define "better control of the hardware encoder". Which encoder options, in particular?
Check yourself: https://github.com/rigaya/QSVEnc/…C_Options.en.md
Well, given that the quality of hardware encoding is not (yet) as good as software, there are several advantages in using Rigaya encoders over FFMPEG ones (that's why many - if not all - encoding-suites are adopting them):
- many specifically-optimized filters (nnedi, for example);
- better control of hw encoder;
- deeper documented;
- more fine tuned.
That said, I'm personally very interested in using (Intel) hardware acceleration for filters and/or AVC "lossless" encoding.
Just discovered the cool Lensfun library and the relative FFMPEG filter.
Support for lens correction in Voukoder (Pro ?) would be great.
OK, just retested - with same parameters (deint too) - under vegas 21 and both 13.4.1 classic + 1.7.1 connector / 1.3.0 pro worked flawlessly.
I need to deinterlace 50i content to 25p.
Of course I've tried with other pixel formats with the same result.
2024-11-09 12:53:08 (info) Dumping system information:
Architecture: x64
Vendor ID: GenuineIntel
Model name: 12th Gen Intel(R) Core(TM) i5-12500T
Frequency: 1997 MHz
Quantities:
CPU packages : 1
Physical CPUs: 6
Logical CPUs : 12
Caches:
L1:
Size : 49152
Line size : 64
Associativity: 12
Type : Data
L2:
Size : 1310720
Line size : 64
Associativity: 10
Type : Unified
L3:
Size : 18874368
Line size : 64
Associativity: 12
Type : Unified
Instruction set support:
3D-now!: false
MMX : true
SSE : true
SSE2 : true
SSE3 : true
AVX : true
Memory:
Physical:
Available: 26389880832
Total : 34033348608
Virtual:
Available: 140732656033792
Total : 140737488224256
Kernel:
Variant: Windows NT
Version: 10.0.26100 build 1882
OS:
Name : Windows NT
Full name: Microsoft Windows 11 Pro
Version : 10.0.26100 build 2033
GPUs:
No detection methods enabled
2024-11-09 12:53:08 (info) ### PHASE: PRE-INIT
2024-11-09 12:53:08 (debug) Filter config: buffer@da8753016399409d81ae6e26bd21e243=width=1920:height=1080:pix_fmt=yuv420p:time_base=1/30:pixel_aspect=1/1,w3fdif,format=pix_fmts=qsv,buffersink@afe3190ee3f4467dab9ad5afd8061a3d
2024-11-09 12:53:08 (info) ### PHASE: INIT
2024-11-09 12:53:08 (trace) Setting 'width' to value '1920'
2024-11-09 12:53:08 (trace) Setting 'height' to value '1080'
2024-11-09 12:53:08 (trace) Setting 'pix_fmt' to value 'yuv420p'
2024-11-09 12:53:08 (trace) Setting 'time_base' to value '1/30'
2024-11-09 12:53:08 (trace) Setting 'pixel_aspect' to value '1/1'
2024-11-09 12:53:08 (trace) Setting 'pix_fmts' to value 'qsv'
2024-11-09 12:53:08 (trace) detected 12 logical cores
2024-11-09 12:53:08 (trace) w:1920 h:1080 pixfmt:yuv420p tb:1/30 fr:0/1 sar:1/1 csp:unknown range:unknown
2024-11-09 12:53:08 (trace) w:iw h:ih flags:'' interl:0
2024-11-09 12:53:08 (trace) auto-inserting filter 'auto_scale_0' between the filter 'Parsed_w3fdif_1' and the filter 'Parsed_format_2'
2024-11-09 12:53:08 (trace) Impossible to convert between the formats supported by the filter 'Parsed_w3fdif_1' and the filter 'auto_scale_0'
2024-11-09 12:53:08 (error) Unable to configure filter graph.
2024-11-09 12:53:08 (error) Init phase of da875301-6399-409d-81ae-6e26bd21e243 failed!
2024-11-09 12:53:08 (error) Initialization failed: -11
----
Exported 1 frames in 0.180319 seconds.
This is a theoretical average export speed of 5.54573 fps.
IMPORTANT! Real exports using an NLE might be slower due to the NLE overhead.Done. It has exactly the same behavior/result...
...maybe it's a Vegas fault ?!?
(note: no a/v fx used on the timeline but just transitions in a multicam edit. Embedded encoders works flawlessly)
EDIT: I just realized I've posted in a wrong section, please move to Voukoder Classic Bug report.
Sorry for the delay, it's a bit busy period for me (I have to publish 2 festival videos - read 11x4-5min live videos, 1 for each band - and a live classical concert - ~130min video - by december)...
...anyway unfortunally I still can't encode using Voucoder (classic) on Vegas 22.
Render starts but immediately reaches 100% without ever finishing and/or generating any output. Anyway it don't crash.
Here's a screenshot:
Voukoder:
Hi there,
latest Vuokoder + Vegas 22 connector encoding don't start at all on my PC.
On the same machine/project works flawlessly on Vegas 21.
What can I do ?