cleanUpJob deletes .265 files before muxing - 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: cleanUpJob deletes .265 files before muxing (/thread-164.html)

cleanUpJob deletes .265 files before muxing - wolfhowling - 02.12.2017 Hybrid: 2017.10.05.1 The cleanUpJob deletes .265 files before muxing and the mkvmerge triggers a the error of could not open the file since it was deleted.  Only happens when patching for hdr signaling is ticked and enabling all but video format and chroma sample location underneath. I have included the report file with my configuration and the debug file as well. RE: cleanUpJob deletes .265 files before muxing - Selur - 02.12.2017 Looking at the debug output, the jobs look fine,... 1. 12_28_54_6810_01_video creates the video file (output: pp2_12_28_54_6810_01.265): "C:\PROGRA~1\Hybrid\ffmpeg.exe" -y -loglevel fatal -threads 4 -r 25 -analyzeduration 100M -probesize 100M -i "M:\CONVERTING\pp.ts" -map 0:0 -an -sn  -vsync 0 -strict -1 -pix_fmt yuv420p10le  -f yuv4mpegpipe - | "C:\PROGRA~1\Hybrid\NVEncC.exe" --y4m -i - --fps 25.000 --codec h265 --profile main10 --level 5.0 --sar 1:1 --lookahead 16 --output-depth 10 --cbrhq 16000 --max-bitrate 25000 --gop-len 0 --bframes 0 --ref 6 --mv-precision Q-pel --cu-max 32 --cu-min 8 --output "M:\CONVERTING\temp\pp2_12_28_54_6810_01.265" 2. 12_28_54_6810_02_video patches the video file (output: pp2_12_28_54_6810_12_28_54_6810_02.265) "C:\PROGRA~1\Hybrid\nvhsp.exe" -full_range tv -colorprim bt2020 -colormatrix bt2020nc -videoformat unspec -transfer smpte-st-2084 -maxcll bt2020nc -maxfall bt2020nc -chromaloc 2 -masterdisplay G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) "M:\CONVERTING\temp\pp2_12_28_54_6810_01.265" "M:\CONVERTING\temp\pp2_12_28_54_6810_12_28_54_6810_02.265" 3. 12_28_54_6810_03_cleanUp deletes the old video file (pp2_12_28_54_6810_01.265) 4. 12_28_54_6810_04_create creates the mkvmerge tag file (pp2_12_28_54_6810__04.xml) 5. 12_28_54_6810_05_muxing muxes the new video file into an mkv: (this is where the crash occurs) "C:\PROGRA~1\Hybrid\mkvmerge.exe" --ui-language en -o "M:\CONVERTING\pp2.mkv" --global-tags "M:\CONVERTING\temp\pp2_12_28_54_6810__04.xml" -d 0 --default-track 0:yes --default-duration 0:25fps --aspect-ratio-factor 0:1/1 --no-chapters --compression -1:none --forced-track 0:yes --no-audio --no-subtitles "M:\CONVERTING\temp\pp2_12_28_54_6810_12_28_54_6810_02.265" 5. 12_28_54_6810_06_cleanUp deletes the tag file (pp2_12_28_54_6810__04.xml) 12_28_54_6810_07_cleanUp deletes the video file (pp2_12_28_54_6810_12_28_54_6810_02.265) My guess is that there is some problem with the patching. One bug (missing feature) I see is that Hybrid doesn't check atm. whether nvhsp actually creates the output as it should. (fixed that here So my guess atm. is that nvhsp doesn't create the output file and Hybrid only notices it once it tries to use the output for muxing. Since I can't reproduce this here since I don't own a graphic card which can encode 10bit H.265 I need more help to track this down. -> enable "Config->Output->Container Settings->General Settings->Keep intermediate files", recreate the job, enable debug output level 9 and run the job again. Assuming still crashes, post the debug output and I can tell you the nvhsp-call Hybrid uses. You then would need to call that call in a Windows Command Prompt and tell me the output. Cu Selur RE: cleanUpJob deletes .265 files before muxing - wolfhowling - 02.12.2017 OK after doing what you suggested the error still persisted, so i look at the log since you mention nvhsp and found this error: nvhsp.exe: error: argument -maxcll: invalid int value: 'bt2020nc' base on this i looked at the settings "Light Level" under hdr signaling and found that is left as default the output code would be -maxcll 1000 -maxfall 300 but when change like i wanted to it should have been -maxcll 1000 -maxfall 400 but instead added -maxcll bt2020nc -maxfall bt2020nc which is an invalid parameter for nvhsp. You can see this in the first log include in the zip. Now since i notice that i left it as default it was able to move pass but it arrived at another problem. 2017.12.02 - 13:48:11_Windows 10-64bit_2017.10.05.1 - level 9: NVHSP output: Failed to execute script nvhsp_md_sei_v2 This error is found on the second log included in the zip. RE: cleanUpJob deletes .265 files before muxing - Selur - 02.12.2017 Well spotted. -> Will fix and send you a link to a dev version which should fix the issue in a few minutes. (simply extract the files from the download into you Hybrid folder) Cu Selur RE: cleanUpJob deletes .265 files before muxing - wolfhowling - 02.12.2017 That dev version indeed fixed the first error. The second is still present any ideas what that may be due to. I don't seem to find any reference to the script in question. NVHSP output: Failed to execute script nvhsp_md_sei_v2 Thanks It seems the problem for the second error is not Hybrid but the nvhsp program because it happens when i do the same thing  directly using that program without Hybrid, unfortunately it seems that programs is not maintain regularly because it was reported in their issue queue on may and there is not even an answer. I have no clue how else to apply those parameters which are required for HDR to actually work on my tv. RE: cleanUpJob deletes .265 files before muxing - Selur - 02.12.2017 No clue either atm. will try to have a look at it tomorrow.