1. Create separate debug outputs and properly describe what you do since.
2. Give your thread a proper name.
Don't care about repots or logs, etc.
Looked at the end of the first file, problem there is that QProcess::splitCommand returns
Code:
-add
C:\Users\79142\AppData\Local\Temp\2023-09-25@20_42_08_9410_03.265#video:fps=60:name=2023-09-25 11:28:34 UTC:lang=
-brand
hvc1
-add
C:\Users\79142\AppData\Local\Temp\iId_1_aid_0_lang_ru_2023-09-25@20_42_08_9410_01.aac#audio:name=:lang=ru
-mpeg4
-itags
tool=Hybrid 2023.03.17.1
-tmp
C:\Users\79142\AppData\Local\Temp
-new
E:\COOKIE 111\2023-09-25@20_42_08_9410__05.mp4
for:
Code:
-add "C:\Users\79142\AppData\Local\Temp\2023-09-25@20_42_08_9410_03.265"#video:fps=60:name="2023-09-25 11:28:34 UTC":lang="" -brand hvc1 -add "C:\Users\79142\AppData\Local\Temp\iId_1_aid_0_lang_ru_2023-09-25@20_42_08_9410_01.aac"#audio:name="":lang="ru" -mpeg4 -itags tool="Hybrid 2023.03.17.1" -tmp "C:\Users\79142\AppData\Local\Temp" -new "E:\COOKIE 111\2023-09-25@20_42_08_9410__05.mp4"]
which is wrong. since it removed all quotes, but the quotes, which is wrong for
Code:
-add "C:\Users\79142\AppData\Local\Temp\2023-09-25@20_42_08_9410_03.265"#video:fps=60:name="2023-09-25 11:28:34 UTC":lang=""
which should be turned into:
Code:
-add
"C:\Users\79142\AppData\Local\Temp\2023-09-25@20_42_08_9410_03.265"#video:fps=60:name="2023-09-25 11:28:34 UTC":lang=""
=> this will take some time to work around.
launched the Hybrid
uploaded this file 3840*2160p 47.952fps = x265 main 8-bit yuv420
chose x265 and passthrough all
in the x265 tab I selected main 422 10-bit
then in the “filters-deinterlacing” tab I selected qtgmc-bob(ultrafast)
then in the "filters-Frame" tab I selected interframe-FILM(21) --- 60fps
And the separated debug outputs?
then went to the Base tab and made an output, then went to the Jobs tab and clicked Start
in Vapoursynth mode - CRASHED
in Avisynth mode freezes at 0.27%
(25.09.2023, 14:56)Selur Wrote: [ -> ]And the separated debug outputs?
these are both files from vapoursynth mode
is avisynth needed? it just got stuck while processing
(25.09.2023, 14:21)Selur Wrote: [ -> ]this will take some time to work around.
and the usual copy and paste or replace will not help?
x265 8-bit 422 running
Is it impossible to get the correct data from it? it's just a different bit depth
Quote:these are both files from vapoursynth mode
then the issue is the muxing call, not handling the stream name properly
Quote:and the usual copy and paste or replace will not help?
Copy&paste what from where to where?
No clue about your x264 issue haven't looked at it.
Since there is no separate debug output I assume there is no issue, and it doesn't work because of the bug I stated.
Send you a link to a dev version which should fix the muxing issue.
About Avisynth getting stuck: try lowering the number of threads, especially with > HD resolutions, Avisynth might get slow depending on your system and settings.
Cu Selur
Weird
didn't notice the error
about 35% processed then abruptly processed to 100% in 1 second
and when I looked at the player, approximately the first 35% is normal, but the remaining 65% is shown by the last frame of 35%
3840*2160p 24fps
x265 main 422 10-bit
auto-qtgmc-(avisynth)
interframe-FILM(21) --- 48fps
Quote:and when I looked at the player, approximately the first 35% is normal, but the remaining 65% is shown by the last frame of 35%
Sounds like:
a. buggy source
or
b. some issues with the decoding filter
or
c. some issue with the system (overclocking issues, heat, some other program interfering, energy saving,...)
Saw no errors in debug output of last link, didn't look at content of the other links.
Cu Selur