Today, 01:20
Hybrid dev 2026.11.12.1 (portable), Windows 11 26H2 64bit; same with dev 2026.10.22.1 (installed).
Any aomenc 2-pass job (tested: constrained quality cq 28, and VBR 8000 kbit/s) hangs at the start of the 2nd pass, 0 % CPU.
With vspipe named pipes, the 1st pass main call is adjusted correctly:
aomenc --passes=2 --pass=1 ... -o NUL \\.\pipe\2026-11-12@23_25_01_5210_02_video
In the 2nd pass only the helper call is adjusted, the main call keeps stdin:
helper: vspipe "...\encodingTempSynthSkript_2026-11-12@23_25_01_5210_0.vpy" \\.\pipe\2026-11-12@23_25_01_5210_03_video --outputindex 0 -c y4m --progress
main: aomenc --passes=2 --pass=2 ... --fpf="...\test_new_1_2026-11-12@23_25_01_5210_02.stats" ... -o "...\2026-11-12@23_25_01_5210_03.ivf" -
-> vspipe: "Waiting for client to connect to named pipe..." forever, aomenc waits on stdin.
Steps: load any clip, Video: aomenc, 2pass, add to queue, start.
Debug output (this session only) attached.
Any aomenc 2-pass job (tested: constrained quality cq 28, and VBR 8000 kbit/s) hangs at the start of the 2nd pass, 0 % CPU.
With vspipe named pipes, the 1st pass main call is adjusted correctly:
aomenc --passes=2 --pass=1 ... -o NUL \\.\pipe\2026-11-12@23_25_01_5210_02_video
In the 2nd pass only the helper call is adjusted, the main call keeps stdin:
helper: vspipe "...\encodingTempSynthSkript_2026-11-12@23_25_01_5210_0.vpy" \\.\pipe\2026-11-12@23_25_01_5210_03_video --outputindex 0 -c y4m --progress
main: aomenc --passes=2 --pass=2 ... --fpf="...\test_new_1_2026-11-12@23_25_01_5210_02.stats" ... -o "...\2026-11-12@23_25_01_5210_03.ivf" -
-> vspipe: "Waiting for client to connect to named pipe..." forever, aomenc waits on stdin.
Steps: load any clip, Video: aomenc, 2pass, add to queue, start.
Debug output (this session only) attached.