[BUG] х265 main 422 10-bit - Crashed - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: [BUG] х265 main 422 10-bit - Crashed (/thread-3414.html) |
х265 main 422 10-bit - Crashed - humanoid86 - 25.09.2023 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-uKqDLu8uzWjuxtIRLdnVKnGUfy4/view?usp=drive_link https://drive.google.com/file/d/1SRw7lmSMghHANFh8fm9UFvbwZcsRluzk/view?usp=drive_link Weird 8-bit 422 without errors, added SSIM https://drive.google.com/file/d/16kfkatPIzkyB3S4Sq_Oo6VPYvoYtvGiK/view?usp=drive_link RE: Crashed - Selur - 25.09.2023 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 -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"] -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="" -add RE: Crashed - humanoid86 - 25.09.2023 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 RE: Crashed - Selur - 25.09.2023 And the separated debug outputs? RE: Crashed - humanoid86 - 25.09.2023 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 RE: х265 main 422 10-bit - Crashed - Selur - 25.09.2023 Quote:these are both files from vapoursynth modethen 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. RE: х265 main 422 10-bit - Crashed - Selur - 25.09.2023 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 RE: х265 main 422 10-bit - Crashed - humanoid86 - 26.09.2023 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 RE: х265 main 422 10-bit - Crashed - humanoid86 - 26.09.2023 don't understand Test pass 2 with the same settings processed without errors 1. https://drive.google.com/file/d/13lxbTI9E8K5No-_BNfMGZpYjSZdJVeUP/view?usp=drive_link 2. https://drive.google.com/file/d/13FA8m7IlEPb-mjUD_o7PgL1KU39SoyQA/view?usp=drive_link 3. https://drive.google.com/file/d/1uvLz8BFyKyToFww0j5sATiqjUmivii_w/view?usp=drive_link RE: х265 main 422 10-bit - Crashed - Selur - 26.09.2023 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 |