View Full Version : StaxRip 2.0 Support Thread
Revan654
30th October 2018, 20:06
https://i.imgur.com/eRBao8M.png
StaxRip is a video encoding app for Windows with a unrivaled feature set and usability.
- Support for countless formats and tools
- Hardware encoding for AMD, Intel and NVIDIA
- AviSynth and VapourSynth code editor
- Cut/Trim/Edit feature, for MKV output no re-encoding required
- Minimal user interaction required due to rich configuration and automation features
- Pixel perfect High DPI scaling
- HDR10 & HLG Fully Supported
- HDR Metadata Injectors
- Thumbnail, Gif & aPNG Creators
- Massive Libiary of Filters for Both Avisynth+ & VapourSynth
- AV1 Supported in the Form of Rav1e Encoder
Docs: https://staxrip2.readthedocs.io/en/latest/index.html
Complete Release: https://github.com/Revan654/staxrip/releases/latest
You Also Can Grab New Builds at the Pipeline: Here (https://ci.appveyor.com/project/Revan654/staxrip)
https://ci.appveyor.com/api/projects/status/j0alakgd5ahkyjmw?svg=true
The Pipeline Builds Only contain the core Files and None of the External Files.
-QfG-
31st October 2018, 14:22
Removed MediaInfo 18.08.1 Due to Bugs it contains and Re-Added MediaInfo 18.05.
Thanks for this :). For me, the best AVS based encoding GUI.
NikosD
31st October 2018, 14:31
Excellent!
I'll try it using it with QSVEncC.
Get a good start for your new project.
NikosD
31st October 2018, 14:36
Latest Release: https://github.com/Revan654/staxrip/releases/latest
I may be blind, but I only see v1.9.0.0 of Staxrip
-QfG-
31st October 2018, 14:42
I may be blind, but I only see v1.9.0.0 of Staxrip
https://github.com/Revan654/staxrip/releases/tag/2.0.0.0
Zetti
31st October 2018, 14:45
Github Release Page: https://github.com/Revan654/staxrip/releases
NikosD
31st October 2018, 15:47
Thank you all for the path of the latest version.
With my Skylake Core i5 6500, Win 10 x64 iGPU v6326, it seems that QSVEnc HW decoding doesn't work for any source codec (MPEG2, VC-1, H.264)
QSVEnc complains regarding missing DLL files which they are all present inside the app's folder.
Regarding this issue, I maybe have to check it out with rigaya.
Also when I select "Execute command" from the drop down menu inside StaxRip, depending of the path of the file on the disk, the CLI app crashes.
But the same process during normal dialogue of the StaxRip app works fine.
I'm not sure if this is a limitation of the CLI app or of the GUI.
Revan654
31st October 2018, 17:41
I may be blind, but I only see v1.9.0.0 of Staxrip
2.0 is only Beta, Final is not ready yet. Only Stable Releases Are Shown.
Revan654
31st October 2018, 17:44
Thank you all for the path of the latest version.
With my Skylake Core i5 6500, Win 10 x64 iGPU v6326, it seems that QSVEnc HW decoding doesn't work for any source codec (MPEG2, VC-1, H.264)
QSVEnc complains regarding missing DLL files which they are all present inside the app's folder.
Regarding this issue, I maybe have to check it out with rigaya.
Also when I select "Execute command" from the drop down menu inside StaxRip, depending of the path of the file on the disk, the CLI app crashes.
But the same process during normal dialogue of the StaxRip app works fine.
I'm not sure if this is a limitation of the CLI app or of the GUI.
rigaya has a habit of leaving out import dll files, it happened with the last two releases too. My coding PC doesn't have intel encoder support so I have no way to test the exe file.
IbrahimKh
3rd November 2018, 18:06
Please add HDR to SDR script built in :)
Revan654
3rd November 2018, 19:59
Please add HDR to SDR script built in :)
One already exists, two if you add in 3dlut function.
shodan5000
3rd November 2018, 21:42
One already exists, two if you add in 3dlut function.
Apologies, would you mind explaining the simplest approach to doing HDR to SDR using Staxrip? New to HDR content and it would be appreciated.
Revan654
4th November 2018, 00:46
Simple ha, HDR is very complex. There are help files for most filters.
Apps -> Manage -> Avisynth -> DGTonemap -> Help
JKyle
5th November 2018, 08:15
Hi.
Here's my system information and error log:
-------------------------- System Environment --------------------------
StaxRip : 2.0.0.0
Windows : Windows 10 Home 1803
Language : English (United States)
CPU : Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz
GPU : NVIDIA GeForce GTX 1060 with Max-Q Design, Intel(R) HD Graphics 630
Memory : 8 GB
Resolution : 2560 x 1080
DPI : 120
...
---------------- Error Video encoding using NVEnc 4.20 ----------------
Video encoding using NVEnc 4.20 failed with exit code: 1 (0x1)
The exit code might be a system error code: STATUS_WAIT_1
The exit code might be a system error code: Incorrect function.
------------------- Video encoding using NVEnc 4.20 -------------------
C:\Utilities\StaxRip\Apps\NVEnc\NVEncC64.exe --avhw cuda --vbrhq 2000 --codec h265 --preset quality --aq --vpp-deband -i "C:\Work\input.mkv" -o "C:\Work\input_temp\input_new_out.h265"
avcuvid: avcodec: failed to load dlls.
avcuvid: please make sure "avcodec-58.dll", "avformat-58.dll",
avcuvid: "avutil-56.dll", "avfilter-7.dll", "swresample-3.dll"
avcuvid: is installed in your system.
Failed to open input file.
Start: 10:45:09 PM
End: 10:45:15 PM
Duration: 00:00:05
...
The dll files are put in the same folder where NVEncC64.exe is.
This may sound like a very basic question but what extra steps do I need to take to avoid this error? I just copied the files in the released 7z file to my own specific folder and that was it. For a reference, I have no problem encoding a file using x264 or x265.
BTW, I run into the same 'missing dll files' error when I try to use qaac for audio encoding.
Revan654
6th November 2018, 22:59
Hi.
Here's my system information and error log:
-------------------------- System Environment --------------------------
StaxRip : 2.0.0.0
Windows : Windows 10 Home 1803
Language : English (United States)
CPU : Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz
GPU : NVIDIA GeForce GTX 1060 with Max-Q Design, Intel(R) HD Graphics 630
Memory : 8 GB
Resolution : 2560 x 1080
DPI : 120
...
---------------- Error Video encoding using NVEnc 4.20 ----------------
Video encoding using NVEnc 4.20 failed with exit code: 1 (0x1)
The exit code might be a system error code: STATUS_WAIT_1
The exit code might be a system error code: Incorrect function.
------------------- Video encoding using NVEnc 4.20 -------------------
C:\Utilities\StaxRip\Apps\NVEnc\NVEncC64.exe --avhw cuda --vbrhq 2000 --codec h265 --preset quality --aq --vpp-deband -i "C:\Work\input.mkv" -o "C:\Work\input_temp\input_new_out.h265"
avcuvid: avcodec: failed to load dlls.
avcuvid: please make sure "avcodec-58.dll", "avformat-58.dll",
avcuvid: "avutil-56.dll", "avfilter-7.dll", "swresample-3.dll"
avcuvid: is installed in your system.
Failed to open input file.
Start: 10:45:09 PM
End: 10:45:15 PM
Duration: 00:00:05
...
The dll files are put in the same folder where NVEncC64.exe is.
This may sound like a very basic question but what extra steps do I need to take to avoid this error? I just copied the files in the released 7z file to my own specific folder and that was it. For a reference, I have no problem encoding a file using x264 or x265.
BTW, I run into the same 'missing dll files' error when I try to use qaac for audio encoding.
The Creator of NVEnc has a Habit of leaving out required dll files. Just download the Shared version of FFMPEG and replaced all the dll with those.
I don't have a Nvidia Card on this PC so I can't test if give Encoder works with a given Card.
JKyle
7th November 2018, 19:04
The Creator of NVEnc has a Habit of leaving out required dll files. Just download the Shared version of FFMPEG and replaced all the dll with those.
I don't have a Nvidia Card on this PC so I can't test if give Encoder works with a given Card.
I think I figured out the cause of the NVEnc error. It happens only when I choose 'NVEnc Cuda' as a decoder. 'NVEnc Native' and 'AviSynth/VapourSynth' do not cause any errors, although 'AviSynth/VapourSynth' imposes much more work load on CPU than 'NVEnc Native' does, which is quite natural considering the properties of the scripts.
BTW, I looked up the qaac issue on your GitHub site, and found your solution on the issue track. I applied it and the issue is fixed. Thank you very much. :)
NikosD
7th November 2018, 21:12
...although 'AviSynth/VapourSynth' imposes much more work load on CPU than 'NVEnc Native' does, which is quite natural considering the properties of the scripts. Avisynth & VapourSynth means CPU decoding.
NVEnc native means HW DXVA2 decoding, which means < 5% CPU usage.
steelfatboy
9th November 2018, 17:12
Forgive my noobishness, but just starting to get into 4k encoding. From your description (HDR Metadata Injectors), does that mean if I encode using nvenc h.265 and output to mkv, it can retain the HDR10 metadata tag? I've been messing around with the main version of StaxRip and the files I've been producing contain the correct color info, such as color primaries, maximum content light level, etc. But the HDR10 tag is missing.
Revan654
10th November 2018, 16:58
Forgive my noobishness, but just starting to get into 4k encoding. From your description (HDR Metadata Injectors), does that mean if I encode using nvenc h.265 and output to mkv, it can retain the HDR10 metadata tag? I've been messing around with the main version of StaxRip and the files I've been producing contain the correct color info, such as color primaries, maximum content light level, etc. But the HDR10 tag is missing.
It means it adds the remaining Metadata for HDR10 to be fully up to Spec to the latest HDR10 standards.
If the HDR10 is missing your missing something in the basic Encoding settings in x265. My guess is the no-open-gop.
FYI 4K != HDR.
Revan654
10th November 2018, 18:38
x265 VUI Transfer Options: https://x265.readthedocs.io/en/default/cli.html#cmdoption-transfer
This is why VUI Import Keeps Breaking:
https://i.imgur.com/joRwG8U.png
https://i.imgur.com/VOhEzrK.png
MediaInfo keeps changing the Names to Names that doesn't even exist from the Transfer list. There not Such Transfer called HLG, It's called arib-std-b67, At lease use the Proper Name. This forces me to build even more functions on top other other functions that wouldn't even be needed if they just use the correct names.
Plus half the Metadata is missing from HLG file.
Atlease FFProbe Got it Right: Stream #0:0[0x1c9]: Video: hevc (Main 10) ([36][0][0][0] / 0x0024), yuv420p10le(tv, bt2020nc/bt2020/arib-std-b67)
steelfatboy
11th November 2018, 07:00
It means it adds the remaining Metadata for HDR10 to be fully up to Spec to the latest HDR10 standards.
If the HDR10 is missing your missing something in the basic Encoding settings in x265. My guess is the no-open-gop.
FYI 4K != HDR.
Thanks for the info! Yes the original mkv has HDR10 tag, so it's not just a 4K file. I'm using --strict-gop option, would that be the same? Or is the issue that I'm using nvenc h.265 rather than regular x265? My nvidia card encodes very fast and the quality is great with the right settings.
DaMacFunkin
11th November 2018, 12:24
Hi, Can anybody help with what might be wrong here?
Thank you.
-------------------------- System Environment --------------------------
StaxRip : 1.9.0.0
Windows : Windows 10 Home 1803
Language : English (United Kingdom)
CPU : Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
GPU : Intel(R) HD Graphics 630, NVIDIA GeForce GTX 1060
Memory : 1 GB
Resolution : 1920 x 1080
DPI : 96
------------------------ MediaInfo Source File ------------------------
E:\Video\John_Wick_Chapter_2\John_Wick_Chapter_2_t00.mkv
General
Complete name : E:\Video\John_Wick_Chapter_2\John_Wick_Chapter_2_t00.mkv
Format : Matroska
Format version : Version 2
File size : 71.2 GiB
Duration : 2 h 2 min
Overall bit rate mode : Variable
Overall bit rate : 83.2 Mb/s
Movie name : John Wick: Chapter 2
Encoded date : UTC 2018-11-11 08:26:08
Writing application : MakeMKV v1.12.3 win(x64-release)
Writing library : libmakemkv v1.12.3 (1.3.5/1.4.7) win(x64-release)
Video
ID : 1
ID in the original source medium : 4113 (0x1011)
Format : HEVC
Format/Info : High Efficiency Video Coding
Commercial name : HDR10
Format profile : Main 10@L5.1@High
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 2 min
Bit rate : 77.9 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.392
Stream size : 66.6 GiB (94%)
Writing library : ATEME Titan File 3.7.9 (4.7.9.0)
Language : English
Default : No
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Original source medium : Blu-ray
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0000 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Level : 510 cd/m2
Audio #1
ID : 2
ID in the original source medium : 4352 (0x1100)
Format : TrueHD
Format profile : TrueHD+Atmos / TrueHD
Codec ID : A_TRUEHD
Duration : 2 h 2 min
Bit rate mode : Variable
Bit rate : 4 603 kb/s
Maximum bit rate : 7 806 kb/s
Channel(s) : Object Based / 8 channels
Channel positions : Object Based / Front: L C R, Side: L R, Back: L R, LFE
Sampling rate : / 48.0 kHz
Frame rate : 1 200.000 FPS (40 SPF)
Bit depth : 24 bits
Compression mode : Lossless
Stream size : 3.93 GiB (6%)
Title : Surround 7.1
Language : English
Default : Yes
Forced : No
Original source medium : Blu-ray
Audio #2
ID : 3
ID in the original source medium : 4352 (0x1100)
Format : AC-3
Format/Info : Audio Coding 3
Codec ID : A_AC3
Duration : 2 h 2 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 560 MiB (1%)
Title : Surround 5.1
Language : English
Service kind : Complete Main
Default : No
Forced : No
Original source medium : Blu-ray
Text #1
ID : 4
ID in the original source medium : 4768 (0x12A0)
Format : PGS
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 1 h 49 min
Bit rate : 13.9 kb/s
Count of elements : 1338
Stream size : 11.0 MiB (0%)
Language : English
Default : No
Forced : No
Original source medium : Blu-ray
Text #2
ID : 6
ID in the original source medium : 4769 (0x12A1)
Format : PGS
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 1 h 54 min
Bit rate : 17.8 kb/s
Count of elements : 1862
Stream size : 14.5 MiB (0%)
Language : English
Default : No
Forced : No
Original source medium : Blu-ray
Menu
00 : 00:00.000 : en:Chapter 01
00 : 06:31.307 : en:Chapter 02
00 : 16:57.933 : en:Chapter 03
00 : 26:35.385 : en:Chapter 04
00 : 34:38.034 : en:Chapter 05
00 : 42:07.816 : en:Chapter 06
00 : 48:07.050 : en:Chapter 07
00 : 56:41.648 : en:Chapter 08
01 : 01:42.782 : en:Chapter 09
01 : 10:27.473 : en:Chapter 10
01 : 17:15.839 : en:Chapter 11
01 : 24:22.557 : en:Chapter 12
01 : 32:11.192 : en:Chapter 13
01 : 40:01.328 : en:Chapter 14
01 : 46:34.763 : en:Chapter 15
01 : 54:01.042 : en:Chapter 16
02 : 02:22.251 : en:Chapter 17
------------------ Demux MKV using mkvextract 26.0.0 ------------------
"D:\Encode Plus\StaxRip\Apps\MKVToolNix\mkvextract.exe" E:\Video\John_Wick_Chapter_2\John_Wick_Chapter_2_t00.mkv tracks 3:"D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00 ID4 English.sup" 4:"D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00 ID5 English.sup" 1:"D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00 ID1 English.thd" 2:"D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00 ID2 English.ac3" --ui-language en
Extracting track 1 with the CodecID 'A_TRUEHD' to the file 'D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00 ID1 English.thd'. Container format: TrueHD
Extracting track 2 with the CodecID 'A_AC3' to the file 'D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00 ID2 English.ac3'. Container format: Dolby Digital (AC-3)
Extracting track 3 with the CodecID 'S_HDMV/PGS' to the file 'D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00 ID4 English.sup'. Container format: SUP
Extracting track 4 with the CodecID 'S_HDMV/PGS' to the file 'D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00 ID5 English.sup'. Container format: SUP
Start: 10:46:58
End: 11:01:05
Duration: 00:14:07
General
Complete name : D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00 ID1 English.thd
Format : TrueHD
File size : 3.93 GiB
Overall bit rate mode : Variable
Audio
Format : TrueHD
Format profile : TrueHD+Atmos / TrueHD
Bit rate mode : Variable
Maximum bit rate : 7 806 kb/s
Channel(s) : Object Based / 8 channels
Channel positions : Object Based / Front: L C R, Side: L R, Back: L R, LFE
Sampling rate : / 48.0 kHz
Frame rate : 1 200.000 FPS (40 SPF)
Compression mode : Lossless
General
Complete name : D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00 ID2 English.ac3
Format : AC-3
Format/Info : Audio Coding 3
File size : 560 MiB
Duration : 2 h 2 min
Overall bit rate mode : Constant
Overall bit rate : 640 kb/s
Audio
Format : AC-3
Format/Info : Audio Coding 3
Duration : 2 h 2 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 560 MiB (100%)
Service kind : Complete Main
-------------- Demux xml chapters using mkvextract 26.0.0 --------------
"D:\Encode Plus\StaxRip\Apps\MKVToolNix\mkvextract.exe" E:\Video\John_Wick_Chapter_2\John_Wick_Chapter_2_t00.mkv chapters D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00_chapters.xml
File 'E:\Video\John_Wick_Chapter_2\John_Wick_Chapter_2_t00.mkv': container: Matroska
Track ID 0: video (MPEG-H/HEVC/h.265)
Track ID 1: audio (TrueHD Atmos)
Track ID 2: audio (AC-3)
Track ID 3: subtitles (HDMV PGS)
Track ID 4: subtitles (HDMV PGS)
Chapters: 17 entries
Start: 11:01:05
End: 11:01:05
Duration: 00:00:00
-------------- Demux ogg chapters using mkvextract 26.0.0 --------------
"D:\Encode Plus\StaxRip\Apps\MKVToolNix\mkvextract.exe" E:\Video\John_Wick_Chapter_2\John_Wick_Chapter_2_t00.mkv chapters D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00_chapters.txt --simple
File 'E:\Video\John_Wick_Chapter_2\John_Wick_Chapter_2_t00.mkv': container: Matroska
Track ID 0: video (MPEG-H/HEVC/h.265)
Track ID 1: audio (TrueHD Atmos)
Track ID 2: audio (AC-3)
Track ID 3: subtitles (HDMV PGS)
Track ID 4: subtitles (HDMV PGS)
Chapters: 17 entries
Start: 11:01:05
End: 11:01:05
Duration: 00:00:00
----------------------- Indexing using ffmsindex -----------------------
"D:\Encode Plus\StaxRip\Apps\Plugins\both\ffms2\ffmsindex.exe" E:\Video\John_Wick_Chapter_2\John_Wick_Chapter_2_t00.mkv D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00.ffindex
Writing index... done.
Start: 11:01:06
End: 11:15:08
Duration: 00:14:01
--------------------------- AviSynth Script ---------------------------
LoadCPlugin("D:\Encode Plus\StaxRip\Apps\Plugins\both\ffms2\ffms2.dll")
FFVideoSource("E:\Video\John_Wick_Chapter_2\John_Wick_Chapter_2_t00.mkv", colorspace = "YV12", \
cachefile = "D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00.ffindex")
-------------------------- Script Properties --------------------------
Source Frame Count : 176062
Source Frame Rate : 23.976024
Source Duration : 02:02:23.2530000
Target Frame Count : 176062
Target Frame Rate : 23.976024
Target Duration : 02:02:23.2530000
----------------------- MediaInfo Audio Source 1 -----------------------
General
Complete name : D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00 ID1 English.thd
Format : TrueHD
File size : 3.93 GiB
Overall bit rate mode : Variable
Audio
Format : TrueHD
Format profile : TrueHD+Atmos / TrueHD
Bit rate mode : Variable
Maximum bit rate : 7 806 kb/s
Channel(s) : Object Based / 8 channels
Channel positions : Object Based / Front: L C R, Side: L R, Back: L R, LFE
Sampling rate : / 48.0 kHz
Frame rate : 1 200.000 FPS (40 SPF)
Compression mode : Lossless
---------------- Error Video encoding using NVEnc 4.16 ----------------
Video encoding using NVEnc 4.16 failed with exit code: 1 (0x1)
The exit code might be a system error code: STATUS_WAIT_1
The exit code might be a system error code: Incorrect function.
------------------- Video encoding using NVEnc 4.16 -------------------
"D:\Encode Plus\StaxRip\Apps\NVEnc\NVEncC64.exe" --avhw cuda --vbrhq 17500 --codec h265 --preset quality --level 4.1 --bframes 0 --ref 5 --qp-init 1 --aq --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --max-cll "1000,510" --lookahead 32 --vbr-quality 20 -i E:\Video\John_Wick_Chapter_2\John_Wick_Chapter_2_t00.mkv -o D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00_out.h265
Failed to Initialize the encoder
.: 8 (NVENC indicates that one or more of the parameter passed to the API call is invalid.)
------------------- Video encoding using NVEnc 4.16 -------------------
"D:\Encode Plus\StaxRip\Apps\NVEnc\NVEncC64.exe" --avhw cuda --vbrhq 17500 --codec h265 --preset quality --level 4.1 --bframes 0 --ref 5 --qp-init 1 --aq --colormatrix bt2020nc --colorprim bt2020 --transfer smpte2084 --max-cll "1000,510" --lookahead 32 --vbr-quality 20 -i E:\Video\John_Wick_Chapter_2\John_Wick_Chapter_2_t00.mkv -o D:\Cache\John_Wick_Chapter_2_t00_temp\John_Wick_Chapter_2_t00_out.h265
Failed to Initialize the encoder
.: 8 (NVENC indicates that one or more of the parameter passed to the API call is invalid.)
Start: 11:16:54
End: 11:16:58
Duration: 00:00:03
Atlantis
11th November 2018, 19:42
I would also like to know how to do simple HDR to SDR conversion.
The link provided DGTonemap -> Help did not help much. Couldn't make it work. I'm using StaxRip because it makes things easy.
If someone could tell how to do HDR to SDR within the StaxRip GUI, it would be appreciated.
videoh
12th November 2018, 01:54
I would also like to know how to do simple HDR to SDR conversion. Do you have a recent nVidia card? If so, I can give you a really easy way.
The link provided DGTonemap -> Help did not help much. Couldn't make it work. Tell us what error you got. We cannot read minds, ya know?
I'm using StaxRip because it makes things easy.
Maybe StaxRip doesn't make things so easy. ;)
Revan654
12th November 2018, 04:55
Thanks for the info! Yes the original mkv has HDR10 tag, so it's not just a 4K file. I'm using --strict-gop option, would that be the same? Or is the issue that I'm using nvenc h.265 rather than regular x265? My nvidia card encodes very fast and the quality is great with the right settings.
No, No-Open-gop and strict-gop are two different Flags.
x265 has allot more Flags, It's the preferred method when encoding videos with HDR colorspace. The NVIDIA Encoder doesn't have all the HDR Flags, There slowly being added. Allot is based off what the current Nvidia SDK has and what the Encoder can access.
Revan654
12th November 2018, 05:13
snip
Post the text file next time,instead of a massive wall of text.
1. Since your encoding to HDR, your missing Master-Display flag.
2. Depth needs to be increased to 10bit and Profile needs to be Main10.
3. The Dev has a Habit of Breaking the Encoder, I would Upgrade to 4.20 & make sure you have all the required dll files.
steelfatboy
12th November 2018, 06:05
No, No-Open-gop and strict-gop are two different Flags.
x265 has allot more Flags, It's the preferred method when encoding videos with HDR colorspace. The NVIDIA Encoder doesn't have all the HDR Flags, There slowly being added. Allot is based off what the current Nvidia SDK has and what the Encoder can access.
Once again, thank you for the info. I'll stick to x265 for now.
Zetti
12th November 2018, 12:58
FFmpeg v4.1 is released.
Revan654
13th November 2018, 02:08
FFmpeg v4.1 is released.
Has been out for awhile.
Trench
13th November 2018, 05:56
A couple observations I had from 1.7.0.6, which today I've been able to determine still exist in 1.9.0.0 x64:
1. When trying to use non-default options for the ffmpeg "dynaudnorm" process, the options are incorrectly constructed in the ffmpeg command line. For example if you de-select "Enable channel coupling", the command line options are constructed as:
ffmpeg -q:a 4 -af dynaudnorm n=false
instead of being correctly constructed as:
ffmpeg -q:a 4 -af dynaudnorm=n=false
Per ffmpeg filtering guide documentation (https://trac.ffmpeg.org/wiki/FilteringGuide), additional options would need to be colon-separated, such as this example of adding "r=0.95" to the previous command line:
ffmpeg -q:a 4 -af dynaudnorm=n=false:r=0.95
2. Specifying a non-default RMS of "0.95" in the dynaudnorm options is accepted by the GUI, and is added to the command line (not withstanding the incorrect construction issue already described). But when you then re-enter the GUI of dynaudnorm options, it shows the current RMS as being "1.0", instead of the "0.95" that was selected and is still visible within the command line. (Screen shot attached, once available.)
3. I rip one of my Blu-Rays, and have eac3to extract my preferred 5.1+ audio file to FLAC. In making an MP4 of this video, I now want to re-encode this FLAC audio "two ways" into my resulting MP4 container: Once to AAC while down-mixing to stereo for when I'm playing on my crappy TVs (so that the audio is "loud enough"), and again to AAC while keeping the original 5.1/6.1/7.1 the Blu-Ray contained (in case I don't have crappy TVs in the future and want to select playback of a higher-quality audio track).
But StaxRip defies doing this, saying "The first and second audio source files or streams are identical", apparently in reference to the having the same FLAC file selected as the input for the two different output encodings. (Screen shot attached, once available.)
It's not that "it literally cannot be done"; StaxRip seems to just be complaining about the file name being the same for the input in both sources, even though the resulting ACC re-encodings into the MP4 container will be different. If I manually duplicate and create a separate input FLAC file which is simply a copy the first FLAC file, the "two different encodings of the same input FLAC file" (now with two different input file names) is allowed.
Rather than StaxRip saying "you can't get there from here" and requiring manual intervention, it seems like StaxRip could at minimum be performing the same thing I'm having to do manually: Simply duplicate the FLAC (or whatever the "duplicate" source file is) to a temporary file, and use it as input for the second encoding.
Hmm... is this actually just a temp file name management issue? e.g. Is StaxRip's complaint really based on the fact that the temp file name(s) generated for these re-encoding attempts will be identical? (i.e. same FLAC file base name, same export track ID number in file name, etc.) Such that it could really be solved by just appending a "target track ID" to the temp file names, representing what track number it will be in the resulting MP4 file. Thereby preventing the two separate re-encoding processes of the same input file from stepping on each other's temp file names.
Thanks for considering.
EDIT: Can now confirm all three issues remain unchanged in 2.0.0.0, for what it's worth.
steelfatboy
13th November 2018, 19:46
I found a program called nvhsp that was created specifically to use with nvenc encodes to add HDR10 color data back. It looks like some even found a way to integrate it into StaxRip, but I have no idea how to do that. For now, I am manually extracting the mkv, using nvhsp to add the HDR10 info, then merging the files back into mkv. It doesn't take long, but it is a bit cumbersome. If anyone needs any details, let me know and I'll do my best to document my process.
Revan654
13th November 2018, 20:31
I found a program called nvhsp that was created specifically to use with nvenc encodes to add HDR10 color data back. It looks like some even found a way to integrate it into StaxRip, but I have no idea how to do that. For now, I am manually extracting the mkv, using nvhsp to add the HDR10 info, then merging the files back into mkv. It doesn't take long, but it is a bit cumbersome. If anyone needs any details, let me know and I'll do my best to document my process.
It's completely useless now, Since all the functions it has, Has already been added to nvenc encoder. It was only adding colorspace for device playback and such. Nothing to do with core flags that have to be set at the time of encoding.
Not to mention mkvtoolnix could already do everything the script was doing.
steelfatboy
13th November 2018, 23:05
It's completely useless now, Since all the functions it has, Has already been added to nvenc encoder. It was only adding colorspace for device playback and such. Nothing to do with core flags that have to be set at the time of encoding.
Not to mention mkvtoolnix could already do everything the script was doing.
You are not wrong. It did add the HDR10 tag but as you said not to the core flags. Ah well, thought I had something there. Back to x265 I go.
Trench
14th November 2018, 18:18
2.0 is only Beta, Final is not ready yet. Only Stable Releases Are Shown.
Not sure what the expectation might have been, but on a Windows 10 x64 machine where I was running StaxRip 1.9.0.0 successfully including ffmpeg.exe encoding, when I tried to run StaxRip 2.0.0.0 on that same machine StaxRip didn't prompt me for any application installation updates. But ffmpeg failed to run, citing only the generic STATUS_DLL_NOT_FOUND (0xC0000135) in the StaxRip log.
Attempting to run ffmpeg.exe manually outside of StaxRip 2.0.0.0 reported VSScript.dll wasn't being found. Attempting to launch the VapourSynth installer failed because a suitable Python installation wasn't found. After installing Python, VapourSynth installation required download of the VC_REDIST for C++ 2017.
I think the expectation was that StaxRip 2.0.0.0 needed to realize the installations that hadn't occurred yet, rather than just hitting the non-descript failure to run ffmpeg.exe. So for what it's worth.
Trench
14th November 2018, 18:29
Does this symptom already sound familiar: "My HEVC+AAC MP4 acts frozen. It allows me to seek to any offset and see the correct video frame at that offset, but refuses to actually play normally from start or from any offset. And the cause is somehow the AAC encoding."
Hopefully that symptom already means something to someone, for a known issue or something I'm doing wrong. But at minimum, maybe the information is useful to anyone else who might encounter the same unknown issue I did after switching to StaxRip 1.9.0.0, even though it appears to be an ffmpeg issue and not any kind of StaxRip issue.
Details:
After switching to 1.9.0.0, I came to realize that some of the Blu-Ray-to-MP4 work I was doing resulted in an MP4 which wouldn't "play". The symptom on playback through WMP12+LAVFilter was as though the playback was "permanently paused". It won't play upon opening, but I can seek to any offset I want, and I will get a correct frame of video displayed for that offset. But it will just stay "frozen" at that offset rather than actually "playing".
One of the Blu-Rays this happened with was one I had successfully processed through StaxRip 1.7.0.6 just days before, which got me looking at the tool differences as compared to 1.9.0.0. After trial and error and dividing and conquering, the difference seems to be ffmpeg.exe 4.0.2 versus the previous ffmpeg.exe 3.3.4. With these command lines:
ffmpeg.exe -i "Track1.flac" -q:a 4 -af dynaudnorm -ac 2 -y -hide_banner "Track1.m4a"
ffmpeg.exe -i "Track2.flac" -q:a 4 -af dynaudnorm -y -hide_banner "Track2.m4a"
...using the ffmpeg.exe 4.0.2 provided with StaxRip 1.9.0.0, the resulting AAC files when combined into the MP4 result in the described "frozen" symptom.
If I change nothing except to use ffmpeg.exe 3.3.4 from StaxRip 1.7.0.6 to re-encode the AAC using the same command lines and source files (and just muxing the the same previously-encoded HEVC output by x265.exe from 1.9.0.0, and still the same MP4Box from 1.9.0.0), the resulting MP4 now plays normally.
The same problem of "frozen" playback occurs with StaxRip 2.0.0.0 and the included "ffmpeg version N-92272-g0e9c01fd87", for what it's worth. Only reverting to use of the older ffmpeg.exe 3.3.4 from StaxRip 1.7.0.6 has allowed success thus far.
DaMacFunkin
14th November 2018, 19:45
Post the text file next time,instead of a massive wall of text.
1. Since your encoding to HDR, your missing Master-Display flag.
2. Depth needs to be increased to 10bit and Profile needs to be Main10.
3. The Dev has a Habit of Breaking the Encoder, I would Upgrade to 4.20 & make sure you have all the required dll files.
Hi Thanks for that, still getting errors though, file not found???
Any ideas?
Cheers
Revan654
14th November 2018, 20:17
Not sure what the expectation might have been, but on a Windows 10 x64 machine where I was running StaxRip 1.9.0.0 successfully including ffmpeg.exe encoding, when I tried to run StaxRip 2.0.0.0 on that same machine StaxRip didn't prompt me for any application installation updates. But ffmpeg failed to run, citing only the generic STATUS_DLL_NOT_FOUND (0xC0000135) in the StaxRip log.
Attempting to run ffmpeg.exe manually outside of StaxRip 2.0.0.0 reported VSScript.dll wasn't being found. Attempting to launch the VapourSynth installer failed because a suitable Python installation wasn't found. After installing Python, VapourSynth installation required download of the VC_REDIST for C++ 2017.
I think the expectation was that StaxRip 2.0.0.0 needed to realize the installations that hadn't occurred yet, rather than just hitting the non-descript failure to run ffmpeg.exe. So for what it's worth.
FFMpeg has been Completely Rebuilt and Stripped away any unless codecs. It's under 50 Mbs right now.
The readme/changelog tells you it requires VC_REDIST for C++ 2017. Windows 10 post Launch build has it already installed. It's nothing new that C++ runtimes are required, after all it runs on dotnet.
Trench
14th November 2018, 22:22
The readme/changelog tells you it requires VC_REDIST for C++ 2017. Windows 10 post Launch build has it already installed. It's nothing new that C++ runtimes are required, after all it runs on dotnet.
Agreed on .NET Framework requirement & presence on Windows 10. The runtime in question is Visual C++ 2017 Runtime, which is not already present, and is a dependency of this latest VapourSynth and not StaxRip itself. But maybe we don't put Microsoft dependencies in the Apps folder like we do other dependencies; in which case letting VapourSynth download it from Microsoft.com instead of pre-resolving it from a local source is fine.
The observation I was raising isn't that it's unexpected that FFMPEG would require VapourSynth, nor unexpected that VapourSynth would require Python. The observation was that StaxRip 2.0.0.0 didn't appear to be aware of these dependencies, and wasn't intercepting "Hey, you're trying to run something that is going to require VapourSynth to be installed, here's an install button for you." (And in turn, first installing Python before installing VapourSynth.)
i.e. It wasn't expected to me anyway that 2.0.0.0 would run FFMPEG and let it fail with 0xC0000135, rather than guiding the user to install Python and VapourSynth first. I don't think I'm off base in thinking 1.9.0.0 and 1.7.0.6 did manage these dependencies; or else I'm not explaining myself correctly. Thanks.
frenchfries
15th November 2018, 02:42
Hey @Revan654
As always, great work.
I had given up on quicksync but Rigaya has squashed a bunch of bugs supposedly that should make it viable again.
Are you able to update the flags to support the extra/missing colormatrixes? Most notably BT 2020 NC?
I have tested the commandline again and it appears to actually work this time but stax is much more convenient as it allows audio time offset and other tuning, rather than having to modify those values later. V3.11 is what I have tested and is currently the latest. https://github.com/rigaya/QSVEnc/releases
Atlantis
15th November 2018, 04:13
StaxRip 2.0.0.0 does not add the HDR10 flag. When I used the old version 1.7.0.0 it added the HDR10 flag when encoding HDR videos. Using mediainfo you could easily see HDR10 but now you can't.
The resulted file is HDR and when played on TV, it does trigger HDR, the only problem is that mediainfo doesn't show it anymore. It was a quick way to check if a file is HDR. Version 1.7.0.0 does this correctly.
mediainfo:
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Commercial name : HDR10 <--- missing
Format profile : Main 10@L5.1@High
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 4 min
Bit rate : 53.5 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
frenchfries
15th November 2018, 05:44
StaxRip 2.0.0.0 does not add the HDR10 flag. When I used the old version 1.7.0.0 it added the HDR10 flag when encoding HDR videos. Using mediainfo you could easily see HDR10 but now you can't.
The resulted file is HDR and when played on TV, it does trigger HDR, the only problem is that mediainfo doesn't show it anymore. It was a quick way to check if a file is HDR. Version 1.7.0.0 does this correctly.
mediainfo:
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Commercial name : HDR10 <--- missing
Format profile : Main 10@L5.1@High
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 4 min
Bit rate : 53.5 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Your problem is probably the issue with mediainfo versions.
ie. there are a few parts to make that little HDR10 flag appear.
You need to have the color primaries, you may need to google them as mediainfo now also buggers this up,colormatrix and transfer. You should also check if the max CLL and Max FALL is set and manually adjust if required.
example primaries below
DCI-P3: --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --max-cll 1000,1
RGB: G(x=0.265, y=0.690), B(x=0.150, y=0.060), R(x=0.680, y=0.320), WP(x=0.3127, y=0.329), L(max=1000, min=0.0000)
Rec.709: --master-display G(15000,30000)B(7500,3000)R(32000,16500)WP(15635,16450)L(10000000,1) --max-cll 1000,1
RGB: G(x=0.30, y=0.60), B(x=0.150, y=0.060), R(x=0.640, y=0.330), WP(x=0.3127,y=0.329), L(max=1000, min=0.0000)
Rec.2020: --master-display G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,1) --max-cll 1000,1
RGB: G(x=0.170, y=0.797), B(x=0.131, y=0.046), R(x=0.708, y=0.292), WP(x=0.3127,y=0.329), L(max=1000, min=0.0000)
Revan654
15th November 2018, 06:01
StaxRip 2.0.0.0 does not add the HDR10 flag. When I used the old version 1.7.0.0 it added the HDR10 flag when encoding HDR videos. Using mediainfo you could easily see HDR10 but now you can't.
Actually it does if you enabled the proper encoding flags, Mediainfo and how it reads HDR10 was changed allot.
As I said before, It no longer has color coordinate system which wipes out the VUI import feature if your video clip doesn't use the standard BT.2020 colorspace it will not automatically adjust the settings for you.
Revan654
15th November 2018, 06:11
Your problem is probably the issue with mediainfo versions.
ie. there are a few parts to make that little HDR10 flag appear.
You need to have the color primaries, you may need to google them as mediainfo now also buggers this up,colormatrix and transfer. You should also check if the max CLL and Max FALL is set and manually adjust if required.
example primaries below
DCI-P3: --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --max-cll 1000,1
RGB: G(x=0.265, y=0.690), B(x=0.150, y=0.060), R(x=0.680, y=0.320), WP(x=0.3127, y=0.329), L(max=1000, min=0.0000)
Rec.709: --master-display G(15000,30000)B(7500,3000)R(32000,16500)WP(15635,16450)L(10000000,1) --max-cll 1000,1
RGB: G(x=0.30, y=0.60), B(x=0.150, y=0.060), R(x=0.640, y=0.330), WP(x=0.3127,y=0.329), L(max=1000, min=0.0000)
Rec.2020: --master-display G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,1) --max-cll 1000,1
RGB: G(x=0.170, y=0.797), B(x=0.131, y=0.046), R(x=0.708, y=0.292), WP(x=0.3127,y=0.329), L(max=1000, min=0.0000)
DCI seems to be slightly off:
Bt.709 is not part of the HDR colorspace.
Your DCI-P3 is actually Display P3
These are mine , Which I calculated my self.
DCI-P3: G(13250,34500)B(7500,3000)R(34000,16000)WP(15700,17550)L(10000000,1)
Display-P3: G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)
BT.2020: G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,1)
Revan654
15th November 2018, 06:20
Hey @Revan654
As always, great work.
I had given up on quicksync but Rigaya has squashed a bunch of bugs supposedly that should make it viable again.
Are you able to update the flags to support the extra/missing colormatrixes? Most notably BT 2020 NC?
I have tested the commandline again and it appears to actually work this time but stax is much more convenient as it allows audio time offset and other tuning, rather than having to modify those values later. V3.11 is what I have tested and is currently the latest. https://github.com/rigaya/QSVEnc/releases
Allot has been added to most of the Encoders. Should already be in the Code, Since I tried to add anything that was worth adding.
frenchfries
15th November 2018, 06:25
Allot has been added to most of the Encoders. Should already be in the Code, Since I tried to add anything that was worth adding.
Ta for the color space values. I'll have to check and see if I was just conflating the two different P3 values or whether I have buggered stuff up.
Are you saying that master has the colorspace stuff added? ie. after release 2.0?
Atlantis
15th November 2018, 12:15
What "proper encoding flags" should I enable? With Staxrip version 1.7.0.0 it did it all itself, I didn't have to do anything. The result had all the "proper encoding flags".
bin.n2f
15th November 2018, 12:32
smdegrain not found in latest release!!!or havsfunc script...
Atlantis
15th November 2018, 13:00
So I did a little test and loaded the same HDR file in both versions. Here is the command line I get
StaxRip 2.0.0.0
--crf 20 --output-depth 10 --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --max-cll "1452,519"
StaxRip 1.7.0.0
--crf 20 --profile main10 --output-depth 10 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited
So StaxRip 2.0.0.0 is not adding
--master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)" --range limited
Revan654
15th November 2018, 18:15
What "proper encoding flags" should I enable? With Staxrip version 1.7.0.0 it did it all itself, I didn't have to do anything. The result had all the "proper encoding flags".
No it didn't, MediaInfo at the time reported incorrect data, Which is why MediaInfo was changed in HDR area since. Some based on the info I gave him.
1.7 didn't even have all the HDR10 Flags inside the x265 encoder.
--no-open-gop
--hdr
--hrd
--aud
--colorprim bt2020
--transfer smpte2084
--colormatrix bt2020nc
--output-depth 10
--repeat-headers
--range limited
+ Ingest Function.
or just use the PowerShell Script + --No-open-Gop + Ingest
Revan654
15th November 2018, 18:19
smdegrain not found in latest release!!!or havsfunc script...
Nothing has been removed, Scripts have just been moved to Script Folder.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.