This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[BUG] х265 main 422 10-bit - Crashed
#1
3840*2160p 47.952fps < x265 main 422 10-bit + qtgmc-bob(ultrafast) + interframe-FILM(21) --- 60fps

in Avisynth mode freezes at 0.27%
in Vapoursynth mode - CRASHED

https://drive.google.com/file/d/1HotW-uK...drive_link

https://drive.google.com/file/d/1SRw7lmS...drive_link

Weird
8-bit 422 without errors, added SSIM https://drive.google.com/file/d/16kfkatP...drive_link
Reply
#2
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
-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:
-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
-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:
-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.
Reply
#3
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
Reply
#4
And the separated debug outputs?
Reply
#5
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
Reply
#6
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.
Reply
#7
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
Reply
#8
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
Reply
#9
don't understand

Test pass 2 with the same settings processed without errors

1. https://drive.google.com/file/d/13lxbTI9...drive_link

2. https://drive.google.com/file/d/13FA8m7I...drive_link

3. https://drive.google.com/file/d/1uvLz8BF...drive_link
Reply
#10
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
Reply


Forum Jump:


Users browsing this thread: 4 Guest(s)