Encoding crashes with SMPTE-ST-2084 settings

[rudiano]

Hi Selur, I hope you can help me here. I am trying to encode a video using X265 and the following "Signaling" settings



I need these exact settings, but when I use the SMPTE-ST-2084 settings, the encoding crashes everytime. This is what Hybrid shows:

-> Creating jobs for source 1,...
 -> Generating calls for: C:\Users\User\Desktop\TEST FILE.mp4
  adding x265 calls for source: 1
  createJobs for C:\Users\User\Desktop\TEST FILE.mp4
   creating audio subjobs,...
   creating attachment extraction subjobs
   creating video subjobs
   creating muxing subjobs
   optimizing the subJobs
 -> finished creating subjobs for current source
  added new job with id 03_58_11_4310
 -> should be there after processing: C:\Users\User\AppData\Local\Temp\iId_1_aid_0_lang_en_DELAY_-43ms_03_58_11_4310_01.aac
starting 03_58_11_4310_01_audio@03:58:11.536 - C:\Users\User\Desktop\TEST FILE.mp4
finished after 00:00:00.108
 -> should be there after processing: C:\Users\User\AppData\Local\Temp\iId_1_aid_0_lang_en_DELAY_-43ms_03_58_11_4310_02.aac
starting 03_58_11_4310_02_audio@03:58:11.660 - C:\Users\User\Desktop\TEST FILE.mp4
finished after 00:00:00.406
delete C:\Users\User\AppData\Local\Temp\iId_1_aid_0_lang_en_DELAY_-43ms_03_58_11_4310_01.aac
 -> should be there after processing: C:\Users\User\AppData\Local\Temp\03_58_11_4310_04.265
starting 03_58_11_4310_04_video@03:58:12.109 - C:\Users\User\Desktop\TEST FILE.mp4
finished after 00:00:00.065
-> 03_58_11_4310_04_video crashed: ERROR: C:\Users\User\AppData\Local\Temp\03_58_11_4310_04.265 was not created!
Aborting '03_58_11_4310_04_video' due to: ERROR: C:\Users\User\AppData\Local\Temp\03_58_11_4310_04.265 was not created!
Job 03_58_11_4310 finished!

Do you know why this is happening? I know others why use the exact same settings and they have no problems. I have tried using "prefer FFmpeg" "use gpu for decoding" "FFmpeg instead of MP4box" but it still crashes thanks

[Selur]

Using a different muxer has nothing to do with it.
You crash happens during the encoding.
Since you

• shared a part of the log which starts with:
  This log is only intended for user information. It should not be part of a bug/problem report!!
• clearly did not read the the sticky or ignored it
  

and thus I have no clue what exact settings are used for the decoding and reencoding of the source, what are the characteristics of your source,....
The encoding settings itself seem, but there might be some problem with the decoding and may be filtering.

Wild guess: In case your input was interlaced it might be related to: https://forum.selur.net/showthread.php?tid=555

Other than that provide proper details to reproduce and understand the issue, otherwise I can't help.

Cu Selur

[rudiano]

Using a different muxer has nothing to do with it.
You crash happens during the encoding.
Since you

• shared a part of the log which starts with:
  This log is only intended for user information. It should not be part of a bug/problem report!!
  
• clearly did not read the the sticky or ignored it
  

and thus I have no clue what exact settings are used for the decoding and reencoding of the source, what are the characteristics of your source,....
The encoding settings itself seem, but there might be some problem with the decoding and may be filtering.

Wild guess: In case your input was interlaced it might be related to: https://forum.selur.net/showthread.php?tid=555

Other than that provide proper details to reproduce and understand the issue, otherwise I can't help.

Cu Selur

Hi, sorry I rushed into it :-\ I have now uploaded the HybridDebugOutput.txt file for you
I used Hybrid 2018.06.18.1 Windows 64 bit

I hope this is the correct info to provide to you, thanks

[Selur]

Re-read the sticky on how to create a debug output.
Problem with your debut output is that it only contains the file analysis and nothing more.

Cu Selur

Ps.: Your debug output sadly only shows the analysis of the source not the processing of the jobs so no clue what settings you are using. -> re-read sticky

[rudiano]

Re-read the sticky on how to create a debug output.
Problem with your debut output is that it only contains the file analysis and nothing more.

Cu Selur

Ps.: Your debug output sadly only shows the analysis of the source not the processing of the jobs so no clue what settings you are using. -> re-read sticky

I have now done everything the "sticky" says to do.
1) Used the latest Hybrid (2018.08.05.1)
2) I then set Default output path
3) I then enabled Debug output
4) I did everything that caused the problem. Which was choose the input video, output video, all the settings I needed for my output and then clicked on "Add to queue and start queue"
5) Once I start the queue it stops 1 second later and on the Hybrid log it states
-> 21_24_10_3410_04_video crashed: ERROR: C:\Users\User\AppData\Local\Temp\21_24_10_3410_04.265 was not created!
Aborting '21_24_10_3410_04_video' due to: ERROR: C:\Users\User\AppData\Local\Temp\21_24_10_3410_04.265 was not created!
Job 21_24_10_3410 finished!

6) I have uploaded the HybridDebugOutput.txt file here for you.

[Selur]

Debug output still doesn't contain the job creation and job processing.
Hybrid will create the debut output inside the output path, the main point of setting a default output path is to know where that is.
If you change the output path, the location the debug output will be written to changes.

Cu Selur

[rudiano]

Debug output still doesn't contain the job creation and job processing.
Hybrid will create the debut output inside the output path, the main point of setting a default output path is to know where that is.
If you change the output path, the location the debug output will be written to changes.

Cu Selur

I just realised that a 2nd HybridDebugOutput.txt file was being created on my desktop each time I used Hybrid. So I think this is the right one for you, Ive attached it here, thanks

[Selur]

What happens if you call:

"C:\PROGRA~1\Hybrid\64bit\ffmpeg.exe" -y -threads 8 -i "C:\Users\User\Desktop\cmon.mov" -map 0:0 -an -sn   -vf zscale=rangein=tv:range=tv -pix_fmt yuv420p10le -strict -1 -vsync 0  -f yuv4mpegpipe - | "C:\PROGRA~1\Hybrid\64bit\x265.exe" --input - --output-depth 10 --y4m --profile main10 --no-high-tier --level-idc 5.1 --qg-size 8 --limit-modes --no-open-gop --opt-ref-list-length-pps --keyint 60 --min-keyint 1 --lookahead-slices 0 --bitrate 40000 --crf-min 0.00 --crf-max 0.00 --opt-qp-pps --cbqpoffs -2 --crqpoffs -2 --limit-refs 0 --ssim-rd --psy-rd 2.50 --rdoq-level 2 --psy-rdoq 10.00 --aq-mode 0 --vbv-maxrate 40000 --vbv-bufsize 40000 --hrd --aud --deblock=-1:-1 --limit-sao --repeat-headers --range limited --colorprim bt2020 --transfer smpte-st-2084 --colormatrix bt2020nc --master-display "G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,1)" --max-cll "1000,180" --hdr --output "C:\Users\User\AppData\Local\Temp\06_39_58_5510_04.265"

inside a Windows Command Prompt?

My guess atm. is that your source isn't supported by ffmpeg.

Cu Selur

[rudiano]

What happens if you call:

"C:\PROGRA~1\Hybrid\64bit\ffmpeg.exe" -y -threads 8 -i "C:\Users\User\Desktop\cmon.mov" -map 0:0 -an -sn   -vf zscale=rangein=tv:range=tv -pix_fmt yuv420p10le -strict -1 -vsync 0  -f yuv4mpegpipe - | "C:\PROGRA~1\Hybrid\64bit\x265.exe" --input - --output-depth 10 --y4m --profile main10 --no-high-tier --level-idc 5.1 --qg-size 8 --limit-modes --no-open-gop --opt-ref-list-length-pps --keyint 60 --min-keyint 1 --lookahead-slices 0 --bitrate 40000 --crf-min 0.00 --crf-max 0.00 --opt-qp-pps --cbqpoffs -2 --crqpoffs -2 --limit-refs 0 --ssim-rd --psy-rd 2.50 --rdoq-level 2 --psy-rdoq 10.00 --aq-mode 0 --vbv-maxrate 40000 --vbv-bufsize 40000 --hrd --aud --deblock=-1:-1 --limit-sao --repeat-headers --range limited --colorprim bt2020 --transfer smpte-st-2084 --colormatrix bt2020nc --master-display "G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,1)" --max-cll "1000,180" --hdr --output "C:\Users\User\AppData\Local\Temp\06_39_58_5510_04.265"

inside a Windows Command Prompt?

My guess atm. is that your source isn't supported by ffmpeg.

Cu Selur

This is what I get when I put that on Command Prompt



I dont think the problem is the source file either, I have tried the exact same settings with other video files such as MP4 with H264, MP4 with X265 and the exact same error keeps showing

[Selur]

Using:

"I:\Hybrid\64bit\ffmpeg.exe" -y -threads 8 -i "D:\TestClips&Co\files\test.avi" -map 0:0 -an -sn   -vf zscale=rangein=tv:range=tv -pix_fmt yuv420p10le -strict -1 -vsync 0  -f yuv4mpegpipe - | "i:\Hybrid\64bit\x265.exe" --input - --output-depth 10 --y4m --profile main10 --no-high-tier --level-idc 5.1 --qg-size 8 --limit-modes --no-open-gop --opt-ref-list-length-pps --keyint 60 --min-keyint 1 --lookahead-slices 0 --bitrate 40000 --crf-min 0.00 --crf-max 0.00 --opt-qp-pps --cbqpoffs -2 --crqpoffs -2 --limit-refs 0 --ssim-rd --psy-rd 2.50 --rdoq-level 2 --psy-rdoq 10.00 --aq-mode 0 --vbv-maxrate 40000 --vbv-bufsize 40000 --hrd --aud --deblock=-1:-1 --limit-sao --repeat-headers --range limited --colorprim bt2020 --colormatrix bt2020nc --master-display "G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,1)" --max-cll "1000,180" --hdr --output "d:\06_39_58_5510_04.265"

(just changed, the path to the tools and the location of the temp folder), the call works fine for me.

I get the same errors you did when the temp folder doesn't exist.
(tried different sources and couldn't reproduce the issue)

-> Does the folder: ""C:\Users\User\AppData\Local\Temp\" exist and can your user write to it?

Cu Selur