Posts: 24
Threads: 3
Joined: Jul 2021
Hah! It worked! I'd read that in the other thread but didn't think to do it because the version I was using was after you updated to QT6, I guess now at least people can opt to use the vapoursynth folder from 2021.04.12.1 instead. Thanks again for your help!
Posts: 10.987
Threads: 57
Joined: May 2017
Yes,but I didn't update Qt6 for Vapoursynth at that time.
Cu Selur
Posts: 24
Threads: 3
Joined: Jul 2021
So, after attempting 2-pass average bitrate it stops after finishing the first pass. 1-pass ABR encodes to completion and works just fine.
I think this might not just be me though? Has 'Specific filesize/bitrate (2-pass)' been tested yet? I made sure to select 2 pass and not 2nd pass.
Posts: 24
Threads: 3
Joined: Jul 2021
(22.07.2021, 18:08)Selur Wrote: Yes,but I didn't update Qt6 for Vapoursynth at that time.
Cu Selur
I checked the debug log, and it looks like it either ignored or couldn't find the .stats file from the first pass, or maybe it failed to create it? I've attached it
Posts: 10.987
Threads: 57
Joined: May 2017
Yup, seems like a bug in the job creation since it creates a stats file named "C:\Users\ADMINI~1\AppData\Local\Temp\2021-07-22@15_27_31_2310_02.stats", but in the second pass it expects one named "C:\Users\Administrator\AppData\Local\Temp\Normalized cpu-used-4 aomenc with adjustments.stats".
Can't reproduce this here, when I create a 2pass encoding the pass file names are the same in both paths.
-> Need a debug output of the job creation and a small step-by-step what you do.
Cu Selur
Posts: 24
Threads: 3
Joined: Jul 2021
(23.07.2021, 05:32)Selur Wrote: Yup, seems like a bug in the job creation since it creates a stats file named "C:\Users\ADMINI~1\AppData\Local\Temp\2021-07-22@15_27_31_2310_02.stats", but in the second pass it expects one named "C:\Users\Administrator\AppData\Local\Temp\Normalized cpu-used-4 aomenc with adjustments.stats".
Can't reproduce this here, when I create a 2pass encoding the pass file names are the same in both paths.
-> Need a debug output of the job creation and a small step-by-step what you do.
Cu Selur
The steps I take are as follows:
1. Start Hybrid
2. Add video
3. Name video "Normalized cpu-used-4 aomenc with adjustments.mkv", it's my naming convention to help me remember which is which since these all go to a folder which a bunch of different test encodes. I have 'output path to source' selected if that matters
4. Apply an aomenc profile I had saved since auto-save defaults doesn't seem to be working with aomenc
5. Delete the audio stream since I don't need audio
6. Change the CPU utilization modifier from 3 to 4 as I don't want to wait too long if it does work by accident
7. Press the 'Add to queue and start queue' button
8. Wait until it finishes the first pass and then close hybrid as it stalls at this point
Posts: 10.987
Threads: 57
Joined: May 2017
will look at it this evening
Posts: 10.987
Threads: 57
Joined: May 2017
I think I found the culprit in the job creation.
Will send you a link to a dev version for testing in ~15min.
Cu Selur