StaxRip 2.0 Support Thread

[Revan654]

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-]

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]

Excellent!

I'll try it using it with QSVEncC.

Get a good start for your new project.

[NikosD]

Latest Release: https://github.com/Revan654/staxrip/releases/latest
I may be blind, but I only see v1.9.0.0 of Staxrip

[-QfG-]

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]

Github Release Page: https://github.com/Revan654/staxrip/releases

[NikosD]

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]

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]

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]

Please add HDR to SDR script built in :)

[Revan654]

Please add HDR to SDR script built in :)

One already exists, two if you add in 3dlut function.

[shodan5000]

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]

Simple ha, HDR is very complex. There are help files for most filters.

Apps -> Manage -> Avisynth -> DGTonemap -> Help

[JKyle]

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]

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]

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]

...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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

FFmpeg v4.1 is released.

[Revan654]

FFmpeg v4.1 is released.

Has been out for awhile.

[Trench]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

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]

smdegrain not found in latest release!!!or havsfunc script...

[Atlantis]

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]

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]

smdegrain not found in latest release!!!or havsfunc script...

Nothing has been removed, Scripts have just been moved to Script Folder.

[Revan654]

2.0 Beta 2

2.0 Beta 2
- Released Two Versions, One that Supports Preview Build of Dotnet 4.8 and Standard 4.7.*.
- Updated a few of FFMpeg Flags for Audio Demuxing / Encoding.
- Moved HDR Ingest in Options Menu to Video Tab.
- Support for HLG Metadata has been Added to Ingest.
- Added Support for VUI for the Following ColorSpaces: Display P3 and DCI P3 (It still Must pass the other HDR Checks)
- Proper Master-Display data has been added for Display P3 and DCI P3.
- Support for Webm Subtitles has been Added For srt, sup, idx Files.
- Updated the VUI Import for HDR10, Due to MediaInfo Changes to Output Names.
- Changed the VUI import name for HLG, Due to MediaInfo not using proper colorspace name.
- Added Some Support for HLG to VUI import function, MediaInfo does not contain all HLG Metadata.
- Updated all the Help Files for the Encoders.
- Rav1e Encoder Has Been Added to Support AV1 codec.
Flags:
--tune
--limit
--speed
--quantizer
--keyint
--low_latency
--custom
- NVEnc Added Flags:
-profile(h265)
-vpp-padding(Left,Top,Right,Bottom)
-vpp-tweak(Contrast,Gamma,Saturation,Hue,Brightness)
-chromaloc
-interlace tff
-interlace bff
-tier
-pic-struct
-aud
-slices
+ Others...
- QSVEnc Added Flags:
-vbv-bufsize
-chromaloc
-vpp-scaling -> -vpp-resize
-Filter: mctf
-sao
-ctu
-tskip
+ Others...
- Removed any Switches that no longer exist in the CLI Encoders.
- Updated FFMPEG to 4.1
- ReBuilt MPVNet to work on Both older and Newer Systems.
- Support has been added for MKV, Webm and MP4 to AV1.
- 32 Float Filters have been Added(Oyster, Plum, Vine)
- FFMPEG Shared dll Files has been Updated to 4.1
- Added mpvnet back with fully working mpv dll file.
- Re-Enabled MediaInfo Folder, It's Been Fixed to with latest MediaInfo Code.
- x264 has Been Updated to 2935
- x265 has Been Updated to 2.9+9
- Cleaned up the Config Files.
- Update Script has been moved to Python Code, instead of basic Powershell Script.
- Site Packges Required: bs4(BeautifulSoup), Requests, win32api, tqdm, & psutil
- Added Update Script for NVEnc & QVSEnc.
- mtn has been Updated, Uses less Shared files.


Dotnet 4.7 Link: https://github.com/Revan654/staxrip/releases/download/2.0-Beta-2/2.0.0.0.Beta2.Dotnet4.7.x64.7z
Dotnet 4.8 Link: https://github.com/Revan654/staxrip/releases/download/2.0-Beta-2/2.0.0.0.Beta2.Dotnet4.8.x64.7z

[AMED]

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)Would it be better in the longer run to ditch MediaInfo and use FFProbe?

[DaMacFunkin]

So, I previously got told no special settings where needed to re-encode HDR10 to HDR10 in staxrip, but I think the last few pages have shown not to be true, what exactly needs to be set to do this correctly please?
Thank you.

[Revan654]

Would it be better in the longer run to ditch MediaInfo and use FFProbe?

FFProbe is to limited of what it outputs. Not to mention Mediainfo is used for just about everything in StaxRip. Mediainfo is much easier to add functions then ffprobe.

[Revan654]

So, I previously got told no special settings where needed to re-encode HDR10 to HDR10 in staxrip, but I think the last few pages have shown not to be true, what exactly needs to be set to do this correctly please?
Thank you.

Already been posted here: https://forum.doom9.org/showpost.php?p=1857632&postcount=49

along with master-display.

[lansing]

The control of this program is still very buggy.

When I loaded in a 1080p mp4 and preview, and then hold and drag the preview window around, it lags.

Also when I switch to use vs filter, loaded in a video, and then source->dgsource, the dgsourcenv window keep popping up in an infinite loop after I closed one.

Another problem, if I have one video loaded with the vs filters, and then drag and open another video into the program, it will automatically switch back to avs filters.

[Revan654]

The control of this program is still very buggy.

When I loaded in a 1080p mp4 and preview, and then hold and drag the preview window around, it lags.

Also when I switch to use vs filter, loaded in a video, and then source->dgsource, the dgsourcenv window keep popping up in an infinite loop after I closed one.

Another problem, if I have one video loaded with the vs filters, and then drag and open another video into the program, it will automatically switch back to avs filters.

The Control is perfectly fine.

I don't have any other dg software installed since there payware.

Lag is on your side.

It loads the default template before loading any new videos.

Video encoding software / editor performance is based off your system specs.

[RainyDog]

2.0 Beta 2

Thanks for the new Beta Revan. Can confirm that the master display info is now imported for HDR sources so can finally leave version 1.7 behind for good.

On another note, is there anything I need to set for DXVA2 ffmpeg decoding to work? It's just ever worked for me for some reason, in StaxRip 1.0 or 2.0. So I wondered if it required an additional program or external setting somewhere?

[RainyDog]

Revan, do you know which field or deinterlacing setting I need for the below source please? It's definitely not interlaced, despite what the media info states. But StaxRip 2.0 imports it as a 25fps source and if I try and re-encode it just as-is, the resulting output plays back at half speed.

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings : CABAC / 2 Ref Frames
Format settings, CABAC : Yes
Format settings, ReFrames : 2 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 35 min
Bit rate mode : Variable
Bit rate : 37.9 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 50.000 FPS
Original frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan type, store method : Separated fields
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.365
Stream size : 25.3 GiB (100%)
Language : French
Default : Yes
Forced : No

Thanks.

[Betsy25]

What I really miss in Staxrip is some source detection feature like with MeGUI, to know if deinterlacing is needed.
It's the only thing that keeps me from switching from MeGUI to Staxrip, even though MeGUI is terribly buggy lately.

[DaMacFunkin]

Is there a batch for source files, i.e. Can I add a few playlists and/or Mkv files and leave them to demux/index/autosave then go back later to change any parameters that may need changing?

Thank you.

[DaMacFunkin]

In the new beta after a file has demuxed and indexed it takes 3-4 minutes before the staxrip gui is available again, task manager shows staxrip is still accessing the hard drive, it is as if it does another index in the background? There is nothing in the log file?
Ps this only seems to happen with mkv, blu ray folder is fine.

[lansing]

The Control is perfectly fine.

I don't have any other dg software installed since there payware.

Lag is on your side.

It loads the default template before loading any new videos.

Video encoding software / editor performance is based off your system specs.

I'm pretty sure that the preview window lag when dragged around is a bug, because the lag only occurs on the first 100px of the movement. For example, if I drag the window from left of the screen to the right, the movement lags for about the first 100px, after that it moves smoothly.

I don't have the dgindexnv either, I'm just testing the program. And when I select the dgsource, the tools window will pop up, when I closed it, another tools window popped. So it's a bug.

The "auto load default template for new file" logic doesn't make much sense either. For example, I don't have the latest avs+ and I only want to open file with vapoursynth. When I started the program and tried to load a video, the tools window will pop up telling me that I don't have avs+, if I close it, the action will cancelled without giving me a choice to switch to vapoursynth filter. If I already have video loaded and tried to load a new one, this problem will prevent me from proceeding, I would have to restart the program in order to load the new file.



And I found another bug with the update function, it's not reading file path correctly if I have space in the folder name.



The system cannot find the file specified

File: C:\apps\Video

Arguments: Editing\StaxRip\staxrip_1.9.0.0.x64\Update.bat

[Revan654]

What I really miss in Staxrip is some source detection feature like with MeGUI, to know if deinterlacing is needed.
It's the only thing that keeps me from switching from MeGUI to Staxrip, even though MeGUI is terribly buggy lately.

It has it, You just need to enabled it.Look in the Script Directory and remove the _ .

More Info Here: https://staxrip2.readthedocs.io/en/latest/powershell.html#aftersourceloaded-ps1

[Revan654]

I'm pretty sure that the preview window lag when dragged around is a bug, because the lag only occurs on the first 100px of the movement. For example, if I drag the window from left of the screen to the right, the movement lags for about the first 100px, after that it moves smoothly.

I don't have the dgindexnv either, I'm just testing the program. And when I select the dgsource, the tools window will pop up, when I closed it, another tools window popped. So it's a bug.

The "auto load default template for new file" logic doesn't make much sense either. For example, I don't have the latest avs+ and I only want to open file with vapoursynth. When I started the program and tried to load a video, the tools window will pop up telling me that I don't have avs+, if I close it, the action will cancelled without giving me a choice to switch to vapoursynth filter. If I already have video loaded and tried to load a new one, this problem will prevent me from proceeding, I would have to restart the program in order to load the new file.



And I found another bug with the update function, it's not reading file path correctly if I have space in the folder name.

StaxRip uses Templates, It's always been like this since Day one. Just Create a Template for VS.

It's all at your end, The App has been fully tested or Multiply PC's.

I know it's on your side now since the Update Function is done through Python and the SubProcess System.

Some how you screwed up all your settings and your settings have not updated for the latest version.

Make Sure you using dotnet version that you have running.

[Revan654]

Is there a batch for source files, i.e. Can I add a few playlists and/or Mkv files and leave them to demux/index/autosave then go back later to change any parameters that may need changing?

Thank you.

Stax76 removed the auto demux feature, I think it was conflicting with something.

Batch function still exists just click on source.

[Revan654]

In the new beta after a file has demuxed and indexed it takes 3-4 minutes before the staxrip gui is available again, task manager shows staxrip is still accessing the hard drive, it is as if it does another index in the background? There is nothing in the log file?
Ps this only seems to happen with mkv, blu ray folder is fine.

Demux Function is untouched, It's fine at my end. It could be there other metadata or files that was found and are being indexed too. Since every videofile is different, can't really test this without having your source file.

[Revan654]

Docs have been Updated with all the latest tools & Filters that can be used: https://staxrip2.readthedocs.io/en/latest/

[Lynx_TWO]

I purchased and installed SVP4, and now whenever I try to use QTGMC for deinterlacing I get this error:

Plugin [pathname]\Apps\Plugins\VS\SVPFlow\svpflow1_vs64.dll already loaded (com.svp-team.flow1)

Traceback (most recent call last):
File "src\cython\Vapoursynth.pyx", line 1927, in vapoursynth.vpy_evaluateScript
File "src\cython\Vapoursynth.pyx", line 1928, in vapoursynth.vpy_evaluateScript
File "[filenamePath]\new_preview.vpy", line 27, in <module>
core.std.LoadPlugin(r"[pathname]\Apps\Plugins\VS\SVPFlow\svpflow1_vs64.dll")
File "src\cython\Vapoursynth.pyx", line 1883, in vapoursynth.Function.__call__

Vapoursynth.Error: Plugin [pathname]\Apps\Plugins\VS\SVPFlow\svpflow1_vs64.dll already loaded (com.svp-team.flow1)

EDIT: Nevermind, I just deleted the DLLs out of the StaxRip folder and it works.

[lansing]

StaxRip uses Templates, It's always been like this since Day one. Just Create a Template for VS.

I just tried out the template system, and I found problems on its own.

First problem, when I have a video loaded, it doesn't let me create a new template, but it has no option to close the current file, so I will have to restart the program to create it.

Second problem, there is no selection in the main ui to choose "no indexing and demxuing", if I want to save a new template regarding this, I would have to first load the "no indexing and demuxing", then do my changes and save template, which is kind of odd.




It's all at your end, The App has been fully tested or Multiply PC's.

I know it's on your side now since the Update Function is done through Python and the SubProcess System.

I have python 3.7.1(default) and python 3.6 on my machine, and I have reinstalled my .net framework 4.7.2 but the problem are still there.



Some how you screwed up all your settings and your settings have not updated for the latest version.


The program should not be forcing the users to update their avs, it should just give a warning and let the user decide what to do. For me I was trying to use vs but the program was locking me out because I didn't update my avs.

[Revan654]

I just tried out the template system, and I found problems on its own.

First problem, when I have a video loaded, it doesn't let me create a new template, but it has no option to close the current file, so I will have to restart the program to create it.

Second problem, there is no selection in the main ui to choose "no indexing and demxuing", if I want to save a new template regarding this, I would have to first load the "no indexing and demuxing", then do my changes and save template, which is kind of odd.

Template -> whatevertemplate.srip (Closes the file and loads the default values)

Templates can not be Created with Videos Loaded since it would create a null value for both Source and output. Null values will always crash software.


"no indexing and demxuing"

Yes There is.


The program should not be forcing the users to update their avs, it should just give a warning and let the user decide what to do. For me I was trying to use vs but the program was locking me out because I didn't update my avs.

AVS+ is only required, Which is what StaxRip uses.

The default FrameServer is AVS, it's been this way since the start. VS is considered addon. AVS is used on many functions, even when using VS. Not to mention VS has AVS Support.

I would read the docs since many of these subjects are covered.

[Revan654]

I purchased and installed SVP4, and now whenever I try to use QTGMC for deinterlacing I get this error:

Plugin [pathname]\Apps\Plugins\VS\SVPFlow\svpflow1_vs64.dll already loaded (com.svp-team.flow1)

Traceback (most recent call last):
File "src\cython\Vapoursynth.pyx", line 1927, in vapoursynth.vpy_evaluateScript
File "src\cython\Vapoursynth.pyx", line 1928, in vapoursynth.vpy_evaluateScript
File "[filenamePath]\new_preview.vpy", line 27, in <module>
core.std.LoadPlugin(r"[pathname]\Apps\Plugins\VS\SVPFlow\svpflow1_vs64.dll")
File "src\cython\Vapoursynth.pyx", line 1883, in vapoursynth.Function.__call__

Vapoursynth.Error: Plugin [pathname]\Apps\Plugins\VS\SVPFlow\svpflow1_vs64.dll already loaded (com.svp-team.flow1)

EDIT: Nevermind, I just deleted the DLLs out of the StaxRip folder and it works.

You Using Both the Auto-Loading Function and the StaxRip loading Function. VS doesn't allow dual Loading of the same file.

Just be warned there may be issues without the dll's being loaded from the Plugin folder.

[Betsy25]

It has it, You just need to enabled it.Look in the Script Directory and remove the _ .

More Info Here: https://staxrip2.readthedocs.io/en/latest/powershell.html#aftersourceloaded-ps1

I did that and now it just crashed out...

-------------------------- System Environment --------------------------

StaxRip : 2.0.0.0
Windows : Windows 7 Professional
Language : Dutch (Belgium)
CPU : Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
GPU : ATI Radeon HD 4800 Series
Memory : 8 GB
Resolution : 1680 x 1050
DPI : 96

------------------------ MediaInfo Source File ------------------------

I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1.VOB

General
Complete name : I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1.VOB
Format : MPEG-PS
File size : 1 024 MiB
Duration : 25 min 42 s
Overall bit rate mode : Variable
Overall bit rate : 5 567 kb/s
Writing library : |HCenc 0.21.0.0 - (c) 2004/2007|

Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings : CustomMatrix / BVOP
Format, BVOP : Yes
Format, Matrix : Custom
Format, GOP : Variable
Format, picture structure : Frame
Duration : 25 min 42 s
Bit rate mode : Variable
Bit rate : 5 233 kb/s
Maximum bit rate : 7 401 kb/s
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 4:3
Frame rate : 25.000 FPS
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.505
Time code of first frame : 00:00:00:00
Time code source : Group of pictures header
GOP, Open/Closed : Open
GOP, Open/Closed of first frame : Closed
Stream size : 962 MiB (94%)
Writing library : |HCenc 0.21.0.0 - (c) 2004/2007|

Audio
ID : 189 (0xBD)-128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Muxing mode : DVD-Video
Duration : 25 min 42 s
Bit rate mode : Constant
Bit rate : 224 kb/s
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Delay relative to video : -8 ms
Stream size : 41.2 MiB (4%)
Service kind : Complete Main

Menu

---------- DGIndex: Demux & Index MPEG-2 using DGIndex 1.5.8 ----------

"C:\Program Files\Staxrip\Apps\DGIndex\DGIndex.exe" -i "I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1.VOB" -ia 2 -fo 0 -yr 1 -tn 1 -om 2 -drc 2 -dsd 0 -dsa 0 -o "I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1_temp\VTS_01_1" -hide -exit

Start: 17:43:05
End: 17:43:25
Duration: 00:00:19

---------------------- Script file failed to load ----------------------

Source File Path: I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1_temp\VTS_01_1_source.avs
LoadPlugin("C:\Program Files\Staxrip\Apps\Plugins\avs\MPEG2DecPlus\MPEG2DecPlus.dll")
MPEG2Source("I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1_temp\VTS_01_1.d2v")
Plugins: ConvertStacked, DirectShowSource, ImageSeq, Shibatch, TimeStretch, VDubFilter

------------------------------ Exception ------------------------------

System.Exception: AVIFileOpen failed to execute

Failed to open AviSynth script:

I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1_temp\VTS_01_1_source.avs

You can try to open the script with VirtualDub x64, if it don't open it could be a problem with the script or the AviSynth+ x64 setup, if StaxRip don't report a script error and the script looks valid then reinstalling AviSynth+ x64 might fix the problem, the setup is located at:

C:\Program Files\Staxrip\Apps\AviSynthPlus-MT-r2728.exe

at StaxRip.AVIFile..ctor(String path) in C:\Users\Revan\Desktop\StaxRip-2.0\General\AVIFile.vb:line 50
at StaxRip.VideoScript.Synchronize(Boolean convertToRGB, Boolean comparePath) in C:\Users\Revan\Desktop\StaxRip-2.0\General\VideoScript.vb:line 202
at StaxRip.MainForm.ModifyFilters() in C:\Users\Revan\Desktop\StaxRip-2.0\Forms\MainForm.vb:line 2281
at StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isEncoding) in C:\Users\Revan\Desktop\StaxRip-2.0\Forms\MainForm.vb:line 1997

[Revan654]

I did that and now it just crashed out...

-------------------------- System Environment --------------------------

StaxRip : 2.0.0.0
Windows : Windows 7 Professional
Language : Dutch (Belgium)
CPU : Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
GPU : ATI Radeon HD 4800 Series
Memory : 8 GB
Resolution : 1680 x 1050
DPI : 96

------------------------ MediaInfo Source File ------------------------

I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1.VOB

General
Complete name : I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1.VOB
Format : MPEG-PS
File size : 1 024 MiB
Duration : 25 min 42 s
Overall bit rate mode : Variable
Overall bit rate : 5 567 kb/s
Writing library : |HCenc 0.21.0.0 - (c) 2004/2007|

Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@Main
Format settings : CustomMatrix / BVOP
Format, BVOP : Yes
Format, Matrix : Custom
Format, GOP : Variable
Format, picture structure : Frame
Duration : 25 min 42 s
Bit rate mode : Variable
Bit rate : 5 233 kb/s
Maximum bit rate : 7 401 kb/s
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 4:3
Frame rate : 25.000 FPS
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.505
Time code of first frame : 00:00:00:00
Time code source : Group of pictures header
GOP, Open/Closed : Open
GOP, Open/Closed of first frame : Closed
Stream size : 962 MiB (94%)
Writing library : |HCenc 0.21.0.0 - (c) 2004/2007|

Audio
ID : 189 (0xBD)-128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Muxing mode : DVD-Video
Duration : 25 min 42 s
Bit rate mode : Constant
Bit rate : 224 kb/s
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Delay relative to video : -8 ms
Stream size : 41.2 MiB (4%)
Service kind : Complete Main

Menu

---------- DGIndex: Demux & Index MPEG-2 using DGIndex 1.5.8 ----------

"C:\Program Files\Staxrip\Apps\DGIndex\DGIndex.exe" -i "I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1.VOB" -ia 2 -fo 0 -yr 1 -tn 1 -om 2 -drc 2 -dsd 0 -dsa 0 -o "I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1_temp\VTS_01_1" -hide -exit

Start: 17:43:05
End: 17:43:25
Duration: 00:00:19

---------------------- Script file failed to load ----------------------

Source File Path: I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1_temp\VTS_01_1_source.avs
LoadPlugin("C:\Program Files\Staxrip\Apps\Plugins\avs\MPEG2DecPlus\MPEG2DecPlus.dll")
MPEG2Source("I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1_temp\VTS_01_1.d2v")
Plugins: ConvertStacked, DirectShowSource, ImageSeq, Shibatch, TimeStretch, VDubFilter

------------------------------ Exception ------------------------------

System.Exception: AVIFileOpen failed to execute

Failed to open AviSynth script:

I:\Te coderen\Lili en Marleen Seizoen 01 DVD1\VIDEO_TS\VTS_01_1_temp\VTS_01_1_source.avs

You can try to open the script with VirtualDub x64, if it don't open it could be a problem with the script or the AviSynth+ x64 setup, if StaxRip don't report a script error and the script looks valid then reinstalling AviSynth+ x64 might fix the problem, the setup is located at:

C:\Program Files\Staxrip\Apps\AviSynthPlus-MT-r2728.exe

at StaxRip.AVIFile..ctor(String path) in C:\Users\Revan\Desktop\StaxRip-2.0\General\AVIFile.vb:line 50
at StaxRip.VideoScript.Synchronize(Boolean convertToRGB, Boolean comparePath) in C:\Users\Revan\Desktop\StaxRip-2.0\General\VideoScript.vb:line 202
at StaxRip.MainForm.ModifyFilters() in C:\Users\Revan\Desktop\StaxRip-2.0\Forms\MainForm.vb:line 2281
at StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isEncoding) in C:\Users\Revan\Desktop\StaxRip-2.0\Forms\MainForm.vb:line 1997


Make Sure you make the changes in both backup folder and the Script folder.

Also You may have to change group policy in PowerShell, MS changed the security back in April locking out most scripts being run. It's a PIA with all the security MS keeps adding.

I just did a test on my PC with the Script and it works.

Filename: AfterSourceLoaded.ps1

# This script handles the AfterSourceLoaded event, remove the underscore from the
# filename in order to enable it. The script sets QTGMC filter to type 0 (Interlaced) if the
# MediaInfo property 'ScanType' returns 'Interlaced'.
# However if it's not 'interlaced' and the Scantype is Progressive it will set QTGMC to type 1 (Progressive) if the
# MediaInfo property 'ScanType' returns 'Progressive'.

# active project
$p = [ShortcutModule]::p

#global object with miscelenius stuff
$g = [ShortcutModule]::g

if ([MediaInfo]::GetVideo($p.FirstOriginalSourceFile, "ScanType") -eq "Interlaced")
{
$p.Script.SetFilter("Field", "QTGMC Interlaced", "QTGMC(Preset = ""Medium"", InputType=0, SourceMatch=3, Sharpness=0.2, EdiThreads=8)")
}
elseif ([MediaInfo]::GetVideo($p.FirstOriginalSourceFile, "ScanType") -eq "Progressive")
{
$p.Script.SetFilter("Field", "QTGMC Progressive", "QTGMC(Preset = ""Medium"", InputType=1, Sharpness=0.2, EdiThreads=8)")
}

if there still issues remove SourceMatch=3, from the script

You can also try to Upgrade to 2.0 Beta 2 of StaxRip.

[Natty]

will it be possible to have this bath encoding feature again ? :search:

https://forum.doom9.org/showthread.php?p=1815637#post1815637

it was present in old version and was removed in 1.7 i think, it was a very useful feature :thanks:

[Revan654]

will it be possible to have this bath encoding feature again ? :search:

https://forum.doom9.org/showthread.php?p=1815637#post1815637

it was present in old version and was removed in 1.7 i think, it was a very useful feature :thanks:

Stax76 wiped all the code and removed it since it was creating issues with the process system.

I believe you can use scripting to accomplish a similar process.

[Betsy25]

Make Sure you make the changes in both backup folder and the Script folder.

Also You may have to change group policy in PowerShell, MS changed the security back in April locking out most scripts being run. It's a PIA with all the security MS keeps adding.

I just did a test on my PC with the Script and it works.

Filename: AfterSourceLoaded.ps1

# This script handles the AfterSourceLoaded event, remove the underscore from the
# filename in order to enable it. The script sets QTGMC filter to type 0 (Interlaced) if the
# MediaInfo property 'ScanType' returns 'Interlaced'.
# However if it's not 'interlaced' and the Scantype is Progressive it will set QTGMC to type 1 (Progressive) if the
# MediaInfo property 'ScanType' returns 'Progressive'.

# active project
$p = [ShortcutModule]::p

#global object with miscelenius stuff
$g = [ShortcutModule]::g

if ([MediaInfo]::GetVideo($p.FirstOriginalSourceFile, "ScanType") -eq "Interlaced")
{
$p.Script.SetFilter("Field", "QTGMC Interlaced", "QTGMC(Preset = ""Medium"", InputType=0, SourceMatch=3, Sharpness=0.2, EdiThreads=8)")
}
elseif ([MediaInfo]::GetVideo($p.FirstOriginalSourceFile, "ScanType") -eq "Progressive")
{
$p.Script.SetFilter("Field", "QTGMC Progressive", "QTGMC(Preset = ""Medium"", InputType=1, Sharpness=0.2, EdiThreads=8)")
}

if there still issues remove SourceMatch=3, from the script

You can also try to Upgrade to 2.0 Beta 2 of StaxRip.

Tried that, even tried from an installation at C:\StaxRip and I can only conclude that any encoder GUI that relies on that garbage Avisynth+ is simply a waste of time, capable of doing nothing except from setting world records of crashing, thanks anyway.:cool:

BTW, What is the reason the general Avisynth ain't used anymore, perhaps it was too reliable ?

[sgfrisbee]

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.

What dll are missing? The error log shows what dll that will not load and they are in the correct folder with NVEncC64.exe. I did not have this problem with ver. 1.9.0 or 1.8.2

[Revan654]

Tried that, even tried from an installation at C:\StaxRip and I can only conclude that any encoder GUI that relies on that garbage Avisynth+ is simply a waste of time, capable of doing nothing except from setting world records of crashing, thanks anyway.:cool:

BTW, What is the reason the general Avisynth ain't used anymore, perhaps it was too reliable ?

It's works at my end, I'm guessing something it blocking the Script on your PC.

You can Switch the script to VapourSynth as well.

[Revan654]

What dll are missing? The error log shows what dll that will not load and they are in the correct folder with NVEncC64.exe. I did not have this problem with ver. 1.9.0 or 1.8.2

I would just put all the shared ffmpeg dll in the same directory. That will usually address the issue. I don't have a Nvidia GPU on this PC to test the encoder, my Nvidia GPU is installed on my linux system and dotnet doesn't run on linux.

[NikosD]

New versions from Rigaya for everything:
NVenc, QSVenc and even VCEenc.

[Revan654]

# Removed from VCEEnc

--check-vce --avvce

# New Switches:

--avhw --check-hw

Other Two Encoders: Nothing, VCEEnc just renamed the functions, That's all that seemed to changed with regard to StaxRip functions.

[frenchfries]

I think there is an issue with version 2.0 beta 2 and bringing up the quicksync settings.

"------------------------------ Exception ------------------------------

System.Exception: key found twice: --pic-struct
at StaxRip.CommandLineForm..ctor(CommandLineParams params)
at StaxRip.QSVEnc.ShowConfigDialog()
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)"

Hopefully an easy fix for beta 3.

If you'd prefer I can submit a report via guthub but I don't have an account so I'd have to create one.

[Revan654]

I think there is an issue with version 2.0 beta 2 and bringing up the quicksync settings.

"------------------------------ Exception ------------------------------

System.Exception: key found twice: --pic-struct
at StaxRip.CommandLineForm..ctor(CommandLineParams params)
at StaxRip.QSVEnc.ShowConfigDialog()
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)"

Hopefully an easy fix for beta 3.

If you'd prefer I can submit a report via guthub but I don't have an account so I'd have to create one.

Already Been fixed, Still not sure why VS didn't see that and stop the output.

[AntiqueRefrigerator]

Hi. How hard would it be to add long pathname support to Staxrip? I occasionally get errors due to long path names, which requires me to move the file to the a folder such as T:\Temp\File.mkv - This will defeat the errors caused by long path names.

Is the error being caused by Staxrip or MKVToolnix, or Avisynth?

I apologize for not keeping a screenshot or a log of the error. If you insist, I can recreate the error by just putting an MKV into a long filename path for you.

Also thank you for making this program.

Hope you consider! :thanks:

[Revan654]

Hi. How hard would it be to add long pathname support to Staxrip? I occasionally get errors due to long path names, which requires me to move the file to the a folder such as T:\Temp\File.mkv - This will defeat the errors caused by long path names.

Is the error being caused by Staxrip or MKVToolnix, or Avisynth?

I apologize for not keeping a screenshot or a log of the error. If you insist, I can recreate the error by just putting an MKV into a long filename path for you.

Also thank you for making this program.

Hope you consider! :thanks:

:rolleyes:, I seen someone doesn't read the Changelogs. LongPath support was added long ago. But your OS has to support it and you must Enable it. With that being Said I have no idea if MKVTool supports it or not.

Computer Configuration > Administrative Templates > System > Filesystem > Enable NTFS long paths

<longPathAware xmlns="http://schemas.microsoft.com/SMI/2016/WindowsSettings">true</longPathAware>

As you see the Reference is there with support of dealing with long paths. Not going post that code since it's a bit lengthy.

[DaMacFunkin]

Hi, what settings would you recommend for 2160 10 bit HDR hevc to 1080 10 bit HDR hevc with nvenc?
Thanks for any help given.

[NikosD]

Computer Configuration > Administrative Templates > System > Filesystem > Enable NTFS long paths Nice info!
I had the same issue but I was afraid to ask :)

[maupassant]

I have problems when using the AVS noise filter called mClean :

Error Video encoding using x264 2935 (2.0)

Video encoding using x264 2935 failed with exit code: -1073741819 (0xC0000005)

The exit code might be a system error code: The instruction at 0xp referenced memory at 0xp. The memory could not be s.


-------------------- Video encoding using x264 2935 --------------------

C:\STAXRIP\Apps\x264\x264.exe --crf 21 --tune film --output-depth 10 --psy-rd 1:0 --deblock 0:0 --output "C:\File test_temp\File test_out.h264" "C:\File test_temp\File test.avs"




StaxRip.ErrorAbortException: Video encoding using x264 2935 failed with exit code: -1073741819 (0xC0000005)

The exit code might be a system error code: The instruction at 0xp referenced memory at 0xp. The memory could not be s.


-------------------- Video encoding using x264 2935 --------------------

C:\STAXRIP\Apps\x264\x264.exe --crf 21 --tune film --output-depth 10 --psy-rd 1:0 --deblock 0:0 --output "C:\File test_temp\File test_out.h264" "C:\File test_temp\File test.avs"



at StaxRip.Proc.Start()
at StaxRip.x264Enc.Encode(String passName, String commandLine, ProcessPriorityClass priority)
at StaxRip.x264Enc.Encode()
at StaxRip.GlobalClass.ProcessVideo()
at System.Threading.Tasks.Parallel.<>c__DisplayClass4_0.<Invoke>b__0()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at StaxRip.GlobalClass.ProcessJob(String jobPath)

[Revan654]

snip

mClean on AVS side has always been PIA, It's always been one way or the other, it works or it doesn't. Try the VS version it works allot better.

I didn't create the AVS Script Not sure what the core issue is, It would be better to ask in the AVS mClean Thread. Maybe the Dev can pin point what the issue is if he's still around.

[bin.n2f]

hi

is there a way i can adjust staxtip's interface
iam using dark theme windows
https://ibb.co/g6JnCXr
also in high contrast the progress text also hard to visible
:thanks:

[maupassant]

mClean on AVS side has always been PIA, It's always been one way or the other, it works or it doesn't. Try the VS version it works allot better.


Thanks. But there's no mClean for VS ? Unless you know of something equivalent ?

[suprasaiyan123]

could someone please provide some good settings to use with Hable, or Reinhard HDR>SDR conversion? Im having an issue with these two filters being unable to preserve details with lighter colors, where as MADVR looks absolutely gorgeous while preserving white detail, and also having deep colors. Here is an example, http://https://imgur.com/a/kEdOlGU (https://imgur.com/a/kEdOlGU) any help is appreciated! thanks

[Khun_Doug]

Maupassant, I too am a big fan of mClean. I have a fondness for older movies, including B&W that date back into the late 1930's and forward. Obvious with these, even being digitized, they just have a lot of noise. The B&W films tend to have contrast variations in the scenes, including areas such as faces. None of the filters I tried was able to handle these artifacts as well as mClean. SMderain is the closest.

I tried the VS port of mClean and find it unusable. My observations are that the VS port is considerably slower and consumes a tremendous amount of CPU. The output was noticeably soft, almost as though everything was blurred because it was so soft. I use the default settings, same as I do for the AVS version. It saturated all cores on the PC and then was slow to step forward screen by screen. I'm using an I7-6850K with 6 cores, 12 threads. The VS port is not usable for me.

My suggestion is to use something like AVSPmod (I think that is the name of the editor) and build your own script there. Once you have the script done, use something like Virtualdub or Virtualdub2 to write the output file as an uncompressed (lossless) file. Yes, the output file will be large, perhaps 150 GB or more. But then you can process that using Staxrip and do a 2 pass or even 3 pass encode. In the instances where I just couldn't get Staxrip to handle the initial steps, I used this approach and it worked well.

If you need some sample AVS scripts, I can provide some examples to get you going. All the filters and plug-ins are freeware.

[Revan654]

Thanks. But there's no mClean for VS ? Unless you know of something equivalent ?

Yes there is. It's Already part of the Context Menu.

https://i.imgur.com/PzkDIBD.png

[Revan654]

I tried the VS port of mClean and find it unusable. My observations are that the VS port is considerably slower and consumes a tremendous amount of CPU. The output was noticeably soft, almost as though everything was blurred because it was so soft. I use the default settings, same as I do for the AVS version. It saturated all cores on the PC and then was slow to step forward screen by screen. I'm using an I7-6850K with 6 cores, 12 threads. The VS port is not usable for me.


There been a few changes to mClean, I tried to get mClean into StaxRip when the script was first released. It would just crash StaxRip (Since the Script crashed VS forcing VS to kill it's Process). It was only recently added (about a month ago). Since it's finally in a state where it's usable.

mClean is actually more Usable in VS then AVS, Since Half the time mClean Script would just fail to load the dll recources. It's why you get a black screen or access error at times when using mClean.

I'm using an I7-6850K with 6 cores, 12 threads

It's more dependent on System Memory & the Ghz feq of the CPU then the Core count(The Core Count Does Help, at some point your returns can become moot due to coding of the Encoder).
It's why you see an i7 out perform an i9 in Encoding area.

Certain Software Encoders only Support up to x amount of Cores. EX: HandBrake with Libs they use, Max usage is 6 Cores. Allot of features of HandBrake are just stuck in the past.

StaxRip Does not lock the core usage.

Once you have the script done, use something like Virtualdub or Virtualdub2 to write the output file as an uncompressed (lossless) file. Yes, the output file will be large, perhaps 150 GB or more.

No Need to output into to uncompressed, Just use VDUb FrameServer Feature and import the vdr file into StaxRip.

It Fully works with StaxRip(Including Audio (Need to Enable Audio in the AVS Filter)).

-----

vdr is mainly designed for AVS Side, Since VS doesn't have any good audio filters to work with the Script.

Lastly don't forget VS has the ability to import AVS Scripts\filters into VS Script.

--------

Since Every source is unique you have to play around with the filters to see whats works.

Allot of times it becomes a Push & Pull situation. You may clean up one area but adds issues to a different area. Like Sharpeners adding Aliasing issues.

Don't be afraid to Convert it to 16Bit and use Dither Filters.

[Revan654]

hi

is there a way i can adjust staxtip's interface
iam using dark theme windows
https://ibb.co/g6JnCXr
also in high contrast the progress text also hard to visible
:thanks:

Interface yes, I think you mean is there a way to add Theme colors to StaxRip. Answer: No. Since Coding would need to be altered across all the forms and alter the Colors in design mode for each form.

VS 2017 Darker Color Forms don't look that great, Not without using custom Draw feature.

[maupassant]

Yes there is. It's Already part of the Context Menu.

https://i.imgur.com/PzkDIBD.png

Not in mine.
I'm using StaxRip 2.0 Beta 2 with new Dotnet.

[maupassant]

Maupassant, I too am a big fan of mClean. I have a fondness for older movies, including B&W that date back into the late 1930's and forward. Obvious with these, even being digitized, they just have a lot of noise. The B&W films tend to have contrast variations in the scenes, including areas such as faces. None of the filters I tried was able to handle these artifacts as well as mClean. SMderain is the closest.

I tried the VS port of mClean and find it unusable. My observations are that the VS port is considerably slower and consumes a tremendous amount of CPU. The output was noticeably soft, almost as though everything was blurred because it was so soft. I use the default settings, same as I do for the AVS version. It saturated all cores on the PC and then was slow to step forward screen by screen. I'm using an I7-6850K with 6 cores, 12 threads. The VS port is not usable for me.

My suggestion is to use something like AVSPmod (I think that is the name of the editor) and build your own script there. Once you have the script done, use something like Virtualdub or Virtualdub2 to write the output file as an uncompressed (lossless) file. Yes, the output file will be large, perhaps 150 GB or more. But then you can process that using Staxrip and do a 2 pass or even 3 pass encode. In the instances where I just couldn't get Staxrip to handle the initial steps, I used this approach and it worked well.

If you need some sample AVS scripts, I can provide some examples to get you going. All the filters and plug-ins are freeware.

Indeed, mClean is great for old B&W movies. I use it in combination with AutoGain (with AutoWhite included). It can perform miracles. I'll keep your offer in mind. Thank you. :)

[Khun_Doug]

I stopped using the newer builds of StaxRip and have stayed with 1.7.0.6 for handling the encodes that need mClean. I updated all the plug-ins to the latest, including choosing the options with AVX2 support, when that is available. I only use the 64 bit version of AVSPmod and VirtualDub2, and obviously StaxRip is 64 bit. I did forget to mention that I also use PreFetch of 8. That value will need to change depending on your CPU. That moves it along quite nicely. This is all done with AVS. What I noticed with the VS version of mClean was it immediately saturated all processors and the screens rendered so slow, perhaps 1 1/2 per second. I want to emphasize the marked difference in defaults in VS to AVS. In AVS you can hold the step forward button and the video updates fast enough that it looks like a motion picture. The same evaluation in VS renders updates so slowly, all while saturating the CPU. And the filter completely softened the image. The ability to see individual strands of hair disappears, that's how much detail is lost. And this test was done within the last month, and using StaxRip 2.0.0.0. Incidentally, I am a Python code writer so I know my version of Python is working properly.

I just figure that until I need HDR support I will stay with rev 1.7.0.6 and maintain the plug-ins myself. It's easy enough to update x265. Since the filters I need are already working, there isn't any reason to fuss with it. I'll let version 2.xxxx move along until I move into stuff that needs HDR and then revisit the issues at that point.

I will say I am pleased to no end to see StaxRip staying alive. The effort is greatly appreciated.

[Revan654]

Not in mine.
I'm using StaxRip 2.0 Beta 2 with new Dotnet.

I suggest deleting the Settings and starting Fresh.

1.7 & 1.8+ Settings File are not compatible with one another. Since they use two completely different names.

FYI, Don't use the site attachment. It needs approval before it shows up which take a long time.

[maupassant]

Lastly don't forget VS has the ability to import AVS Scripts\filters into VS Script.



Well, I don't know how to do that.
I'd really like to have an AutoGain/AutoWhite filter for VS if it's easy to create. But I don't want to abuse of your help. Thanks.

[imhh11]

could someone please provide some good settings to use with Hable, or Reinhard HDR>SDR conversion? Im having an issue with these two filters being unable to preserve details with lighter colors, where as MADVR looks absolutely gorgeous while preserving white detail, and also having deep colors. Here is an example, http://https://imgur.com/a/kEdOlGU (https://imgur.com/a/kEdOlGU) any help is appreciated! thanks


Same issues on my end. I tried to modify the default setting which gave me better contrast but madvr still output WAY better picture (colors, contrast, highlight details).

Unless I'm doing something wrong, I'm highly disappointed by the HABLE or Reinhard curve.

i get better result with this setting but still no good:
DGHable(1.2, 0.15, 0.42, 0.10, 0.20, 0.02, 0.30, 11.2)

To me, it looks like hable and reinhard are trying to make it look like the 1080p SDR BD while madvr is trying to reproduce the 4k HDR BD.
so if anyone know settings that could get closer result to madvr, i would like to know as well .

thanks

[DaMacFunkin]

Hi, again does anybody have settings to convert 2160hdr to 1080hdr with nvenc please?
Thank you.

[videoh]

Same issues on my end. I tried to modify the default setting which gave me better contrast but madvr still output WAY better picture (colors, contrast, highlight details).

Unless I'm doing something wrong, I'm highly disappointed by the HABLE or Reinhard curve.

i get better result with this setting but still no good:
DGHable(1.2, 0.15, 0.42, 0.10, 0.20, 0.02, 0.30, 11.2)

To me, it looks like hable and reinhard are trying to make it look like the 1080p SDR BD while madvr is trying to reproduce the 4k HDR BD.
so if anyone know settings that could get closer result to madvr, i would like to know as well .

thanks Can you post a link to an unprocessed sample source stream that we can use to investigate your issue?

[Revan654]

Well, I don't know how to do that.
I'd really like to have an AutoGain/AutoWhite filter for VS if it's easy to create. But I don't want to abuse of your help. Thanks.

That's why there help files with the more complex filters. AutoGain from AVS can already be used in VS.

I will not going to be building any filters, Filters are built outside of StaxRip Code and uses VS or AVS FrameWork. There already more then you will ever use, In Context and off Context.

[Zetti]

MKVToolNix v29.0.0 is released.

[Revan654]

Hi, again does anybody have settings to convert 2160hdr to 1080hdr with nvenc please?
Thank you.

For True HDR10 containing all the Metadata NVEnc can not be used, Due to the missing encoding Flags.

You need to use x265.

[Revan654]

*One Small Update* Due to latest Update to VS 2017, It's very buggy which is creating Freezing and such. Going have to wait until there a fix before I add more code, Since I keep losing the work I have done. It might be a little bit longer until the next release due to MS buggy release.

Already Re-installed VS 2017 twice, Both times it was the same results. I really hate these forced updates. 15.9.2 was working great now 15.9.3 is a mess.

[Revan654]

I suggest Upgrading to version 29, Since version 28 had some audio breaking bugs.

[sgfrisbee]

On version. 2.0 now

First Problem:
I'm having problems with MSharpen in ver. 1.8.2, 1.9.0 and 2.0.
I get this error:

Cannot load file '******/msharpen.dll' Platform returned code 126
The specified module could not be found.

I did not have this problem on ver. before 1.8


Second Problem:

The same thing is happening with VSFilterMod.dll

Cannot load file '******/VSFilterMod.dll' Platform returned code 126
The specified module could not be found.



Thanks for any help that you can give me on this.

[Revan654]

On version. 2.0 now

First Problem:
I'm having problems with MSharpen in ver. 1.8.2, 1.9.0 and 2.0.
I get this error:

Cannot load file '******/msharpen.dll' Platform returned code 126
The specified module could not be found.

I did not have this problem on ver. before 1.8


Second Problem:

The same thing is happening with VSFilterMod.dll

Cannot load file '******/VSFilterMod.dll' Platform returned code 126
The specified module could not be found.



Thanks for any help that you can give me on this.

MSharpen hasn't been updated since 2013, the dll is exactly the same.

Don't Forget all dll must be run in 64bit. Same goes for VSFilterMod. Many of these filters are AVX based.

Platform returned code 126
The specified module could not be found.

This means your hardware isn't supported by the dll file.

Not sure if the C++ runtimes will help or not

See: http://avisynth.nl/index.php/MSharpen

[sgfrisbee]

MSharpen hasn't been updated since 2013, the dll is exactly the same.

Don't Forget all dll must be run in 64bit. Same goes for VSFilterMod. Many of these filters are AVX based.



This means your hardware isn't supported by the dll file.

Not sure if the C++ runtimes will help or not

See: http://avisynth.nl/index.php/MSharpen



I had no problem with MSharpen or VSFilterMod on Staxrip 1.8.0.0

OS is Win 10 Pro 64bit, same hardware and software when I had ver 1.8.0.0 running.

On the website about MSharpen I did not have Microsoft Visual C++ 2012 Redistributable Package 86/64 installed. Installed both 86/64
and MSharpen is now working. Do not know why I had Microsoft Visual 2012 installed during Staxrip 1.8.0.0 but not on my computer when I went to 2.0.0.0

VSFilterMod ver 1.1.9.0 is still not working.


Thanks for any help that you can give me on this.

[Revan654]

a word of warning to Everyone on Windows. Don't Update to latest Major Update(November). It has nothing but Problems, It will not even allow me to install my Nvidia Drivers. Intel QSV doesn't even work.

[Revan654]

I had no problem with MSharpen or VSFilterMod on Staxrip 1.8.0.0

OS is Win 10 Pro 64bit, same hardware and software when I had ver 1.8.0.0 running.

On the website about MSharpen I did not have Microsoft Visual C++ 2012 Redistributable Package 86/64 installed. Installed both 86/64
and MSharpen is now working. Do not know why I had Microsoft Visual 2012 installed during Staxrip 1.8.0.0 but not on my computer when I went to 2.0.0.0

VSFilterMod ver 1.1.9.0 is still not working.


Thanks for any help that you can give me on this.

There been allot of Changes to the Windows OS Since 1.8.2.0. Those files havn't been touched since 1.8, If they worked back then, then they should work now. If there issues then the problem lies with Windows.

Check the App Manager and check under runtimes(ignore Python) but make sure you have all the other runtimes installed.

Under Apps -> FFTW Make sure you have this installed in your System Directory.

VSFilterMod Build Date: 2016, it's untouched.

You could try the new Forked version of VSFilter: https://github.com/sorayuki/VSFilterMod/releases

I have no idea what specs they require.

[sgfrisbee]

There been allot of Changes to the Windows OS Since 1.8.2.0. Those files havn't been touched since 1.8, If they worked back then, then they should work now. If there issues then the problem lies with Windows.

Check the App Manager and check under runtimes(ignore Python) but make sure you have all the other runtimes installed.

Under Apps -> FFTW Make sure you have this installed in your System Directory.

VSFilterMod Build Date: 2016, it's untouched.

You could try the new Forked version of VSFilter: https://github.com/sorayuki/VSFilterMod/releases

I have no idea what specs they require.

All is were it should be. The VSFilterMod I have now is build 2016 ver 1.1.9.0 size 964 KB.

Did a google search and I do have sorayuki VSFilterMod now but not replaced the old one. Sorayuki VSFilterMod is ver 1.1.92 size 3879 KB.

Will give it a try, thanks for all the help

[suprasaiyan123]

Can you post a link to an unprocessed sample source stream that we can use to investigate your issue?

Here you go https://www.sendspace.com/file/es0lwp The issue can be seen here by my previous post https://imgur.com/a/kEdOlGU I believe I and imhh11 are having the same issue where the highlights are blown out of proportion, and no amount of playing with either the Hable or Reinhard curve can preserve details in highlights. Please let us know what you find, or if you have a fix for the issue, thanks!!

[Atak_Snajpera]

Here you go https://www.sendspace.com/file/es0lwp The issue can be seen here by my previous post https://imgur.com/a/kEdOlGU I believe I and imhh11 are having the same issue where the highlights are blown out of proportion, and no amount of playing with either the Hable or Reinhard curve can preserve details in highlights. Please let us know what you find, or if you have a fix for the issue, thanks!!

DGHable(exposure=1.0)

[NikosD]

a word of warning to Everyone on Windows. Don't Update to latest Major Update(November). It has nothing but Problems, It will not even allow me to install my Nvidia Drivers. Intel QSV doesn't even work. I have done a clean install since late September, before the official release on my Haswell system and on middle October on Skylake system at work.

Maybe that's why I had problems with QSVEnc but I have no time to fix the problems.

But I see none of the problems mentioned at various sites from the beginning of this release, while on previous version of April 2018 update, the Chrome hadn't worked fine for me ever.

The frozen screen issue using Chrome on April 2018 update was never solved at least for me.

October 2018 update works just fine.

[Arbelisk]

Hey guys. I'm fairly new to using x265 and NVEnc encoding. I noticed when trying to convert a 4K HDR video, that it shows Chroma 4.2.0 (type 2). But the encoded file does not have that same tag. Is there a way to get type2 to the encoded video? Also, @Revan654, you mentioned that HDR would not work with NVEnc encoding, but I have used it before and it seemed to display correctly on my TV. Must be something I didn't understand. Can you clarify a bit? Thanks.

[sneaker_ger]

For both x265 and NVEnc there is the --chromaloc option.

https://x265.readthedocs.io/en/default/cli.html#cmdoption-chromaloc
https://github.com/rigaya/NVEnc/issues/50

[imhh11]

Hey guys. I'm fairly new to using x265 and NVEnc encoding. I noticed when trying to convert a 4K HDR video, that it shows Chroma 4.2.0 (type 2). But the encoded file does not have that same tag. Is there a way to get type2 to the encoded video? Also, @Revan654, you mentioned that HDR would not work with NVEnc encoding, but I have used it before and it seemed to display correctly on my TV. Must be something I didn't understand. Can you clarify a bit? Thanks.


--chromaloc 2

Nvenc is also working fine with all the right hdr metadata / color space on my end. Of course, some metadata need to be set manually but its working.

[Revan654]

Hey guys. I'm fairly new to using x265 and NVEnc encoding. I noticed when trying to convert a 4K HDR video, that it shows Chroma 4.2.0 (type 2). But the encoded file does not have that same tag. Is there a way to get type2 to the encoded video? Also, @Revan654, you mentioned that HDR would not work with NVEnc encoding, but I have used it before and it seemed to display correctly on my TV. Must be something I didn't understand. Can you clarify a bit? Thanks.

I have no idea what TV you have nor the type it playsback.

To meet all the HDR10 Specs you must have all the correct Metadata(They Change from time to Time), Which it doesn't. It's slowly being Added, Just has to wait for Nvidia to all all the Functions to the SDK.

HDR get's very complex as you headed into the different types.

to Name some of the Flags:

-no-open-gop
-hdr
-aud
-hrd
-repeat-headers
-Matrix BT.2020 NC
-transfer ST.2084
-prime BT.2020
-Master-Color-Display (Must set value to Source color)
-Range limited (This is Done for TV viewing)
-MaxFall/CLL
-10Bit(Min)
-Profile Main10
-vui-hrd-info(Becomes Enabled with HRD Enabled)
-vui-timing-info

+ Ingest

[suprasaiyan123]

DGHable(exposure=1.0) Thanks man, that helped quite a bit, seems like every movie requires a different amount of exposure to look ''normal'' although it still seems as though madvr is able to preserve highlights and make the colors appear slightly more vibrant than what hable and reinhard curves are capable of.

[Atak_Snajpera]

Thanks man, that helped quite a bit, seems like every movie requires a different amount of exposure to look ''normal'' although it still seems as though madvr is able to preserve highlights and make the colors appear slightly more vibrant than what hable and reinhard curves are capable of.

Default value 2.0 is too strong according to my tests

1.0
https://i.imgsafe.org/bb/bb8c4ec4f2.png
https://i.imgsafe.org/bb/bb8deaea7a.png

Default 2.0
https://i.imgsafe.org/bb/bb8c8e1b48.png
https://i.imgsafe.org/bb/bb8d6e76de.png

[Revan654]

Default value 2.0 is too strong according to my tests

1.0
https://i.imgsafe.org/bb/bb8c4ec4f2.png
https://i.imgsafe.org/bb/bb8deaea7a.png

Default 2.0
https://i.imgsafe.org/bb/bb8c8e1b48.png
https://i.imgsafe.org/bb/bb8d6e76de.png

This is why ColorGrading should be done for each source title.

A Proper Setup Should be Used, Since AVS Will never be able to Reproduce what a ColorWheel / Scope along with the other tools can Do.

https://static1.squarespace.com/static/54a8c619e4b0d05e1aae752f/t/58137a832994cac66066362c/1477671584260/How+to+Fix+RGB+Separated+Clipped+Whites+with+a+Serial+Nodes?format=1500w

https://static1.squarespace.com/static/54a8c619e4b0d05e1aae752f/t/5813782a2e69cf83de386b8e/1477671008413/Potential+peak+brightnesses+vs+graded+peak+brightness+for+a+series+of+shots?format=1500w

[Zetti]

MediaInfo v18.12 is released.

[Andy]

I have no idea what TV you have nor the type it playsback.

To meet all the HDR10 Specs you must have all the correct Metadata(They Change from time to Time), Which it doesn't. It's slowly being Added, Just has to wait for Nvidia to all all the Functions to the SDK.

HDR get's very complex as you headed into the different types.

to Name some of the Flags:

-no-open-gop
-hdr
-aud
-hrd
-repeat-headers
-Matrix BT.2020 NC
-transfer ST.2084
-prime BT.2020
-Master-Color-Display (Must set value to Source color)
-Range limited (This is Done for TV viewing)
-MaxFall/CLL
-10Bit(Min)
-Profile Main10
-vui-hrd-info(Becomes Enabled with HRD Enabled)
-vui-timing-info

+ Ingest

Hello! How do I find max cll and max fall when mediainfo is not displayed? Thank you.

[Yanak]

Hello all,
long time since my last post on the forum, way too busy with real life stuff... good to see Revan654 taking care of Staxrip, really nice.

So I'm trying to catch up with this and still for now trying to add all the customized stuff i had on my old version of Staxrip into the last v2 Beta, far from finished since i have heavily modified one full of custom templates, event commands, powershell script or custom menus etc... Will take a while before i get all done.


All this said there is already a few things i noticed that i would like to report :

- NPM thumbnailer seems broken, for exampel this is the settings and results i get :
https://imgur.com/a/goiFkYp
(Title edited & blurred images on purpose .. )

Only one column created,
also the selected path is not respected, it creates the picture on the video folder, not where i asked it to be.
By the way: what is the setting "Depth of each shot" doing please ? maybe a stupid question or my English failing me but i don't get what this settings is supposed to do :/

- I saw a few posts speaking about the reactivity of the program, i confirm that i too get some lag and it feels sluggish compared to the original Staxrip where all works in a blink like preview etc, using version with the dotnet 4.7 on a win7 x64 machine if it makes any difference.


- I saw that: "- Added Support for RawSourcePlus for Avisynth and RawSource for VapourSynth. Default Pixel_type is set to YUV420P10 (aka P010)."

As far as i know this plugin doesn't work well with 10 Bits material, there is 2 issues open about this on the github of the plugin : https://github.com/chikuzen/RawSource_2.6x/issues

About this source filer : i was asked by PM many months ago if i could create a source filter to work with raw files, I came up with a dynamic solution, dynamic because if we use something like a .yuv file for input mediainfo can't read anything from it and then the current filter you use doesn't work :

RawSourcePlus("%source_file%", fpsnum=%media_info_video:FrameRate_Num%, fpsden=(%media_info_video:FrameRate_Den%)
Since mediaInfo cannot read anything no fps infos, also seems like the pixel type is missing ( unless it's myself missing something here), anyways my solution at that time was this filter :

Raw_Source =
RawSourcePlus("%source_file%", $select:msg:Select Video Resolution;3840x2160|width=3840,height=2160;2560x1440|width=2560, height=1440;1920x1080|width=1920, height=1080;1280x720|width=1280,height=720$, \
$select:msg:Select ColorSpace;YV12|pixel_type="YV12";YUV420p8|pixel_type="YUV420p8";YUV420p10|pixel_type="YUV420p10"$, \
$select:msg:Select a frame rate;23.976 FPS|fpsnum=24000, fpsden=1001;24 FPS|fpsnum=24, fpsden=1;25 FPS|fpsnum=25, fpsden=1;29.970 FPS|fpsnum=30000, fpsden=1001;30 FPS|fpsnum=30, fpsden=1;50 FPS|fpsnum=50, fpsden=1;59.940 FPS|fpsnum=60000, fpsden=1001;60 FPS|fpsnum=60, fpsden=1;120 FPS|fpsnum=120, fpsden=1$)
# ConvertToYV12()

The last line # ConvertToYV12() is just to trick Staxrip as it was adding this convertto automatically at the end of the source filter, adding it myself into the source filter escaped like this with #, is enough to trick Staxrip and nullify it.

This source filter comes with a few popups asking for the most common video resolution, FPS and pixel type, YUV420p10 is on the list of the possibilities but like i said it doesn't work, example taking one of the videos from here in 10 bits YUV/RAW :
http://ultravideo.cs.tut.fi/#testsequences ex: the dog one in 4k 10 bits Yuv RAW, direct link : http://ultravideo.cs.tut.fi/video/ShakeNDry_3840x2160_120fps_420_10bit_YUV_RAW.7z ( very big file to download and even more big once uncompressed )

Works nicely with 8 bits .yuv/RAW ones, for example the dog one in 8 Bits 1080p 120 fps YUV / Raw : http://ultravideo.cs.tut.fi/video/ShakeNDry_1920x1080_120fps_420_8bit_YUV_RAW.7z

To automate the source filter i have this in Settings > Source Filters > Avisynth > yuv, raw = Raw_Source


Had started to look into Staxrip code when Stax76 decided to stop it and adding some of my stuff into it, gave up on this as i did not really had time to dive into all this and have not touched it since a few months now, and while I'm really not a coder, just following the code logic i had made changes to the code source at this time, needs to be reviewed but who knows, it might help :

in misc.vb i added this in "Public Class FileTypes" :
Shared Property YuvRawSources As String() = {"yuv", "raw"}

and in packages.vb
Add(New PluginPackage With {
.Name = "RawSourcePlus",
.Filename = "RawSourcePlus_x64.dll",
.WebURL = "https://github.com/chikuzen/RawSource_2.6x/releases",
.Description = "Raw (.yuv .raw) source filter",
.AvsFilterNames = {"RawSourcePlus"},
.AvsFiltersFunc = Function() {New VideoFilter("Source", "RawSourcePlus",
$"RawSourcePlus(""%source_file%"", $select:msg:Select Video Resolution;3840x2160|width=3840,height=2160;2560x1440|width=2560, height=1440;1920x1080|width=1920, height=1080;1280x720|width=1280,height=720$, \
$select:msg:Select ColorSpace;YV12|pixel_type=""YV12"";YUV420p8|pixel_type=""YUV420p8"";YUV420p10|pixel_type=""YUV420p10""$, \
$select:msg:Select a frame rate;23.976 FPS|fpsnum=24000, fpsden=1001;24 FPS|fpsnum=24, fpsden=1;25 FPS|fpsnum=25, fpsden=1;29.970 FPS|fpsnum=30000, fpsden=1001;30 FPS|fpsnum=30, fpsden=1;50 FPS|fpsnum=50, fpsden=1;59.940 FPS|fpsnum=60000, fpsden=1001;60 FPS|fpsnum=60, fpsden=1;120 FPS|fpsnum=120, fpsden=1$)
#ConvertToYV12()")}})

In mainForm.vb at " Function ShowSourceFilterSelectionDialog(inputFile As String) As VideoFilter " :
If inputFile.Ext.EqualsAny("yuv", "raw") Then AddSourceFilters({"RawSourcePlus"}, filters)

also in ApplicationSettings.vb :

If Check(AviSynthFilterPreferences, "AviSynth Source Filter Preferences", 1) Then
AviSynthFilterPreferences = New StringPairList
AviSynthFilterPreferences.Add("default", "FFVideoSource")
AviSynthFilterPreferences.Add("264 h264 avc", "LWLibavVideoSource")
AviSynthFilterPreferences.Add("265 h265 hevc hvc", "LWLibavVideoSource")
AviSynthFilterPreferences.Add("d2v", "MPEG2Source")
AviSynthFilterPreferences.Add("dgi", "DGSource")
AviSynthFilterPreferences.Add("dgim", "DGSourceIM")
AviSynthFilterPreferences.Add("mp4 m4v mov", "LSMASHVideoSource")
AviSynthFilterPreferences.Add("ts m2ts mts m2t", "LWLibavVideoSource")
AviSynthFilterPreferences.Add("wmv", "DSS2")
AviSynthFilterPreferences.Add("vdr", "AviSource")
AviSynthFilterPreferences.Add("bmp ebmp jpeg jpg png tga tif tiff", "ImageSource")
AviSynthFilterPreferences.Add("gif", "FFVideoSource")
AviSynthFilterPreferences.Add("yuv raw", "RawSourcePlus")
End If
** Note that on this one there is also some code for .gif input support with FFvideosource (only one accurate for the gif's FPS's detection afaik) + support for static pictures as source files using imagesource as source filter, i had all stuff done for those too since i use them quite a bit myself, not sure if it may interest you or someone else but if interested let me know i'll put the modified code here too for those new source filters.
( plus I'll have to take time and look back at all this but pretty sure i had also modified the code to insert a few simple or avisynth native filters like mirror, rotate, reverse, adding SMPTE and other timers + a few quick other overlay's and such but it's been month since i touched this now :/ )

I think i forgot nothing, well i hope... Like i said i am not a coder, just following the rest of the coding logic so it needs a check from expert eyes but it worked once compiled if i remember well :p


- I saw on the changelog : "Added a new Marco to the list. Script_files%"
It is not listed in the macros list apparently, only the already existing [B%]Script_file%[/B , not sure if active or not as i have not tested something with it yet, question is what this macro do please ? Select all powershell scripts to list them somewhere ?


- And finally while on the macros subject if i may i would like to make a request please :

a new macro for the muxer profiles, we can have let's say 3 different .mp4 extension muxer profiles but all that is possible to do right now is use the extension for macros... and all those muxer profiles have the same of course, not possible to use the muxer profiles names directly as macro, that is something that i always missed in Staxrip, a macro being the muxer profile name will be a nice addition to extend even more the customization and possibilities of this nice tool :)


- Btw speaking of muxer profiles, i don't know if it is supposed to be like this or not but seems like we cannot edit the MKV muxer profiles created or cloned, it is like this since ages in old Staxrip but don't know if it is supposed to be that way, until now i bypass this by making a new template with settings saved for each new MKV muxer profile i need/want.

- One very last thing, since you added av1 encoder into Staxrip : last versions of MP4Box support av1 & VP9 : https://gpac.wp.imt.fr/2018/10/27/official-av1-and-vp9-support-in-gpac/ Not sure if you was aware of this but it opens a few more possibilities ;)

That's all for now, still have loads of stuff to transpose from my old heavily customized version into this new one before starting to test a bit more tho, will take a while before i finish sadly.

Thank you very much for the hard work on this and already sorry for the very long post and all that stuff i posted here

[Revan654]

Hello all,
long time since my last post on the forum, way too busy with real life stuff... good to see Revan654 taking care of Staxrip, really nice.

So I'm trying to catch up with this and still for now trying to add all the customized stuff i had on my old version of Staxrip into the last v2 Beta, far from finished since i have heavily modified one full of custom templates, event commands, powershell script or custom menus etc... Will take a while before i get all done.


All this said there is already a few things i noticed that i would like to report :

- NPM thumbnailer seems broken, for exampel this is the settings and results i get :
https://imgur.com/a/goiFkYp
(Title edited & blurred images on purpose .. )



Only one column created,
also the selected path is not respected, it creates the picture on the video folder, not where i asked it to be.
By the way: what is the setting "Depth of each shot" doing please ? maybe a stupid question or my English failing me but i don't get what this settings is supposed to do :/



Not Sure what you mean by NPM, If you Mean MTN

MTN just might support your CPU or something. It works at my end.

Read About all the Details at the Project Page: https://github.com/Revan654/movie-thumbnailer-mtn


- I saw a few posts speaking about the reactivity of the program, i confirm that i too get some lag and it feels sluggish compared to the original Staxrip where all works in a blink like preview etc, using version with the dotnet 4.7 on a win7 x64 machine if it makes any difference.



All Tests are Done on Windows 10 x64 with i7 2600k, 8 Gigs of Ram with Standard 7200rpm Drive.

Seems like there might be issues with newer hardware not getting along with older code.


- I saw that: "- Added Support for RawSourcePlus for Avisynth and RawSource for VapourSynth. Default Pixel_type is set to YUV420P10 (aka P010)."



As far as i know this plugin doesn't work well with 10 Bits material, there is 2 issues open about this on the github of the plugin : https://github.com/chikuzen/RawSource_2.6x/issues

About this source filer : i was asked by PM many months ago if i could create a source filter to work with raw files, I came up with a dynamic solution, dynamic because if we use something like a .yuv file for input mediainfo can't read anything from it and then the current filter you use doesn't work :



Works Fine with Sources I loaded, That included Uncompressed HDR 10Bit formats.




- I saw on the changelog : "Added a new Marco to the list. Script_files%"
It is not listed in the macros list apparently, only the already existing [B%]Script_file%[/B , not sure if active or not as i have not tested something with it yet, question is what this macro do please ? Select all powershell scripts to list them somewhere ?



The Script_Files returns value in Quotes, There was a bunch of code that was lost, that could never be recovered, It could been part of that.

It was added due to Windows FileSystem not liking certain paths and required quotes.


------

StaxRip is just starting to show it's age, As times goes on and newer code for dotnet is Released it will become slower. GUI just will not be as fast as a GUI coded in C+.

Object Code vs Machine Code.

Getting to the point it might just be worth creating New Software from the ground up.

[Trench]

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.

Just to briefly follow-up, in case someone does search on this symptom and wonders what the cause was: The channel layout generated for the same 5.1 FLAC input -- using the later FFMPEG build -- when requesting "keep original channels" (-ac omitted from command line) was different and apparently an invalid channel layout.

The FLAC has 5.1(side) layout ("L R C LFE Ls Rs"), and with the later FFMPEG being invoked for AAC to "keep original channels", the AAC output ended up with "L R C Cb Rls Rb". This in turn appeared to cause issues in the LAV Splitter/Audio selection of tracks and resulted in the "frozen" playback symptoms.

So I needed to pay closer attention to the output channel map being created, because it was not already "correct by default" in this case, even though "I was invoking FFMPEG in exactly the same way with exactly the same input" through StaxRip.

That's all, nothing else to see here.

[Yanak]

Hi,

Yes it's MTN , was a typo from my part, I used the .exe in link you provided and made various tests in command line, no problems there beside that the timestamps are incorrect, apparently reported in github and issue closed but not fixed it seems : https://github.com/Revan654/movie-thumbnailer-mtn/issues/1

Small test on a 15mn colorbars video having a timer displayed, so we can compare times stamped on each tile vs real times :
cmd:
mtn -c 4 -j 100 -h 240 -w 1920 -X -z -P --shadow=2 -g 6 -L 4:2 "H:\colorbars.mp4" -O "H:/"
result: https://i.imgur.com/hnFcF0d.jpg
after tile 7 all timestamps are messed up

cmd :
mtn -c 4 -r 8 -j 100 -h 240 -w 1920 -X -z -P --shadow=2 -g 6 -L 4:2 "H:\colorbars.mp4" -O "H:/"
result : https://i.imgur.com/Hcgtxc5.jpg
after tile 9 the timestamps are wrong

and Using the -Z command for more accurate timing :
mtn -c 4 -j 100 -h 240 -w 1920 -X -Z -P --shadow=2 -g 6 -L 4:2 "H:\colorbars.mp4" -O "H:/"
result : https://i.imgur.com/YdxHrhm.jpg
same thing, timestamps wrong after 7th tile


- So in Staxrip the parameters :
"Height of Each Shot" = minimum height of each tile like the name suggest, then "Width of Each Shot" suggests that it's the width of each tile, but nope, it's the total width of the final image it seems since such parameter does not exist in the .exe... mis-wording i guess.

Also in Staxrip we cannot set the total width ("Width of Each Shot" parameter) to be higher than 1280px, 1280px seems hard coded as the max width for some reasons, using the .exe in command line we can set 1920px width for example like in examples above.

The output path : like i said inside staxrip this does not work, no matter what i set for the output path the thumbnailer will always create the image where the video is located, output path using the .exe in command line works.

I'll probably create my own custom menu associated with a custom command line directly in Staxrip, well that is if i find out why the timestamps do not work, rather pointless to use it if timestamps on the tiles are messed up, but the various parameters for customization of the final image are interesting, full customization of the colors/fonts etc is nice.



- For RawSourcePlus plugin :
This plugin is interesting to use for things like .YUV, .2VUY extension files for example, files where there is no header infos, see also this page : http://avisynth.nl/index.php/RawSource26
You can test the tiny 2VUY Test.rar sample file too http://avisynth.nl/index.php/RawSource26#Examples

More lecture on yuv vs y4m raw formats : https://github.com/stoyanovgeorge/ffmpeg/wiki/Encode-Raw-Video

Things like .y4m that usually have a header with infos can be opened directly with FFVideoSource, no need of rawsourceplus plugin added for those (i think?), I don' know what is the sample you tested but a 420p10 won't work, just try with the .yuv files i linked in previous post and see by yourself, if downloading those large files is a problem maybe try this instead :

- create a colorbars.avs script with this code content :
ColorBars(width = 1280, height = 720, pixel_type = "YUV420P8", staticframes = false).killaudio().assumefps(60, 1).trim(0,600)
ShowSMPTE(y=300,size=200,text_color=$ffffff,halo_color=$000)

Then use ffmpeg to convert it into YUV using the command :
ffmpeg -hide_banner -i colorbars.avs output.yuv

Rawsourceplus source filter code in Staxrip to open it:
RawSourcePlus("%source_file%", width=1280,height=720, \
pixel_type="YUV420p8", \
fpsnum=60, fpsden=1)
> works

Now the same thing with a 420p10, the colorbars.avs script will be :
ColorBars(width = 1280, height = 720, pixel_type = "YUV420P10", staticframes = false).killaudio().assumefps(60, 1).trim(0,600)
ShowSMPTE(y=300,size=200,text_color=$ffffff,halo_color=$000)
Then encode to yuv wiht ffmpeg, same command as before :
ffmpeg -hide_banner -i colorbars.avs output.yuv
No let's try to open it using rawsourceplus :
RawSourcePlus("%source_file%", width=1280,height=720, \
pixel_type="YUV420p10", \
fpsnum=60, fpsden=1)
Doesn't work, result will look something like this : https://i.imgur.com/KysU6G4.png
All 420p10 source files i tried in the past had the same problem, YUV444P10 souce file works tho, but since you stateed in patch notes "Default Pixel_type is set to YUV420P10 (aka P010)."... And i don't know how you achieve this without adding the pixel_type parameter in the source filter of Staxrip, by default, if not specified the pixel_type is "YUY2" according to the wiki of RawSoucePlus.

Anyways, unless i am missing something the prime interest in having rawsourceplus plugin added is for those raw files having no header infos, no real point having it for things like .y4m files since other source plugins in Staxrip already cover them.


- Indeed Staxrip is not that young but does a fine job once we update plugins and tools used and adapt or create filters for them, i have no clue of how deep you modified the code and what could have been lost in the process and can not be recovered, my machine is also not that young either, the CPU is only one generation ahead of yours, a 3770k, but i'm still on win7 x64 pro, not win10, I don't know what changes were made to the code but the original Staxrip by Stax76 always was hyper-responsive, now it's really sluggish and often a pain to use because of this.


One little last thing i noticed :
- mpvnet player does not work, it asks for Netframework 4.8, while inside the 4.7 package.


Still did not had the time to continue migrating all stuff from my original version of Staxrip into your last beta, will need quite a few more hours dedicated to this before exporting all custom things i have made in it, the excellent thing about Staxrip is the almost infinite possibilities it offers for customization, templates, event commands, custom menus etc etc... I'm afraid no other program trying to come after it will come even half close to those possibilities sadly, it still have numerous years to live before something comes out allowing such degree of personalization :/


Thank you.

[stax76]

The included mpv.net build requires .NET 4.8 which is only available as preview as far as I know.

Here is a new mpv.net build with few improvements:

https://github.com/stax76/mpvnet/releases

- changed minimum runtime to .NET 4.7.2
- fixed mpv.net not working with new mpv lib
- the track name in the title bar was sometimes wrong
- mpv lib updated to 2018-12-16
- quit-watch-later added to context menu (Shift+Q) to exit and resume at the last position
- ab loop added to menu
- added the possibility to modify mpv.conf settings using the context menu
- added link to the manual and default keys to the menu

The new default keys and menu is here:

https://github.com/stax76/mpvnet/blob/master/mpvnet/Resources/input_conf.txt

[Revan654]

Hi,

Yes it's MTN , was a typo from my part, I used the .exe in link you provided and made various tests in command line, no problems there beside that the timestamps are incorrect, apparently reported in github and issue closed but not fixed it seems : https://github.com/Revan654/movie-thumbnailer-mtn/issues/1


Some of these problems are due to FFmpeg and nothing I can do about that.

Legacy Formats or improper Coded videos with invalid timestamps or misplaced timestamps will create issues.

I would run the Debug Code and see what the issue is, I can only fix problems that can be re-produced.



The output path : like i said inside staxrip this does not work, no matter what i set for the output path the thumbnailer will always create the image where the video is located, output path using the .exe in command line works.

I'll probably create my own custom menu associated with a custom command line directly in Staxrip, well that is if i find out why the timestamps do not work, rather pointless to use it if timestamps on the tiles are messed up, but the various parameters for customization of the final image are interesting, full customization of the colors/fonts etc is nice.



This is Caused by how data is passed through ObjectStorage. It should be fixed in the next update.



Things like .y4m that usually have a header with infos can be opened directly with FFVideoSource, no need of rawsourceplus plugin added for those (i think?), I don' know what is the sample you tested but a 420p10 won't work.

The Source was P010 (YUV420p10) 100% Raw & Uncompressed.

My source came directly from HDR Source. It's the main reason why I added RawSourcePlus, Since it was one of the few filters that could actually open the video file.



- Indeed Staxrip is not that young but does a fine job once we update plugins and tools used and adapt or create filters for them, i have no clue of how deep you modified the code and what could have been lost in the process and can not be recovered, my machine is also not that young either, the CPU is only one generation ahead of yours, a 3770k, but i'm still on win7 x64 pro, not win10, I don't know what changes were made to the code but the original Staxrip by Stax76 always was hyper-responsive, now it's really sluggish and often a pain to use because of this.



if the data is to be trusted, it says 10,000+ line changes or 500 commits.

Every person's PC is different, I test it on the oldest hardware I have. If it works on that it should work on any PC.


One little last thing i noticed :
- mpvnet player does not work, it asks for Netframework 4.8, while inside the 4.7 package.

You can Install it.

https://github.com/Microsoft/dotnet-framework-early-access/tree/master/release-notes/NET48

4.8 does come pre-installed in Next update for Windows 10 along with VS 2019.

[Yanak]

Hello Stax76,

glad to see you still around ( missing you man :) ) and thank your for the update I'll try this one tomorrow, won't have time to play with this today but will test and report on git page is there is any issue.

Thank you very much.

@Revan :

- If this can help, some steps to reproduce :

create testvid.avs script :
ColorBars(width = 1280, height = 720, pixel_type = "YUV420P8", staticframes = false).killaudio().assumefps(60, 1).trim(0,54000)
ShowSMPTE(y=300,size=200,text_color=$ffffff,halo_color=$000)

Quick convert the avs to mp4 using ffmpeg :
ffmpeg -hide_banner -i testvid.avs output.mp4

Some of the Mtn commands i tried ( + many others ), all giving wrong timestamps :
mtn -c 4 -j 100 -h 240 -w 1920 -X -z -P --shadow=2 -g 6 -L 4:2 "H:\output.mp4" -O "H:/"

mtn -c 4 -j 100 -h 240 -w 1920 -X -Z -P --shadow=2 -g 6 -L 4:2 "H:\output.mp4" -O "H:/"

Same problem with all videos i encoded and tried with, among others tests:
- Encoded to x264 using x264-r2901-7d0ff22 > Muxed to mp4 with MP4Box
- Encoded to x264 using x264-r2901-7d0ff22 > Muxed to MKV with MKVToolnix
- Encoded to x265 using x265_2.9+14-3023bd8b05c0 > Muxed to mp4 with MP4Box
- Encoded to x265 using x265_2.9+14-3023bd8b05c0 > Muxed to MKV with MKVToolnix
- Encoded to VP9 using ffmpeg-20181218-3a36b0c-win64-static > to direct webm and also muxed inside a MKV container
All those videos i encoded and tested ended in the same wrong timestamps using the command line tool.


- Good to hear you fixed the output path in staxrip for the thumbnailer, thank you.

- I explained long enough and gave numerous links for samples or examples to create and test real raw videos for RawSourcePlus to test with, seems you do not want to hear, good for you if your sample worked... but again without even specifying in the source filter the pixel_type="YUV420p10" parameter it seems a miracle to see that "Default Pixel_type is set to YUV420P10 (aka P010)."... anyways, i won't continue loose my time pissing against the wind about this so do as it pleases you, i gave more than enough infos.

-Well you made 2 package versions, one for 4.7 and one for 4.8, this version of mpv.net was inside the package specified to be for dotnet 4.7, so... And I'd rather wait a bit before starting to install 4.8 or vs2019 that are still in preview releases, anyways this is fixed now by Stax himself so all good :)


Good luck with continuing with Staxrip2, myself i think i will continue to update plugins and adapt Stax76's last version to my needs as after pushing a bit more the testings on this one i just cannot deal with how irresponsive and slow it became, plus i don't deal much with HDR content so it can wait, i know you probably done a lot of changes and put a lot of efforts into this version and sadly maybe some of those are not for the better, at least for me :/ , I just hope others have better luck than me.

Wishing you the best of luck for this project, for now i will keep this v2 on hold and I'll give a few more tries when things will be a bit more advanced and sorted out.

Thanks a lot.

[Arhu]

I'm trying to cut out a part from the middle of a video. The cutting snippet looks like this example:

clip = clip[100:200] + clip[220:300]

The resulting video is fine and is missing frames 201-219 as intended, but the audio isn't being cut in the middle and is thus out of sync after the middle cut. Audio trimming in the beginning and end works fine. Is this a known limitation or is there a way to make it do what I want?

Source audio is FLAC, source filter is LWLibavSource or ffms2.

[Revan654]

I'm trying to cut out a part from the middle of a video. The cutting snippet looks like this example:

clip = clip[100:200] + clip[220:300]

The resulting video is fine and is missing frames 201-219 as intended, but the audio isn't being cut in the middle and is thus out of sync after the middle cut. Audio trimming in the beginning and end works fine. Is this a known limitation or is there a way to make it do what I want?

Source audio is FLAC, source filter is LWLibavSource or ffms2.

You have to check all the filters being used, Also check the audio settings.

Some filters will not resync correctly. This is specially known with the Framerate filters.

Options -> Audio is another area you might want to look at. Sometimes it's a good idea to use avisynth audio function over the standalone method. of Course if you use VapourSynth you don't have this option. Atlease Natively.

[Revan654]

Hello Stax76,

glad to see you still around ( missing you man :) ) and thank your for the update I'll try this one tomorrow, won't have time to play with this today but will test and report on git page is there is any issue.

Thank you very much.

@Revan :

- If this can help, some steps to reproduce :

create testvid.avs script :
ColorBars(width = 1280, height = 720, pixel_type = "YUV420P8", staticframes = false).killaudio().assumefps(60, 1).trim(0,54000)
ShowSMPTE(y=300,size=200,text_color=$ffffff,halo_color=$000)

Quick convert the avs to mp4 using ffmpeg :
ffmpeg -hide_banner -i testvid.avs output.mp4

Some of the Mtn commands i tried ( + many others ), all giving wrong timestamps :
mtn -c 4 -j 100 -h 240 -w 1920 -X -z -P --shadow=2 -g 6 -L 4:2 "H:\output.mp4" -O "H:/"

mtn -c 4 -j 100 -h 240 -w 1920 -X -Z -P --shadow=2 -g 6 -L 4:2 "H:\output.mp4" -O "H:/"

Same problem with all videos i encoded and tried with, among others tests:
- Encoded to x264 using x264-r2901-7d0ff22 > Muxed to mp4 with MP4Box
- Encoded to x264 using x264-r2901-7d0ff22 > Muxed to MKV with MKVToolnix
- Encoded to x265 using x265_2.9+14-3023bd8b05c0 > Muxed to mp4 with MP4Box
- Encoded to x265 using x265_2.9+14-3023bd8b05c0 > Muxed to MKV with MKVToolnix
- Encoded to VP9 using ffmpeg-20181218-3a36b0c-win64-static > to direct webm and also muxed inside a MKV container
All those videos i encoded and tested ended in the same wrong timestamps using the command line tool.


- Good to hear you fixed the output path in staxrip for the thumbnailer, thank you.

- I explained long enough and gave numerous links for samples or examples to create and test real raw videos for RawSourcePlus to test with, seems you do not want to hear, good for you if your sample worked... but again without even specifying in the source filter the pixel_type="YUV420p10" parameter it seems a miracle to see that "Default Pixel_type is set to YUV420P10 (aka P010)."... anyways, i won't continue loose my time pissing against the wind about this so do as it pleases you, i gave more than enough infos.

-Well you made 2 package versions, one for 4.7 and one for 4.8, this version of mpv.net was inside the package specified to be for dotnet 4.7, so... And I'd rather wait a bit before starting to install 4.8 or vs2019 that are still in preview releases, anyways this is fixed now by Stax himself so all good :)


Good luck with continuing with Staxrip2, myself i think i will continue to update plugins and adapt Stax76's last version to my needs as after pushing a bit more the testings on this one i just cannot deal with how irresponsive and slow it became, plus i don't deal much with HDR content so it can wait, i know you probably done a lot of changes and put a lot of efforts into this version and sadly maybe some of those are not for the better, at least for me :/ , I just hope others have better luck than me.

Wishing you the best of luck for this project, for now i will keep this v2 on hold and I'll give a few more tries when things will be a bit more advanced and sorted out.

Thanks a lot.

Like I said 4.8 is in the next update for Windows. It will be there if you want it or not. Windows 7 is already on Life Support.

Source filter I'm just giving you the means to use a different source filter, It's up to the user to tweak it to there neeeds. It doesn't mean ever source is going to work. Same is said with L-Smash & ffms.

Everyone's PC is different, Software could run flawless on one machine, where it could struggle on another.

I believe the VFW might be the part of the problem. I couldn't find allot of docs on it. It remained untouched for now until I find more details. My goal is try to get the VFW to use GPU that way sluggish viewing would be a thing of the past.

Lastly WinForms Framework is getting old, Not much is added to WinForms by MS. There focus is on WPF which is newer forms. It still very young(I really don't like the toolsets for it) and GUI would have to be rebuilt from the ground to work with that. The advantage of WPF has it uses the GPU for allot of the rendering over just the CPU.

I would personally use Python over WPF, Even though IDE for python GUI is very limited.

Lastly Programming is not easy task to start with, It sometimes hard to pin point where something is slowing down.

VB is one of the easier Coding system, it was deisgned as a stepping stone to C# and God tier Code of C++.

[Arhu]

You have to check all the filters being used, Also check the audio settings.
I tried to isolate the issue and found that it only happens when using Opus (ffmpeg libopus) as the audio target. With other audio codecs the middle part is cut out correctly.

Both libopus and other codecs get an identical "[filename]_cut_ ID1.flac" as input, only the opus output has the wrong length. The log doesn't really help pinpoint this further.

[Revan654]

I tried to isolate the issue and found that it only happens when using Opus (ffmpeg libopus) as the audio target. With other audio codecs the middle part is cut out correctly.

Both libopus and other codecs get an identical "[filename]_cut_ ID1.flac" as input, only the opus output has the wrong length. The log doesn't really help pinpoint this further.

The settings for opus is the same if you use AAC for example, It gets passed to FFMpeg. The issue looks to be something in ffmpeg.

It's very possible due to a bug in ffmpeg & the libs that ffmpeg are using, You could try nightly release and see if anything get fixed.

Also tell ffmpeg devs about the issue and see what they have to say.

[mparade]

encoder : Lavc58.35.100 flac
[dca @ 0000023cd4738e40] 10 XLL channels is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been implemented.
[dca @ 0000023cd4738e40] If you want to help, upload a sample of this file to ftp://upload.ffmpeg.org/incoming/ and contact the ffmpeg-devel mailing list. (ffmpeg-devel@ffmpeg.org)
[dca @ 0000023cd4738e40] Read past end of XLL band data

Should I ignore it? DTS-HD audio track encode completed. I just have checked the log and found this warning about encoding.

[mparade]

I have no idea what TV you have nor the type it playsback.

To meet all the HDR10 Specs you must have all the correct Metadata(They Change from time to Time), Which it doesn't. It's slowly being Added, Just has to wait for Nvidia to all all the Functions to the SDK.

HDR get's very complex as you headed into the different types.

to Name some of the Flags:

-no-open-gop
-hdr
-aud
-hrd
-repeat-headers
-Matrix BT.2020 NC
-transfer ST.2084
-prime BT.2020
-Master-Color-Display (Must set value to Source color)
-Range limited (This is Done for TV viewing)
-MaxFall/CLL
-10Bit(Min)
-Profile Main10
-vui-hrd-info(Becomes Enabled with HRD Enabled)
-vui-timing-info

+ Ingest

I am still using open gops with hdr encodes. Is -no-open-gop really required? when using unrestricted level x265 keeps complaining about not setting VBV parameters for hrd parameters all the time. Is it required to set a specific level as well with hdr encodes?
With SDR encodes I always use unrestricted letting the encoder decide.

[mparade]

Staxrip doesn't want to demux to mkv complaining about missing of Haali&LAV, however both of them have been installed on my system.


Any kind of advice is well appreciated.

[Revan654]

I am still using open gops with hdr encodes. Is -no-open-gop really required? when using unrestricted level x265 keeps complaining about not setting VBV parameters for hrd parameters all the time. Is it required to set a specific level as well with hdr encodes?
With SDR encodes I always use unrestricted letting the encoder decide.

Yes, No-open-gop is required when dealing with HDR.

VBV can be set, I haven't noticed any difference other then size and such. I usually forget about VBV most of the time.

Levels don't really need to be set, If I'm remember correctly( I could be confusing it with the other option, still very early here) the levels only play a role with certain hardware device(Usually Legacy devices). Levels get set by the resolution output.

[Revan654]

Staxrip doesn't want to demux to mkv complaining about missing of Haali&LAV, however both of them have been installed on my system.


Any kind of advice is well appreciated.

That's very vague and nothing I can do without knowing what the main issue is.

I don't even use or have LAV or Halli installed and most source files should demux without much issue.

mkv demux should be handled by mkvtoolnix, I would check to make sure it's linked up correctly and your using up to date version.

Like the doc says LAV & Halli will overwrite one another. Those two apps are only really needed if your going to use eac3to(Audio) or source file is TS with AVC source and needs to write to mkv when correcting audio problems.

Check Pre-Process Settings to set how things get demux.

[Revan654]

Should I ignore it? DTS-HD audio track encode completed. I just have checked the log and found this warning about encoding.

It's hard to say, I would check the audio and compare it to raw video file. Also make sure everything syncs up.

I have found ffmpeg does struggle with certain audio files. It's usually the DTS, and files that come from HDR content.

It might be worth using eac3to over ffmpeg when the audio is DTS.

[Revan654]

Release 2.0

2.0
- Brand New Update System All done within the App
- New Tab Added to x265 for Bitstream due to all the new Flags.
- Updated the default state of the x265 flags that were changed.
- x265 Flags Added:
- Zone File
- HRD Concat(The Flag is currently improperly marked in x265 cli)
- Dolby Vision RPU
- Dolby Vision Profiles
- Tuning: Animation
- Refine CTU Distortion
- hevc-aq
- qp-adaptation-range
- refine-mv-type renamed to refine-analysis-type
- rav1e Flags Added:
- Matrix
- transfer
- primaries
- Min Key Int
- Added Support additional support for LongPaths
- There are two ways the app can name the files & Folders based on your OS & Harddrive Type
- If One Method fails it now has a fallback method to use.
- Fixed QSVEnc key, Which was locking some users out.
- Updated the VapourSynth scripts that have been updated recently.
- Updated the filter names for Vapoursynth and removed the ones that don't exist anymore.
- Updated the switches for VCEnc
- Updated the MTModes Syntax for AVSynth
- Updated DFTTest syntax for Vapoursynth, Opt Settings is now set to AVX2(Settings it below 3 will set it to AVX or None).
- Added additional source filter when StaxRip internal thumbnail is used, some source files did not get along with ffms.
- Updated VapourSynth and Tweaked SVPFlow & Added Additional Option to use BlockFPS.
- Updated FFmpeg, MKVToolNix, NVENC, Rav1e, x265 & MediaInfo
- Python Support now includes MiniCoda as well.
- Included Both Old and Newer versions of MediaInfo Just incase it breaks something again.
- Re-Enabled MediaInfo Folder Function, Since The Bug in MediaInfo has been fixed.
- Added & Updated All the Output Path Options for MTN, StaxRip Thumbnailer, Gif & PNG Creators.
- The Help System for the Encoders Has been Altered. All the Help System works the Same now.
- Updated the dll files for both Avisynth & VapourSynth for filters that have been updated.
- Support for PNG has been added for VFW Saving Screenshot(Default Options are PNG & BMP, With JPG being able to be added in the Edit Menu).
- Cleaned up and Organized for File Structure inside App Folder.
- a small tweak in regards to the VFW.
- Updated mpvnet
- Plus some other changes as well.

Link: https://github.com/Revan654/staxrip/releases/download/2.0.0.0/Staxrip.2.0.0.0.x64.rar

[Natty]

Release 2.0


Link: https://github.com/Revan654/staxrip/releases/download/2.0-Beta-1/2.0.0.0.x64.7z

https://github.com/Revan654/staxrip/releases/download/2.0.0.0/Staxrip.2.0.0.0.x64.rar


different file sizes.. which one is correct ? :thanks:

[NikosD]

Release 2.0


Thanks again for the new release.
IIUC the new update removes the beta from the name, so it's the first 2.0 stable release.

Does QSVEncC work with Win 10 October 2018 update eventually ?

I'll probably give it a try on two days using Skylake H.265 at work.

[Revan654]

https://github.com/Revan654/staxrip/releases/download/2.0.0.0/Staxrip.2.0.0.0.x64.rar


different file sizes.. which one is correct ? :thanks:

Something got screwed up, As long as the link doesn't say Beta, your fine.

[Revan654]

Thanks again for the new release.
IIUC the new update removes the beta from the name, so it's the first 2.0 stable release.

Does QSVEncC work with Win 10 October 2018 update eventually ?

I'll probably give it a try on two days using Skylake H.265 at work.

Have no idea, I could never get quicksync to work. It requires to many hoops to jump through to get it to work. I still hasn't been able to install newer Nvidia drivers on Windows 10 2018 update.

[NikosD]

Have no idea, I could never get quicksync to work. It requires to many hoops to jump through to get it to work. I still hasn't been able to install newer Nvidia drivers on Windows 10 2018 update. Happy New Year to everyone!

I downloaded StaxRip 2.0 today and started to run a few QSVEncC tests on my Haswell system (Win 10 ver 1809 build 17763.195) and iGPU HD 4400 (Drivers: 20.19.15.5058 MediaSDK Hardware API v1.20)

First of all, during installation, the StaxRip's installation stopped completely in order to force me to install FFTW (!)

Why ?

I saw that a filter needs that library, but I may not ever use this particular filter, so why is this installation mandatory in order to proceed to the StaxRip installation ?

I tried to install it from StaxRip by pressing the button, like AviSynth+, but the button didn't work and I had to google it in order to find the DLL.

Please, fix the button and remove it completely from the mandatory installations of StaxRip.

After StaxRip's installation I did some tests with QSVEncC v3.17, the built-in StaxRip version.

All "Decoders" options worked, except of the most interesting aka the fastest and with lower CPU utilization which is of course the "QSVEnc Intel".
StaxRip gave me a message of missing DLL files which I could see them all inside the folder - nothing was missing.

So, I downloaded the original files from Rigaya's repository and tried again by replacing your DLL files inside StaxRip.

It worked like a charm (!)

So, my friend Revan654, I compared the DLL files inside your StaxRip distribution with the original source DLL files from rigaya and I was shocked (!)

Your DLL files are x2 - x3 times bigger!

I checked them with VirusTotal site and fortunately it was not a virus.

But definitely something really, really bad is happening with ALL your DLL files for both hardware encoders of rigaya (NVEnc, QSVEnc)

For reasons unknown to me, it seems that VCEEnc version of StaxRip uses the right DLLs.

So, please RE-DOWNLOAD everything from rigaya's repository and all hardware encoders will work like a charm on every Windows 10 PC.

Thank you!

[minda76]

Hello,
QSVEnc still not working for me:

NullReferenceException (2.0.0.0)

Object reference not set to an instance of an object.

System.NullReferenceException: Object reference not set to an instance of an object.
at StaxRip.QSVEnc.EncoderParams.OnValueChanged(CommandLineParam item)
at StaxRip.BasicVideoEncoder.ImportCommandLine(String commandLine, CommandLineParams params)

[paauw]

Same over here, even after updating QSVencc from Rigaya latest version 3.17

[Revan654]

Happy New Year to everyone!

I downloaded StaxRip 2.0 today and started to run a few QSVEncC tests on my Haswell system (Win 10 ver 1809 build 17763.195) and iGPU HD 4400 (Drivers: 20.19.15.5058 MediaSDK Hardware API v1.20)

First of all, during installation, the StaxRip's installation stopped completely in order to force me to install FFTW (!)

Why ?

I saw that a filter needs that library, but I may not ever use this particular filter, so why is this installation mandatory in order to proceed to the StaxRip installation ?

I tried to install it from StaxRip by pressing the button, like AviSynth+, but the button didn't work and I had to google it in order to find the DLL.

Please, fix the button and remove it completely from the mandatory installations of StaxRip.

After StaxRip's installation I did some tests with QSVEncC v3.17, the built-in StaxRip version.

All "Decoders" options worked, except of the most interesting aka the fastest and with lower CPU utilization which is of course the "QSVEnc Intel".
StaxRip gave me a message of missing DLL files which I could see them all inside the folder - nothing was missing.

So, I downloaded the original files from Rigaya's repository and tried again by replacing your DLL files inside StaxRip.

It worked like a charm (!)

So, my friend Revan654, I compared the DLL files inside your StaxRip distribution with the original source DLL files from rigaya and I was shocked (!)

Your DLL files are x2 - x3 times bigger!

I checked them with VirusTotal site and fortunately it was not a virus.

But definitely something really, really bad is happening with ALL your DLL files for both hardware encoders of rigaya (NVEnc, QSVEnc)

For reasons unknown to me, it seems that VCEEnc version of StaxRip uses the right DLLs.

So, please RE-DOWNLOAD everything from rigaya's repository and all hardware encoders will work like a charm on every Windows 10 PC.

Thank you!

Allot of filters use FFTW, Not just one or two. Even more on VapourSynth side. I have FFTW tied to AVS instead of any selected filter(Since System only allows One Filter), This removes the issue of possible null values, exit1 codes or filter not loading correctly.

Unless you know how the code work with every single file supplied & the source, I wouldn't be asking to remove things that could break the software.

Next time read the complete doc for Staxrip, since it outlines everything you need to know. The files are in the Support folder.

---

ffmpeg files are directly from ffmpeg website(and Most Up to date version & the core version). His Builds are likely built with only a few flags enabled(aka Only whats needed to run). I have no idea what flags he has enabled or disabled. Not to mention he has a habit of forgetting to add all the required files.

ffmpeg has dozens and dozens of flags that can be enabled or disabled.

ffmpeg can reach over 200Megs per file if you enabled everything.

NVEnc works perfectly fine with the supplied dll files, I already tested a few times.

QuickSync is a massive PIA due to how it gets enabled. You must pass certain checks (This is set in stone by Intel & your CPU) for QS to work 100% correctly. Each CPU & Motherboard is different when enabling QVS.

VCEEnc never gets any new functions, everything is pretty much the same since 2016 release.

------

Don't go around Saying there something wrong with the files when there clearly no issue with them.

All this is going to do is spread false information.

-----

Lastly you need to make sure you have fresh Settings file, if older Setting file is used then none of newer functions will work or know where certain folders are.

Everything is fully Tested before being released.

[Revan654]

Hello,
QSVEnc still not working for me:

NullReferenceException (2.0.0.0)

Object reference not set to an instance of an object.

System.NullReferenceException: Object reference not set to an instance of an object.
at StaxRip.QSVEnc.EncoderParams.OnValueChanged(CommandLineParam item)
at StaxRip.BasicVideoEncoder.ImportCommandLine(String commandLine, CommandLineParams params)

Run Check Hardware, if you get Error or not available Then your System does not have QS enabled. Staxrip will always return null value if it can't find QS. Since the hardware can not be enabled.

Don't bother with the intel SDK since it will not help in this type of scenario.

[NikosD]

Many things to resolve and correct, so let's start !

Unless you know how the code work with every single file supplied & the source, I wouldn't be asking to remove things that could break the software. I clearly didn't say to remove the FFTW completely, just from the mandatory installations of StaxRip v2.0.
Unless you say to me that StaxRip is unusable without FFTW, so we have to install FFTW in order for StaxRip to work (!)

Next time read the complete doc for Staxrip, since it outlines everything you need to know. The files are in the Support folder. In all other cases of StaxRip, when you press the install button, it just runs the installer or redirect you to the installer's site.
If an installer is not provided and run automatically, then instead of an install button you could have a link or mention the path for DLLs in order to install them manually.

ffmpeg files are directly from ffmpeg website(and Most Up to date version & the core version). His Builds are likely built with only a few flags enabled(aka Only whats needed to run). I have no idea what flags he has enabled or disabled. Not to mention he has a habit of forgetting to add all the required files.

ffmpeg has dozens and dozens of flags that can be enabled or disabled.

ffmpeg can reach over 200Megs per file if you enabled everything. It really doesn't matter how the files are produced and how big they are, for the user.
I only mentioned the size in order to say that your versions are a lot different.
The DLLs provided only need to work and the files provided by you do not work.
On the other hand the files provided by rigaya do work.

Maybe because the hardware encoders are his and not yours and probably he knows better his apps.
Maybe he has made custom compilations and the DLLs are special and not generic FFMPEG in order to work for his apps.

NVEnc works perfectly fine with the supplied dll files, I already tested a few times. How do you know that ? In the post above you replied to me that you couldn't install drivers for the nVidia card on Win 10 October 2018 Update.

QuickSync is a massive PIA due to how it gets enabled. You must pass certain checks (This is set in stone by Intel & your CPU) for QS to work 100% correctly. Each CPU & Motherboard is different when enabling QVS. You don't seem to understand the problem or you are pretending that you don't understand.
QSV works just fine and it can be detected by QSVEnc.
The problem is that QSVEnc is complaining about the DLLs regarding FFMPEG support.
The DLLs mentioned above.

Don't mess general QSV support in this discussion.
It's a completely different subject.

The DLLs of FFMPEG provided by StaxRip is the problem.

Don't go around Saying there something wrong with the files when there clearly no issue with them.

All this is going to do is spread false information. As explained above the DLLs are definitely wrong regarding QSVEnc support.
Because with your ffmpeg distribution DLL files, QSVEnc doesn't work but with rigaya's ffmpeg DLL files, QSVEnc does work.

All in all, the solution for QSVEnc's malfunction using StaxRip with Win 10 October 2018 Update, is just to use rigaya's original source DLLs and not generic FFMPEG files.

You have said a lot of times that you hadn't manage to make QSVEnc and NVEnc to work with Win 10 October 2018 update.

Well, I found out a very simple solution and I told you about in order to correct it.

It's so simple, where exactly is the problem ?

If you don't like my solution to the problem (to include original DLLs from rigaya) and you want to use generic FFMPEG files, please provide a working solution because StaxRip doesn't work as is.

And please stop saying wrong things like QSV support of Win 10 October 2018 update or QSV support of motherboards.
This has nothing to do with the problem.

Sometimes it's much easier and efficient to go by the book and just copy the original repository of third party apps, instead of trying to do it your way, unless you are in a position to test it - and you aren't as you have already said.

[paauw]

I checked the qsvencc --check-hw..it said it is enabled...b.t.w. staxrip 1.7 till 2 beta are working fine

if i choose the intel h265 with the stax 2.000 after a fresh install it also comes with the error if i choose intel h265 profile

if i ignore it en run the movie conversion it crashes when starting with qsvenc...the pre jobs run fine









NullReferenceException (2.0.0.0)

Object reference not set to an instance of an object.

System.NullReferenceException: Object reference not set to an instance of an object.
at StaxRip.QSVEnc.EncoderParams.OnValueChanged(CommandLineParam item)
at StaxRip.QSVEnc.Encode()
at StaxRip.GlobalClass.ProcessVideo()
at System.Threading.Tasks.Parallel.<>c__DisplayClass4_0.<Invoke>b__0()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at StaxRip.GlobalClass.ProcessJob(String jobPath)
at StaxRip.GlobalClass.ProcessJobs()

[minda76]

QSVEnc

Checked hardware too:

Success: QuickSyncVideo (hw encoding) available

[AMED]

Just wondering if anybody knows an easyish way of automating the copying the network located source file in to the local staxrip temp folder so it can be processed a little faster and not encoded over the local network.

[Atak_Snajpera]

Just wondering if anybody knows an easyish way of automating the copying the network located source file in to the local staxrip temp folder so it can be processed a little faster and not encoded over the local network.

It won't be processed faster. 100Mbps network is more than enough for encoding blu-ray movie (~40Mbps). I doubt that your pc can encode 1920x1080 frames faster than 2xrealtime (48fps+) with x264/x265.

[AMED]

ahh ok, thanks for the answer.

I thought copying the source locally would speed up the demuxing, FFMS indexing and other staxrip functions. Then again probably time for the copy would offset the gains if any.

[Revan654]

Many things to resolve and correct, so let's start !

I clearly didn't say to remove the FFTW completely, just from the mandatory installations of StaxRip v2.0.
Unless you say to me that StaxRip is unusable without FFTW, so we have to install FFTW in order for StaxRip to work (!)

In all other cases of StaxRip, when you press the install button, it just runs the installer or redirect you to the installer's site.
If an installer is not provided and run automatically, then instead of an install button you could have a link or mention the path for DLLs in order to install them manually.


It transfer the files to System Directory, Just Incase. I updated the Source code with additional syntax(Code is on Github).



It really doesn't matter how the files are produced and how big they are, for the user.
I only mentioned the size in order to say that your versions are a lot different.
The DLLs provided only need to work and the files provided by you do not work.
On the other hand the files provided by rigaya do work.



ffmpeg is ffmpeg, Only thing that differs is what switches are enabled during compile time and how new the source code is. ffmpeg gets re-built every day. It could be a bug that happened.

They work fine for NVEnc, ffmpeg could have removed QS support from the default files. It's doubtful since there dev site still has it listed as active. Might be an issue at your end. Plus additional files like intel SDK will create problems.


Maybe because the hardware encoders are his and not yours and probably he knows better his apps.
Maybe he has made custom compilations and the DLLs are special and not generic FFMPEG in order to work for his apps.

How do you know that ? In the post above you replied to me that you couldn't install drivers for the nVidia card on Win 10 October 2018 Update.



Not sure you understand how programming works or how ffmpeg code works.


You don't seem to understand the problem or you are pretending that you don't understand.
QSV works just fine and it can be detected by QSVEnc.
The problem is that QSVEnc is complaining about the DLLs regarding FFMPEG support.
The DLLs mentioned above.



I don't think your comprehending what I'm saying.



You have said a lot of times that you hadn't manage to make QSVEnc and NVEnc to work with Win 10 October 2018 update.

I never said that, I said I could get drivers installed. Two very different things. If you actually read my comment I said I tested NVEnc and it worked perfectly.



And please stop saying wrong things like QSV support of Win 10 October 2018 update or QSV support of motherboards.
This has nothing to do with the problem.

Sometimes it's much easier and efficient to go by the book and just copy the original repository of third party apps, instead of trying to do it your way, unless you are in a position to test it - and you aren't as you have already said.

again your not comprehending what I'm saying.

[Revan654]

QSVEnc

Checked hardware too:

Success: QuickSyncVideo (hw encoding) available


This is null value for not being able to start-up intel Encoder or able to find the Encoder path.

since you can do Checked hardware you can rule out path issue.

Have your tried to input the commandline into cmd prompt to see if QVSEnc will run without StaxRip? If it does, Then we can rule out QSVEnc, if it doesn't then the issues is something to do with your setup or QVSEnc.

Try other decoders and see if anything changes.

[Revan654]

For those using AVS, This only effects anyone who has AVX2 only CPU's. Which effects Skylake(6700)+ CPU's. Not sure what CPU's on AMD side are AVX2 Only.

- If you have a CPU with only AVX2 support, Any AVX coded filter will not work. You will get a return code of no module found, no entry point found or no platform was found.

For example: FFT3DGPU. Which also effects the usage of XAA, DeNoiseMF & MCTemporalDenoise. They could be more, but I haven't gone through each one filter yet.

If one of the filters you use is effected my suggestion would be heading to Vapoursynth and see if it's been ported or try to find a different filter to use.

[paauw]

if i use execute command (encoder option) line with intel h265 encoder option it starts converting but if i use de default 'next' it comes with the error mentioned

ps..

x265 is working fine so others work

[Revan654]

if i use execute command (encoder option) line with intel h265 encoder option it starts converting but if i use de default 'next' it comes with the error mentioned

ps..

x265 is working fine so others work

x265 is pure software based, so it will run no matter what unless you get a bad filter into the mix. Intel is both software & hardware based on the options you select. if it doesn't like one flag it will return null value which creates your issue. In Programming null usually crashes the program. Debugging hardware encoders are harder to do. Plus I don't have QS enabled PC, I kind of limited of type of help I can offer.

Have your checked to make sure your CPU/iGPU can encode HEVC? Some can only do AVC Encoding. Others can only do decoding.

QS is PIA sometimes get up and running, Even on Handbrake support there many that can't get QS to work.

1. Check both Frameservers, it could just be an issue with AVS or VS and how the script is sent.

2. If you haven't update your iGPU drivers, Update the drivers to latest version.

3. Last thing could be something in VS2017/dotnet, I have no way to test & debug QVSEnc at my end.

The Encoding process hasn't been touched since 1.7. The flags & everything else looks the same based off the doc. The dev tool helper that reads each encoder and reports the changes is not reporting any kind of new or remove additions.

It would be a good idea to upload your log.

[Revan654]

Tweaked a few functions in the source for QVSEnc, Anyone having issues can try to compile it and report the outcome.

[paauw]

@Nikosd

maybe not intended but your reply is to aggressive and Revan deserves more respect for taking staxrip to the next level...and yes troubleshooting could be better but lack to own intel/qsv does not help...

@revan

QSV is working fine till 2.0 (from 1.7 till beta) the problem is not qsv because the commandline works.

Something inside of staxrip must have changed after 2.0 beta in the gui or in the call to start qsv .

as i mentioned , choosing the qsv profile (intel h265) the first time without starting qsv already brings up the error...

is there something changed in the gui or in the way you start/choose the profile in the gui after beta2 of staxrip ?

[Zetti]

MKVToolNix v30.0.0 is released.

[Revan654]

@Nikosd

maybe not intended but your reply is to aggressive and Revan deserves more respect for taking staxrip to the next level...and yes troubleshooting could be better but lack to own intel/qsv does not help...

@revan

QSV is working fine till 2.0 (from 1.7 till beta) the problem is not qsv because the commandline works.

Something inside of staxrip must have changed after 2.0 beta in the gui or in the call to start qsv .

as i mentioned , choosing the qsv profile (intel h265) the first time without starting qsv already brings up the error...

is there something changed in the gui or in the way you start/choose the profile in the gui after beta2 of staxrip ?

The core gui is untouched, The process commands that sends out the command is also untouched. Basically the entire code for QSVEnc is untouched other then a few flag updates. Those would not create those issues. Since NVEnc got the same flags and runs. It has to be something package file, dotnet and how it all links up.

I could revert back to 1.7 code and see if that helps. I not sure if that would help or not. The commands called are the same, I compared the two codes last night and there the same. It's likely something in dotnet broke it.

Current Code to call the process:
Using proc As New Proc
proc.Header = "Video encoding"
proc.Package = Package.QSVEnc
proc.SkipString = " frames: "
proc.File = "cmd.exe"
proc.Arguments = "/S /C """ + Params.GetCommandLine(True, True) + """"
proc.Start()
End Using

Original Code:

Using proc As New Proc
proc.Header = "Video encoding"
proc.Package = Package.QSVEnc
proc.SkipString = " frames: "
proc.File = "cmd.exe"
proc.Arguments = "/S /C """ + Params.GetCommandLine(True, True) + """"
proc.Start()
End Using

[paauw]

Hi Revan

I tested staxrip 2 with an old qsv enc and its dll's ...same error...i updated .dot 4.8 preview ...same error
here's my log file of staxrip

[Zetti]

MKVToolNix v30.1.0 is released.

[Revan654]

Hi Revan

I tested staxrip 2 with an old qsv enc and its dll's ...same error...i updated .dot 4.8 preview ...same error
here's my log file of staxrip

I found the issue, I had to go line by line. to find it. It was one of the filters throwing in null value if it was used or not. The next update will have this fixed or re-compile it from source.

[paauw]

Thanx revan...i must admit that my next step intended to check the option changes from the encode options...

How can i recompile it ...is that easy ?

[Revan654]

Thanx revan...i must admit that my next step intended to check the option changes from the encode options...

How can i recompile it ...is that easy ?

Install VS 2017.

- At the Top Select Release & x64 (if it isn't already selected)

Click on the Build tab & Select Build Staxrip. The software will do the rest of the work.

Make sure you read the changelog to add any additional filters that have been added or removed since the last release.

Remember this is Dev Build, Sometimes there can be be bugs or hiccups in the code.

----

hmm this just showed up on my PC:

https://i.imgur.com/5M56jMD.png

It not longer says Error.

I guess QS is now working on my PC, I don't have H.265 encodinig functon since Intel didn't create that feature for my CPU/iGPU.

[paauw]

well never done this before but i managed to instal VS2017..
clone your git and started to build...but unfortunitely it gave errors...see screenshot...any ideas or should i just wait til staxrip 2.0.0.1

[Arhu]

I'm having various problems in 2.0 related to the length of temporary folders / file names. It was fine in the last 2.0 beta release.

Before, temporary folder names were truncated like this: "Very Long Fil..._temp". Now in staxrip 2.0 they have this format: "Very Long Filename that really is way too long_temp". As a result, often ffmpeg can't find some wrongly demuxed files. I tried using older versions of MediaInfo / mkvtoolnix, but that didn't really help. Anything I can do on my end (besides renaming source files to make them shorter)?

[Revan654]

I'm having various problems in 2.0 related to the length of temporary folders / file names. It was fine in the last 2.0 beta release.

Before, temporary folder names were truncated like this: "Very Long Fil..._temp". Now in staxrip 2.0 they have this format: "Very Long Filename that really is way too long_temp". As a result, often ffmpeg can't find some wrongly demuxed files. I tried using older versions of MediaInfo / mkvtoolnix, but that didn't really help. Anything I can do on my end (besides renaming source files to make them shorter)?

Many of the cli lines need to be updated, This is specially true for the decoders.

Anything that gets passed to the cli just make sure it's in quotes which will solve most of the problem. The cli doesn't like spaces and such.

I'll likely add an option in the next update for this.

Also enable LongPath, How to do that is posted a few pages back.

[Revan654]

well never done this before but i managed to instal VS2017..
clone your git and started to build...but unfortunitely it gave errors...see screenshot...any ideas or should i just wait til staxrip 2.0.0.1

Can't view the image.

Don't upload to the site, Upload to imgur or something like that. Files need approval for others to see. Your log still hasn't been approved.

[paauw]

https://imgur.com/a/vbBiBgp



hope this helps

[K.i.N.G]

Is there any way to manually add an audio encoder?
I'd like to add OpusEnc.exe ... since it results in better quality than the ffmpeg included one (according to ffmpeg documentation).

[Revan654]

https://imgur.com/a/vbBiBgp



hope this helps

It's likely you have the strict option enable which throw up an warning if it doesn't follow it's guideline.

Right click on Staxrip on right menu -> Properties

Compile Tab -> Disable all warnings.

FYI, I don't use github app when import project. I do it all manually, I found the github to be a giant PIA to use and creates a bunch of issues.

[Revan654]

Is there any way to manually add an audio encoder?
I'd like to add OpusEnc.exe ... since it results in better quality than the ffmpeg included one (according to ffmpeg documentation).

The audio should be very similar to one another since, OpusEnc libs are used to compile ffmpeg.

----

Technically yes, You have to create command events and command cli. Not sure how well it will work in automation chain. You will have to disable the main audio function.

Just remember, Staxrip also has normalize audio functions and such. Not sure if OpusEnc has additional functions.

[paauw]

you were right the github clone was PIA...
i downloaded master.zip from github...opened the staxrip file
(had to install 4.7.2. sdk) and the build did go well...

I hope i did the right thing and copied the files in the bin directory of the unzipped masterfile (staxrip.exe and others) to your staxrop 2.0.0.0 directory and started staxrip...no more errors like before but when i started to encode it failed when it did try to start qsvencc with the message :

----------------------------- QSVEnc Error -----------------------------

H.265/HEVC isn't supported by your Hardware.



any suggestions ?

[paauw]

this is the message also

QSVEnc Error (2.0.0.0)

H.265/HEVC isn't supported by your Hardware.

StaxRip.ErrorAbortException: H.265/HEVC isn't supported by your Hardware.
at StaxRip.QSVEnc.Encode()
at StaxRip.GlobalClass.ProcessVideo()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at StaxRip.GlobalClass.ProcessJob(String jobPath)

[paauw]

is it also possible that paralel processing does not work anymore...?

[katzenjoghurt]

Thanks for keeping StaxRip alive, Revan!

I got the feeling that the colors aren't off in the video comparison tool any more when comparing an 8bit with am 10bit encoded movie - could that be?
If yes... great work!!

I got two other issues though with the tool...

1) After importing a bigger video file (like a 20GB AVC clip taken from a BluRay) the comparer seems to take a long break now where the application won't react for minutes.

2) For whatever reason source and encoded video are often (not always!) async by one frame now in the video comparison tool although frame count and fps are the same.
The same videos would show in sync when comparing with 1.7.0.6.
Would have loved to give you examples but I couldn't reproduce it with test clips.
But this could also be turned into a feature request - the ability to set a frame offset for each compared video would be something I always missed as I rarely had problems with async files in old StaxRip as well.

[Revan654]

you were right the github clone was PIA...
i downloaded master.zip from github...opened the staxrip file
(had to install 4.7.2. sdk) and the build did go well...

I hope i did the right thing and copied the files in the bin directory of the unzipped masterfile (staxrip.exe and others) to your staxrop 2.0.0.0 directory and started staxrip...no more errors like before but when i started to encode it failed when it did try to start qsvencc with the message :

----------------------------- QSVEnc Error -----------------------------

H.265/HEVC isn't supported by your Hardware.



any suggestions ?

Source files are Work in Progress, Assume you may run into a bug or two as progress goes on. Just have to re-check for updated files as progress goes on.

It's just part of programming, you fix one thing but breaks another.

[Revan654]

is it also possible that paralel processing does not work anymore...?

Depends on you expect to happen. It does encode, audio & video at the same time.

[Revan654]

Thanks for keeping StaxRip alive, Revan!

I got the feeling that the colors aren't off in the video comparison tool any more when comparing an 8bit with am 10bit encoded movie - could that be?
If yes... great work!!

I got two other issues though with the tool...

1) After importing a bigger video file (like a 20GB AVC clip taken from a BluRay) the comparer seems to take a long break now where the application won't react for minutes.

2) For whatever reason source and encoded video are often (not always!) async by one frame now in the video comparison tool although frame count and fps are the same.
The same videos would show in sync when comparing with 1.7.0.6.
Would have loved to give you examples but I couldn't reproduce it with test clips.
But this could also be turned into a feature request - the ability to set a frame offset for each compared video would be something I always missed as I rarely had problems with async files in old StaxRip as well.

I usually forget that app even exist at times. It has not been updated since 1.7.

- You are loading a massive file into the code, it takes time to index & cache that file. It uses FFVideoSource as the source filter using AVS.

- Many of offset is usually based off the codec, filter, or if the fps is off by .1 even if it doesn't show it in info data.

It's why it's usually a good idea to respec the video before encoding just incase something is off.

- There allot of elements to take into account like range, Depth, and the display. Most PC Monitors are only 8Bit. You will not get the full effect of 10Bit color.

[Forteen88]

@Revan654. When I used your Staxrip.2.0.0.0.x64, and "aq-mode" set to "Enabled", it still sets aq-mode to 2...
I hope you fix that, because I've gone over to use MeGUI instead (even though MeGUI produced a green video when using DGDec on a mpeg1-video, while Staxrip2.0 didn't (I don't know which mpeg-1 decoder it uses)).
Thanks in advance, if you fix that bug.

[videoh]

MeGUI produced a green video when using DGDec on a mpeg1-video DGDecNV does not support MPEG1. DGMPGDec (DGIndex + MPEG2Source) does support MPEG1.

[Forteen88]

DGDecNV does not support MPEG1. DGMPGDec (DGIndex + MPEG2Source) does support MPEG1.Thanks, but I don't think that I used DGDecNV, I used MeGUI:s default MPEG-1 decoder. I don't see DGDecNV in,
C:\Utils\MeGUI-2896-64\tools\dgindex

The only DLL in that directory is DGDecode.dll

[videoh]

If you can give me a link to the source file, I can look into it.

Does the file open when opening with DGIndex/DGDecode directly, rather than through MeGUI?

[Forteen88]

If you can give me a link to the source file, I can look into it.

Does the file open when opening with DGIndex/DGDecode directly, rather than through MeGUI?Download source from here, https://www5.zippyshare.com/v/1par8rZv/file.html

It's a very small video file, I just used it for test, so don't bother fixing that bug if it takes much time fixing it.

I don't know exactly what you mean, I think I saw something in MeGUI mentioning DGDec (but I'm not 100% sure) when encoding this video to x265-video with "One-click" encode mode.
Thanks.

[videoh]

Works fine using DGIndex/DGDecode standalone, so any issue you see must be MeGUI-related.

[Revan654]

@Revan654. When I used your Staxrip.2.0.0.0.x64, and "aq-mode" set to "Enabled", it still sets aq-mode to 2...
I hope you fix that, because I've gone over to use MeGUI instead (even though MeGUI produced a green video when using DGDec on a mpeg1-video, while Staxrip2.0 didn't (I don't know which mpeg-1 decoder it uses)).
Thanks in advance, if you fix that bug.

aq-mode in what Encoder. aq-mode doesn't give much details, since most encoders have aq-mode.

[Natty]

I got two other issues though with the tool...

1) After importing a bigger video file (like a 20GB AVC clip taken from a BluRay) the comparer seems to take a long break now where the application won't react for minutes.

2) For whatever reason source and encoded video are often (not always!) async by one frame now in the video comparison tool although frame count and fps are the same.
The same videos would show in sync when comparing with 1.7.0.6.
Would have loved to give you examples but I couldn't reproduce it with test clips.
But this could also be turned into a feature request - the ability to set a frame offset for each compared video would be something I always missed as I rarely had problems with async files in old StaxRip as well.
i have the same issue along with a few other bugs/issues but revan always replies stuffs like "nothing has been changed much" so i dont report the issues/bugs anymore.

[Forteen88]

aq-mode in what Encoder. aq-mode doesn't give much details, since most encoders have aq-mode.In x265-3.0_RC+10-672ce05_vs2017-AVX2 (msystem).7z

EDIT: Thanks videoh, for telling me. Then I can report to MeGUI-devs that there's a bug in their MPEG-1 conversion.

[Forteen88]

aq-mode in what Encoder. aq-mode doesn't give much details, since most encoders have aq-mode.Oh, never mind, they changed default AQ-mode in x265 from 1 to 2 (it might differ which preset you use). Thanks anyway.
https://bitbucket.org/multicoreware/x265/commits/b14834a9d1c1864ea7e94d9cfed4e33f37e767c6

But there should be a way to still set x265 aq-mode to 1 in StaxRip.

EDIT: Thanks ukmark for the tip using custom commandline instead.

[Revan654]

Oh, never mind, they changed default AQ-mode in x265 from 1 to 2 (it might differ which preset you use). Thanks anyway.
https://bitbucket.org/multicoreware/x265/commits/b14834a9d1c1864ea7e94d9cfed4e33f37e767c6

But there should be a way to still set x265 aq-mode to 1 in StaxRip.

If it's a default value it doesn't show up in the command line.

I tweaked the default value just in case, Uploaded the changes to the Resp.

x265 docs don't post all the changes. It hard to figure the update value change.

[katzenjoghurt]

Hey Revan. :)

I usually forget that app even exist at times. It has not been updated since 1.7.


Whaaat? That thing is so awesome to check the output quality.


- You are loading a massive file into the code, it takes time to index & cache that file. It uses FFVideoSource as the source filter using AVS.


Sure...
But try to import a big video in 1.7.0.6 and afterwards try to import it in 2.0.0.0.
In the latter the application will freeze for some time after the indexing is done.


- Many of offset is usually based off the codec, filter, or if the fps is off by .1 even if it doesn't show it in info data.


Hm. So why could 1.7.0.6 behave different than 2.0.0.0 then?
I'm back to using the old version now again because... as I said the import often takes ages now due to the freeze and every second time I can't really work with it due to that 1 frame offset which won't occur in 1.7.0.6.

It's a pity I could only reproduce it with full movies and not with some free downloaded YouTube samples to give you a test case.


It's why it's usually a good idea to respec the video before encoding just incase something is off.


respec?


- There allot of elements to take into account like range, Depth, and the display. Most PC Monitors are only 8Bit. You will not get the full effect of 10Bit color.

You're addressing the color difference between 8bit and 10bit I mentioned?
It's really some issue in that comparison tool - as I don't see those color differences when comparing VLC snapshots.
It gets pretty obvious in dark scenes.
Some other user mentioned it already here and Stax replied to it:
https://forum.doom9.org/showthread.php?p=1831455#post1831455

I checked that part of the code Stax mentions and it indeed changed.
And it feels like the colors are at least less off now. Though I still see
some slight differences sometimes - not sure if that's due to encoding though.
Didn't compare these frames in VLC yet.

[Revan654]

Hey Revan. :)



Whaaat? That thing is so awesome to check the output quality.



I just forget it exist, There are allot of files needed to create Staxrip.



Sure...
But try to import a big video in 1.7.0.6 and afterwards try to import it in 2.0.0.0.
In the latter the application will freeze for some time after the indexing is done.

Hm. So why could 1.7.0.6 behave different than 2.0.0.0 then?
I'm back to using the old version now again because... as I said the import often takes ages now due to the freeze and every second time I can't really work with it due to that 1 frame offset which won't occur in 1.7.0.6.




ffms source filter & indexer is different but that's it. The app is unchanged. It could also be dotnet(I don't have control over this).

I could try to do what I did with the thumbnailer, Which skips the index completely and loads instantly. Some files do not get along with ffms.


youtube and such are reencoded using latest standards, It very unlikely those files would create any kind of issues.



respec?


It removes all the data and sets colormatrix and such to unspec. You would unspec like so(This function is already build in to the context menu):

clip = core.resize.Point(clip, matrix_in_s="unspec",range_s="limited")
clip = core.std.AssumeFPS(clip, fpsnum = int(%media_info_video:FrameRate% * 1000), fpsden = 1000)
clip = core.std.SetFrameProp(clip=clip, prop="_ColorRange", intval=1)


Just double check the framerate section, mediainfo and such can throw it slightly off.

When you respec it you might use something like so:

clip = core.fmtc.resample (clip, css="444")
clip = core.fmtc.matrix (clip, mats="709", matd="709")
clip = core.fmtc.resample (clip, css="420")
clip = core.fmtc.bitdepth(clip, bits=8, fulls = False, fulld = False)


Some files can have strange framerates, This was file from the web. unspec would properly scale to the correct rate.

https://i.imgur.com/LN2GsRW.jpg


You're addressing the color difference between 8bit and 10bit I mentioned?
It's really some issue in that comparison tool - as I don't see those color differences when comparing VLC snapshots.
It gets pretty obvious in dark scenes.
Some other user mentioned it already here and Stax replied to it:
https://forum.doom9.org/showthread.php?p=1831455#post1831455

I checked that part of the code Stax mentions and it indeed changed.
And it feels like the colors are at least less off now. Though I still see
some slight differences sometimes - not sure if that's due to encoding though.
Didn't compare these frames in VLC yet.

When dealing with color there allot to take into account, Plus VLC uses a very engine and it has multiple ways to render including GPU.

Like I said to get the fully 10 Bit you need a 10Bit monitor plus your GPU set completely.

Not sure if the viewer processes any of the alpha channels. That could be throwing things off too. I think it just uses the standard RGB.

[ukmark]

Oh, never mind, they changed default AQ-mode in x265 from 1 to 2 (it might differ which preset you use). Thanks anyway.
https://bitbucket.org/multicoreware/x265/commits/b14834a9d1c1864ea7e94d9cfed4e33f37e767c6

But there should be a way to still set x265 aq-mode to 1 in StaxRip.

You can set it under x265 'options' then use 'custom' section to enter '--aq-mode 1' and it will show up at the bottom next to the other x265 settings.

[katzenjoghurt]

Thanks for your reply Revan.
I will play around with it.

[Malonn]

I can't update Staxrip from within the program. If I do it through the interface (tools -> advanced -> update) nothing happens, no messages; nothing. If I do it via command line, it throws a "system.exception" error. Any ideas? Is this feature a known broken that I'm not aware of?

[Revan654]

I can't update Staxrip from within the program. If I do it through the interface (tools -> advanced -> update) nothing happens, no messages; nothing. If I do it via command line, it throws a "system.exception" error. Any ideas? Is this feature a known broken that I'm not aware of?

The html code changed on github, so the source code has to be updated.

[Malonn]

Oh, okay. You have to update StaxRip. Np, np. Now I know, and knowing is half the battle.

[Revan654]

You Can Grab New Builds at Here (https://ci.appveyor.com/project/Revan654/staxrip)

https://ci.appveyor.com/api/projects/status/j0alakgd5ahkyjmw?svg=true

These will range From Beta to Final, But will not contain any External Files.

[paauw]

qsvencc is working with this 2.0.0.1 build

thanx revan

[Revan654]

qsvencc is working with this 2.0.0.1 build

thanx revan

NP.

FYI, Appveyor Names the base number. Use the Info tab to get the real build number. The First one will be accurate after that not so much.

The Filesize is about .5 megs smaller compared to MSBuilder(VS 2017).

Any xml files or pdb files can be deleted.

[Revan654]

Slight Update(From The Pipeline):

2.0.0.1 (Pipeline Version: 2.0.0.3)

- Updated Video Comparison Form, Will No longer need to index the File before View the Video.
- x265: Reset Some of the Defaults to there New defaults.
- Core: ImageUtils(Moved MKV to ffms instead of Using L-Smash)
- Core: Updated Caption for Thumbnails(If No Audio Exists it will Will leave the Field Blank).
- Core: Slight Renaming of two of Menu Items(Nothing Major)
- Core: Slight Tweak to to Temp Folder Creator, Nothing Noticeable.
- x265: AQmode Tweaked
- XAA Temp Remove from AVS, Code Needs to be Re-Worked with New Syntax.
- VS: Updated DGIndexNV Load Function It now loads using it's native method instead of AVS load function.
- VS: G41Fun replaces hnwvsfunc
- VS: hnwvsfunc Script removed
- VS: fvsfunc functions updated
- VS: Auto-Deblock Added to Context Menu
- VS: nnedi3_rpow2 added to Script folder for Support.
- VS: Added FixTelecinedFades to Context Menu for RCR.
- Encoders: Rebuilt QVSEnc Encoder Code.
- x265: Has been updated to 3.0+RC*
- x265: Updated the Defaults to there New defaults.
- x264/x265 Control CRF: Updated the Range. It Starts at 12 CRF and Ends at default value of 28.

^Just Pushed a New Update Mainly for the new VS Script and altered source filter for ImageUtil.

Mpvnet Slightly Updated:
Link: https://github.com/Revan654/mpvnet/releases/download/2.0/Mpvnet.2.0.rar

[frenchfries]

Hey

I'm loading a test MKV into stax that I have just manually updated to 2.0.0.1/2.0.0.4 and also the mpvnet update and it's asking for handbrake. That seems weird to me.

Any comment on that?

[AVspace]

I also just installed the newest update and it's requiring me to install Handbrake same as the person above when i add a source file. Is this really necessary to the program now? I'd prefer not to use that in my encoding they were working fine without it.

If it uses Handbrake in any way to encode i'd sooner go back to the older version. I haven't good experiences with encoding using that in the past.

[AVspace]

In two-pass mode using a quick first pass can anyone inform me how to change a few of the first pass settings to achieve a slightly better quality? From what i read if you change a few things like raising the -me a few notches it gives you an improvement? In my command line it just shows the same settings as my main settings and i don't seem to be able to change anything.

[Revan654]

I also just installed the newest update and it's requiring me to install Handbrake same as the person above when i add a source file. Is this really necessary to the program now? I'd prefer not to use that in my encoding they were working fine without it.

If it uses Handbrake in any way to encode i'd sooner go back to the older version. I haven't good experiences with encoding using that in the past.

I kind bundle everything in single folder. VS2017/StaxRip scanned the Folder and picked it up. It will be fixed in the next Push.

Version: 2.0.0.5 will have it Removed.

It Should be up on the Site Shortly.

[Revan654]

In two-pass mode using a quick first pass can anyone inform me how to change a few of the first pass settings to achieve a slightly better quality? From what i read if you change a few things like raising the -me a few notches it gives you an improvement? In my command line it just shows the same settings as my main settings and i don't seem to be able to change anything.

Any Defaults will not Show up, Some require additional Options to become enabled.

Just be aware When No-Slow-pass is Enabled it also enables/changes these values:

--fast-intra --no-rect --no-amp --early-skip --ref 1 --max-merge 1 - -me DIA --subme 2 --rd 2

You also try use one of the lossless flags.

These are some of the Settings I use:

--output-depth 10 --aq-mode 1 --colorprim bt709 --colormatrix bt709 --transfer bt709 --range limited --no-info --no-deblock --no-sao --no-strong-intra-smoothing

The Last three options tends to detroy the detail in the picture. I have no idea why these are enabled by default.

This is one option that a major Studio uses with x265

--output-depth 10 --cu-lossless --limit-modes --aq-mode 1 --no-open-gop --pmode --pme --colorprim bt709 --colormatrix bt709 --transfer bt709 --range limited --repeat-headers --no-info --hrd --aud --no-deblock --no-sao --psy-rd 1 --no-strong-intra-smoothing

[AVspace]

I kind bundle everything in single folder. VS2017/StaxRip scanned the Folder and picked it up. It will be fixed in the next Push.

Version: 2.0.0.5 will have it Removed.

It Should be up on the Site Shortly.

Thanks for the update. I was easily able to go back to the previous version so it wasn't too much of an issue. I'll go for 2.0.0.5

[AVspace]

Any Defaults will not Show up, Some require additional Options to become enabled.

Just be aware When No-Slow-pass is Enabled it also enables/changes these values:

--fast-intra --no-rect --no-amp --early-skip --ref 1 --max-merge 1 - -me DIA --subme 2 --rd 2

You also try use one of the lossless flags.

These are some of the Settings I use:

--output-depth 10 --aq-mode 1 --colorprim bt709 --colormatrix bt709 --transfer bt709 --range limited --no-info --no-deblock --no-sao --no-strong-intra-smoothing

The Last three options tends to detroy the detail in the picture. I have no idea why these are enabled by default.

This is one option that a major Studio uses with x265

--output-depth 10 --cu-lossless --limit-modes --aq-mode 1 --no-open-gop --pmode --pme --colorprim bt709 --colormatrix bt709 --transfer bt709 --range limited --repeat-headers --no-info --hrd --aud --no-deblock --no-sao --psy-rd 1 --no-strong-intra-smoothing

Oh, this is my fault. I forgot to mention i use 264. That's my bad.

That's still helpful though especially if i do some x265 encodes. So if it's a default value it doesn't show up in the bottom where it shows --pass 1 and i'd have to custom change it to show up. I find out what the default values for a quick first pass are and then manually adjust it. I found the "custom first pass" section in the settings so i just need to find out what the default values for a quick first pass are and enter any adjustment. I didn't realize stuff like this --colorprim bt709 --colormatrix bt709 --transfer bt709 --range limited --no-info had much of an effect i have them all set to undefined i'll look more into this.

[Revan654]

Thanks for the update. I was easily able to go back to the previous version so it wasn't too much of an issue. I'll go for 2.0.0.5

There should be zero conflict switching between version from 2.0+ and using your Settings file.

[Revan654]

Oh, this is my fault. I forgot to mention i use 264. That's my bad.

That's still helpful though especially if i do some x265 encodes. So if it's a default value it doesn't show up in the bottom where it shows --pass 1 and i'd have to custom change it to show up. I find out what the default values for a quick first pass are and then manually adjust it. I found the "custom first pass" section in the settings so i just need to find out what the default values for a quick first pass are and enter any adjustment. I didn't realize stuff like this --colorprim bt709 --colormatrix bt709 --transfer bt709 --range limited --no-info had much of an effect i have them all set to undefined i'll look more into this.

I no longer use x264, I just don't see the point.

The x264 doc hasn't been updated for years. Just Right click on the Text in x264 option(StaxRip) and it will show you the cli with it's default value(If argopt is proper typed out.)

colorprim is mainly triggers for videoplayers so it knows what settings to use when playing things back.

--no-info not sure if x264 has this option or not, It's just debug code. and it junks of the metadata.


THis is what I been using with x265, x264 should be similar.

--pass 1 --bitrate 140496 --output-depth 10 --limit-refs 1 --cu-lossless --aq-mode 1 --pmode --pme --colorprim bt709 --colormatrix bt709 --transfer bt709 --range limited --no-info --no-deblock --no-sao --psy-rd 1 --no-strong-intra-smoothing

Along with Medium Preset, 10Bit & Two Pass Mode(CBR Mode should never be used).

CRF is nice but you can not target a certain bitrate or size.

[AVspace]

It's mainly the speed benefit i get when using x264 and i was able to find very solid setting with x264 that give me good results and a look i like from being able to use higher settings with the faster encoding time.

"The x264 doc hasn't been updated for years. Just Right click on the Text in x264 option(StaxRip) and it will show you the cli with it's default value"

Thanks again. That worked.

[dev84]

Hello Revan654 thank You for keeping StaxRip alive, please tell me is Your 2.0.0. completely different software from original StaxRip 1.7.0 or is it compatible and old cfg files will work with new version or is it better to start it from zero and cfg it fresh?

Thx
Pawel

[Revan654]

Hello Revan654 thank You for keeping StaxRip alive, please tell me is Your 2.0.0. completely different software from original StaxRip 1.7.0 or is it compatible and old cfg files will work with new version or is it better to start it from zero and cfg it fresh?

Thx
Pawel

cfg file hasn't been used for ages. Everything uses .dat / srip format.

You will need to start Fresh.

[dev84]

ok, thx

[Revan654]

Python has breaking very easily as of late. This is the second time it broke without me even touching it. It finally started to work once I installed numpy & Pillow.

[brucethemoose]

Python has breaking very easily as of late. This is the second time it broke without me even touching it. It finally started to work once I installed numpy & Pillow.

You're using a portable python, right? Forgive me, its been a few months since I installed Staxrip, so I can't remember if it's an external dependency or included in the download.

Anyway, I've been fed up with Python too, which is why I love the portable install the VS Fatpack uses. It seems to be immune to borked system installs, and worst case, you can just delete the whole Python directory and restore it from an archive without hunting down other settings a regular install spreads through your system.

[Revan654]

You're using a portable python, right? Forgive me, its been a few months since I installed Staxrip, so I can't remember if it's an external dependency or included in the download.

Anyway, I've been fed up with Python too, which is why I love the portable install the VS Fatpack uses. It seems to be immune to borked system installs, and worst case, you can just delete the whole Python directory and restore it from an archive without hunting down other settings a regular install spreads through your system.

I had Anaconda installed since I needed Python Dev IDE, Since MS has no plans to update Python to 3.7 until VS 2019 gets released.

Flatpack is also almost triple the size of the base python.

StaxRip uses VFW for the preview window which requires access to the registry, It needs the python & VS registry keys. Yes you could add manually keys but it's not worth effort when install does all this work for you already. Nor the risk of screwing up your registry.

I wish there was a way to package VS into a single exe file and use it in that form. Don't think that is possible due to how VS works and how many external resources are needed.

[Schattenspieler]

You Can Grab New Builds at Here (https://ci.appveyor.com/project/Revan654/staxrip)Is what we want to download behind the "Artifacts" button? There is one StaxRip.zip with an executable and some libs and stuff in there.
Sorry if this seems like a stupid question, but there are no hints and the FAQ doesn't cover that.

[Revan654]

Is what we want to download behind the "Artifacts" button? There is one StaxRip.zip with an executable and some libs and stuff in there.
Sorry if this seems like a stupid question, but there are no hints and the FAQ doesn't cover that.

Artifact = Package Files. So, Yes.

[Schattenspieler]

Sry, didn't know and the faq there doesn't give clues. I'm used to "artifacts" being usually unwanted visual or acustic leftovers from processing videos.
Learned smth. new today! (:

[sellers]

You Can Grab New Builds at Here (https://ci.appveyor.com/project/Revan654/staxrip)

https://ci.appveyor.com/api/projects/status/j0alakgd5ahkyjmw?svg=true

These will range From Beta to Final, But will not ladbrokes bonus code (https://top10casinobonuscodes.com/ladbrokes-promo-codes) contain any External Files.

Thanks!

[Z'Hadum]

Hello Revan654,
in the latest (test) Version (2.0.0.6):
It seems that importing the encoder options does not work correct:
For example if I import the following Commandline:
--crf 20 --preset slower --tune grain --level-idc 5.1 --rd 5 --ctu 32 --psy-rdoq 4 --aq-strength 0.9 --qcomp 0.65 --cbqpoffs -3 --crqpoffs -3 --vbv-bufsize 160000 --vbv-maxrate 160000
--pbratio 1.2 --rc-lookahead 80 --min-keyint 1 --keyint 240 --no-strong-intra-smoothing --psy-rd 2.5
The Option "no-strong-intra-smoothing" is not set.

Another very small issue:
it seems the psy-rd Parameter is not in your menu or I can't find it (I found only psy-rdoq).
Afaik in past versions this options had a dedicated switch


Last but not least: :thanks: for your work. :)

regards
Z'Hadum

[Revan654]

Hello Revan654,
in the latest (test) Version (2.0.0.6):
It seems that importing the encoder options does not work correct:
For example if I import the following Commandline:
--crf 20 --preset slower --tune grain --level-idc 5.1 --rd 5 --ctu 32 --psy-rdoq 4 --aq-strength 0.9 --qcomp 0.65 --cbqpoffs -3 --crqpoffs -3 --vbv-bufsize 160000 --vbv-maxrate 160000
--pbratio 1.2 --rc-lookahead 80 --min-keyint 1 --keyint 240 --no-strong-intra-smoothing --psy-rd 2.5
The Option "no-strong-intra-smoothing" is not set.

Another very small issue:
it seems the psy-rd Parameter is not in your menu or I can't find it (I found only psy-rdoq).
Afaik in past versions this options had a dedicated switch


Last but not least: :thanks: for your work. :)

regards
Z'Hadum

psy-rd is in Other Menu at the bottom, It will only show up if it differs from the defaults(Defaults have changed recently).

Import function will only enable switches not disable them.

[Vesdaris]

Hey guys, I wanted to ask you, how is the quality of nvenc hevc 10 bit encodes on the latest nvidia gpus (Turing)?

If you set every setting to get the best quality out of it how would nvenc hevc 10 bit fare against a software hevc 10 bit? I don't care about the size being larger than hevc software endode coz it would be still smaller than x264 encode.=)

I know hardware encoders were notoriously bad once but afaik they have been getting better.

Thank you

[videoh]

The nVidia Video SDK 9 required for Turing is not yet available (Coming Soon! :sly:). So nobody can answer that yet.

[IbrahimKh]

Hi, where can I get the latest build (2.0.0.6)?
I have no idea where is the download button here https://ci.appveyor.com/project/Revan654/staxrip
and https://github.com doesn't have v 2.0.0.6

[Vesdaris]

The nVidia Video SDK 9 required for Turing is not yet available (Coming Soon! :sly:). So nobody can answer that yet.


Ah I see.. I didn't know that.

What about Pascal's hevc 10bit encodes quality? Still unacceptable?

[gonca]

Ah I see.. I didn't know that.

What about Pascal's hevc 10bit encodes quality? Still unacceptable?

They are decent enough

[Vesdaris]

When I try to install FFTW I get this error

https://imgur.com/a/fnfGd6e

Any ideas on how to fix this?

Cheers

[Episodio1]

When I try to install FFTW I get this error

https://imgur.com/a/fnfGd6e

Any ideas on how to fix this?

Cheers

I got the same error. The DLL's needed are in \StaxRip\Apps\Support\FFTW
1.) Copy 3 of them to \windows\system32
2.) Staxrip will detect them but it expects FFTW version 3.3.6. Press on "VERSION" in staxrip and type in: 3.3.8

[Revan654]

When I try to install FFTW I get this error

https://imgur.com/a/fnfGd6e

Any ideas on how to fix this?

Cheers

Your still using the beta build, This had been fixed with Final Release or Pipeline.

[Revan654]

New Pipeline Build: https://ci.appveyor.com/project/Revan654/staxrip/build/artifacts

Added Merge: Chapter Cutting Feature to MkvMuxer (Credit: wybb)

Not Sure how it works yet, Since I have not tested it.

[jkilez]

Sure...
But try to import a big video in 1.7.0.6 and afterwards try to import it in 2.0.0.0.
In the latter the application will freeze for some time after the indexing is done.

Hm. So why could 1.7.0.6 behave different than 2.0.0.0 then?
I'm back to using the old version now again because... as I said the import often takes ages now due to the freeze and every second time I can't really work with it due to that 1 frame offset which won't occur in 1.7.0.6.
ffms source filter & indexer is different but that's it. The app is unchanged. It could also be dotnet(I don't have control over this).
There definitely is a problem with the "ffmsindex.exe" included in the 2.0 package. The problem apparently does not occur when the indexing time is short, but when indexing takes more than 3-4 minutes, the indexer will actually index the file *twice*, causing StaxRip to hang while it does the second pass. The problem disappears if you replace the FFMS2 files in the 2.0 package with those from the 1.9 package.

[mcjordan]

NVEnc v4.3.1 by rigaya

Changelog:

Finally NVENC SDK 9.0 was released, so I updated it with a scatch.

[Common]
Updated to NVENC SDK 9.0. NVIDIA graphics driver 418.81 or later required.
Added B ref mode setting for HEVC encoder. (--bref-mode middle / each)

[NVEnc.auo]
- Added "quality (--preset)" and "B frame reference mode (--bref-mode)" on the setting screen.

[NVEncC]
Added --preset to readme.

According to NVENC SDK, the update point of Turing's NVENC function is as follows.

Improvement of compression efficiency by supporting B frame in HEVC.
* Other improvements in both H.264 / HEVC. Support by referring to RDO (distortion rate optimization) and multiple frames.

** important point **
Of Turing, only TU 117 (GTX 1650x) Does not support HEVC B frame, that is, TU 116 (GTX 1660x) Supports HEVC B frame in reverse.
Does it mean that TU117 does not change so much with GP 107, even if it is not bad? Even so, I do not want such a confusing thing.

https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md

[Revan654]

There definitely is a problem with the "ffmsindex.exe" included in the 2.0 package. The problem apparently does not occur when the indexing time is short, but when indexing takes more than 3-4 minutes, the indexer will actually index the file *twice*, causing StaxRip to hang while it does the second pass. The problem disappears if you replace the FFMS2 files in the 2.0 package with those from the 1.9 package.

The source code from 1.9 and 2.0 comes from the same place and the indexing code is unchanged. It's very possible the source is the issue.

[Revan654]

FYI, Here New Released Program of mine, Contact Sheet Maker Using WPF Framework. Also There a Winform version if you prefer. It uses AVS+ Portable along with ffms2 / L-Smash source filters to create the Contact Sheet.

Link: https://github.com/Revan654/Thumbnailer/releases

https://raw.githubusercontent.com/Revan654/Thumbnailer/master/Docs/Screenshots/WPFPreview.png

[jkilez]

The source code from 1.9 and 2.0 comes from the same place and the indexing code is unchanged. It's very possible the source is the issue.
You had just stated in previous post that the indexer *was* changed, and it is obvious that it has. Even the index files it creates are different from the indexer included in the 1.9 package.

From the 1.9 distro (\Apps\Plugins\Both\FFMS2\):
09/15/2018 08:28 PM 35,147 COPYING.GPLv3
02/12/2019 01:54 PM <DIR> doc
09/15/2018 08:28 PM 6,779 FFMS2.avsi
09/15/2018 08:28 PM 31,737,068 ffms2.dll
01/01/2018 03:25 PM 15,656,960 ffms2k.dll
09/15/2018 08:28 PM 3,462,877 ffmsindex.exe
5 File(s) 50,898,831 bytes

From the 2.0 distro (\Apps\Plugins\Both\FFMS2\):
02/10/2019 12:42 PM 35,147 COPYING.GPLv3
02/12/2019 01:52 PM <DIR> doc
02/10/2019 12:42 PM 6,779 FFMS2.avsi
02/10/2019 12:42 PM 31,737,068 ffms2.dll
02/10/2019 12:42 PM 13,276 ffms2.lib
02/10/2019 12:42 PM 16,110,080 ffms2k.dll
02/10/2019 12:42 PM 15,958,528 ffmsindex.exe
6 File(s) 63,860,878 bytes

Edit: Note that moving "ffmsindex.exe" from the 2.0 package to 1.9 causes 1.9 to have the same problem. There is either a problem with that version of "ffmsindex.exe" or a problem with how that version interacts with StaxRip.

[jkilez]

I have a relatively easy enhancement (or fix) request.

The Problem: When encoding with xvid_encraw using the "-progress" option, the little status bar in the "job processing" window does not get used, and the actual log file gets filled up with many lines of progess updates. This is not a problem if the "-progress" option is not used, but that default output is not as useful as the "-progess" output, which looks like this:
1441 frames( 19%) encoded, 40.45 fps, Average Bitrate = 4856kbps
1451 frames( 19%) encoded, 40.34 fps, Average Bitrate = 4884kbps
1461 frames( 20%) encoded, 40.28 fps, Average Bitrate = 4899kbps
1471 frames( 20%) encoded, 40.23 fps, Average Bitrate = 4911kbps
The Fix: Add another SkipString definition for "xvid_encraw" so that the "-progress" output is properly processed.

In file "Encoding\VideoEncoder.vb" lines 517-527 (changes in red):
Function GetSkipStrings(commands As String) As String()
If commands.Contains("xvid_encraw") Then
Return {"key=", "frames("}
ElseIf commands.Contains("x264") Then
Return {"%]"}
ElseIf commands.Contains("NVEnc") Then
Return {"frames: "}
Else
Return {" [ETA ", ", eta ", "frames: ", "frame= "}
End If
End Function
As this output includes a percentage value, it would also allow the little graphical progress bar in the "job processing" window to function when encoding with Xvid.

[Revan654]

You had just stated in previous post that the indexer *was* changed, and it is obvious that it has. Even the index files it creates are different from the indexer included in the 1.9 package.

From the 1.9 distro (\Apps\Plugins\Both\FFMS2\):
09/15/2018 08:28 PM 35,147 COPYING.GPLv3
02/12/2019 01:54 PM <DIR> doc
09/15/2018 08:28 PM 6,779 FFMS2.avsi
09/15/2018 08:28 PM 31,737,068 ffms2.dll
01/01/2018 03:25 PM 15,656,960 ffms2k.dll
09/15/2018 08:28 PM 3,462,877 ffmsindex.exe
5 File(s) 50,898,831 bytes

From the 2.0 distro (\Apps\Plugins\Both\FFMS2\):
02/10/2019 12:42 PM 35,147 COPYING.GPLv3
02/12/2019 01:52 PM <DIR> doc
02/10/2019 12:42 PM 6,779 FFMS2.avsi
02/10/2019 12:42 PM 31,737,068 ffms2.dll
02/10/2019 12:42 PM 13,276 ffms2.lib
02/10/2019 12:42 PM 16,110,080 ffms2k.dll
02/10/2019 12:42 PM 15,958,528 ffmsindex.exe
6 File(s) 63,860,878 bytes

Edit: Note that moving "ffmsindex.exe" from the 2.0 package to 1.9 causes 1.9 to have the same problem. There is either a problem with that version of "ffmsindex.exe" or a problem with how that version interacts with StaxRip.

I don't think you completely read what I said. Second this isn't a StaxRip issue but an issue with ffmsindex, The commands are being passed just fine.

[RainyDog]

Hi Revan, I add a few additional AVS scripts such as FillBorders, BalanceBorders etc. into StaxRip Filter Profiles so they're there as selectable options in the menus.

I'm looking to migrate over to Vapoursynth but I can't seem to make any sense out of how the scripting works on a basic level. I've got FillBorders up and running in VS using clip = core.fb.FillBorders() through trial and error.

But, for example, would you know how I can get VS script bbmod2 (https://pastebin.com/YMBnDLE4) working in StaxRip please?

I've got as far as saving the script as a .py file in C:\Program Files\VapourSynth\plugins64 anyway :)

Thanks! :thanks:

[jkilez]

Found another little glitch...

The Problem: When running an Xvid compressibility check, the recorded time stats in the log are erroneous due to the start time not being set properly. It gives an output like this:

Start: 12:00:00 AM
End: 11:46:17 AM
Duration: 17690435:46:17

53 %

The Fix: Move the initial Xvid compressibility check log messages to the "proc" routine. The start time is set when the proc.header is logged. When a new proc structure is created, it has its own LogBuilder structure, which would require the header to logged within that context.

Another minor side glitch: The log file should probably be saved at the end of the routine so that the log gets flushed. As it stands, the compressibility percentage value does not make it into the log until something else is logged or the project closed.

In file "Encoding\VideoEncoder.vb" lines 569- (Deletions in Blue, Additions in Red):

Overrides Sub RunCompCheck()
If CompCheckCommandLines = "" OrElse CompCheckCommandLines.Trim = "" Then
ShowConfigDialog()
Exit Sub
End If

If Not g.VerifyRequirements Then Exit Sub
If Not g.IsValidSource Then Exit Sub

Log.WriteHeader("Compressibility Check")

Dim script As New VideoScript
script.Engine = p.Script.Engine
script.Filters = p.Script.GetFiltersCopy
Dim code As String
Dim every = ((100 \ p.CompCheckRange) * 14).ToString

If script.Engine = ScriptEngine.AviSynth Then
code = "SelectRangeEvery(" + every + ",14)"
Else
code = "fpsnum = clip.fps_num" + BR + "fpsden = clip.fps_den" + BR +
"clip = core.std.SelectEvery(clip = clip, cycle = " + every + ", offsets = range(14))" + BR +
"clip = core.std.AssumeFPS(clip = clip, fpsnum = fpsnum, fpsden = fpsden)"
End If

Log.WriteLine(code + BR2)
script.Filters.Add(New VideoFilter("aaa", "aaa", code))
script.Path = p.TempDir + p.TargetFile.Base + "_CompCheck." + script.FileType
script.Synchronize()

Dim batchPath = p.TempDir + p.TargetFile.Base + "_CompCheck.bat"
Dim batchCode = Proc.WriteBatchFile(batchPath, GetBatchCode(Macro.Expand(CompCheckCommandLines)))
Log.WriteLine(batchCode + BR2)

Using proc As New Proc
proc.Header = "Compressibility Check"
proc.WriteLog(code + BR2)
proc.WriteLog(batchCode + BR2)
proc.SkipStrings = GetSkipStrings(batchCode)
proc.File = "cmd.exe"
proc.Arguments = "/C call """ + batchPath + """"

Try
proc.Start()
Catch ex As AbortException
Exit Sub
Catch ex As Exception
g.ShowException(ex)
Exit Sub
End Try
End Using

Dim bits = (New FileInfo(p.TempDir + p.TargetFile.Base + "_CompCheck." + OutputExt).Length) * 8
p.Compressibility = (bits / script.GetFrames) / (p.TargetWidth * p.TargetHeight)

OnAfterCompCheck()

g.MainForm.Assistant()

Log.WriteLine(CInt(Calc.GetPercent).ToString() + " %")
Log.Save()
End Sub

[Revan654]

Hi Revan, I add a few additional AVS scripts such as FillBorders, BalanceBorders etc. into StaxRip Filter Profiles so they're there as selectable options in the menus.

I'm looking to migrate over to Vapoursynth but I can't seem to make any sense out of how the scripting works on a basic level. I've got FillBorders up and running in VS using clip = core.fb.FillBorders() through trial and error.

But, for example, would you know how I can get VS script bbmod2 (https://pastebin.com/YMBnDLE4) working in StaxRip please?

I've got as far as saving the script as a .py file in C:\Program Files\VapourSynth\plugins64 anyway :)

Thanks! :thanks:

All Scripts need to be saved to the Staxrip/Apps/Plugins/VS/Scripts.

Then you just need to use the import command to use them.

It will usually always be clip = scriptname.function(source, syntax)

bbmod2(c, cTop = None, cBottom = None, cLeft = None, cRight = None, thresh = 128, blur = 999)

It should be something like this:

import Scriptname
clip = Scriptname.bbmod2(clip, options....)

My suggestion is learn a bit of Python that way VS will be very easy to understand or have Staxrip build a script and use that as a reference point.

[Revan654]

Found another little glitch...

The Problem: When running an Xvid compressibility check, the recorded time stats in the log are erroneous due to the start time not being set properly. It gives an output like this:



Your likely the only person who actually still uses XviD, XviD code hasn't been updated since 2016-. Instead of keep posting source code, just submit a merge on github. If it passes it could then possible be added to the Code if it passes Testing.

[RainyDog]

All Scripts need to be saved to the Staxrip/Apps/Plugins/VS/Scripts.

Then you just need to use the import command to use them.

It will usually always be clip = scriptname.function(source, syntax)

bbmod2(c, cTop = None, cBottom = None, cLeft = None, cRight = None, thresh = 128, blur = 999)

It should be something like this:

import Scriptname
clip = Scriptname.bbmod2(clip, options....)

My suggestion is learn a bit of Python that way VS will be very easy to understand or have Staxrip build a script and use that as a reference point.

Thanks Revan.

But I've copied the script file into the Staxrip/Apps/Plugins/VS/Scripts folder and still can't get it to work unfortunately.

Both the scriptname and function is bbmod2, but clip = bbmod2.bbmod2(c, cTop = None, cBottom = None, cLeft = None, cRight = None, thresh = 128, blur = 999) still throws up the following error :-

Python exception: name 'bbmod2' is not defined

Traceback (most recent call last):
File "src\cython\vapoursynth.pyx", line 1927, in vapoursynth.vpy_evaluateScript
File "src\cython\vapoursynth.pyx", line 1928, in vapoursynth.vpy_evaluateScript
File "C:\Encoding\Source\The Revenge A S..._temp\The Revenge A Scar That Never Disappears (1996).vpy", line 12, in <module>
clip = bbmod2.bbmod2(c, cTop = None, cBottom = None, cLeft = None, cRight = None, thresh = 128, blur = 999)
NameError: name 'bbmod2' is not defined

[Revan654]

Thanks Revan.

But I've copied the script file into the Staxrip/Apps/Plugins/VS/Scripts folder and still can't get it to work unfortunately.

Both the scriptname and function is bbmod2, but clip = bbmod2.bbmod2(c, cTop = None, cBottom = None, cLeft = None, cRight = None, thresh = 128, blur = 999) still throws up the following error :-

That's because you didn't define your source & you didn't import the Script.

import ScriptName
clip = bbmod2.bbmod2(c, cTop = None, cBottom = None, cLeft = None, cRight = None, thresh = 128, blur = 999)

c should be replaced with clip

ScriptName should be replaced with the name of the script.

[fredlkrue]

I am trying to update StaxRip but I am getting the following message, any idea how to fix it?:

https://i.imgur.com/zmpyPDH.png

[jkilez]

Your likely the only person who actually still uses XviD, XviD code hasn't been updated since 2016-.
I assumed that the Xvid code would not be a high priority. That is why I spent the time to investigate the issues and provided solutions to the problems found.

Instead of keep posting source code, just submit a merge on github. If it passes it could then possible be added to the Code if it passes Testing.
Hopefully, there will not be a need to post more code, but if I spot more glitches, I will check out the github merge process.

[Revan654]

I assumed that the Xvid code would not be a high priority. That is why I spent the time to investigate the issues and provided solutions to the problems found.


Hopefully, there will not be a need to post more code, but if I spot more glitches, I will check out the github merge process.

XviD is considered Legacy, I've been considering just to drop it Completely and let it remain in FFmpeg.

Any Code Posted So far should also be added to merge.

[Revan654]

I am trying to update StaxRip but I am getting the following message, any idea how to fix it?:

https://i.imgur.com/zmpyPDH.png

That looks like old Code, It's all based on how you make a connection with github. That message looks to be from sourceForge connection when StaxRip used 7zip portable.

Things keep changing and it's hard to keep up with them. I never really bothered with the API. I should look into one day.

It will not download any releases from the Pipeline (https://ci.appveyor.com/project/Revan654/staxrip/build/artifacts) you have to do that manually. I don't think appveyor has an API, The site uses unique keys. You would need to do a bunch of web scrapping to get the key Which Requires cookiedata + another Key to create the key, then use that key to obtain the dl page.

My other Program does it for another site, Code is another 300+ lines and Usage of RestAPI. I really don't want to add more files to required files for StaxRip to run.

[gonca]

My needs are simple
I want to load a Vaporsynth/Avisynth script and use the encoder of my choice. Then I would mux to MKV (video only)
Is there a way to use StaxRip with only x265 and Mkvmerge (no AvsMeter, BDSup2Sub, etc)

[fredlkrue]

That looks like old Code, It's all based on how you make a connection with github. That message looks to be from sourceForge connection when StaxRip used 7zip portable.

Things keep changing and it's hard to keep up with them. I never really bothered with the API. I should look into one day.

It will not download any releases from the Pipeline (https://ci.appveyor.com/project/Revan654/staxrip/build/artifacts) you have to do that manually. I don't think appveyor has an API, The site uses unique keys. You would need to do a bunch of web scrapping to get the key Which Requires cookiedata + another Key to create the key, then use that key to obtain the dl page.

My other Program does it for another site, Code is another 300+ lines and Usage of RestAPI. I really don't want to add more files to required files for StaxRip to run.
Its not a big deal, I can update it manually, thanks.

P.S. Where do I get all the updated 3rd party apps used by StaxRip?

[Magik Mark]

Raven

v20013 temp file directory doesn't save in your preferred location

[jkilez]

Any Code Posted So far should also be added to merge.
Sure thing. A pull request has been created.

[Revan654]

Raven

v20013 temp file directory doesn't save in your preferred location

Like I said it's Completely untested. Other then MKVToolNix function nothing was changed.

[jkilez]

Like I said it's Completely untested. Other then MKVToolNix function nothing was changed.
Just created another pull request for the temp file glitch.

[jkilez]

Like I said it's Completely untested. Other then MKVToolNix function nothing was changed.Just created another pull request for the temp file glitch.

Revan- The new change that you made only fixes the issue for Windows 10. For other versions, it still does not check if TempDir is already defined. Please, just take a look at the code order in my pull request.

[jkilez]

Any Code Posted So far should also be added to merge.Sure thing. A pull request has been created.
Revan- Thank you for merging in the Xvid fixes. It works much better now.

[Revan654]

Revan- The new change that you made only fixes the issue for Windows 10. For other versions, it still does not check if TempDir is already defined. Please, just take a look at the code order in my pull request.

Everythingis still WIP. I was half asleep when I wrote it. Elseif Statement just needs to be added.

**Edit**

Re-Wrote it with different form of Try and removed the need to know the OS.

[Natty]

There definitely is a problem with the "ffmsindex.exe" included in the 2.0 package. The problem apparently does not occur when the indexing time is short, but when indexing takes more than 3-4 minutes, the indexer will actually index the file *twice*, causing StaxRip to hang while it does the second pass. The problem disappears if you replace the FFMS2 files in the 2.0 package with those from the 1.9 package.

you are right. it lags and even fails sometimes. :)

[MrScientist]

Hello, thank you for continuing to support this project. When I choose Intel H.264 or Intel H.265, I receive the following message...

"NullReferenceException (2.0.0.0)

Object reference not set to an instance of an object.

System.NullReferenceException: Object reference not set to an instance of an object.
at StaxRip.QSVEnc.EncoderParams.OnValueChanged(CommandLineParam item)
at StaxRip.BasicVideoEncoder.ImportCommandLine(String commandLine, CommandLineParams params)"

I have Intel 8700K with UHD 630 graphics and current graphics drivers.

Thank you.

[Revan654]

Hello, thank you for continuing to support this project. When I choose Intel H.264 or Intel H.265, I receive the following message...

"NullReferenceException (2.0.0.0)

Object reference not set to an instance of an object.

System.NullReferenceException: Object reference not set to an instance of an object.
at StaxRip.QSVEnc.EncoderParams.OnValueChanged(CommandLineParam item)
at StaxRip.BasicVideoEncoder.ImportCommandLine(String commandLine, CommandLineParams params)"

I have Intel 8700K with UHD 630 graphics and current graphics drivers.

Thank you.

Your using Old Build which has Been tweaked in the Pipeline builds and make sure QS is Enabled.

On Skylake if your using GPU like Nvidia. QS would not enable unless you tweak the setting in your Bios. Not sure if intel/ Motherboards have changed this Since Skylake release.

[Revan654]

you are right. it lags and even fails sometimes. :)

ffindex does use LAVF demuxer, Without that or some other demuxer ffindex will struggle. It's why I try to compile a static version of ffindex with some resource already contained inside.

I guess i'm the only one with ffindex working correctly.


When using MP4 L-Smash Should be used, Other Formats DG or ffms should be used.

------

honestly, I would upgrade to DGDecNV and pay the tiny amount of money. Since it's well worth the price.

Only common format that it does not support are Apple formats(Not yet atlease Based on Dec Release) & VP9(Using Webm).

Link: http://rationalqm.us/dgdecnv/dgdecnv.html

[RainyDog]

Hi Revan, save as PNG from the preview window is broken in the latest pipeline build.

Save as JPG works fine though.

[Revan654]

Hi Revan, save as PNG from the preview window is broken in the latest pipeline build.

Save as JPG works fine though.

Works perfectly fine at my end. Nothing has been altered with preview window.

[Natty]

is it possible to get option to view bitrate used in preview window? :)

[videoh]

honestly, I would upgrade to DGDecNV You're my hero, Revan654. You know that. You know it's true.

[Revan654]

is it possible to get option to view bitrate used in preview window? :)

In it's current State, No. It doesn't use MediaInfo or anything like that for displaying those values. It uses Windows resources when building the data.

Not sure of all functions and sub functions of avifil32.dll. Plus can't really find any docs for it, When you try google it you get nothing but How to fix missing dll problems.

[MrScientist]

Thank you for the info. The Pipeline build works.

Just FYI, there were no BIOS settings on either my Kaby Lake or Coffee Lake motherboards to turn on QSV. It's on automatically.

Your using Old Build which has Been tweaked in the Pipeline builds and make sure QS is Enabled.

On Skylake if your using GPU like Nvidia. QS would not enable unless you tweak the setting in your Bios. Not sure if intel/ Motherboards have changed this Since Skylake release.

[vanden]

Hello,

when I do a "Run Compressibility Check" I have an error Error :Error Compressibility Check using x265 2.9+34 (2.0.0.1)

Compressibility Check using x265 2.9+34 failed with exit code: -1073741795 (0xC000001D)

The exit code might be a system error code: {EXCEPTION}
Instruction non autorisée
Tentative d’exécution d’une instruction interdite.


--------------- Compressibility Check using x265 2.9+34 ---------------

"C:\Program Files\Staxrip.2.x64\Apps\Support\avs2pipemod\avs2pipemod64.exe" -y4mp F:\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_temp\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_new_source_CompCheck.avs | "C:\Program Files\Staxrip.2.x64\Apps\Encoders\x265\x265.exe" --crf 18 --output-depth 10 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "1529,380" --hdr --repeat-headers --hrd --aud --frames 8358 --y4m --output F:\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_temp\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_new_source_CompCheck.hevc -

avs2pipemod[info]: writing 8358 frames of 24000/1001 fps, 3840x1606,
sar 0:0, YUV-420-planar-8bit progressive video.
avs2pipemod[info]: finished, wrote 0 frames [0%].
avs2pipemod[info]: total elapsed time is 1.470 sec.
avs2pipemod[error]: only wrote 0 of 8358 frames.



StaxRip.ErrorAbortException: Compressibility Check using x265 2.9+34 failed with exit code: -1073741795 (0xC000001D)

The exit code might be a system error code: {EXCEPTION}
Instruction non autorisée
Tentative d’exécution d’une instruction interdite.


--------------- Compressibility Check using x265 2.9+34 ---------------

"C:\Program Files\Staxrip.2.x64\Apps\Support\avs2pipemod\avs2pipemod64.exe" -y4mp F:\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_temp\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_new_source_CompCheck.avs | "C:\Program Files\Staxrip.2.x64\Apps\Encoders\x265\x265.exe" --crf 18 --output-depth 10 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "1529,380" --hdr --repeat-headers --hrd --aud --frames 8358 --y4m --output F:\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_temp\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_new_source_CompCheck.hevc -

avs2pipemod[info]: writing 8358 frames of 24000/1001 fps, 3840x1606,
sar 0:0, YUV-420-planar-8bit progressive video.
avs2pipemod[info]: finished, wrote 0 frames [0%].
avs2pipemod[info]: total elapsed time is 1.470 sec.
avs2pipemod[error]: only wrote 0 of 8358 frames.


à StaxRip.Proc.Start()
à StaxRip.x265Enc.Encode(String passName, String commandLine, ProcessPriorityClass priority)
à StaxRip.x265Enc.RunCompCheck()
Does anyone have an idea of the problem ?
And same with encode :
Error Video encoding using x265 2.9+34 (2.0.0.1)

Video encoding using x265 2.9+34 failed with exit code: -1073741795 (0xC000001D)

The exit code might be a system error code: {EXCEPTION}
Instruction non autorisée
Tentative d’exécution d’une instruction interdite.


------------------- Video encoding using x265 2.9+34 -------------------

"C:\Program Files\Staxrip.2.x64\Apps\Support\avs2pipemod\avs2pipemod64.exe" -y4mp F:\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_temp\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_track1_[eng].avs | "C:\Program Files\Staxrip.2.x64\Apps\Encoders\x265\x265.exe" --pass 1 --bitrate 6014 --preset slow --tune fastdecode --output-depth 10 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "1529,380" --hdr --repeat-headers --hrd --aud --frames 167130 --y4m --stats F:\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_temp\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_track1_[eng].stats --output NUL -

avs2pipemod[info]: writing 167130 frames of 24000/1001 fps, 3840x1606,
sar 0:0, YUV-420-planar-8bit progressive video.
avs2pipemod[info]: finished, wrote 0 frames [0%].
avs2pipemod[info]: total elapsed time is 1.196 sec.
avs2pipemod[error]: only wrote 0 of 167130 frames.



StaxRip.ErrorAbortException: Video encoding using x265 2.9+34 failed with exit code: -1073741795 (0xC000001D)

The exit code might be a system error code: {EXCEPTION}
Instruction non autorisée
Tentative d’exécution d’une instruction interdite.


------------------- Video encoding using x265 2.9+34 -------------------

"C:\Program Files\Staxrip.2.x64\Apps\Support\avs2pipemod\avs2pipemod64.exe" -y4mp F:\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_temp\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_track1_[eng].avs | "C:\Program Files\Staxrip.2.x64\Apps\Encoders\x265\x265.exe" --pass 1 --bitrate 6014 --preset slow --tune fastdecode --output-depth 10 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "1529,380" --hdr --repeat-headers --hrd --aud --frames 167130 --y4m --stats F:\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_temp\Passengers.2016.2160p.UHD.BluRay.HEVC.HDR.Muti.VFF.DTS-HD.MA-tlub_track1_[eng].stats --output NUL -

avs2pipemod[info]: writing 167130 frames of 24000/1001 fps, 3840x1606,
sar 0:0, YUV-420-planar-8bit progressive video.
avs2pipemod[info]: finished, wrote 0 frames [0%].
avs2pipemod[info]: total elapsed time is 1.196 sec.
avs2pipemod[error]: only wrote 0 of 167130 frames.


à StaxRip.Proc.Start()
à StaxRip.x265Enc.Encode(String passName, String commandLine, ProcessPriorityClass priority)
à StaxRip.x265Enc.Encode()
à StaxRip.GlobalClass.ProcessVideo()
à System.Threading.Tasks.Parallel.<>c__DisplayClass4_0.<Invoke>b__0()
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
à StaxRip.GlobalClass.ProcessJob(String jobPath)
Work with x264 ... !!

[vanden]

Well finally I found the problem : it is the x265 version provided by staxrip (2.9 + 34) that does not work at home.
Replace with version 3.0_Au + 7 it works.

I still have some questions my source file is 420 10bit HDR :

1. In the AVS file I have: format = "YUV420P8" and in the encoding log I have :
avs2pipemod [info]: writing 2843 frames of 24000/1001 fps, 3840x1600,
sar 0: 0, YUV-420-planar-8bit progressive video.
y4m [info]: 3840x1600 fps 24000/1001 i420p8 unknown frame count
raw [info]: output file: NUL

Normally it should not be 10 bit ?

2. in the encoding log I also :
x265 [warning]: NAL HRD parameters require VBV parameters, ignored

What do these parameters correspond to ?

3. Is it better to use LSMASHSource.dll or ffms2.dll ?

Are there any other parameters to modify to encode in HDR ?

[sneaker_ger]

1. Your AviSynth script seems to convert to 8 bit.
2. --vbv-maxrate and --vbv-bufsize
3. ffms2 is a bit simpler because it supports native high-bitdepth formats. (i.e. it might solve question/problem 1)

[vanden]

OK, thanks

I redid a test with ffms2 but in the encoding log I always 8bit :
------------------ Video encoding using x265 3.0_Au+7 ------------------

"C:\Program Files\Staxrip.2.x64\Apps\Support\avs2pipemod\avs2pipemod64.exe" -y4mp F:\Lucy_temp\Test-001_new.avs | "C:\Program Files\Staxrip.2.x64\Apps\Encoders\x265\x265.exe" --pass 1 --bitrate 9161 --output-depth 10 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte2084 --range limited --max-cll "1000,400" --hdr --repeat-headers --hrd --aud --frames 2843 --y4m --stats F:\Lucy_temp\Test-001_new.stats --output NUL -

avs2pipemod[info]: writing 2843 frames of 24000/1001 fps, 3840x1600,
sar 0:0, YUV-420-planar-8bit progressive video.
y4m [info]: 3840x1600 fps 24000/1001 i420p8 unknown frame count
raw [info]: output file: NUL
x265 [info]: HEVC encoder version 3.0_Au+7-cb3e172a5f51
x265 [info]: build info [Windows][GCC 8.2.1][64 bit] 10bit
x265 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.1 Cache64
x265 [info]: Main 10 profile, Level-5 (Main tier)
x265 [info]: Thread pool created using 24 threads
x265 [info]: Slices : 1
x265 [info]: frame threads / pool features : 4 / wpp(25 rows)
x265 [warning]: NAL HRD parameters require VBV parameters, ignored
x265 [info]: Coding QT: max CU size, min CU size : 64 / 8
x265 [info]: Residual QT: max TU size, max depth : 32 / 1 inter / 1 intra
x265 [info]: ME / range / subpel / merge : hex / 57 / 2 / 2
x265 [info]: Keyframe min / max / scenecut / bias: 23 / 250 / 40 / 5.00
x265 [info]: Lookahead / bframes / badapt : 20 / 4 / 2
x265 [info]: b-pyramid / weightp / weightb : 1 / 1 / 0
x265 [info]: References / ref-limit cu / depth : 3 / on / on
x265 [info]: AQ: mode / str / qg-size / cu-tree : 2 / 1.0 / 32 / 1
x265 [info]: Rate Control / qCompress : ABR-9161 kbps / 0.60
x265 [info]: tools: rd=3 psy-rd=2.00 rskip signhide tmvp strong-intra-smoothing
x265 [info]: tools: lslices=8 deblock sao stats-write
can it be necessary to specify 10 bit in the file avs ?
My AVS :
LoadCPlugin("C:\Program Files\Staxrip.2.x64\Apps\Plugins\both\ffms2\ffms2.dll")
FFVideoSource("F:\Lucy_temp\Test-001.mkv", colorspace = "YV12", \
cachefile = "F:\Lucy_temp\Test-001.ffindex")
What are the value for --vbv-maxrate and --vbv-bufsize on Bluray UHD ?

[sneaker_ger]

Try to remove "colorspace" parameter:
LoadCPlugin("C:\Program Files\Staxrip.2.x64\Apps\Plugins\both\ffms2\ffms2.dll")
FFVideoSource("F:\Lucy_temp\Test-001.mkv", cachefile = "F:\Lucy_temp\Test-001.ffindex")

[vanden]

Super it works ! Thank you !
avs2pipemod[info]: writing 2843 frames of 24000/1001 fps, 3840x1600,
sar 0:0, YUV-420-planar-10bit progressive video.
y4m [info]: 3840x1600 fps 24000/1001 i420p10 unknown frame count

[Magik Mark]

Guys,

Is there a guideline in coverting UHD hdr(mkv) to Blueray(mkv)?

[vanden]

Just resize in 1920x1080, do a tone mapping (+Add/Color/HDRCore/Tone Mapping).
Choose between DGReinhard and DGHable.
Encode in x264.

[Revan654]

OK, thanks

I redid a test with ffms2 but in the encoding log I always 8bit :

What are the value for --vbv-maxrate and --vbv-bufsize on Bluray UHD ?

If not defined it uses the default value which is 0.

--blu-ray-compat to x265, enforcing profile, level and tier limits as well as GOP structure limitations defined by the Blu-Ray Disc Association.

If I recall Flag is mainly for Legacy devices, It does nothing for newer hardware that has HDR / UHD support.

Many of the auto Switches are set to 8 Bit, I should remove them, Since allot are creating more problems then they solve.

[Revan654]

1. Your AviSynth script seems to convert to 8 bit.
2. --vbv-maxrate and --vbv-bufsize
3. ffms2 is a bit simpler because it supports native high-bitdepth formats. (i.e. it might solve question/problem 1)

3. Kind of, It's support some. I could never get some P010 source to load correctly. Same goes with other 10Bit+ Formats.

[Revan654]

Well finally I found the problem : it is the x265 version provided by staxrip (2.9 + 34) that does not work at home.
Replace with version 3.0_Au + 7 it works.

I still have some questions my source file is 420 10bit HDR :

1. In the AVS file I have: format = "YUV420P8" and in the encoding log I have :
avs2pipemod [info]: writing 2843 frames of 24000/1001 fps, 3840x1600,
sar 0: 0, YUV-420-planar-8bit progressive video.
y4m [info]: 3840x1600 fps 24000/1001 i420p8 unknown frame count
raw [info]: output file: NUL

Normally it should not be 10 bit ?

2. in the encoding log I also :
x265 [warning]: NAL HRD parameters require VBV parameters, ignored

What do these parameters correspond to ?

3. Is it better to use LSMASHSource.dll or ffms2.dll ?

Are there any other parameters to modify to encode in HDR ?

Yes, All Flags & data required have been posted a few pages back. You need to met all of them for certain functions to work(x265).

StaxRip switched to 3.0 awhile ago.

FYI, I have no idea if x265 flag HRD Concat is correctly marked or not. the cli list it as ---hrd-concat and the doc has it as the normal two dash flag --hrd-concat. I assume it an oversight in the cli

If it's MP4 LSMASHSource(LWLibavVideoSource should be used since it has a larger range of support) Just be careful with ffms2 it has a history of reporting incorrect metadata since it doesn't read certain mediaFiles correctly.

[Revan654]

Anyone Here who codes or using VS 2019 RC build? Notice any type freezing where you can't type anyone without re-clicking the screen?

https://i.imgur.com/yuF7r4Uh.jpg

[Magik Mark]

Raven,

There are times the default source doesn't work. I have to explicitly put "LWLibavVideoSource". I was wondering why does it create a "*.lwi" file in the source directory instead in the designated temp folder?

[Revan654]

Raven,

There are times the default source doesn't work. I have to explicitly put "LWLibavVideoSource". I was wondering why does it create a "*.lwi" file in the source directory instead in the designated temp folder?

Technically ffms2 should work the best with most formats. It's why it's listed as default. it's just best guess based on what has worked in the past. Of course with newer formats being released it's hard to judge now of days.

I really wish some more sourcefilters would get released to expand source filter choices.

DG Index works the best with most common formats(minus webm (Since there VP9 or VP8) and Apple encoded mp4 files. videoh has apple supported files planned for releases sometime in the future. The tool is Well worth the small fee if you got hardware that supports it.

.lwi is created where ever the source is (This is hard coded inside the dll), I can't do anything about that Since it's not directly tied to StaxRip.

If you call ffms2 without indexing it will create a similar type file. Technically I could tell StaxRip to delete the file Once encoding is complete. However It could screw things up with the encoding process if you try to encode it again.

With the Thumbnailer, I have it set to auto delete the index file once done.

[Revan654]

VS 2019 Visual Basic Setting: This feature is not available yet(Where C# version is). I guess MS really wants to kill of VB and WinForms based on whats being updated in dotnet 4.8.

[Natty]

latest ffms2 has so many bugs so you may try to use older version. this is a new trend.

https://forum.doom9.org/showthread.php?p=1866797#post1866797

[Revan654]

latest ffms2 has so many bugs so you may try to use older version. this is a new trend.

https://forum.doom9.org/showthread.php?p=1866797#post1866797

StaxRip doesn't use the base ffms2(It's Included if Needed). It uses ffms2 C-plugin.

[zildan]

StaxRip is the best tool,
congratulations

Please add
ffmpeg | AMD | Amd H.264 -c:v h264_amf
ffmpeg | AMD | Amd H.265 -c:v hevc_amf

VCEEncC replace with version 4.02 (https://drive.google.com/open?id=1FsRO-F8jNYYGz8OLijEst9usH-jc8LVI)by rigaya, build Dec 11 2018 21:03:34,

and add :

--crop <int>,<int>,<int>,<int>
set crop pixels of left, up, right, bottom.

option.


I have Amd Ryzen7 with VEGA 10 (https://www.amd.com/en/products/apu/amd-ryzen-7-2700u)

With VCEEncC (x64) 4.02 it encodes 120 FPS 1080 HEVC using LAV Video Decoder 0.73.1

thank you

[suckerpuncher]

@Revan654
Thanks for your work on StaxRip. Is there any ETA on an updated version?

[Revan654]

@Revan654
Thanks for your work on StaxRip. Is there any ETA on an updated version?

There always a newer Beta release in the pipeline.

[Revan654]

StaxRip is the best tool,
congratulations

Please add
ffmpeg | AMD | Amd H.264 -c:v h264_amf
ffmpeg | AMD | Amd H.265 -c:v hevc_amf

VCEEncC replace with version 4.02 (https://drive.google.com/open?id=1FsRO-F8jNYYGz8OLijEst9usH-jc8LVI)by rigaya, build Dec 11 2018 21:03:34,

and add :

--crop <int>,<int>,<int>,<int>
set crop pixels of left, up, right, bottom.

option.


I have Amd Ryzen7 with VEGA 10 (https://www.amd.com/en/products/apu/amd-ryzen-7-2700u)

With VCEEncC (x64) 4.02 it encodes 120 FPS 1080 HEVC using LAV Video Decoder 0.73.1

thank you

Crop already exists, it has for a very long time. It's done by using crop hardware function.

[Revan654]

Release 2.0.0.1 Beta

2.0.0.1 Beta
- Tweaked the Groupbox UI Scaling for lower DPI Monitors (Credit: Stax76)
- This is a pure Refresh Release, Mainily designed to update some of the encoding tools.
- This Release contains all the Changes from the Pipeline along with the Following.
- Updated Temp Folder Creation and Long Path Checker (Usually Only used on OS below Windows 10 or Non-NTFS harddrive)
- Updated Comparison Tool It shouldn't need to index file when ffms2 is used.
- Updated Both Contact Sheet Creator and Video Comparison tool to use LWLibavVideoSource over the Standard L-Smash.
- Updated Visual Studio to 2019 RC, Anything Compiled will be using RC Build of VS 2019.
- Included additional config files for dotnet 4.8 along with standard 4.7.2.
- VS: The default Resizer Code is slightly Different Compared to Base VS Resizer Code in the Context Menu.
- VS: SVPFlow Altered to Target CurrentFramte & Num / Den to achieve the Final Framerate instead of rounding. Type quality has also been Changed, aswell linear light support has been added (GPU Only).
- x265: AQmode Tweaked for the new Defaults.
- XAA Remove from AVS (Temp), due to certain Functions being alter in AVS+ core. Will be Re-Added Once Re-Coded.
- VS: Updated DGIndexNV Load Function It now loads using it's native method instead of AVS load function.
- VS: G41Fun replaces hnwvsfunc
- VS: hnwvsfunc Script removed
- VS: fvsfunc functions updated
- VS: Auto-Deblock Added to Context Menu
- VS: nnedi3_rpow2 added to Script folder for Support.
- VS: Added FixTelecinedFades to Context Menu for RCR.
- Core: Fixed Some of Search Paths, They didn't include the sub folders in rare cases.
- Rebuilt QVSEnc Encoder Script, Added Pre-Check and Will become Enabled as long as your CPU support QSV Encoding(Note Some QSV enabled CPU's only support decoding).
- x265 Has been updated to 3.0-AU+ With any Additional Changes.
- Tweaked some of the x265 profiles to include the new defaults.
- Changed the default CFR to the default (28.0)
- Added Merge: XviD Encoding code has been Updated (Credit: jkilez)
- Added Merge: Chapter Cutting Feature to MkvMuxer (Credit: wybb)
- Rav1e Added The Following Flags(In Progress):
- content_light(aka MAX CLL / FALL)
- Bitrate
- Passes
- Threads
- Range
- mastering_display

*Note dotnet 4.8 is in RC Stage this is the same Release that will be included in the next update of Windows 10. So you can download the Preview if you wish to use dotnet 4.8 now. This is also the first Staxrip compiled with VS 2019 RC.

Link: https://github.com/Revan654/staxrip/releases/download/2.0.0.1/Staxrip.2.0.0.1.Beta.rar

The File size did shrink some how. Last Release: 297 MB, This Release: 274 MB

[suckerpuncher]

Thanks for the new Beta.

I found one issue so far. When trying to use ffmpeg and QSVEncC I get the following error message:
Video encoding using QSVEnc 3.17 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: Unzulässige Funktion.

y4m: failed to parse y4m header.

It worked before in StaxRip.2.0.0.0 without any problems.

There seems to be an issue with the provided ffmpeg.exe. Updating the ffmpeg.exe to the latest version fixes this in case anyone else has this error.

[wallander]

Revan654,

thank you for the new Beta!
Can I copy my *.srip template- files from 2.0.0.0-release to 2.0.0.1-beta?

I have about 10 templates and it is much work to generate the files new in every version.

...when I update Avisynth+ in my windows 10 system over the 2.0.0.1-beta, are problems to be expected in the operation of the previous version 2.0.0.0-release?


Thank you for help :)

[Revan654]

Revan654,

thank you for the new Beta!
Can I copy my *.srip template- files from 2.0.0.0-release to 2.0.0.1-beta?

I have about 10 templates and it is much work to generate the files new in every version.


Thank you for help :)

Templates files are fine, Since they don't really change.

[wallander]

@Revan654, thank you for answer.

What ist with updated Avisynth+ from 2728 to 2772.
Does it work fine with StaxRip 2.0.0.0-release (if I have to go back to the release version)?

[stax76]

@Revan654

The visual clitch I reported does still appear using your latest release. Was that built before you fixed the issue? I checked the file modified date but it's not present in the rar archieve, using the packer from www.7-zip.org the dates are preserved. To prepare a release or test build I used a utility written in VB.NET, for mpv.net I use powershell, looks like so.


$scriptDir = Split-Path -Path $PSCommandPath -Parent
$exePath = $scriptDir + "\mpv.net\bin\Debug\mpvnet.exe"
$version = [Diagnostics.FileVersionInfo]::GetVersionInfo($exePath).FileVersion
$desktopDir = [Environment]::GetFolderPath("Desktop")
$targetDir = $desktopDir + "\mpv.net-" + $version
if (Test-Path $targetDir) { rd $targetDir -recurse }
Copy-Item $scriptDir\mpv.net\bin\Debug $targetDir -recurse
$addonDir = $targetDir + "\Addons"
remove-item $addonDir -Recurse -Include *mpvnet.exe, *mpvnet.exe.config, *mpvnet.pdb
$7zPath = "C:\Program Files\7-Zip\7z.exe"
$args = "a -t7z -mx9 $targetDir.7z -r $targetDir\*"
Start-Process -FilePath $7zPath -ArgumentList $args



Shared Sub ReleaseStaxRip()
Dim sourceDir = "D:\Projekte\VS\VB\StaxRip\bin\"
Dim version = Assembly.LoadFile(sourceDir + "StaxRip.exe").GetName.Version
Dim releaseType = "-stable"

If version.Revision <> 0 Then releaseType = "-test"

If Not Directory.Exists(sourceDir) Then
Msg("Source directory not found." + BR2 + sourceDir, MessageBoxIcon.Error)
Exit Sub
End If

Dim info = FileVersionInfo.GetVersionInfo(sourceDir + "StaxRip.exe")
Dim targetDir = Path.Combine(Environment.GetFolderPath(Environment.SpecialFolder.Desktop),
"StaxRip-x64-" + info.FileVersion + releaseType + "\")

FileSysUtil.DeleteDir(targetDir)
FileSystem.CopyDirectory(sourceDir, targetDir)

For Each i In Directory.GetDirectories(targetDir + "Apps\Plugins\vs")
Dim cacheDir = i + "\__pycache__"
If Directory.Exists(cacheDir) Then FileSysUtil.DeleteDir(cacheDir)
Next

FileSysUtil.DeleteDir(targetDir + ".vs")
FileSysUtil.DeleteDir(targetDir + "Apps\qaac\QTfiles64")

FileSysUtil.DeleteFile(targetDir + "debug.log")
FileSysUtil.DeleteFile(targetDir + "_StaxRip.log")
FileSysUtil.DeleteFile(targetDir + "StaxRip.vshost.exe")
FileSysUtil.DeleteFile(targetDir + "StaxRip.vshost.sln")
FileSysUtil.DeleteFile(targetDir + "StaxRip.vshost.exe.config")
FileSysUtil.DeleteFile(targetDir + "StaxRip.vshost.exe.manifest")
FileSysUtil.DeleteFile(targetDir + "Apps\eac3to\log.txt")
FileSysUtil.DeleteFile(targetDir + "Apps\DGIndex\DGIndex.ini")
FileSysUtil.DeleteFile(targetDir + "Apps\MKVToolNix\mkvtoolnix.ini")
FileSysUtil.DeleteFile(targetDir + "Apps\MKVToolNix\mkvtoolnix-gui.ini")
FileSysUtil.DeleteFile(targetDir + "Apps\ProjectX\X.ini")
FileSysUtil.DeleteFile(targetDir + "Apps\AVSMeter\AVSMeter.ini")

For Each i In Directory.GetFiles(targetDir, "*.ini", IO.SearchOption.AllDirectories)
Msg(i, MessageBoxIcon.Exclamation)
Exit Sub
Next

Pack({targetDir}.ToList)

If releaseType = "-test" Then
For Each i In {
"C:\Users\Frank\Dropbox\public\StaxRip\Builds\",
"C:\Users\Frank\OneDrive\StaxRip test build\"}

FileSystem.CopyFile(targetDir.TrimEnd("\"c) + ".7z", i + DirPath.GetName(targetDir) + ".7z", UIOption.AllDialogs)
Process.Start(i)
Next
End If
End Sub

Shared Sub Pack(args As List(Of String))
For Each i In args
If i.EndsWith("\") Then i = i.TrimEnd("\"c)
Dim targetName = i + ".7z"
i += "\" + "*"

Using p As New Process
p.StartInfo.FileName = Environment.ExpandEnvironmentVariables("%programfiles%\7-Zip\7z.exe")
p.StartInfo.Arguments = " a -t7z -mx9 """ + targetName + """ -r """ + i + """"
p.Start()
p.WaitForExit()
If p.ExitCode <> 0 Then Throw New Exception("7z failed with exit code " + p.ExitCode.ToString + ".")
End Using
Next
End Sub

[leo5111]

i installed 2.0 staxrip from dec and using my nvidia card for nvidea265 is SLOW like 15fps same file on 1.7 is like 160fps? what setting am i missing?

[Revan654]

@Revan654

snip

don't think the files synced up.

This version will have the fix: https://ci.appveyor.com/project/Revan654/staxrip/build/artifacts.

Not sure what the problem was with the UI not scaling at on some DPI's.

[Revan654]

@Revan654, thank you for answer.

What ist with updated Avisynth+ from 2728 to 2772.
Does it work fine with StaxRip 2.0.0.0-release (if I have to go back to the release version)?

The build shouldn't matter, unless function is changed and it affects scripts or plugins.

[stax76]

@Revan654

It renders fine now, thanks!

I've made a pull request to install FFTW only if needed:

https://github.com/Revan654/staxrip/pull/87/files

[Mister XY]

Same problem with mediainfo.dll . This is the same error looks like many weeks before.

[ukmark]

Hi,

A very small cosmetic issue. When on the main StaxRip window, where you see the video codec and container chosen on the RHS, the descriptions for the x265 quality settings are the same as x264. As x265 is more efficient than x264, should the descriptions for x265 be changed?

For example, quality of 26 shows as "very low" for both x264 and x265. Should a setting of 26 for x265 be set to "medium"?? There is a link below to an ffmpeg doc saying that CRF 23 on x264 is about the same as CRF 28 on x265.

https://trac.ffmpeg.org/wiki/Encode/H.265

[hailingyou]

I've been wanting to try StaxRip 2.0.0.0 after it was recently recommended to me but I'm having a difficult time getting it to run.
When I first run it and try to load a video it prompts me to install avisynth+ which installs fine. Then it prompts me to install FFTW, and when I click on that it returns an error. I have also manually added the .dll's described in the link http://avisynth.nl/index.php/QTGMC but it still gives me the error.

Any idea on how to get running? Thanks.

https://i.imgur.com/BFVWJPk.jpg

[Revan654]

I've been wanting to try StaxRip 2.0.0.0 after it was recently recommended to me but I'm having a difficult time getting it to run.
When I first run it and try to load a video it prompts me to install avisynth+ which installs fine. Then it prompts me to install FFTW, and when I click on that it returns an error. I have also manually added the .dll's described in the link http://avisynth.nl/index.php/QTGMC but it still gives me the error.

Any idea on how to get running? Thanks.

https://i.imgur.com/BFVWJPk.jpg

That should have been fixed, Just drop the fftw files into your system folder.

[Revan654]

Hi,

A very small cosmetic issue. When on the main StaxRip window, where you see the video codec and container chosen on the RHS, the descriptions for the x265 quality settings are the same as x264. As x265 is more efficient than x264, should the descriptions for x265 be changed?

For example, quality of 26 shows as "very low" for both x264 and x265. Should a setting of 26 for x265 be set to "medium"?? There is a link below to an ffmpeg doc saying that CRF 23 on x264 is about the same as CRF 28 on x265.

https://trac.ffmpeg.org/wiki/Encode/H.265

I started to change them, I never got around to finish it.

I just have way to many projects I'm working on, Plus switching from c# to VB can be slightly annoying. I don't have allot of extra time to make some changes I have ideas for. Plus I have to switch from WPF to WinForms.

[hailingyou]

That should have been fixed, Just drop the fftw files into your system folder.

Thanks, It worked fine in 2.0.0.1 Beta.

[jonrodrigos]

Hello friends, I have come to ask for the help of everyone with a problem that I try to solve for months and I can not find a way to solve it.

I already activated the HDR in windows 10 and QLED55q6fn TV and everything seems to work normal, since in games the HDR activates normally and stays show.

I use staxrip to convert my videos, usually movies I down in 1080p remux h264 (.mkv) or 4k h265 all without HDR.

But all the videos I try to convert with the staxrip using x265 10bit adding HDR settings does not look good, it looks like the image is too red, and with too much contrast or gamma I can not say for sure what it is exactly.
I also used the Nvidia h265 10bit configuration with HDR configuration and it conforms to the phitos.
already tried to convert the video with commands ffmpeg adding HDR commands and the same thing happens.
already tried all kinds of configuration and nothing.
What can I be doing wrong?
follow images below and images of the current staxrip, use version 2.0.0.0 - x64.

Setting the video after conversion

mediainfo

Video
ID: 1
Format: HEVC
Format / Info: High Efficiency Video Coding
Commercial name: HDR10
Format profile: Main 10 @ L6.2 @ High
Codec ID: V_MPEGH / ISO / HEVC
Duration: 2 h 29 min
Bit rate: 5 883 kb / s
Width: 1 920 pixels
Height: 1 080 pixels
Display aspect ratio: 2.40: 1
Frame rate mode: Constant
Frame rate: 23.976 (24000/1001) FPS
Color space: YUV
Chroma subsampling: 4: 2: 0
Bit depth: 10 bit
Bits / (Pixel * Frame): 0.118
Stream size: 6.14 GiB (91%)
Language: English
Default: Yes
Forced: No
Color range: Limited
Primary color: BT.2020
Transfer characteristics: PQ
Matrix coefficients: BT.2020 non-constant
Mastering display primary color: BT.2020
Mastering display luminance: min: 0.0001 cd / m2, max: 1000 cd / m2
Maximum Content Light Level: 1000 cd / m2
Maximum Frame-Average Light Le: 1 cd / m2


images with HDR color problem
https://i.imgur.com/HOJW7cN.jpg
https://i.imgur.com/KM0LE64.jpg
https://i.imgur.com/n6yXd5A.jpg

images without HDR enabled
https://i.imgur.com/Qjin6qw.jpg
https://i.imgur.com/APbcEmn.jpg
https://i.imgur.com/RTAp1XM.jpg

image Staxrip config

https://i.imgur.com/yZdPsfU.jpg
https://i.imgur.com/5vsmzV8.jpg
https://i.imgur.com/XpW7nhL.jpg
https://i.imgur.com/6vrLEQ0.jpg

[AMED]

I'm having an issue with 2.0.1beta where it seems to fail the audio conversion from DTS to AAC\M4A. If i roll back to the 2.0.0 bundle it works as it should.

EDIT: Gah it's mediainfo.dll causing it, copied the 2.0.0 version over the top of the 2.0.1 version and it works.

-------------------------- System Environment --------------------------

StaxRip : 2.0.0.1
Windows : Windows 10 Education 1809
Language : English (New Zealand)
CPU : Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
GPU : Radeon RX 580 Series
Resolution : 2560 x 1440
DPI : 96

------------------------ MediaInfo Source File ------------------------

W:\-UPLOAD-\XxXxXxXxXxX.1080p.x264.5.1.DTS.mkv

General
Complete name : W:\-UPLOAD-\XxXxXxXxXxX.1080p.x264.5.1.DTS.mkv
Format : Matroska
Format version : Version 4
File size : 36.6 MiB
Duration : 55 min 28 s
Overall bit rate : 92.3 kb/s
Encoded date : UTC 2019-03-08 21:40:34
Writing application : mkvmerge v31.0.0 ('Dolores In A Shoestand') 64-bit
Writing library : libebml v1.3.6 + libmatroska v1.4.9
IsTruncated : Yes

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings : CABAC / 4 Ref Frames
Format, CABAC : Yes
Format, ReFrames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 55 min 28 s
Nominal bit rate : 8 732 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.176
Writing library : x264 core 144 r2525 40bb568
Language : English
Default : Yes
Forced : No

Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 55 min 28 s
Bit rate mode : Constant
Bit rate : 1 509 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 599 MiB
Language : English
Default : Yes
Forced : No

Text #1
ID : 3
Format : VobSub
Muxing mode : zlib
Codec ID : S_VOBSUB
Codec ID/Info : Picture based subtitle format used on DVDs
Language : English
Default : No
Forced : No

Text #2
ID : 4
Format : VobSub
Muxing mode : zlib
Codec ID : S_VOBSUB
Codec ID/Info : Picture based subtitle format used on DVDs
Language : English
Default : No
Forced : No

Menu
00 : 00:00.000 : en:00:00:00.000
00 : 01:19.830 : en:00:01:19.830
00 : 06:37.480 : en:00:06:37.480
00 : 15:21.629 : en:00:15:21.629
00 : 25:20.811 : en:00:25:20.811
00 : 35:55.904 : en:00:35:55.904
00 : 45:14.754 : en:00:45:14.754
00 : 54:10.622 : en:00:54:10.622

------------------ Demux MKV using mkvextract 31.0.0 ------------------

D:\Staxrip.2.0.0.1.Beta\Apps\Support\MKVToolNix\mkvextract.exe "W:\-UPLOAD-\XxXxXxXxXxX.1080p.x264.5.1.DTS.mkv" tracks 2:"C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS ID3 English" 3:"C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS ID4 English" 1:"C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS ID1 English.mka" --ui-language en

Extracting track 1 with the CodecID 'A_DTS' to the file 'C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS ID1 English.mka'. Container format: Digital Theater System (DTS)
Extracting track 2 with the CodecID 'S_VOBSUB' to the file 'C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.sub'. Container format: VobSubs
Error: Failed to create the VobSub data file 'C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.sub': open file error

Start: 3:50:01 PM
End: 3:50:01 PM
Duration: 00:00:00

General
Complete name : C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS ID1 English.mka
File size : 0.00 Byte

-------------- Demux xml chapters using mkvextract 31.0.0 --------------

D:\Staxrip.2.0.0.1.Beta\Apps\Support\MKVToolNix\mkvextract.exe "W:\-UPLOAD-\XxXxXxXxXxX.1080p.x264.5.1.DTS.mkv" chapters "C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS_chapters.xml"

File 'W:\-UPLOAD-\XxXxXxXxXxX.1080p.x264.5.1.DTS.mkv': container: Matroska
Track ID 0: video (MPEG-4p10/AVC/h.264)
Track ID 1: audio (DTS)
Track ID 2: subtitles (VobSub)
Track ID 3: subtitles (VobSub)
Chapters: 8 entries

Start: 3:50:01 PM
End: 3:50:02 PM
Duration: 00:00:00

-------------- Demux ogg chapters using mkvextract 31.0.0 --------------

D:\Staxrip.2.0.0.1.Beta\Apps\Support\MKVToolNix\mkvextract.exe "W:\-UPLOAD-\XxXxXxXxXxX.1080p.x264.5.1.DTS.mkv" chapters "C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS_chapters.txt" --simple

File 'W:\-UPLOAD-\XxXxXxXxXxX.1080p.x264.5.1.DTS.mkv': container: Matroska
Track ID 0: video (MPEG-4p10/AVC/h.264)
Track ID 1: audio (DTS)
Track ID 2: subtitles (VobSub)
Track ID 3: subtitles (VobSub)
Chapters: 8 entries

Start: 3:50:02 PM
End: 3:50:02 PM
Duration: 00:00:00

----------------------- Indexing using ffmsindex -----------------------

D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\both\ffms2\ffmsindex.exe "W:\-UPLOAD-\XxXxXxXxXxX.1080p.x264.5.1.DTS.mkv" "C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS.ffindex"

Writing index... done.

Start: 3:50:02 PM
End: 3:50:02 PM
Duration: 00:00:00

-------------------------- VapourSynth Script --------------------------

import os
import sys
ScriptPath = 'D:/Staxrip.2.0.0.1.Beta/Apps/Plugins/VS/Scripts'
sys.path.append(os.path.abspath(ScriptPath))
import vapoursynth as vs
core = vs.get_core()
import importlib.machinery
psharpen = importlib.machinery.SourceFileLoader('psharpen', r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\VS\Scripts\psharpen.py").load_module()
mvsfunc = importlib.machinery.SourceFileLoader('mvsfunc', r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\VS\Scripts\mvsfunc.py").load_module()
adjust = importlib.machinery.SourceFileLoader('adjust', r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\VS\Scripts\adjust.py").load_module()
havsfunc = importlib.machinery.SourceFileLoader('havsfunc', r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\VS\Scripts\havsfunc.py").load_module()
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\both\ffms2\ffms2.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\fmtconv\fmtconv.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\AWarpSharp2\libawarpsharp2.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\CTMF\CTMF.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\VS\DCTFilter\DCTFilter.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\VS\Deblock\Deblock.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\DFTTest\DFTTest.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\EEDI2\EEDI2.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\EEDI3m\EEDI3m.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\FFT3DFilter\fft3dfilter.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\FluxSmooth\libfluxsmooth.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\HQDN3D\libhqdn3d.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\both\KNLMeansCL\KNLMeansCL.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\BM3D\BM3D.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\mvtools\libmvtools.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\VS\nnedi3\libnnedi3.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\VS\nnedi3\NNEDI3CL.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\Sangnom\libsangnom.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\scenechange\scenechange.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\VS\SVPFlow\svpflow1_vs64.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\VS\SVPFlow\svpflow2_vs64.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\vs\TTempSmooth\TTempSmooth.dll")
core.std.LoadPlugin(r"D:\Staxrip.2.0.0.1.Beta\Apps\Plugins\VS\nnedi3\vsznedi3.dll")
clip = core.ffms2.Source(r"W:\-UPLOAD-\XxXxXxXxXxX.1080p.x264.5.1.DTS.mkv", cachefile = r"C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS.ffindex")
clip = core.fmtc.bitdepth (clip, bits=16)
clip = core.resize.Spline36(clip, 1280, 720)
clip = havsfunc.SMDegrain(clip, tr=4, RefineMotion=True, thSAD=500)
clip = psharpen.psharpen(clip)
clip.set_output()

-------------------------- Script Properties --------------------------

Source Frame Count : 1058
Source Frame Rate : 23.976024
Source Duration : 00:00:44.1270000
Target Frame Count : 240
Target Frame Rate : 24.000000
Target Duration : 00:00:10

----------------------- MediaInfo Audio Source 1 -----------------------

General
Complete name : C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS ID1 English.mka
File size : 0.00 Byte

------------------ Error Find Gain 1 using ffmpeg 4.1 ------------------

Find Gain 1 using ffmpeg 4.1 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.


--------------------- Find Gain 1 using ffmpeg 4.1 ---------------------

D:\Staxrip.2.0.0.1.Beta\Apps\Encoders\ffmpeg\ffmpeg.exe -i "C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS ID1 English.mka" -sn -vn -hide_banner -af volumedetect -f null NUL

[matroska,webm @ 0000020a4b453900] Format matroska,webm detected only with low score of 1, misdetection possible!
[matroska,webm @ 0000020a4b453900] EBML header parsing failed
C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS ID1 English.mka: Invalid data found when processing input

--------------------- Find Gain 1 using ffmpeg 4.1 ---------------------

D:\Staxrip.2.0.0.1.Beta\Apps\Encoders\ffmpeg\ffmpeg.exe -i "C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS ID1 English.mka" -sn -vn -hide_banner -af volumedetect -f null NUL

[matroska,webm @ 0000020a4b453900] Format matroska,webm detected only with low score of 1, misdetection possible!
[matroska,webm @ 0000020a4b453900] EBML header parsing failed
C:\TMP\XxXxXxXxXxX.1080p.x264.5.1.DTS_temp\XxXxXxXxXxX.1080p.x264.5.1.DTS ID1 English.mka: Invalid data found when processing input

Start: 3:50:09 PM
End: 3:50:09 PM
Duration: 00:00:00

Start: 12:00:00 AM
End: 3:50:10 PM
Duration: 17691135:50:10

[qtwigg]

https://media.discordapp.net/attachments/506134052898603009/555477152498319361/unknown.png?width=1335&height=616

[AMED]

@qtwigg
https://forum.doom9.org/showthread.php?p=1868551#post1868551

[Revan654]

Hello friends, I have come to ask for the help of everyone with a problem that I try to solve for months and I can not find a way to solve it.

I already activated the HDR in windows 10 and QLED55q6fn TV and everything seems to work normal, since in games the HDR activates normally and stays show.

I use staxrip to convert my videos, usually movies I down in 1080p remux h264 (.mkv) or 4k h265 all without HDR.

But all the videos I try to convert with the staxrip using x265 10bit adding HDR settings does not look good, it looks like the image is too red, and with too much contrast or gamma I can not say for sure what it is exactly.
I also used the Nvidia h265 10bit configuration with HDR configuration and it conforms to the phitos.
already tried to convert the video with commands ffmpeg adding HDR commands and the same thing happens.
already tried all kinds of configuration and nothing.
What can I be doing wrong?
follow images below and images of the current staxrip, use version 2.0.0.0 - x64.

Setting the video after conversion

mediainfo

Video
ID: 1
Format: HEVC
Format / Info: High Efficiency Video Coding
Commercial name: HDR10
Format profile: Main 10 @ L6.2 @ High
Codec ID: V_MPEGH / ISO / HEVC
Duration: 2 h 29 min
Bit rate: 5 883 kb / s
Width: 1 920 pixels
Height: 1 080 pixels
Display aspect ratio: 2.40: 1
Frame rate mode: Constant
Frame rate: 23.976 (24000/1001) FPS
Color space: YUV
Chroma subsampling: 4: 2: 0
Bit depth: 10 bit
Bits / (Pixel * Frame): 0.118
Stream size: 6.14 GiB (91%)
Language: English
Default: Yes
Forced: No
Color range: Limited
Primary color: BT.2020
Transfer characteristics: PQ
Matrix coefficients: BT.2020 non-constant
Mastering display primary color: BT.2020
Mastering display luminance: min: 0.0001 cd / m2, max: 1000 cd / m2
Maximum Content Light Level: 1000 cd / m2
Maximum Frame-Average Light Le: 1 cd / m2




Resize your images, if your going to post them in 4K.

Picture color for this has nothing to do with the encoder but the filters. Anytime HDR is stripped from the source you have to make the change so it can be viewable on normal displays.

Tonemapping must be applied to the source file or 3d lut file(aka cube filter).

NVEnc doesn't contain all HDR Settings to start with for HDR10 / HDR10+.

Did you try using the Built in HDR Function? It will tweak the Colors according to the HDR Metadata(It must contain the HDR Metadata).

[stax76]

Hey everybody, a few days ago I released my Open with++ shell extension for the first time 12 years later it was built, I use my launcher and this 100 times a day. I use it for instance to integrate StaxRip's media info GUI into the win file explorer. It does pretty much the same as Open++.

The macros in the options dialog don't have a default value yet, so far there aren't any default values and no documentation, I've use the following macros:

%video% = mpg avi vob mp4 d2v divx mkv avs 264 mov wmv part flv ifo h264 asf webm dgi mpeg mpv y4m avc hevc 265 h265 m2v m2ts vpy mts webm ts m4v part
%audio% = mp2 mp3 ac3 wav w64 m4a dts dtsma dtshr dtshd eac3 thd thd+ac3 ogg mka aac opus flac mpa
%subtitle% = sub sup idx ass aas srt
%image% = png jpg gif bmp

The definition for StaxRip's media info GUI is:

args: -mediainfo %items%
File Types: %audio% %video% %subtitle% %image%

mpv.net and other players:

args: %items%
File Types: %audio% %video% %subtitle% %image%

It needs some work to make it easer to use for new users. I Hope you find it usefull.

The project is located here:

https://github.com/stax76/OpenWithPlusPlus

[jonrodrigos]

Resize your images, if your going to post them in 4K.

Picture color for this has nothing to do with the encoder but the filters. Anytime HDR is stripped from the source you have to make the change so it can be viewable on normal displays.

Tonemapping must be applied to the source file or 3d lut file(aka cube filter).

NVEnc doesn't contain all HDR Settings to start with for HDR10 / HDR10+.

Did you try using the Built in HDR Function? It will tweak the Colors according to the HDR Metadata(It must contain the HDR Metadata).
Hello, sorry for the photos without resizing, I'm newbie in the forum.
how do I apply Tonemapping or 3d lut? I use the final 2.0 staxrip.

[IbrahimKh]

Hi, how do I apply auto crop black border for batch project?

[stax76]

If I remember right then you only have to check the crop checkbox in the filter list of the main dialog.

[Natty]

stax76, your latest version works without lags but revan's version lags while editing filters, dragging dropping source, clicking next etc. please take a look.

[Revan654]

Hello, sorry for the photos without resizing, I'm newbie in the forum.
how do I apply Tonemapping or 3d lut? I use the final 2.0 staxrip.

It should be in Misc or Color Filter section.

3d luts are files you attach to filter, Which has to be created or obtained.

tone mapping, are basic filter like any other filter, you have to play with the settings to achieve what you want. There no set default that will work for all HDR sources.

[stax76]

stax76, your latest version works without lags but revan's version lags while editing filters, dragging dropping source, clicking next etc. please take a look.

I tested a little bit, it was OK except for QTGMC avs not working, I do some further tests.

The tools number increased from 100 to 200 (mostly filters) which should have a impact since for every operation it checks for problems including if any of the tools report a problem.

What surprised me is how much code/comments where added.

PS C:\Users\frank\Daten\Projekte\PY> py .\count-lines.py C:\Users\frank\Daten\Projekte\VB\staxrip2

Enter the file extension: vb

71218

PS C:\Users\frank\Daten\Projekte\PY> py .\count-lines.py C:\Users\frank\Daten\Projekte\VB\staxrip17

Enter the file extension: vb

54817

[Revan654]

I tested a little bit, it was OK except for QTGMC avs not working, I do some further tests.

The tools number increased from 100 to 200 (mostly filters) which should have a impact since for every operation it checks for problems including if any of the tools report a problem.

What surprised me is how much code/comments where added.

PS C:\Users\frank\Daten\Projekte\PY> py .\count-lines.py C:\Users\frank\Daten\Projekte\VB\staxrip2

Enter the file extension: vb

71218

PS C:\Users\frank\Daten\Projekte\PY> py .\count-lines.py C:\Users\frank\Daten\Projekte\VB\staxrip17

Enter the file extension: vb

54817

Plus the System specs, the Resolution & Bitrate of the video all play a role on the performance. Place a SD video in the preview window it's smooth. You may experience issues once you hit 1080p+.

------

I wonder if creating a WPF file and using media element with the WinForm WPF host would improve anything.

of course it will not be a simple as plug and play.

[stax76]

I wasn't refering to the preview but operations in the main dialog that trigger the assistant routine. It's probably possible to speedup the preview but I don't have the required knowledge (DirectX drawing and possibly image data processing) and I'm not looking for a coding challenge at the moment. I hope you, me or somebody else will code it some day.

I wonder if creating a WPF file and using media element with the WinForm WPF host would improve anything.

One problem here is that I don't think it's frame accurate (it uses probably Media Foundation), maybe a WPF picture box if it uses DirectX instead of GDI.

[stax76]

@Revan654

I did some research on the slow preview drawing, there are .NET wrappers for DirectX which can draw .NET bitmaps, I've researched two and both had problems, SlimDX requires a installer and GAC assemplies. SharpDX supports NearestNeighbor and Linear for scaling which I'm not sure if it's good enough and I don't know if it would work and how fast it would be. The other other option is write something in C++ which would be a bit challenging for me though I should probably code something in C++ before I forget every thing.

[jsdukeboy08]

upgraded to the new 2.0.0.1 beta and got everything set up, I am having an issue when I'm encoding where at the end of the encode, when mkvmerge is about to be launched I get this error code. Not sure if it matters but the content I am encoding is HEVC with HDR.

Error Video encoding using x265 3.0 (2.0.0.1)
Video encoding using x265 3.0 failed with exit code: -1073740940 (0xC0000374)
The exit code might be a system error code: A heap has been corrupted.

[Revan654]

upgraded to the new 2.0.0.1 beta and got everything set up, I am having an issue when I'm encoding where at the end of the encode, when mkvmerge is about to be launched I get this error code. Not sure if it matters but the content I am encoding is HEVC with HDR.

Error Video encoding using x265 3.0 (2.0.0.1)
Video encoding using x265 3.0 failed with exit code: -1073740940 (0xC0000374)
The exit code might be a system error code: A heap has been corrupted.

It's very likely tied to python.

STATUS_HEAP_CORRUPTION: ntstatus.h

[jsdukeboy08]

It's very likely tied to python.

STATUS_HEAP_CORRUPTION: ntstatus.h

Doing a little more testing I see that this only happens to encodes that contain —zones. I have uninstalled python and installed the one included with 2.0.0.1 beta. What you included, is that a command I need to run? Also I am using x265 3.0-AU+14 because the one included crashes right when you start encoding when using zones

[onekmilesbehind]

Doing a little more testing I see that this only happens to encodes that contain —zones.

Have you tried any of Ma's builds at http://msystem.waw.pl/x265/ by chance?

There's a discussion over in the x265 thread, starting around post 6766 (https://forum.doom9.org/showthread.php?p=1866868#post1866868), with confirmation that it was working again with the 3.0_AU+8 builds in post 6770. Evidently the new x265_copy_params function caused (or still causes?) issues with --zones.

[jsdukeboy08]

Have you tried any of Ma's builds at http://msystem.waw.pl/x265/ by chance?

There's a discussion over in the x265 thread, starting around post 6766 (https://forum.doom9.org/showthread.php?p=1866868#post1866868), with confirmation that it was working again with the 3.0_AU+8 builds in post 6770. Evidently the new x265_copy_params function caused (or still causes?) issues with --zones.

I've tried several different ones and I can't recall whether I've used that particular build, after my current encode that doesn't require zones I'll give it a shot

Edit: after doing some additional tests it appears that the 3.0_AU+8 works fine with zones and has no errors in staxrip upon encoding completion. The two other versions, +10 and +14, however do not work and will give the same corrupted heap error.

[IbrahimKh]

Hi, is it possible to encode Enhanced AC-3 with Joint Object Coding or Dolby Digital Plus with Dolby Atmos with Staxrip?

[imhh11]

can I insert 2 blanks (black) frames at the start of my encode?? if yes how?

thank you

edit:
i tried this script and it created the 2 blank frames but i want to insert them before my encode.
is it possible or do i need to encode both parts and then join them together with mkvtoolnix ?

https://extraimage.net/images/2019/03/29/b81bf27f1c3077f12a1e10e30c488b88.png

[sneaker_ger]

video=FFVideoSo....
black_frames=BlankClip(video, length=2)
black_frames++video
Something like this.

http://avisynth.nl/index.php/Splice

[imhh11]

Many thanks! exactly what I was looking for :)

[Natty]

The tools number increased from 100 to 200 (mostly filters) which should have a impact since for every operation it checks for problems including if any of the tools report a problem.

confirmed, its caused by too many files in my plugin+ folders and tools bundled in stax.

sometimes stax progress window disappears while encoding.. anyway to restore it??

Edit 1: Issue Fixed https://i.imgur.com/sS4t2YC.png

https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer

[jlw_4049]

Failed to load script.

Cannot load a 32 bit DLL in 64 bit Avisynth: 'C:/Program Files (x86)/AviSynth/plugins/AddGrainC.dll'.

[Taurus]

Failed to load script.

Cannot load a 32 bit DLL in 64 bit Avisynth: 'C:/Program Files (x86)/AviSynth/plugins/AddGrainC.dll'.
What are you doing?
StaxRip2.0 has the AddGrainC.dll 64bit version onboard:confused::p!
If you are using custom scripts make sure to load the desired 64bit plugins from either your StaxRip Avisynth folder or from the autoload Avisynth 64 (+)folder.
Never ever try to mix 32 with 64bit plugins
except you know what you're doing:D.

[stax76]

@Revan

I thought I can improve the drawing performance in the preview and was able to draw with WPF but it wasn't faster, there are ways to make it faster but it's difficult to code unless you are an expert in video processing and video rendering and probably not worth the time it would need to build and it's not only the drawing that lacks but also frame servers have much slower seek performance than players, it probably has to do with frame accuracy and overhead that cannot be avoided in frame servers.

I could still find a major bottleneck when avisynth is used however, this is where it's at:

https://github.com/Revan654/staxrip/blob/master/General/Package.vb#L2076

I don't remember if there is a good reason why I used GetFullScript here, I made some tests and it looks like it's not needed, replacing GetFullScript with GetScript is twenty times faster.

[Revan654]

@Revan

I thought I can improve the drawing performance in the preview and was able to draw with WPF but it wasn't faster, there are ways to make it faster but it's difficult to code unless you are an expert in video processing and video rendering and probably not worth the time it would need to build and it's not only the drawing that lacks but also frame servers have much slower seek performance than players, it probably has to do with frame accuracy and overhead that cannot be avoided in frame servers.

I could still find a major bottleneck when avisynth is used however, this is where it's at:

https://github.com/Revan654/staxrip/blob/master/General/Package.vb#L2076

I don't remember if there is a good reason why I used GetFullScript here, I made some tests and it looks like it's not needed, replacing GetFullScript with GetScript is twenty times faster.

Was WPF being brought into StaxRip or was this just a separate WPF control? It could be the WinForm host adding to the bottlenecking.

I know, I changed a few lines in preview class, Which did improve performance. I think it was that image font icon with one or more of the buttons. I'll take a look at that change, I jsut havn't had much time to do anything with StaxRip due to my other project has been eat up all my time.

[stax76]

It was a WPF custom control hosted in winforms, WPF has a interop method to convert a System.Drawing.Bitmap to a WPF BitmapSource which was used as source for a WPF Image. Not was it only slow but it was also leaking memory and both problems were already described by other people.

When I made this experiment I didn't know that it's not a problem to create a WPF window from a winforms window, I tried it today (because mpv.net is also a mix of winforms and WPF) and it just works according to my first test, the documentation always describes only hosting controls and there isn't a WPF window template in a winforms project.

The reason why I probably give up here is because the seeking part is already very slow regardless of which frame server or source filter is used so it don't matter too much that drawing makes it more slower. Also many people that encode have very fast systems so it's bearable for them.

Lucky for you that you have a project. :-), I'd like to build something but don't know really what, being mostly happy with all software I use.

[ABurns]

I've just started playing with the buttons and knobs on this, and I'm looking at this as a potential alternative to meGUI 1-click. I have a quick question about a few things that seem a little opaque.

How does this detect and deal with hard 3:2 telecine and other types of interlacing? The vast majority of my rips are DVD TV shows, and the problem with TV is that even within a single disc there can be both soft and hard telecine material, so each episode has to be scanned individually for that. Is there an auto-IVTC capability?

[stax76]

@ABurns

It hasn't any detection and automatic handling for this type of source I'm afraid.


@Revan654

Three things I noticed opening a The Orville episode, .eac3 is demuxed as .mka, .srt is demuxed without file extension, the processing window goes to the background instead of staying in the foreground.

[Revan654]

It was a WPF custom control hosted in winforms, WPF has a interop method to convert a System.Drawing.Bitmap to a WPF BitmapSource which was used as source for a WPF Image. Not was it only slow but it was also leaking memory and both problems were already described by other people.

When I made this experiment I didn't know that it's not a problem to create a WPF window from a winforms window, I tried it today (because mpv.net is also a mix of winforms and WPF) and it just works according to my first test, the documentation always describes only hosting controls and there isn't a WPF window template in a winforms project.

The reason why I probably give up here is because the seeking part is already very slow regardless of which frame server or source filter is used so it don't matter too much that drawing makes it more slower. Also many people that encode have very fast systems so it's bearable for them.

Lucky for you that you have a project. :-), I'd like to build something but don't know really what, being mostly happy with all software I use.

You could port Staxrip to WPF in C#. :) using MVVM Patterns. That would be a massive undertaking to port it over. Not everything that exist in VB works in C#.

I did a real quick mock up what codec window could be like using WPF. It uses MVVM Pattern with the whole View -> ViewModel <-> Model design.

I just threw this together in a few seconds just for an example.

https://i.imgur.com/cv0tR3Sl.png

WPF memory usage is very hard to judge(With memory leak you can force call GC.Collection & Finalizer).

Others who have built Video Encoders using WPF at idle it sits around around 100 to 200 from my experience.

Another way would be to create some sort of wrapper with would allow you to build the viewer in any coding you wish all the way up to C++.

[Revan654]

@ABurns

It hasn't any detection and automatic handling for this type of source I'm afraid.


@Revan654

Three things I noticed opening a The Orville episode, .eac3 is demuxed as .mka, .srt is demuxed without file extension, the processing window goes to the background instead of staying in the foreground.

That is tied to MediaInfo bug from what I recall. If you revert back to an earlier build like from 2018 / 2017, it will work perfectly. Not 100% sure what was changed in MediaInfo code to create this issue. I did report it to MediaInfo devs but it doesn't seem like there interested in fix that issue right now. After all it took them over year+ about to fix the HDR issue I reported the previous year.

[Revan654]

I've just started playing with the buttons and knobs on this, and I'm looking at this as a potential alternative to meGUI 1-click. I have a quick question about a few things that seem a little opaque.

How does this detect and deal with hard 3:2 telecine and other types of interlacing? The vast majority of my rips are DVD TV shows, and the problem with TV is that even within a single disc there can be both soft and hard telecine material, so each episode has to be scanned individually for that. Is there an auto-IVTC capability?

Automation for source scanned is not part of StaxRip core, you can build a script to detect the source and alter the filters when certain params are detected.

Like with the sample script it enables deinterlacing if the source is interlaced. by default these scripts are disabled.

[Natty]

some features which are needed. please do if possible.

1- encoding of more than 2 audios in case of file batch (~20 files)

2- muxing of all subs in same case as above.

3- selection of different filter, encoding settings for few files in batch.

[Revan654]

some features which are needed. please do if possible.

1- encoding of more than 2 audios in case of file batch (~20 files)

2- muxing of all subs in same case as above.

3- selection of different filter, encoding settings for few files in batch.

1. Already Exists(Inside the Container Option).

2. Already exists(Inside the Container Option).

3. This is basically Apply filter to x queues. This would basically need a profile filter system, then apply that given profile to the x project.

[Natty]

1. Already Exists(Inside the Container Option).

2. Already exists(Inside the Container Option).

3. This is basically Apply filter to x queues. This would basically need a profile filter system, then apply that given profile to the x project.

i know about container tab. for single file its easy. i am talking about batch files. :) example there are 20 files with 5 audios each. i would like to encode 1st audio at q100 tvbr in qaac and rest 4 in he-aac cvbr. how to do that in case of batch? :readguid:

[Lynx_TWO]

Hello!

One thing that is currently missing is the ability to export an image sequence instead of simply encoding to a different format. This would be extremely useful to be able to use the power of QTGMC to deinterlace a video, export all frames as a numbered sequence, then use Gigapixel AI to upscale and denoise the images as a batch process, finally encoding them from the image sequence back to a video. This could be great for older shows, especially animation.

Topaz Gigapixel AI v4.0.3 supports JPG, JPEG, TIF, TIFF, and PNG formats. The software can also convert to different color profiles: sRGB, ProPhoto RGB, AdobeRGB, AppleRGB, and Wide-GamutRGB. Not that it's useful for video but worth mentioning.

The software also reliably re-imagines detail from the original source up to 6x. For a 720x480 video, that would be 4,320x2,880, downsized to HD would really make it pop...

Thanks!!

[Z'Hadum]

Hello!

One thing that is currently missing is the ability to export an image sequence instead of simply encoding to a different format. This would be extremely useful to be able to use the power of QTGMC to deinterlace a video, export all frames as a numbered sequence, then use Gigapixel AI to upscale and denoise the images as a batch process, finally encoding them from the image sequence back to a video. This could be great for older shows, especially animation.

Topaz Gigapixel AI v4.0.3 supports JPG, JPEG, TIF, TIFF, and PNG formats. The software can also convert to different color profiles: sRGB, ProPhoto RGB, AdobeRGB, AppleRGB, and Wide-GamutRGB. Not that it's useful for video but worth mentioning.

The software also reliably re-imagines detail from the original source up to 6x. For a 720x480 video, that would be 4,320x2,880, downsized to HD would really make it pop...

Thanks!!

I saw the example for DS9 - it is realy cool stuff.
(if we get a Babylon 5 upscale it would be fantastic :D)

But I think this is outside the topic by staxrip.

Best would be if it would be possible to integrate the Gigapixel-AI as a filter into the process.
But afaik there is no api (yet?) for this....
May be something you should ask to the Gigapixel developers?

[Revan654]

I saw the example for DS9 - it is realy cool stuff.
(if we get a Babylon 5 upscale it would be fantastic :D)

But I think this is outside the topic by staxrip.

Best would be if it would be possible to integrate the Gigapixel-AI as a filter into the process.
But afaik there is no api (yet?) for this....
May be something you should ask to the Gigapixel developers?

If the filter / API does not exist inside of already existing VS / AVS / DX / GDI. It can not be added. There are limitations of what the drawer can do. I also don't want to stack more resources on top of the drawer, since it already struggles with higher resolutions. There has been some improvement to the preview window recently which should help in the long run.

outputting a small range of images in the current state shouldn't be to hard, since it just needs a loop and stack the image encoder inside of that.

Allot of reference software and such that is written in C++, not VB / C# with .net Framework. Again there are limitations, Where C++ doesn't really many, since C++ is pure machine code.

---

With Upscaling software there are limitations, You upscale the size and such, but what some may fail to notice is the finer details are usually removed. Like a small pattern on the wall or on the persons clothing. It's removed or flatten, it's sometimes hard to notice without comparing the two.

Then you can introduce other problems into the picture as well like artifacts(Which is very common on upscaling) and aliasing.

This is a double edge sword situation.

[Lynx_TWO]

With Upscaling software there are limitations, You upscale the size and such, but what some may fail to notice is the finer details are usually removed. Like a small pattern on the wall or on the persons clothing. It's removed or flatten, it's sometimes hard to notice without comparing the two.

Then you can introduce other problems into the picture as well like artifacts(Which is very common on upscaling) and aliasing.

This is a double edge sword situation.


Well, here are some of the crappiest test files you'll ever see. I own the software, so send me a link to any screenshot you want to be upscaled as a test. Keep in mind these were also then all compressed with JPEGMini pro to save file size :D

There's no detail loss, rather far more detail added as it re-imagines what would have been there. It's basically magic in some cases...

The software has been out for like, (a year)? And they are on version 4.0.3 already. You buy once and have lifetime updates. Each version includes more epochs of training and so keeps rapidly getting better. And no, I don't work for or am invested in them lol

https://drive.google.com/drive/folders/1TxB1B-TX97B5hWGqgscjr-y3LEORtd8j?usp=sharing

Link (https://drive.google.com/drive/folders/1TxB1B-TX97B5hWGqgscjr-y3LEORtd8j?usp=sharing)

[Natty]

https://extraimage.net/images/2019/04/20/0d9d2c7d9e28a370e9dd75dfd6176668.png

is this necessary? i want to remove it. can i?

[Z'Hadum]

With Upscaling software there are limitations, You upscale the size and such, but what some may fail to notice is the finer details are usually removed. Like a small pattern on the wall or on the persons clothing. It's removed or flatten, it's sometimes hard to notice without comparing the two.

Then you can introduce other problems into the picture as well like artifacts(Which is very common on upscaling) and aliasing.

This is a double edge sword situation.

This is true for "conventional" up-scaling...
But this is a special A.I.-based Algorithm....and it is impressing what can be done with it.
I also hope to use something similar for old DVD releases in the near future.
Or may be some time in the future such algorithms can be used by software like madVR in real-time....
With it much better compression algorithms could be possible...:D

But all this is Off-Topic here.

[Zetti]

MediaInfo v19.04 is released.

[IbrahimKh]

Hi, what is the correct filter to demux vp9? I tried different version of Staxrip and still cannot demux it properly. The framerate has always been get the wrong value.
https://i.postimg.cc/jDnZSfYk/screenshot-8.png (http://postimg.cc/jDnZSfYk)

[Natty]

Hi, what is the correct filter to demux vp9? I tried different version of Staxrip and still cannot demux it properly. The framerate has always been get the wrong value.
https://i.postimg.cc/jDnZSfYk/screenshot-8.png (http://postimg.cc/jDnZSfYk)

lwlibav

[gonca]

Is it possible to use StaxRip without all the support apps being in the system.
Example
can I delete all the audio encoders since I don't plan on doing any audio encoding?

[videoh]

Here you go https://www.sendspace.com/file/es0lwp The issue can be seen here by my previous post https://imgur.com/a/kEdOlGU I believe I and imhh11 are having the same issue where the highlights are blown out of proportion, and no amount of playing with either the Hable or Reinhard curve can preserve details in highlights. Please let us know what you find, or if you have a fix for the issue, thanks!! How about this?

dgsource("Last Stand Test Snippet (1)-001.dgi",fulldepth=true)
dghdrtosdr(roll=1.0,light=150)

Sorry for the late reply.

[Trench]

Is there anything "smart" I could do (using the term loosely) in Staxrip if my desire is to convert a non-letterboxed 4:3 video to fill a 16:9 display?

Clearly I could just invoke the crop to bring the display aspect ratio from 1.33 to 1.85, but with a significant information loss top and bottom on the picture.

Some 16:9 displays I've seen have a 4:3 display mode that does some non-linear X-axis stretching in order to crop much less top and bottom and still "fill the screen" on a 16:9 display. Meaning they only crop a little top and bottom, and then gradually from the center of the image to the left and right, they being stretching to ultimately fit the width without being as visually obvious about it. i.e. Stretched less in the middle of the image, but increasing amounts as you get to the outer edge.

Is there some existing filter that could allow me do to a non-linear type of stretching such as that? I'm probably using the wrong technical terms when trying to search for the capability. Thanks.

[frenchfries]

Is there anything "smart" I could do (using the term loosely) in Staxrip if my desire is to convert a non-letterboxed 4:3 video to fill a 16:9 display?

Clearly I could just invoke the crop to bring the display aspect ratio from 1.33 to 1.85, but with a significant information loss top and bottom on the picture.

Some 16:9 displays I've seen have a 4:3 display mode that does some non-linear X-axis stretching in order to crop much less top and bottom and still "fill the screen" on a 16:9 display. Meaning they only crop a little top and bottom, and then gradually from the center of the image to the left and right, they being stretching to ultimately fit the width without being as visually obvious about it. i.e. Stretched less in the middle of the image, but increasing amounts as you get to the outer edge.

Is there some existing filter that could allow me do to a non-linear type of stretching such as that? I'm probably using the wrong technical terms when trying to search for the capability. Thanks.

The term is non-linear stretch.
First google result of a search "avs script non linear stretch"
http://avisynth.nl/index.php/SimpleResize

[jlw_4049]

Can anyone give me a rough guide on how exactly to encode 4k/x265 HDR content, while retaining all the HDR with this program? I would certainly appreciate it. I cant seem to find much information on the subject.

EDIT: Each time I'm done indexing with StaxRip, the program just disappears into the task manager. UI is gone completely?
EDIT: Apparently it just minimizes for like 4 to 5 minutes before it comes back up. I'm assuming it's doing something.

Sent from my SM-G965U1 using Tapatalk

[Natty]

EDIT: Each time I'm done indexing with StaxRip, the program just disappears into the task manager. UI is gone completely?
EDIT: Apparently it just minimizes for like 4 to 5 minutes before it comes back up. I'm assuming it's doing something.


it's doing 2nd pass or something in ffmsindex. i solved that issue by using older version of it from staxrip 1.8.2.0 apps folder:sly:

[jlw_4049]

it's doing 2nd pass or something in ffmsindex. i solved that issue by using older version of it from staxrip 1.8.2.0 apps folder:sly:

Thanks for that information. I don't mind the few minutes waiting time. It's my home server, I'm mainly just using StaxRip for 4k HDR encoding. Seems to be one of the only GUI's supporting it "easily." :thanks:

[Revan654]

Is it possible to use StaxRip without all the support apps being in the system.
Example
can I delete all the audio encoders since I don't plan on doing any audio encoding?

You can delete the Opus one, Since that was never added in, but everything is locked. most of the audio is done via ffmpeg and sometimes uses support tools. If you plan to do audio encoding or not there still needed. They only take up less then 40 mbs, which is tiny.

[gonca]

Thank you for the response

[jlw_4049]

Program works great. After I got used to it. I honestly like it quite a bit.

Sent from my SM-G965U1 using Tapatalk

[lordalibaski]

Hi Revan glad someone has kept updating this software it's done wonders for me over the years. I do apologise I put my problem in the old topic didn't see this topic here is my problem

https://forum.doom9.org/showthread.php?p=1873772#post1873772

[jlw_4049]

Revan, I'm having a small issue where when I abort a job to change some settings. The program doesn't "free" the ram up that it was using. So, for example it'll go from 2.5gbs used to 9. Then with the next job (even tho I aborted the first job) So, say I decided to abort this 2nd job, the ram will still be at 9 or 10. If I am to start another job it can actually crash the encoder because it ran out of RAM.

If when I abort, I close the program, restart and add with the AVS file. This doesn't happen.

Maybe it's me doing something wrong?

[Natty]

Revan, I'm having a small issue where when I abort a job to change some settings. The program doesn't "free" the ram up that it was using. So, for example it'll go from 2.5gbs used to 9. Then with the next job (even tho I aborted the first job) So, say I decided to abort this 2nd job, the ram will still be at 9 or 10. If I am to start another job it can actually crash the encoder because it ran out of RAM.

If when I abort, I close the program, restart and add with the AVS file. This doesn't happen.

Maybe it's me doing something wrong?

yes that is the bug in stax which eats all ram and slows down or locks your system, a fix i found was after doing your encoding and filtering settings click on project - save.. it will save a .srip file. close all instances of stax to free up ram, then open it again and project - open - .srip.. this will start u from where u left.

there are few more bugs which makes it really unstable / unusable.

[Natty]

Hi Revan glad someone has kept updating this software it's done wonders for me over the years. I do apologise I put my problem in the old topic didn't see this topic here is my problem

https://forum.doom9.org/showthread.php?p=1873772#post1873772

download 32/64 version

extract and move contents to C:\Windows\System32\

[jlw_4049]

yes that is the bug in stax which eats all ram and slows down or locks your system, a fix i found was after doing your encoding and filtering settings click on project - save.. it will save a .srip file. close all instances of stax to free up ram, then open it again and project - open - .srip.. this will start u from where u left.

there are few more bugs which makes it really unstable / unusable.Thanks for clearing that up. I am using it for HDR 4k encoding. I usually use MeGUI.

So far with staxrip this is the only issue i have ran into.

Sent from my SM-G965U1 using Tapatalk

[stax76]

yes that is the bug in stax which eats all ram and slows down or locks your system

Does that happen with staxrip 1.7 too? 2.0 uses ffms2 with C interface and that leaks memory if I remember right, just choose another source filter in 2.0.

[Natty]

Does that happen with staxrip 1.7 too? 2.0 uses ffms2 with C interface and that leaks memory if I remember right, just choose another source filter in 2.0.

1.7 has no such issue. :thanks:

[jlw_4049]

Does that happen with staxrip 1.7 too? 2.0 uses ffms2 with C interface and that leaks memory if I remember right, just choose another source filter in 2.0.

I need the latest ffms2 in order to encode 4k HDR. As I have read (correct me of I'm wrong and point me in the right direction) FFvideosource is the only 1 that supports over an 8-bit pipeline?

Thanks!

[lordalibaski]

download 32/64 version

extract and move contents to C:\Windows\System32\

This is what I'm saying windows 64bit won't let you, you extract them straight into the system32 folder it looks like it's extracting to the folder but once complete they are not in there they go to the syswow64 folder.

[jlw_4049]

This is what I'm saying windows 64bit won't let you, you extract them straight into the system32 folder it looks like it's extracting to the folder but once complete they are not in there they go to the syswow64 folder.The solution to your problem.

Uninstall avisynth all the way. Control panel, add and remove, uninstall.

Go into regedit, search for all traces of AviSynth. Remove them.

Inside the staxrip folder there is a tools or app folder. There will be an AviSynth+ installer and python and something else. Install all those and that will solve your problem.

Sent from my SM-G965U1 using Tapatalk

[Natty]

I need the latest ffms2 in order to encode 4k HDR. As I have read (correct me of I'm wrong and point me in the right direction) FFvideosource is the only 1 that supports over an 8-bit pipeline?

Thanks!

remove yuv420p8 from ffvideosource line to retain same bitdepth as source.
https://imgur.com/warOucS

[lordalibaski]

I've sorted the problem, I have teracopy installed on my pc which for some reason didn't have access to the system32 folder I removed teracopy and windows copied the dll files straight away all is working fine again....thanks for all the advise gents.

[Revan654]

Does that happen with staxrip 1.7 too? 2.0 uses ffms2 with C interface and that leaks memory if I remember right, just choose another source filter in 2.0.

I know one of the builds had leaks, I think it's been plugged since. I don't even bother with these filters anymore, since there rarely updated anymore.

[Revan654]

.netFramework is officially dead. Everything is heading to .netCore. With today's announcement it put the final nails in the coffin of .netFramework. .Net 5 will be pure .netCore. Which may make things a bit more difficult to with StaxRip 2.0 or older programs. I have to see what works in .netCore, if I can ever get it to show up in VS 2019.

[stax76]

@Revan654

It's dead but also will live forever like 30 years old win32 apps. I don't think it's a good idea to port a big app like staxrip right now, maybe it's never a good idea because I heard in a Build interview that they can only make it work with a huge rewrite running the form designer out of process making it unstable possibly for years or forever. The form designer wasn't always as stable as in recent years, there were times it had issues.

New apps should rather be Core but also should not be WinForms but rather be WPF or UWP. I'll probably wait 1-2 years before I port mpv.net, I don't see any real advantages to port it right now, too risky.

I'll try to fix a couple of issues in staxrip2 using a new repo at:

https://github.com/staxrip/staxrip

You probably can write to it because I've sent a invitation. Right now I really don't know much about git unfortunately, it's something I need to learn.

Most important thing now is watching a few Build sessions. :)

[jlw_4049]

I know one of the builds had leaks, I think it's been plugged since. I don't even bother with these filters anymore, since there rarely updated anymore.What filter so you recommend for 4k HDR encoding?

Sent from my SM-G965U1 using Tapatalk

[stax76]

@jlw_4049

You can try the following ffms2 build:

https://drive.google.com/drive/folders/1xZQABtoaSFgGu11YstmHKYLzO3elemlC

This build supports only VapourSynth!

[jlw_4049]

@jlw_4049

You can try the following ffms2 build:

https://drive.google.com/drive/folders/1xZQABtoaSFgGu11YstmHKYLzO3elemlC

This build supports only VapourSynth!Thank you. I guess I'm going to have to learn VaporSynth :)

Sent from my SM-G965U1 using Tapatalk

[stax76]

@Revan

I started doing a little work today. What I've changed is:

https://github.com/staxrip/staxrip/blob/master/changelog.md

600 MB disk space is a lot. I was thinking to offer different downloads for people that prefer a lightweight package. It could look like so:

light AviSynth only
light VapourSynth only

full AviSynth only
full VapourSynth only

fat which includes everything

github don't seem to have a download counter like sourceforge unfortunately.

[gonca]

@stax76
like the different version idea
Like I mentioned earlier, I create my own scripts and encode with x265 or NVEncC, then mux to mkv
A lighter version would be awesome.

[Natty]

600 MB disk space is a lot. I was thinking to offer different downloads for people that prefer a lightweight package. It could look like so:

light AviSynth only
light VapourSynth only

full AviSynth only
full VapourSynth only

fat which includes everything


awesome :goodpost::helpful::thanks::cool:

[stax76]

Here is a first build. I hope it don't has major bugs and I hope the download link works.

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

https://github.com/staxrip/staxrip/blob/master/changelog.md

[Havokdan]

Here is a first build. I hope it don't has major bugs and I hope the download link works.

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

https://github.com/staxrip/staxrip/blob/master/changelog.md

Mirrors?

[stax76]

I'll add a dropbox mirror shortly.

[ashlar42]

Today I was trying a quick encode for a friend. I needed to resize from 1080p to 720p and, as I was using NVENC H264, I opted for Cubic_Catmull resizing.

StaxRip gave an error message stating that I needed nppi64_80.dll. That file is in C:\Users\ashlar42\Documents\StaxRip\Apps\NVEnc but I got the error anyway.

If it helps, I'm on Windows 10 Pro x64, using a GTX980. StaxRip 2.0.0.0 Stable.

[stax76]

You can try copying it C:\Windows\SysWOW64

[Havokdan]

I'll add a dropbox mirror shortly.

Thanks

[ashlar42]

C:\Users\ashlar42\Documents\StaxRip\Apps\Encoders\NVEnc\NVEncC64.exe --cqp 18:20:22 --preset quality --vpp-resize cubic_catmull --output-res 720x392 -i "E:\Movie\Movie.avs" -o "E:\Movie_temp\Movie_out.h264"

resize: --vpp-resize cubic_catmull requires "nppi64_80.dll", not available on your system.
resize: switching to spline36.

This after copying nppi64_80.dll from the NVENC directory under StaxRip to SysWOW64.

[stax76]

dropbox mirror:

https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

[stax76]

Maybe the nvencc author knows what's wrong.

https://github.com/rigaya/NVEnc/issues

[ashlar42]

Maybe the nvencc author knows what's wrong.

https://github.com/rigaya/NVEnc/issuesOk, I discovered one thing. I updated from a previous version of StaxRip and, before, the path was StaxRip/Apps/NVENC. Now it's StaxRip/Apps/Encoders/NVENC, which is why the file was not found. I copied all the files in the correct directory but now I suspect the problem is different, since I'm getting a different error...
resize: failed to resize: -22, NPP_INTERPOLATION_ERROR.

I suspect there's a problem with the CUDA SDK files version. In StaxRip there are functions exposed that are not supported out of the box, as the needed CUDA DLLs are not in the installation file. So now I'm using old files or wrong files, I don't know. :(

[stax76]

@ashlar42

I cannot test it because my graphics card don't support nvenc.

[stax76]

Currently, it's 200 MB download size and 600 MB disk space.

Would it make sense to offer three downloads, one with VapourSynth, one with AviSynth and one with both?

What would you download? I'd take both I guess.

[Havokdan]

Currently, it's 200 MB download size and 600 MB disk space.

Would it make sense to offer three downloads, one with VapourSynth, one with AviSynth and one with both?

What would you download? I'd take both I guess.
The most complete.

[ashlar42]

The most complete.Same for me.

I'm sorry NVENC cannot be tested. Maybe in the future. :)

[stax76]

Maybe I'll buy a better card in the future. I had a GTX 1060 but lost my PC in an unfortunate incident and didn't want to bother spending much time and money to build a new one, so I just bought a basic HP PC with i5-8400 CPU that can fit a GT 1030 card, I don't know if I can fit a better card in this PC due to possible heat and power restrictions.

I'm not sure GT 1030 is good enough for UHD content, I had a file recently (see below) which I can't get to play fluently, other UHD files are better.

http://tvdl.zdf.de/none/zdf/diverse/190417_wagenrennen_fj83i_uhd_tex_4328k_p1112v12.mp4

CompleteName : C:\Users\frank\Daten\Samples\Brot und Spiele - Wagenrennen im alten Rom.mp4
Format/String : MPEG-4
Format_Profile : Base Media / Version 2
CodecID/String : mp42 (isom/mp42)
FileSize/String : 1.83 GiB
Duration/String : 58 min 40 s
OverallBitRate/String : 4 468 kb/s
Encoded_Date : UTC 2019-04-17 09:03:11
Tagged_Date : UTC 2019-04-17 09:03:11

Video

ID/String : 1
Format/String : HEVC
Format/Info : High Efficiency Video Coding
Format_Profile : Main 10@L5.1@Main
CodecID : hvc1
CodecID/Info : High Efficiency Video Coding
Duration/String : 58 min 40 s
BitRate/String : 4 330 kb/s
Width/String : 3 840 pixels
Height/String : 2 160 pixels
DisplayAspectRatio/String: 16:9
FrameRate_Mode/String : Constant
FrameRate/String : 50.000 FPS
ColorSpace : YUV
ChromaSubsampling/String : 4:2:0
BitDepth/String : 10 bits
Bits-(Pixel*Frame) : 0.010
StreamSize/String : 1.77 GiB (97%)
Encoded_Library/String : x265 3.0:[Linux][GCC 6.3.0][64 bit] 10bit
Language/String : German
Encoded_Date : UTC 2019-04-17 09:03:11
Tagged_Date : UTC 2019-04-17 09:03:16
colour_range : Limited
colour_primaries : BT.2020
transfer_characteristics : HLG
matrix_coefficients : BT.2020 non-constant
Codec configuration box : hvcC

[Natty]

Currently, it's 200 MB download size and 600 MB disk space.

Would it make sense to offer three downloads, one with VapourSynth, one with AviSynth and one with both?

What would you download? I'd take both I guess.

i will take avisynth full pack. for vapoursynth encoding I would need atleast 32 GB ram. I can do same thing (not as efficient as vapoursynth) in avisynth in ~2 GB

[jlw_4049]

Maybe I'll buy a better card in the future. I had a GTX 1060 but lost my PC in an unfortunate incident and didn't want to bother spending much time and money to build a new one, so I just bought a basic HP PC with i5-8400 CPU that can fit a GT 1030 card, I don't know if I can fit a better card in this PC due to possible heat and power restrictions.



I'm not sure GT 1030 is good enough for UHD content, I had a file recently (see below) which I can't get to play fluently, other UHD files are better.



http://tvdl.zdf.de/none/zdf/diverse/190417_wagenrennen_fj83i_uhd_tex_4328k_p1112v12.mp4



CompleteName : C:\Users\frank\Daten\Samples\Brot und Spiele - Wagenrennen im alten Rom.mp4

Format/String : MPEG-4

Format_Profile : Base Media / Version 2

CodecID/String : mp42 (isom/mp42)

FileSize/String : 1.83 GiB

Duration/String : 58 min 40 s

OverallBitRate/String : 4 468 kb/s

Encoded_Date : UTC 2019-04-17 09:03:11

Tagged_Date : UTC 2019-04-17 09:03:11



Video



ID/String : 1

Format/String : HEVC

Format/Info : High Efficiency Video Coding

Format_Profile : Main 10@L5.1@Main

CodecID : hvc1

CodecID/Info : High Efficiency Video Coding

Duration/String : 58 min 40 s

BitRate/String : 4 330 kb/s

Width/String : 3 840 pixels

Height/String : 2 160 pixels

DisplayAspectRatio/String: 16:9

FrameRate_Mode/String : Constant

FrameRate/String : 50.000 FPS

ColorSpace : YUV

ChromaSubsampling/String : 4:2:0

BitDepth/String : 10 bits

Bits-(Pixel*Frame) : 0.010

StreamSize/String : 1.77 GiB (97%)

Encoded_Library/String : x265 3.0:[Linux][GCC 6.3.0][64 bit] 10bit

Language/String : German

Encoded_Date : UTC 2019-04-17 09:03:11

Tagged_Date : UTC 2019-04-17 09:03:16

colour_range : Limited

colour_primaries : BT.2020

transfer_characteristics : HLG

matrix_coefficients : BT.2020 non-constant

Codec configuration box : hvcCYou could add another gtx 1060 in there fine. Pascal cards are super effecient. Might need to buy an adapted for PSU. A gtx 1650 or gtx 1050 would even suffice.

Sent from my SM-G965U1 using Tapatalk

[jlw_4049]

i will take avisynth full pack. for vapoursynth encoding I would need atleast 32 GB ram. I can do same thing (not as efficient as vapoursynth) in avisynth in ~2 GBDoes vapoursynth really use that much RAM? Is it faster or something?

Sent from my SM-G965U1 using Tapatalk

[Natty]

Does vapoursynth really use that much RAM? Is it faster or something?

Sent from my SM-G965U1 using Tapatalk

yes it does. in my test it took 10 GB ram in just 4 filters. but encoding was faster. supports 16bit natively. multi threaded. etc. its great for heavy pcs.

[jlw_4049]

yes it does. in my test it took 10 GB ram in just 4 filters. but encoding was faster. supports 16bit natively. multi threaded. etc. its great for heavy pcs.I was thinking about learning it here soon, but my home server rig is only outfitted with 16gb ram. I won't add more until I upgrade to a wider home server. Hopefully a 16+ core threadripper or ryzen 3xxx.

Sent from my SM-G965U1 using Tapatalk

[stax76]

You could add another gtx 1060 in there fine. Pascal cards are super effecient. Might need to buy an adapted for PSU. A gtx 1650 or gtx 1050 would even suffice.

The PC is called HP Pavilion 590-p0599ng and the PSU has 180 W, the CPU 65 W, if it fits well I consider buying a GTX 1650.

[jlw_4049]

The PC is called HP Pavilion 590-p0599ng and the PSU has 180 W, the CPU 65 W, if it fits well I consider buying a GTX 1650.You could easily slap a 25 dollar evga 450 watt psu in there and put what ever card you desire in there. You can buy mini cards of almost every one of those.

However the gtx 1650 is fully powered by the motherboard, no need for any pci e wires from PSU. (You buy the base clocked model)

Sent from my SM-G965U1 using Tapatalk

[stax76]

You could easily slap a 25 dollar evga 450 watt psu in there and put what ever card you desire in there. You can buy mini cards of almost every one of those.

However the gtx 1650 is fully powered by the motherboard, no need for any pci e wires from PSU. (You buy the base clocked model)

Sent from my SM-G965U1 using Tapatalk

Sounds good. :thanks:

[Forteen88]

...if it fits well I consider buying a GTX 1650.I hear that Nvidia GTX 1650 doesn't have Turing-encoding, it uses old Volta Nvidia Encoder (NVENC) for GPU-encoding.
https://www.tomshardware.com/news/nvidia-geforce-gtx-1650-volta-nvenc,39161.html

[NikosD]

I'm not sure GT 1030 is good enough for UHD content, I had a file recently (see below) which I can't get to play fluently, other UHD files are better.

http://tvdl.zdf.de/none/zdf/diverse/190417_wagenrennen_fj83i_uhd_tex_4328k_p1112v12.mp4 That's an easy to play 4K50 fps HEVC 10bit file, due to the very low bitrate (frame rate is high though)

Especially for GPUs, any chip with a fixed-function unit (AMD from Polaris onward, nVidia from Maxwell 2nd gen onward, Intel Kabylake onward) could handle it easily.

[sneaker_ger]

Yeah, decoding 4Kp50 HEVC to raw bitstream should be easy for the GT 1030. So either HW decoding is not activated or other parts are too slow. E.g. copying the frames from/to GPU/memory, scaling, tonemapping.

[stax76]

HW decoding is on. I've tried it with mpv and with mpc/madvr and in either case it looks rather jerky to me, in particular starting at 1:50.

My task manager:

https://postimg.cc/bdBCdHJL

[NikosD]

He doesn't have GT 1030 yet.

Actually, he doesn't have any nVidia card or any other discrete card, if I understood correctly.

He just expressed his doubts regarding GT 1030.

Update:

So, you have a GT 1030 in your hands not capable of playing this clip.
Weird.

Update 2:
Try MPC-HC or PotPlayer in DXVA2 native mode.

Update 3:
No madVR for GT 1030.
Try EVR/ EVR-CP

[stax76]

I have/use a GT 1030. No matter which player I use, this file always don't look smooth but jerky, I mean it's watchable, it just don't look particularly great, maybe I've too high expectations. I didn't notice a difference between mpv and mpc.

[Natty]

thank you for staxrip 2.0.1.1..loading times and filter editing is fast like before. everything is so smooth. just 1 issue. true hd was demuxed as mka file. fixed that by old mediainfo dll. thanks.

[stax76]

Many audio streams were de-muxed as mka and still some might be.

MediaInfo never had issues or breaking changes all the years except recently breaking many things in staxrip. I'm not sure but I think it was announced many years ago that when the major version changes (18 -> 19) there will be breaking changes. For me that's fine as I think modernizing things makes sense. First I thought Revan introduced a bug but now after seeing some of his improvements and changes I think he did very well. There was this ffms2 memory leak but I also learned this the hard way some years ago, for a long time I was thinking the leek is in staxrip. Some things were slowed down because of many new filters were added and the original code base didn't scale well.

I'm not sure I have a true hd test file because I wiped out my entire test file collection when I announced that I will give up staxrip maintenance. I'll see if I can find some true hd files.

[Natty]

i think there might be some memory leak still, after using preview window a few times, stax was using around 500 MB in idle state.

the detailed progress bar is great, shows estimated size and all ;) thanks :)

adding new job, editing filters are now very smooth, i am loving it.

[NikosD]

I have/use a GT 1030. No matter which player I use, this file always don't look smooth but jerky, I mean it's watchable, it just don't look particularly great, maybe I've too high expectations. I didn't notice a difference between mpv and mpc. I downloaded the HUGE file and tried MPC-HC using LAV Video in NVCUVID mode with my GTX 1660.

Well, the GPU clock is the lowest (base) clock of 1530MHz (Video clock 1410 MHz) and the Video Engine load is ~15% all the time.

GPU load is ~17 %.

I tried also a different system, a Skylake Core i5 in SW mode using its iGPU and although the CPU can decode the clip ~70fps in renderless mode, using the EVR-CP renderer the iGPU can't go more than 25 fps.

Using a discrete GPU like GT 1030, you shouldn't have any problems with an "easy" renderer (forget madVR)

Did you try EVR/ EVR-CP ?

[stax76]

i think there might be some memory leak still, after using preview window a few times, stax was using around 500 MB in idle state.

If it happens with all filters it might be staxrip issue, otherwise it's likely caused by a certain filter.

the detailed progress bar is great, shows estimated size and all thanks

I like that too, most likely x265 does that, otherwise it was implemented by Revan.

[stax76]

Did you try EVR/ EVR-CP ?

2 GB being huge? :)

I did try EVR-CP in mpc but it did not really look better.

At some time I might buy a better card if I can find a small one with Turing encoding and 75 W.

[jlw_4049]

i think there might be some memory leak still, after using preview window a few times, stax was using around 500 MB in idle state.

the detailed progress bar is great, shows estimated size and all ;) thanks :)

adding new job, editing filters are now very smooth, i am loving it.Is there a new release?

Sent from my SM-G965U1 using Tapatalk

[stax76]

Is there a new release?

Sent from my SM-G965U1 using Tapatalk

The latest is 2.0.1.1

https://github.com/staxrip/staxrip/blob/master/changelog.md

[jlw_4049]

The latest is 2.0.1.1



https://github.com/staxrip/staxrip/blob/master/changelog.mdOh nice. Am I still able to do 4k HDR encodes with ffvideosource?

Sent from my SM-G965U1 using Tapatalk

[frenchfries]

The latest is 2.0.1.1

https://github.com/staxrip/staxrip/blob/master/changelog.md

Hey Stax

Are there any issues in applying your releases over Revans? I.e. are they compatible. It looks like you merged in his changes but I'm not sure.

[Havokdan]

The latest is 2.0.1.1

https://github.com/staxrip/staxrip/blob/master/changelog.md
Stable or test build?

[wallander]

Hallo stax76,

thank you for the new version 2.0.1.0.
I encode since many years all my TV-series captures with staxrip and x264, quality 22 and mp3 audio (compatibility).
Now I have a problem with ffmpeg encoder.
There is the following error:

Error Audio encoding 1 using ffmpeg 2019-05-12 (Wolfberry built) (2.0.1.0)

Audio encoding 1 using ffmpeg 2019-05-12 (Wolfberry built) 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: Unzulässige Funktion.


------ Audio encoding 1 using ffmpeg 2019-05-12 (Wolfberry built) ------

D:\PortableSuite\Video\StaxRip-x64-2.0.1.0-stable\Apps\Encoders\ffmpeg\ffmpeg.exe -i "G:\Cut\This is us.S03.E08 Feiertagssituationen.mpa" -c:a libmp3lame -q:a 6 -af volume=3.3dB -y -hide_banner "G:\Cut\This is us.S03.E08 Feiertagssituationen_temp\This is us.S03.E08 Feiertagssituationen_a1.mp3"

[mp3 @ 000002f4e1f2b080] Estimating duration from bitrate, this may be inaccurate
Input #0, mp3, from 'G:\Cut\This is us.S03.E08 Feiertagssituationen.mpa':
Duration: 00:40:34.68, start: 0.000000, bitrate: 192 kb/s
Stream #0:0: Audio: mp2, 48000 Hz, stereo, fltp, 192 kb/s
Unknown encoder 'libmp3lame'



StaxRip.ErrorAbortException: Audio encoding 1 using ffmpeg 2019-05-12 (Wolfberry built) 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: Unzulässige Funktion.


------ Audio encoding 1 using ffmpeg 2019-05-12 (Wolfberry built) ------

D:\PortableSuite\Video\StaxRip-x64-2.0.1.0-stable\Apps\Encoders\ffmpeg\ffmpeg.exe -i "G:\Cut\This is us.S03.E08 Feiertagssituationen.mpa" -c:a libmp3lame -q:a 6 -af volume=3.3dB -y -hide_banner "G:\Cut\This is us.S03.E08 Feiertagssituationen_temp\This is us.S03.E08 Feiertagssituationen_a1.mp3"

[mp3 @ 000002f4e1f2b080] Estimating duration from bitrate, this may be inaccurate
Input #0, mp3, from 'G:\Cut\This is us.S03.E08 Feiertagssituationen.mpa':
Duration: 00:40:34.68, start: 0.000000, bitrate: 192 kb/s
Stream #0:0: Audio: mp2, 48000 Hz, stereo, fltp, 192 kb/s
Unknown encoder 'libmp3lame'


bei StaxRip.Proc.Start() in C:\Users\frank\Daten\Projekte\VB\staxrip\General\Proc.vb:Zeile 338.
bei StaxRip.GUIAudioProfile.Encode() in C:\Users\frank\Daten\Projekte\VB\staxrip\General\AudioProfile.vb:Zeile 664.
bei StaxRip.GlobalClass._Closure$__._Lambda$__31-0() in C:\Users\frank\Daten\Projekte\VB\staxrip\General\GlobalClass.vb:Zeile 105.
bei System.Threading.Tasks.Parallel.<>c__DisplayClass4_0.<Invoke>b__0()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
bei StaxRip.GlobalClass.ProcessJob(String jobPath) in C:\Users\frank\Daten\Projekte\VB\staxrip\General\GlobalClass.vb:Zeile 137.

What's the problem.
Can sombody help me?

Thanks

[stax76]

Oh nice. Am I still able to do 4k HDR encodes with ffvideosource?

I don't have much expertise regarding HDR, Revan did much work in this area, if it relies on ffms2 then I would rather use VapourSynth because it has a much newer ffms2 built.

Are there any issues in applying your releases over Revans? I.e. are they compatible. It looks like you merged in his changes but I'm not sure.

I don't think there are issues, I think all of Revans improvements are present.

Stable or test build?

Test built should be fairly stable.

I encode since many years all my TV-series captures with staxrip and x264, quality 22 and mp3 audio (compatibility).

Apparently Wolfberry didn't enable --enable-libmp3lame, I've requested it for the next built.

https://forum.doom9.org/showthread.php?p=1874404#post1874404

You can download a static x64 ffmpeg built with enabled --enable-libmp3lame here:

https://ffmpeg.zeranoe.com/builds

[Natty]

earlier mediainfo demuxed dtshdma as .dtsma and 2.0.2.2 demuxed it as .dtshd.
encodes fine, but not sure if its a correct method.:helpful:

[stax76]

earlier mediainfo demuxed dtshdma as .dtsma and 2.0.2.2 demuxed it as .dtshd.
encodes fine, but not sure if its a correct method.:helpful:

dtshd file extension should be fine for DTS Master Audio.

[jlw_4049]

dtshd file extension should be fine for DTS Master Audio.

With VapourSynth how can I use a code like SelectRangeEvery(x,x)?

[wallander]

You can download a static x64 ffmpeg built with enabled --enable-libmp3lame here:

https://ffmpeg.zeranoe.com/builds

Works very well!
:thanks:

[stax76]

With VapourSynth how can I use a code like SelectRangeEvery(x,x)?

https://forum.doom9.org/showthread.php?p=1727482#post1727482

[stax76]

https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

2.0.1.3

new: again new experimental icon, please give feedback if you like it,
if it's not liked then it will be reverted to the classic icon, the problem
with the classic icon is it looks outdated because it's not flat. The icon
of the previous built was looking good but it was not dark mode compatible

new: added ConvertFromDoubleWidth to AviSynth profiles, it's useful to fix the
double width output that l-smash outputs for 10 (or more) bit sources.
The profiles were not reset so the changes are only available
after reseting the profiles manually

new: in the x265 dialog it's possible to select the preferred piping tool,
use at your own risk, not all combinations will work. In theory the included
x265 built don't need a piping tool but I could not make it work without
a piping tool. Options are: Automatic, None, vspipe, avs2pipemod, ffmpeg

update: ffmpeg, unlike the built before this one supports mp3 encoding

update: x264, x265

update: d2v vs filter plugin

[benjen]

I hear that Nvidia GTX 1650 doesn't have Turing-encoding betting sites (https://topfootballbettingsites.com/), it uses old Volta Nvidia Encoder (NVENC) for GPU-encoding.
https://www.tomshardware.com/news/nvidia-geforce-gtx-1650-volta-nvenc,39161.html

Thanks!

[imhh11]

Thanks stax76, I like the new grey icon.

https://extraimage.net/images/2019/05/16/803a406e30a2e1738376d5d7a3c3b1b4.jpg

[stax76]

Thanks stax76, I like the new grey icon.

https://extraimage.net/images/2019/05/16/803a406e30a2e1738376d5d7a3c3b1b4.jpg

I've found the grey icon here:

https://www.flaticon.com/search/8?word=movie

There are two up votes on the tracker for the tombstone icon of 1.7 so it's still an option, it has also the problem that black is not dark mode compatible.

https://github.com/staxrip/staxrip/issues/1

[Revan654]

What filter so you recommend for 4k HDR encoding?

Sent from my SM-G965U1 using Tapatalk

DGIndexNV, It's not freeware though, But it fully supports HDR.

At times some of the other source filters can report bad info(Mainly the time). ffms being one of them. I had one video that time was 32 Mins but ffms only reported 28 Mins. L-Smash was a bit better or the other ffms2 variant.

[Revan654]

With VapourSynth how can I use a code like SelectRangeEvery(x,x)?

http://www.vapoursynth.com/doc/functions/selectevery.html

EX:

It would be something on the lines of:

clip = core.std.SelectEvery(clip = clip, cycle = x, offsets = list(range(0, 14)))

[jlw_4049]

http://www.vapoursynth.com/doc/functions/selectevery.html



EX:



It would be something on the lines of:



clip = core.std.SelectEvery(clip = clip, cycle = x, offsets = list(range(0, 14)))I can't figure out where to put it in staxrip. It seems to ignore if I add it manually. If i add it under the crop section it gives an error.

Sent from my SM-G965U1 using Tapatalk

[imhh11]

Hi, I'm trying to encode a V210 capture (AVI YUV 422 10bits) to x265 10bits 4:2:0 using fmtconv.
It's working but I get very high RAM usage and a warning msg(memory limit exceeded).
what am I doing wrong? sorry, I'm a newbie. Thank you!

https://extraimage.net/images/2019/05/16/4946e19d620539e2d7b54b53f2f79fa6.png

https://extraimage.net/images/2019/05/16/21d70cfd9d7a2559114aa85f2b5c3126.png https://extraimage.net/images/2019/05/16/ccaf7a87452ca930c34a13e1690b45fc.png





it works fine with AviSynth without having to use/configure fmtc but I would prefer to use VapourSynth/ffms2 if possible.

https://extraimage.net/images/2019/05/16/cbecf01d2ffe0d05e6f6cff35e5daa52.png

https://extraimage.net/images/2019/05/16/6de7c313060c768098418bd123b3834a.png https://extraimage.net/images/2019/05/16/6c1fc1726cf6ed0c50cce175bb7d25fc.png

[stax76]

I can't figure out where to put it in staxrip. It seems to ignore if I add it manually. If i add it under the crop section it gives an error.

Sent from my SM-G965U1 using Tapatalk

Here is an example:

https://postimg.cc/8F3SV104

@imhh11

The problem is not caused by something that staxrip does, I suggest creating a thread in the VapourSynth section of the forum because many experienced VapourSynth users don't read this thread.

[Exaris]

Hello Revan and stax76,
Are there any hardware accelerated source filters for VapourSynth that support 10-bit video?
From my tests I have found that only two of StaxRip's source filters output true 10bit (LWLibavSource and ffms2),
and ffms2 has VFR issues and poor automatic FPS detection so I am stuck only using LWLibavSource.
Both of them are software decoders (not great when decoding 4K HDR10 HEVC files).
I have tested NVDec, but it dithers 10bit to 8bit so I can't use it for 10bit encodes.
I would like to make use of my 1080Ti's HW decoding if possible, what do you recommend I do?
Is there some kind of undocumented setting for NVDec that enables 10bit output?

[Natty]

Hi, I'm trying to encode a V210 capture (AVI YUV 422 10bits) to x265 10bits 4:2:0 using fmtconv.
It's working but I get very high RAM usage and a warning msg(memory limit exceeded).



https://forum.doom9.org/showthread.php?p=1874627#post1874627

[stax76]

Hello Revan and stax76,
Are there any hardware accelerated source filters for VapourSynth that support 10-bit video?
From my tests I have found that only two of StaxRip's source filters output true 10bit (LWLibavSource and ffms2),
and ffms2 has VFR issues and poor automatic FPS detection so I am stuck only using LWLibavSource.
Both of them are software decoders (not great when decoding 4K HDR10 HEVC files).
I have tested NVDec, but it dithers 10bit to 8bit so I can't use it for 10bit encodes.
I would like to make use of my 1080Ti's HW decoding if possible, what do you recommend I do?
Is there some kind of undocumented setting for NVDec that enables 10bit output?

Hi and welcome Exaris,
you mean DGDecNV with NVDec?

[Abu3safeer]

How to use "insertsign" function in StaxRip,
I went through settings and found out that I need to use "vapoursynth" in order to have "insertsign" enabled,
but whenever I try to change the filter to "vapoursynth" I get this error message:

https://imgpile.com/images/1xMh5i.png


So I decided to use VirtualDub as mentioned in the error message, but I get this:

https://imgpile.com/images/1xM9cu.png



I don't know much about python, so I don't know if it is because of python, or from ffms2.dll, or from something else.

I have this simple script which I tried to use with AVS filter but didn't work, it show errors:


function insertsign(clip mainclip, clip overlayclip, int startframe, int "endframe") {
# make the endframe parameter optional (defaulting to where the overlay clip ends)
endframe = default(endframe,startframe+overlayclip.framecount()-1) # is endframe not specified?
endframe = (endframe == 0) ? startframe+overlayclip.framecount()-1 : endframe # is it specified but zero?
# is it specified but >= the main clip's last frame? (may have been caused by the previous line or specified by the user)
# in that case make it equal to the last frame of the main clip (this is important later)
endframe = (endframe >= mainclip.framecount()-1) ? mainclip.framecount()-1 : endframe


# make sure the special case startframe=1 is dealt with correctly
# (needed because trim(0,0) returns the entire clip, which is obviously not what we want)
# note that the first frame of the clip is zero, NOT one!
begin = (startframe == 1) ? mainclip.trim(0,-1) : mainclip.trim(0,startframe-1)
middle = mainclip.trim(startframe,endframe)
# make sure the special case endframe = last frame of the clip is handled properly.
end = (endframe == mainclip.framecount()-1) ? blankclip(mainclip,length=0) : mainclip.trim(endframe+1,0)

middleoverlay = Overlay(middle, overlayclip, mask=overlayclip.showalpha())

# deal with the special case startframe=0 (in which case we don't have anything before the overlay)
# note that trim(-1,0) does nothing (it returns the same as trim(0,0)...)
final = (startframe == 0) ? middleoverlay ++ end : begin ++ middleoverlay ++ end
return final
}

[gonca]

Hello Revan and stax76,
Are there any hardware accelerated source filters for VapourSynth that support 10-bit video?
From my tests I have found that only two of StaxRip's source filters output true 10bit (LWLibavSource and ffms2),
and ffms2 has VFR issues and poor automatic FPS detection so I am stuck only using LWLibavSource.
Both of them are software decoders (not great when decoding 4K HDR10 HEVC files).
I have tested NVDec, but it dithers 10bit to 8bit so I can't use it for 10bit encodes.
I would like to make use of my 1080Ti's HW decoding if possible, what do you recommend I do?
Is there some kind of undocumented setting for NVDec that enables 10bit output?

If you are referring to DGDecNV and DGIndexNV then use
fulldepth=True
This is explained in the manual

[stax76]

@Abu3safeer

It looks like VapourSynth isn't working, you can try to re-install Python 3.7.3 x64 and VapourSynth R45 x64.

[Exaris]

Thanks, went back and read it. This was the problem ;)

[Abu3safeer]

@Abu3safeer

It looks like VapourSynth isn't working, you can try to re-install Python 3.7.3 x64 and VapourSynth R45 x64.

Thank you, I will try.

[Abu3safeer]

Mmm... strange, it turned out that I have 32bit python, so I removed that and installed 64bit, but I get worse error message:

https://imgpile.com/images/1xMmIg.png

This happens the moment I put .vpy into "VirtualDub"

So According to "Access Violence" I thought running "VirtualDub" as Administrator would solve the problem, but looks like the same

https://imgpile.com/images/1xM8eW.png

VirtualDub crash report -- build 35491 (release)
--------------------------------------

Disassembly:
00000000: 0000 add [eax], al <-- FAULT
00000002: 0000 add [eax], al
00000004: 0000 add [eax], al
00000006: 0000 add [eax], al
00000008: 0000 add [eax], al
0000000a: 0000 add [eax], al
0000000c: 0000 add [eax], al
0000000e: 0000 add [eax], al
00000010: 0000 add [eax], al
00000012: 0000 add [eax], al
00000014: 0000 add [eax], al
00000016: 0000 add [eax], al
00000018: 0000 add [eax], al
0000001a: 0000 add [eax], al
0000001c: 0000 add [eax], al
0000001e: 0000 add [eax], al
00000020: 0000 add [eax], al
00000022: 0000 add [eax], al
00000024: 0000 add [eax], al
00000026: 0000 add [eax], al
00000028: 0000 add [eax], al
0000002a: 0000 add [eax], al
0000002c: 0000 add [eax], al
0000002e: 0000 add [eax], al
00000030: 0000 add [eax], al
00000032: 0000 add [eax], al
00000034: 0000 add [eax], al
00000036: 0000 add [eax], al
00000038: 0000 add [eax], al
0000003a: 0000 add [eax], al
0000003c: 0000 add [eax], al
0000003e: 0000 add [eax], al
00000040: 0000 add [eax], al
00000042: 0000 add [eax], al
00000044: 0000 add [eax], al
00000046: 0000 add [eax], al
00000048: 0000 add [eax], al
0000004a: 0000 add [eax], al
0000004c: 0000 add [eax], al
0000004e: 0000 add [eax], al
00000050: 0000 add [eax], al
00000052: 0000 add [eax], al
00000054: 0000 add [eax], al
00000056: 0000 add [eax], al
00000058: 0000 add [eax], al
0000005a: 0000 add [eax], al
0000005c: 0000 add [eax], al
0000005e: 0000 add [eax], al
00000060: 0000 add [eax], al
00000062: 0000 add [eax], al
00000064: 0000 add [eax], al
00000066: 0000 add [eax], al
00000068: 0000 add [eax], al
0000006a: 0000 add [eax], al
0000006c: 0000 add [eax], al
0000006e: 0000 add [eax], al
00000070: 0000 add [eax], al
00000072: 0000 add [eax], al
00000074: 0000 add [eax], al
00000076: 0000 add [eax], al
00000078: 0000 add [eax], al
0000007a: 0000 add [eax], al
0000007c: 0000 add [eax], al
0000007e: 0000 add [eax], al
00000080: 0000 add [eax], al
00000082: 0000 add [eax], al
00000084: 0000 add [eax], al
00000086: 0000 add [eax], al
00000088: 0000 add [eax], al
0000008a: 0000 add [eax], al
0000008c: 0000 add [eax], al
0000008e: 0000 add [eax], al
00000090: 0000 add [eax], al
00000092: 0000 add [eax], al
00000094: 0000 add [eax], al
00000096: 0000 add [eax], al
00000098: 0000 add [eax], al
0000009a: 0000 add [eax], al
0000009c: 0000 add [eax], al
0000009e: 0000 add [eax], al
000000a0: 0000 add [eax], al
000000a2: 0000 add [eax], al
000000a4: 0000 add [eax], al
000000a6: 0000 add [eax], al
000000a8: 0000 add [eax], al
000000aa: 0000 add [eax], al
000000ac: 0000 add [eax], al
000000ae: 0000 add [eax], al
000000b0: 0000 add [eax], al
000000b2: 0000 add [eax], al
000000b4: 0000 add [eax], al
000000b6: 0000 add [eax], al
000000b8: 0000 add [eax], al
000000ba: 0000 add [eax], al
000000bc: 0000 add [eax], al
000000be: 0000 add [eax], al
000000c0: 0000 add [eax], al
000000c2: 0000 add [eax], al
000000c4: 0000 add [eax], al
000000c6: 0000 add [eax], al
000000c8: 0000 add [eax], al
000000ca: 0000 add [eax], al
000000cc: 0000 add [eax], al
000000ce: 0000 add [eax], al
000000d0: 0000 add [eax], al
000000d2: 0000 add [eax], al
000000d4: 0000 add [eax], al
000000d6: 0000 add [eax], al
000000d8: 0000 add [eax], al
000000da: 0000 add [eax], al
000000dc: 0000 add [eax], al
000000de: 0000 add [eax], al
000000e0: 0000 add [eax], al
000000e2: 0000 add [eax], al
000000e4: 0000 add [eax], al
000000e6: 0000 add [eax], al
000000e8: 0000 add [eax], al
000000ea: 0000 add [eax], al
000000ec: 0000 add [eax], al
000000ee: 0000 add [eax], al
000000f0: 0000 add [eax], al
000000f2: 0000 add [eax], al
000000f4: 0000 add [eax], al
000000f6: 0000 add [eax], al
000000f8: 0000 add [eax], al
000000fa: 0000 add [eax], al
000000fc: 0000 add [eax], al
000000fe: 0000 add [eax], al

Built on Althena on Sun Oct 27 15:59:07 2013 using compiler version 1400

Windows 6.3 (Windows 7 x64 build 9600) []
Memory status: virtual free 1871M/2048M, commit limit 17868M, physical total 16312M

EAX = 00000000
EBX = 751d72a4
ECX = 00000000
EDX = 00000000
EBP = 0019e2f8
ESI = 0610812c
EDI = 06108108
ESP = 0019e2e4
EIP = 00000000
EFLAGS = 00210246
FPUCW = 027f
FPUTW = ffff

Crash reason: Access Violation

Crash context:
An out-of-bounds memory access (access violation) occurred in module 'VirtualDub'...

...reading address 00000000.

Pointer dumps:

EBX 751d72a0: 70dd8bac 00000001 00000000 000000c0 46000000 000001e1 00000000 000000c0
ESI 06108128: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000f
EDI 06108108: 663dbd80 663dbd58 663dbe24 663dbdbc 00000001 00000000 00000000 00000000
ESP 0019e2e0: 663c2234 663c224b 06108108 0019fad4 663c4320 ffffffff 0019e30c 663d61b0
0019e300: fffffffc 0610eca4 00afe7a8 0019e31c 663d5eed 0019e54c 663d5ec0 0019e3fc
0019e320: 75269e3b 0610eca4 751d72a4 0019e54c 00000000 00afe7a8 0019e54c 00300030
0019e340: 00afe7a8 0610eca4 0019e54c 751d72a4 00000062 00000000 00000000 00000000
EBP 0019e2f8: 0019e30c 663d61b0 fffffffc 0610eca4 00afe7a8 0019e31c 663d5eed 0019e54c
0019e318: 663d5ec0 0019e3fc 75269e3b 0610eca4 751d72a4 0019e54c 00000000 00afe7a8
0019e338: 0019e54c 00300030 00afe7a8 0610eca4 0019e54c 751d72a4 00000062 00000000
0019e358: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Thread call stack:
663c224b: VSScript!_vsscript_getVSApi@0 [663c0000+2210+3b]
663d61b0: vsvfw!DllCanUnloadNow [663d0000+5f00+2b0]
663d5eed: vsvfw!DllGetClassObject [663d0000+5ec0+2d]
75269e3b: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+39cb]
75269cd3: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+3863]
77b63779: ntdll!RtlAllocateHeap [77b20000+41f00+1879]
774e440b: ucrtbase!_o_malloc [774b0000+34320+eb]
75269c7f: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+380f]
75269b78: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+3708]
75269b3b: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+36cb]
7526b605: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+5195]
7526e4f5: combase!CoGetMarshalSizeMax [751b0000+bcd40+17b5]
7529d1f0: combase!CoSetErrorInfo [751b0000+eca20+7d0]
7529d21d: combase!CoSetErrorInfo [751b0000+eca20+7fd]
7526d8ed: combase!CoGetMarshalSizeMax [751b0000+bcd40+bad]
7526b824: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+53b4]
7526b8fe: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+548e]
7526beb8: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+5a48]
7526ba2a: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+55ba]
7526bc55: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+57e5]
7526bb57: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+56e7]
7526d7c8: combase!CoGetMarshalSizeMax [751b0000+bcd40+a88]
7526b9c0: combase!CoGetCurrentLogicalThreadId [751b0000+b6470+5550]
7526d8b6: combase!CoGetMarshalSizeMax [751b0000+bcd40+b76]
7526d9ca: combase!CoGetMarshalSizeMax [751b0000+bcd40+c8a]
7526d9fd: combase!CoGetMarshalSizeMax [751b0000+bcd40+cbd]
7526d991: combase!CoGetMarshalSizeMax [751b0000+bcd40+c51]
7526d8bd: combase!CoGetMarshalSizeMax [751b0000+bcd40+b7d]
7526e4f5: combase!CoGetMarshalSizeMax [751b0000+bcd40+17b5]
752a68b2: combase!CoCreateInstance [751b0000+f5900+fb2]
77b6d147: ntdll!RtlConvertSidToUnicodeString [77b20000+4ce90+2b7]
77b6d147: ntdll!RtlConvertSidToUnicodeString [77b20000+4ce90+2b7]
77b6cffa: ntdll!RtlConvertSidToUnicodeString [77b20000+4ce90+16a]
77b6d022: ntdll!RtlConvertSidToUnicodeString [77b20000+4ce90+192]
77b5d997: ntdll!RtlAppendUnicodeToString [77b20000+3d940+57]
77b6cdfe: ntdll!RtlFormatCurrentUserKeyPath [77b20000+4cd70+8e]
77b650a0: ntdll!RtlFreeHeap [77b20000+44ec0+1e0]
77b575d2: ntdll!RtlAppendUnicodeStringToString [77b20000+37590+42]
752a5692: combase!RoGetActivationFactory [751b0000+f2b90+2b02]
752a4eda: combase!RoGetActivationFactory [751b0000+f2b90+234a]
752a4fd4: combase!RoGetActivationFactory [751b0000+f2b90+2444]
77b909fc: ntdll!NtCreateFile [77b20000+709f0+c]
6a5d085c: apphelp!DWM8And16Bit_RestoreDisplayMode_CallOut [6a560000+6a2f0+656c]
752f375d: combase!InternalTlsAllocData [751b0000+141310+244d]
752a66d9: combase!CoCreateInstance [751b0000+f5900+dd9]
752a625c: combase!CoCreateInstance [751b0000+f5900+95c]
77b905fc: ntdll!NtQueryValueKey [77b20000+705f0+c]
7634dd47: KERNELBASE!RegOpenKeyExInternalW [76250000+fdc10+137]
7634d6f3: KERNELBASE!RegQueryValueExW [76250000+fd620+d3]
76b7e769: advapi32!SetNamedSecurityInfoW [76b60000+1e6d0+99]
7634c8fd: KERNELBASE!CLOSE_LOCAL_HANDLE_INTERNAL [76250000+fc8b0+4d]
76b7d29d: advapi32!RegQueryValueW [76b60000+1d1f0+ad]
76b7d2a4: advapi32!RegQueryValueW [76b60000+1d1f0+b4]
664869ff: AVIFIL32!DllGetClassObject [66480000+6600+3ff]
66486a1d: AVIFIL32!DllGetClassObject [66480000+6600+41d]
66486c0a: AVIFIL32!AVIFileExit [66480000+6a40+1ca]
66486c22: AVIFIL32!AVIFileExit [66480000+6a40+1e2]
752a5b95: combase!CoCreateInstance [751b0000+f5900+295]
0051b8f1: VDaswprintf()
752a59a7: combase!CoCreateInstance [751b0000+f5900+a7]
6a5d06a9: apphelp!DWM8And16Bit_RestoreDisplayMode_CallOut [6a560000+6a2f0+63b9]
005fb4f2: _calloc_impl()
66486c7d: AVIFIL32!AVIFileOpenW [66480000+6c30+4d]
004e98ee: InputFileAVI::Init()
00480043: VDProjectUI::MenuHit()
77b74ceb: ntdll!SbSelectProcedure [77b20000+54ba0+14b]
77b74d03: ntdll!SbSelectProcedure [77b20000+54ba0+163]
77b63779: ntdll!RtlAllocateHeap [77b20000+41f00+1879]
6a5d08a3: apphelp!DWM8And16Bit_RestoreDisplayMode_CallOut [6a560000+6a2f0+65b3]
77b650a0: ntdll!RtlFreeHeap [77b20000+44ec0+1e0]
77b61f3e: ntdll!RtlAllocateHeap [77b20000+41f00+3e]
005f8482: (special)()
77b623b0: ntdll!RtlAllocateHeap [77b20000+41f00+4b0]
005f7add: free()
005f7afc: free()
005f7afc: free()
00520141: VDFile::~VDFile()
004e49d1: VDAutoselectInputDriverForFile()
77b61f3e: ntdll!RtlAllocateHeap [77b20000+41f00+3e]
77b61f3e: ntdll!RtlAllocateHeap [77b20000+41f00+3e]
005f8482: (special)()
005f848e: (special)()
004e974b: VDInputDriverAVI1::CreateInputFile()
004763c4: VDProject::Open()
005210cc: VDAutoLogger::VDAutoLogger()
00461edc: OpenAVI()
0047f6f1: VDProjectUI::MenuHit()
77825a5d: USER32!GetWindowLongA [777f0000+35a10+4d]
0048de10: VDUIFrame::DefProc()
00480e93: _catch$?MainWndProc@VDProjectUI@@IAEJIIJ@Z$0()
77825a69: USER32!GetWindowLongA [777f0000+35a10+59]
00477090: VDProjectUI::WndProc()
0048e525: VDUIFrame::StaticWndProc()
7783635b: USER32!AddClipboardFormatListener [777f0000+46310+4b]
7782729c: USER32!CallWindowProcW [777f0000+36770+b2c]
778337ef: USER32!IsRectEmpty [777f0000+435e0+20f]
77b904dc: ntdll!NtCallbackReturn [77b20000+704d0+c]
77833807: USER32!IsRectEmpty [777f0000+435e0+227]
778270eb: USER32!CallWindowProcW [777f0000+36770+97b]
778263db: USER32!DispatchMessageW [777f0000+361a0+23b]

-- End of report


All what I want is to use insertSign, I hope the result deserves the troubles.

[gonca]

Abu3safeer
Are you using Vdub or Vdub2?
Use
https://www.videohelp.com/software/VirtualDub2

[stax76]

Files might be corrupted, ensure that you've re-downloaded and re-installed VapourSynth x64 and StaxRip.

https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

use 7zip to unpack

https://www.7-zip.org

VapourSynth x64 installer is in StaxRip included under Apps\Installers

you can try a diagnostic script found here:

https://github.com/theChaosCoder/vapoursynth-plugin-check/blob/master/vs_plugin_check.py


in Windows File Explorer go to the desktop folder
save the script as test.py in desktop folder
open a console and navigate to the desktop folder, easy way to do this is enter cmd in Windows File Explorer address bar and press enter
run the script with the console by executing following command:


py test.py

[Bahamuth]

I have a little problem. StaxRip2 takes really long to load a file, then it tells me this:
https://i.imgur.com/7eyCFXQ.png

I also cannot go to Crop afterwards, because it tells me the same. And everything takes 5 seconds to load, propably because he tries to load the file again.

But the file is there, I haven't tampered with it. I installed most current version of AviSynth+ and VapourSynth (though I don't know how to make StaxRip2 use VapourSynth).

Your python file tells me this:
#######################################
VapourSynth Video Processing Library
Copyright (c) 2012-2018 Fredrik Mellbin
Core R45
API R3.5
Options: -

Architecture 64bit - Windows-7-6.1.7601-SP1
Python build: ('v3.7.3:ef4ec6ed12', 'Mar 25 2019 22:22:05')

#######################################
checking dlls in C:\apps\video\VapourSynth\plugins64
#######################################

No problems found, nice!
#######################################
Found 0 dlls. Errors: 0 Notices: 0

Everything is 64bit, I'm running Windows 7 Professional

[stax76]

@Bahamuth

Please post the full code, right click filters > Preview Code

I would guess one of the filters needs a runtime that isn't yet installed and staxrip don't yet has a warning for it.

[Bahamuth]

here it goes:
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\AddGrainC\AddGrainC.dll")
Import("C:\apps\video\Staxrip2\Apps\Plugins\avs\AnimeIVTC\AnimeIVTC.avsi")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\Average\Average.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\Decomb\Decomb.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\DFTTest\dfttest.dll")
Import("C:\apps\video\Staxrip2\Apps\Plugins\AVS\Dither\dither.avsi")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\AVS\Dither\dither.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\EEDI2\EEDI2.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\EEDI3\EEDI3.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\FFT3DFilter\fft3dfilter.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\JPSDR\Plugins_JPSDR.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\both\KNLMeansCL\KNLMeansCL.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\masktools2\masktools2.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\modPlus\modPlus.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\MPEG2DecPlus\MPEG2DecPlus.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\mvtools2\mvtools2.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\RgTools\RgTools.dll")
Import("C:\apps\video\Staxrip2\Apps\Plugins\avs\SMDegrain\SMDegrain.avsi")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\AVS\TDeint\TDeint.dll")
LoadPlugin("C:\apps\video\Staxrip2\Apps\Plugins\avs\yadifmod2\yadifmod2.dll")
LoadCPlugin("C:\apps\video\Staxrip2\Apps\Plugins\both\ffms2\ffms2.dll")
Import("C:\apps\video\Staxrip2\Apps\Plugins\avs\QTGMC\QTGMC.avsi")
FFVideoSource("E:\!media\BluRay\Die Verurteilten\.unreferenced\00001 (EuroVideo).mkv", colorspace = "YV12", \
cachefile = "E:\!media\BluRay\Die Verurteilten\.unreferenced\00001 (EuroVideo)_temp\00001 (EuroVideo).ffindex")
Crop(16, 4, -16, -4)
QTGMC(Preset = "Medium")

but it's not helpful at all. Dependency walker also shows no missing dependencies when loading dfttest.dll. Also strange: upon loading the file it wants to use a size of 5000 mb.
It's just a test video, thus the bitrate goes crazy of course. Old Staxrip has no problem at all, but it also doesn't load that many filters (only ffms2).

I just loaded all of the DLL files into Dependency Walker. Like four of them have dependencies, I don't meet (but also can't):
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL

As much as I found out, these files should come from windows. I looked for them on my hard disk, but couldn't find any version. Visual C++ requirements are all met according to StaxRip.

[stax76]

@Bahamuth

qtgmc loads here, I checked in process explorer and loaded vc++ dlls are msvcp140.dll, msvcp120.dll and msvcp80.dll.

dfttest in dependency walker shows API-MS-WIN-CORE-WINRT and that might be a Win 10 dependency, I'll further investigate it. Grüße

edit:

I'll install Win 7 and see if I can reproduce it.

[NikosD]

Files might be corrupted, ensure that you've re-downloaded and re-installed VapourSynth x64 and StaxRip.

https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

use 7zip to unpack

https://www.7-zip.org I have tried both servers (Dropbox, OneDrive) a few times for StaxRip v2.0.1.3 and using 7zip v19.00 x64, I get the same warning all the time (for both servers)

The file is not 7zip but Zip and it's been extracted as Zip.

I hope the extraction is accurate and full.

Which app did you use for 7zip compression and what version ?

[stax76]

I've used 7zip but probably with incorrect command line arguments, I'll check it.

[Rafawell]

Would you like to put AutoOverlay in the gui or could come on the next release?

Staxrip is a wonderful work I like a lot.

[stax76]

@Rafawell

If it's not a big download then yes.


@Bahamuth

It's probably something specific to your system, maybe files were corrupted, you can try to re-download 2.0.1.3

https://github.com/staxrip/staxrip/blob/master/changelog.md

I was able to load qtgmc in a fresh Win 7 install in vmware, only problem was KNLMeansCL dll failed to load due to opencl.dll missing, I've worked around this by editing the qtgmc.avsi replacing KNLMeansCL with KNL_MeansCL, this prevents staxrip adding a LoadPlugin call for KNLMeansCL, after that qtgmc was loading.

[NikosD]

BTW, I think there are two different versions of "StaxRip" -one from Revan654 and one from stax76.

I don't know their differences besides the icon of the app, but I think it's a little confusing to coexist under the same thread of "StaxRip".

Revan654 put a lot of time and effort to develop StaxRip not from the beginning but based on stax76's work, after stax76's "retirement"

If they are both in a mood to be active developers of StaxRip, I think they both deserve to improve their programs but probably independently and surely with a different name and under a different thread.

Is it time to split the app and the thread using a scheme like MPC-HC and MPC-BE or something like that ?

[stax76]

@NikosD

Revan has owner privileges in the new repo and full control over everything.

I would like to try Linux and join or create a portable audio player but it's not an easy goal.

[Rafawell]

@stax76 Sorry for the lack of clarity.

I was talking about the next staxrip could come with the avisynth AutoOverlay plugin ... Is it possible?

[stax76]

@stax76 Sorry for the lack of clarity.

I was talking about the next staxrip could come with the avisynth AutoOverlay plugin ... Is it possible?

Please add it as feature request to the issue tracker, we'll examine it. :)

https://github.com/staxrip/staxrip/issues

[Forteen88]

Which source-plugin should I use for loading different video-sources (AVC, VC-1, H.265, MPEG) in StaxRip?
I hear that LSMASH is among the best (for no frame-skips) for loading H.264-video, but it's not good for loading interlaced video.

Or should I really just let StaxRip's "Automatic" option to decide that?

Thanks.

[stax76]

@Forteen88

L-Smash and ffms2 are both popular, LigH recently said you try one and if it doesn't work you use the other. I third one that is popular as well is DGDecNV, it has very good transport stream support and it's fast.

[Forteen88]

@Forteen88
L-Smash and ffms2 are both popular, LigH recently said you try one and if it doesn't work you use the other. I third one that is popular as well is DGDecNV, it has very good transport stream support and it's fast.Thanks, but I read that ffms2 drops frames sometimes, and that you should set it to use only 1 thread and seekmode=0. Maybe L-SMASH needs that 1-thread setting too? Does StaxRip set source-filters to only use 1 thread, and if not, how can I set it to use 1 thread myself? Does DGDecNV have this problem too?
l-smash is more reliable for transport streams which I assume your sat feed are. Use threads=1 for highest reliability

eg.
LWLibavVideoSource("video.ts", threads=1) threads=1 is always more reliable for both of them, as is seekmode=0 for ffms2. I think megui automatically adds threads=1 if you use that. Both options slow decoding down decoding considerably when you use for ffms2. You usually don't need seekmode=0, unless you need non linear access (e.g. editing on a timeline, some types of temporal filtering)
https://forum.videohelp.com/threads/374214-Is-there-a-Frame-Accurate-Indexer-for-Videos-with-4-2-2-Chroma

EDIT: Oh, I can change LWLibavVideoSource's parameters (and other source-filter's parameters) by clicking "Edit code..." in StaxRip, the parameters threads=1 & seekmode=0 (for more secure ffms2) are not set as default.
EDIT2: Thanks again stax76, for info about "Profiles" in StaxRip.

[stax76]

@Forteen88

In the same menu where "Edit code..." is, there is also "Profiles...", if you edit profiles, it's then applied every time you open a source.

Which profile is used depends on the source file type, there is a setting where you can configure which profile should be used for which source file type.

[RanmaCanada]

I've only ever used staxrip for "basic" encodes of my anime, and very rarely have I run into the issue I have with a current bluray. Several of the episodes have both Japanese commentary tracks, and English commentary tracks, as well as subtitles for both of those tracks, let alone the regular English dialogue and Japanese dialogue. I am having a doozy of a time trying to get staxrip to show me all these tracks, have the option to name them as commentary with the people included, and have them each at differing bitrates.

Is this possible? ie say both dialogue tracks at 384k opus and named as such, and the commentary at 256 Opus also named properly (total of 4 audio tracks). Since I have some very rare old releases, I would like to preserve as much of the original tracks as possible as I move them over to my NAS.

Normally I would just demux everything, encode the files separately and then remux them back in with proper naming. But as this is several episodes and specials, I would rather prefer to save some time.

If it's not possible I totally understand. Also, if this is a stupid question, I apologize.

[stax76]

@RanmaCanada

Which StaxRip version are you using?

[NikosD]

New HW transcoders from rigaya: (to include in your next update)

NVEncC v4.39

QSVEncC v3.20

VCEEncC v4.02

[stax76]

@NikosD

I've created an issue on the tracker so it cannot be forgotten, thanks.

[RanmaCanada]

@RanmaCanada

Which StaxRip version are you using?

Staxrip.2.0.0.0.x64

though I will use whatever version I have to.

[stax76]

Staxrip.2.0.0.0.x64

though I will use whatever version I have to.

There was a demuxing issue but it was after 2.0.0.0.

Since 2.0.0.0 there were a couple of improvements:

https://github.com/staxrip/staxrip/releases

By default it should demux all audio and subtitle tracks, does that work?

You can add two audio tracks in the main dialog and if you need more audio tracks you can add them in the container options.

[gonca]

Can StaxRip encode 2 videos at the same time with multiple jobs in the queue
i.e.
queue is
video 1
video 2
video 3
etc

can StaxRip_1 encode video 1
StaxRip_2 encode video 2
then
StaxRip_1 encodes video 3
so on

[stax76]

@gonca

Yes but only if you run multiple staxrip instances, the job list is shared amongst multiple instances.

[gonca]

@gonca

Yes but only if you run multiple staxrip instances, the job list is shared amongst multiple instances.
Thank you for the answer

[RanmaCanada]

There was a demuxing issue but it was after 2.0.0.0.

Since 2.0.0.0 there were a couple of improvements:

https://github.com/staxrip/staxrip/releases

By default it should demux all audio and subtitle tracks, does that work?

You can add two audio tracks in the main dialog and if you need more audio tracks you can add them in the container options.

I will endeavor and see if I can figure it out :)

Thank you.

[stax76]

Which icon should be used?

https://i.postimg.cc/N09n6YVg/light.png

https://i.postimg.cc/KzLY41yB/dark.png

[Forteen88]

Which icon should be used?I think the black.ico is more like a traditional clapperboard, so it's most suiting I think.
https://en.wikipedia.org/wiki/Clapperboard

[Natty]

Black.ico

[Havokdan]

Good morning, I would like to know how I create a new video profile to encode in mpeg1 and / or 2, I'm trying, but I'm getting the program: D, does anyone help me?

[imhh11]

my vote goes for the Black.ico too.

[SaboraPie]

Black.ico, i think.

[mcjordan]

Also Black. Like John Snow ;-)

[Natty]

I like that too, most likely x265 does that, otherwise it was implemented by Revan.

its not appearing like that anymore. no idea what happened.

also --stylish doesn't work

[Rafawell]

Vote on Black.ico

[frenchfries]

Black icon with grey substituted for the black colour?

That way it addresses any dark mode or black taskbar issues, where the icon basically disappears.

[Alexander]

Black icon with gray color

[stax76]

I've uploaded a built that allows to define an icon file under:

Tools > Settings > User Interface

This icon is used within staxrip. The icon of the executable is the black one like requested, this is fixed.

The windows start menu uses windows links and windows links allow you to use custom icons so it's possible to configure which icon is used in the start menu.

The icons are located next to StaxRip.exe under:

Apps\Icons

Included are: Black, Grey, Classic, RIP

Most icons come from:

https://www.flaticon.com/search/8?word=movie

nulledone did the white border around the black icon to support dark mode

https://github.com/staxrip/staxrip/issues/1

The idea for custom icons comes from MusicBee. :)

https://github.com/staxrip/staxrip/blob/master/changelog.md

[Exaris]

What Vapoursynth filter should I use for color correction? Westworld's 4K BluRay has an ugly brown tint to everything that is not present in the 1080p BluRay release.
Also, how would I use the preview window to display HDR10 on an 8-bit monitor (like MadVR can) while I try to get rid of the tint?
Would I need to use mobius to tone map to SDR? Does StaxRip even have tonemapping filters for Vapoursynth?

Help would be much appreciated :)

[Natty]

have been getting this error since a long time

https://imgur.com/download/Iwzeo7e

i thought this was because of low ram but many users are getting this issue,mostly when using too many avs filters. preview windows also does the same. encoding starts after retrying 2-3 times, its bad for queuing and batch processing.

[RainyDog]

have been getting this error since a long time

https://imgur.com/download/Iwzeo7e

i thought this was because of low ram but many users are getting this issue,mostly when using too many avs filters. preview windows also does the same. encoding starts after retrying 2-3 times, its bad for queuing and batch processing.

Yeah I often get this too, usually when trying to run a batch of jobs.

Seems it's something to do with StaxRip not flushing open/completed jobs from memory unless the program is closed down.

A way around it is to create a job, send it to the queue and close StaxRip. Then re-open the program and run the job straight from the jobs queue without editing the job again.

But this obviously means you can only run one encode at a time or risk the memory error as there's a ram build up with each concurrent job until the program's closed.

[Natty]

Yeah I often get this too, usually when trying to run a batch of jobs.

Seems it's something to do with StaxRip not flushing open/completed jobs from memory unless the program is closed down.

A way around it is to create a job, send it to the queue and close StaxRip. Then re-open the program and run the job straight from the jobs queue without editing the job again.

But this obviously means you can only run one encode at a time or risk the memory error as there's a ram build up with each concurrent job until the program's closed.

i do that, setup job and save as srip file and restart stax. but it does not solve the issue always. i still get the error while using 3 or more avs filters mostly

[Natty]

its not appearing like that anymore. no idea what happened.

also --stylish doesn't work

updated to 2.0.2.1 today (i thought 2.0.2.2 was latest) , the bundled x265 3.0.0.24 was showing estimated file size, i updated it to 3.0.0.31 from msystem.waw.pl/x265. gcc 9.1.1 avx2 ver and it didn't show it. maybe your version is patched or modded?

[stax76]

updated to 2.0.2.1 today (i thought 2.0.2.2 was latest) , the bundled x265 3.0.0.24 was showing estimated file size, i updated it to 3.0.0.31 from msystem.waw.pl/x265. gcc 9.1.1 avx2 ver and it didn't show it. maybe your version is patched or modded?

Usually I just pick random builds from users that are around for a while and I think can be trusted, it's a very nice feature, I try to find out where it comes from.

have been getting this error since a long time

https://imgur.com/download/Iwzeo7e

Seems it's something to do with StaxRip not flushing open/completed jobs from memory unless the program is closed down.

I try to do more test encodes. In 1.7 batch processing was well tested I think and problems were usually filters leaking memory.

What Vapoursynth filter should I use for color correction? Westworld's 4K BluRay has an ugly brown tint to everything that is not present in the 1080p BluRay release.
Also, how would I use the preview window to display HDR10 on an 8-bit monitor (like MadVR can) while I try to get rid of the tint?
Would I need to use mobius to tone map to SDR? Does StaxRip even have tonemapping filters for Vapoursynth?

Help would be much appreciated

Revan has expertise in this area, my 4K screens unfortunately don't have HDR support.

[vanden]

Sorry, I may not be in the right forum ...

Here is my problem, I have 2 rip bluray 2160p and the problem is that it must miss some info.

Blade Runner 2049:
Do not pass with "madMeasureDynamicClipping", I rename the file .measurements.incomplete in .measurements and I open it with "madMeasureDynamicClipping":
https://nsa40.casimages.com/img/2019/06/01/mini_190601120901821988.jpg (https://www.casimages.com/i/190601120901821988.jpg.html)
************** Texte de l'exception **************
System.OverflowException: The arithmetic operation caused an overflow.
à madMeasureDynamicClipping.FrmMain.ImportData()
à madMeasureDynamicClipping.FrmMain.StartAnalysis()
à System.Windows.Forms.Control.OnClick(EventArgs e)
à System.Windows.Forms.Button.OnClick(EventArgs e)
à System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
à System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
à System.Windows.Forms.Control.WndProc(Message& m)
à System.Windows.Forms.ButtonBase.WndProc(Message& m)
à System.Windows.Forms.Button.WndProc(Message& m)
à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
**************
Reading it with "madMeasureDynamicClipping" I get this :
https://nsa40.casimages.com/img/2019/06/01/mini_190601120904919036.jpg (https://www.casimages.com/i/190601120904919036.jpg.html)
By removing all the .measurements.incomplete and .measurements files, I get this :
https://nsa40.casimages.com/img/2019/06/01/mini_190601120857262445.jpg (https://www.casimages.com/i/190601120857262445.jpg.html)
Pass in "Tone map HDR MadVR" :
https://nsa40.casimages.com/img/2019/06/01/mini_190601120623189391.jpg (https://www.casimages.com/i/190601120623189391.jpg.html)

Sully:
Do not pass with "madMeasureDynamicClipping" :
https://image.noelshack.com/minis/2019/22/4/1559206661-sully2.png (https://www.noelshack.com/2019-22-4-1559206661-sully2.jpg)
Pass in "Tone map HDR MadVR" :
https://nsa40.casimages.com/img/2019/06/01/mini_190601121906235835.jpg (https://www.casimages.com/i/190601121906235835.jpg.html)


Do you have a solution ?


T2 Trainspotting everything is ok :
Ok avec "madMeasureDynamicClipping" :
https://nsa40.casimages.com/img/2019/06/01/mini_19060112302966618.jpg (https://www.casimages.com/i/19060112302966618.jpg.html)
Reading it with "madMeasureDynamicClipping" I get this :
https://nsa40.casimages.com/img/2019/06/01/mini_190601121952878821.jpg (https://www.casimages.com/i/190601121952878821.jpg.html)
By removing all the .measurements files, I get this :
https://nsa40.casimages.com/img/2019/06/01/mini_190601123401283975.jpg (https://www.casimages.com/i/190601123401283975.jpg.html)
Pass in "Tone map HDR MadVR" :
https://nsa40.casimages.com/img/2019/06/01/mini_190601123539772152.jpg (https://www.casimages.com/i/190601123539772152.jpg.html)


EDIT : For sully :
After watching the movie I have some errors at the decompression : Frame that bug to 84274-84280, 85403-85426, 85448-85450, 85629-85646, 85794-85816 ... at this point MPC HC stops the movies, We put back after 59.44 Second ... 85917-85919, 89795-89824, 97386-97394, 98840-98857, 99819-99820, 99970-99971, 100328-100334, 100355-100371 ... at this point MPC HC stops the movies, We put back after 1H09min47sec ... 100401, 101005-101028, 101170-101172 ...

[Natty]

i checked dll files bundled with stax 2.0.2.1 in avsmeter64, needi3 is 32bit. is it ok?

[stax76]

i checked dll files bundled with stax 2.0.2.1 in avsmeter64, needi3 is 32bit. is it ok?

It cannot be 32bit because it would not work.

[katzenjoghurt]

[...]

Edit: after doing some additional tests it appears that the 3.0_AU+8 works fine with zones and has no errors in staxrip upon encoding completion. The two other versions, +10 and +14, however do not work and will give the same corrupted heap error.

This still drives me crazy.
With every new x265 version I hope that things would start working again - but they don't.

Last time Ma fixed that error for me in version AU+8.
Afterwards they did another fix and things would start breaking again in StaxRip. And only for StaxRip.

I can't reproduce the problem when encoding via command line.
This one just works:
"w:\Tools\Video Tools\ffmpeg\ffmpeg.exe" -i aquaman-trailer-cut.mkv -f yuv4mpegpipe - | x265.exe - --crf 22 --tune grain --profile main10 --output-depth 10 --rskip --zones 0,200,b=1.2 --qcomp 0.8 --no-open-gop --no-deblock --no-strong-intra-smoothing --frames 430 --y4m -o output.hevc

...while in StaxRip (no matter if I use 1.7.0.6 or 2.0.0.2) it would crash with the same settings. (No matter what video file I try - long ones, short ones - the encoding will always crash after it has finished).
https://i.imgur.com/thOtxVT.png

This means:
In order to use a newer x265 version together with zones, you have to do the mkv merging yourself after the encoding finished (and crashed).


@Stax, Revan:
Would you mind investigating this issue if you find the time?
I failed in isolating whether this is an x265 or StaxRip related issue.

[-QfG-]

Here is my problem, I have 2 rip bluray 2160p and the problem is that it must miss some info.

The Guy who ripped the UHDs has forgot to set the HDR10+ Metadates with x265. The following Commandline must be set by encoding:

--hdr-opt --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --range limited --bframes 4 --hrd --max-cll "1000,400" --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)"

[stax76]

I can't reproduce the problem when encoding via command line.

The error exit code is there, you are just not checking for it.

[Natty]

plugin update
https://forum.doom9.org/showthread.php?p=1875869#post1875869

[stax76]

Hey everyone, I've uploaded a new built with a few updates and minor improvements.

https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0
https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

2.0.2.2

new icons added and credits in about (info) dialog updated,
thanks to: Freepik, ilko-k, nulledone, vanontom
the progress bar in the processing window has better contrast
video encoding with ffmpeg shows now progress in the progress bar and task bar
if in the codec dialogs search field the enter key is pressed in order to cycle
there is no longer an annoying sound made
encoding was failing when a ambersand (&) character was used in the path
new AV1 codec option added to ffmpeg encoder
various improvements and fixes made in the ffmpeg encoder
new vceenc switches added
new nvencc switches added
new x265 switches added
update: x265, Wolfberry build with avs input support,
in the x265 options: Other > Piping Tool > None
update: mpvnet
update: ffmpeg, Wolfberry build with vpy input support
update: nvencc, untested
update: qsvencc, untested
update: vceencc, untested

[katzenjoghurt]

The error exit code is there, you are just not checking for it.

Thanks for your reply, Stax!
Hm. Is there any way I COULD check for it from command line?

[stax76]

Thanks for your reply, Stax!
Hm. Is there any way I COULD check for it from command line?

Thanks for the feedback! I've reported the issue here:

https://forum.doom9.org/showthread.php?p=1875863#post1875863

It shows how to check for it in Windows batch:

echo %ERRORLEVEL%

I don't know if there are other ways, I've never learned windows batch because I always thought it's a very bad language.

In PowerShell I do it like this:

function CheckExitCode {
if ($LastExitCode -gt 0) {
Write-Host "`nExit code $LastExitCode was returned.`n" -ForegroundColor Red
exit
}
}

I've never verified that the code actually works, I hope it does, it's from a script I use to release mpv.net.

[vanden]

The Guy who ripped the UHDs has forgot to set the HDR10+ Metadates with x265. The following Commandline must be set by encoding:

Strange on the blade nfo I have:
Default: Yes
Forced: No
Color range: Limited
Color primaries: BT.2020
Transfer characteristics: PQ
Matrix coefficients: BT.2020 non-constant
Mastering display color primaries: R: x = 0.680000 y = 0.320000, G: x = 0.265000 y = 0.690000, B: x = 0.150000 y = 0.060000, White point: x = 0.312700 y = 0.329000
Mastering display luminance: min: 0.0050 cd / m2, max: 4000.0000 cd / m2
Maximum Content Light Level: 457 cd / m2
Maximum Frame-Average Light Level: 179 cd / m2

and on selui de Sully I have:
Default: Yes
Forced: No
Color range: Limited
Coordinates of chromaticity? BT.2020
Characteristics of the transfer: PQ
Matrix coefficients: BT.2020 non-constant
MasteringDisplay_ColorPrimaries: R: x = 0.680000 y = 0.320000, G: x = 0.265000 y = 0.690000, B: x = 0.150000 y = 0.060000, White point: x = 0.312700 y = 0.329000
MasteringDisplay_Luminance: min: 0.0050 cd / m2, max: 4000.0000 cd / m2
MaxCLL: 4000 cd / m2
MaxFALL: 290 cd / m2

The following Commandline must be set by encoding : Not possible to send after encoding (without all re-encode) ?

[katzenjoghurt]

Thanks for the feedback! I've reported the issue here:

[...]

In PowerShell I do it like this:
[...]



Ahh... good stuff.
I swear to god I googled through several pages and didn't find anything.

And thanks for reporting. That was exactly what I had in mind to do. :)

I already upvoted an existing issue (https://bitbucket.org/multicoreware/x265/issues/490/x265-crash-when-using-zone) in gitlab weeks ago but as nothing happened I planned to make them aware in the forum too. I just failed to reproduce it via command line.

Thanks so much, Stax!!
I hope they see it and sort it out now.

[Natty]

It cannot be 32bit because it would not work.

https://i.imgur.com/gp5D9a1.png

[Natty]

Hey everyone, I've uploaded a new built with a few updates and minor improvements.


thanks. everything is working fine. :thanks:

[stax76]

@Natty

Yes it was 32bit, I've deleted it, needi3 loads from plugins_JPSDR.dll.

[Taurus]

In case sombody is looking for a 64bit nnedi3....
jpsdr released a new package just the other day.
Look here:
https://forum.doom9.org/showthread.php?p=1662264#post1662264

[vanden]

I'm trying to encode a movie in x265 HDR.
I can do it with ffms2 (Rename) :
LoadPlugin("C:\StaxRip-x64-2.0.2.2-test\Apps\Plugins\avs\ffms2\ffms2.dll")
FFVideoSource("C:\NEW\Billy.Lynns.Long.Halftime.Walk.2016.hevc", colorspace = "YV12", \
cachefile = "C:\NEW\Billy.Lynns.Long.Halftime.Walk.2016_temp\Billy.Lynns.Long.Halftime.Walk.2016.ffindex")
By :
LoadPlugin("C:\StaxRip-x64-2.0.2.2-test\Apps\Plugins\avs\ffms2\ffms2.dll")
FFVideoSource("C:\NEW\Billy.Lynns.Long.Halftime.Walk.2016.hevc", cachefile = "C:\NEW\Billy.Lynns.Long.Halftime.Walk.2016_temp\Billy.Lynns.Long.Halftime.Walk.2016.ffindex")
10bit encoding.


On the other hand in LWLibavVideoSource I have this :
LoadPlugin ( "C: \ StaxRip-x64-2.0.2.2-test \ apps \ Plugins \ avs \ L-SMASH-Works \ LSMASHSource.dll")
LWLibavVideoSource ("C: \ NEW \ Billy.Lynns.Long.Halftime.Walk.2016.hevc", format = "YUV420P8")
What can I do to encode it in 10bit ?
avs2pipemod[info]: writing 405600 frames of 60000/1001 fps, 3840x2160,
sar 0:0, YUV-420-planar-8bit progressive video.
y4m [info]: 3840x2160 fps 60000/1001 i420p8 unknown frame count
raw [info]: output file: NUL
x265 [info]: HEVC encoder version 3.0+2-b4b1d84566d7
x265 [info]: build info [Windows][GCC 9.1.1][64 bit] 10bit

update: x265, wolfberry build with avs input support,
in the x265 options: Other> Piping Tool> None
I put Nome here I guess ?
I have an error message :
https://nsa40.casimages.com/img/2019/06/07/mini_190607104449201087.jpg (https://www.casimages.com/i/190607104449201087.jpg.html)
and also that :
lavf [info]:
Format : avisynth
Codec : rawvideo ( raw video )
PixFmt : yuv420p
Framerate : 60000/1001
Timebase : 1001/60000
Duration : 1:52:46
lavf [info]: 3840x2160 fps 60000/1001 i420p8 frames 0 - 405599 of 405600
raw [info]: output file: NUL
x265 [info]: HEVC encoder version 3.0+2-b4b1d84566d7
x265 [info]: build info [Windows][GCC 9.1.1][64 bit] 10bit

And last question, to make downscaling video (1920x1080) what is the best Resize ?

[Natty]

use avs2pipemod as piping tool

in ffms remove colorspace = "YV12" to let it decide source bitdepth automatically

same lmash or any other, remove format = "YUV420P8"

try lanczos4 (sharp) or blackman (Well balanced)

nothing is best

[stax76]

@vanden

l-smash outputs a double width format that was designed before avisynth had native high bit depth support, you can revert it like this:

LWLibavVideoSource("%source_file%")
ConvertFromDoubleWidth(bits=10)

With wolfberry's x265 built you don't need a piping tool.

Unfortunately I cannot reproduce the exception.

[vanden]

1a. x265, wolfberry build with avs input support,
in the x265 options: Other> Piping Tool> None
I have an error message :
https://nsa40.casimages.com/img/2019/06/07/mini_190607104449201087.jpg (https://www.casimages.com/i/190607104449201087.jpg.html)
I can do it with ffms2 whit Rename :
LoadPlugin("C:\StaxRip-x64-2.0.2.2-test\Apps\Plugins\avs\ffms2\ffms2.dll")
FFVideoSource("C:\NEW\Billy.Lynns.Long.Halftime.Walk.2016.hevc", cachefile = "C:\NEW\Billy.Lynns.Long.Halftime.Walk.2016_temp\Billy.Lynns.Long.Halftime.Walk.2016.ffindex")
10bit encoding :
https://nsa40.casimages.com/img/2019/06/08/mini_190608060439527724.jpg (https://www.casimages.com/i/190608060439527724.jpg.html)



1b. In the x265 options: Other> Piping Tool> Automatic, I can do it with ffms2 whit Rename :
LoadPlugin("C:\StaxRip-x64-2.0.2.2-test\Apps\Plugins\avs\ffms2\ffms2.dll")
FFVideoSource("C:\NEW\Billy.Lynns.Long.Halftime.Walk.2016.hevc", cachefile = "C:\NEW\Billy.Lynns.Long.Halftime.Walk.2016_temp\Billy.Lynns.Long.Halftime.Walk.2016.ffindex")
10bit encoding :
https://nsa40.casimages.com/img/2019/06/08/mini_190608060436942490.jpg (https://www.casimages.com/i/190608060436942490.jpg.html)



2a. x265, wolfberry build with avs input support,
in the x265 options: Other> Piping Tool> None
I have an error message :
https://nsa40.casimages.com/img/2019/06/07/mini_190607104449201087.jpg (https://www.casimages.com/i/190607104449201087.jpg.html)
I can do it with LWLibavVideoSource whit Rename (the rename is very difficult to do, StaxRip renames it several times) :
LoadPlugin("C:\StaxRip-x64-2.0.2.2-test\Apps\Plugins\avs\L-SMASH-Works\LSMASHSource.dll")
LWLibavVideoSource("C:\Billy\Billy.Lynns.Long.Halftime.Walk.hevc")
ConvertFromDoubleWidth(bits=10)
10bit encoding :
https://nsa40.casimages.com/img/2019/06/08/mini_190608060434539941.jpg (https://www.casimages.com/i/190608060434539941.jpg.html)



2b. In the x265 options: Other> Piping Tool> Automatic, I can do it with LWLibavVideoSource whit Rename (the rename is very difficult to do, StaxRip renames it several times) :
LoadPlugin("C:\StaxRip-x64-2.0.2.2-test\Apps\Plugins\avs\L-SMASH-Works\LSMASHSource.dll")
LWLibavVideoSource("C:\Billy\Billy.Lynns.Long.Halftime.Walk.hevc")
ConvertFromDoubleWidth(bits=10)
10bit encoding :
https://nsa40.casimages.com/img/2019/06/08/mini_190608060427774398.jpg (https://www.casimages.com/i/190608060427774398.jpg.html)



What is the best method ?
the x265 options: Other> Piping Tool> None + LWLibavVideoSource ?

[stax76]

@vanden

2.0.2.3 fixes the exception.

What is the best method?

Post a full log file on pastebin.com and with a little luck some people will take a look and tell you if something is wrong or can be improved.

[vanden]

Thanks, 2.0.2.3 fixes the exception.

[Vulpix]

I've not really had much success with Staxrip 2.0. I tried the latest (2.0.0.25 ?) by getting the latest compiled full release, and dropping the pipeline build into it, but both the original as well as the final version crash for me.

Demux is fine, indexing is fine but then the staxrip window disappears and I can only see it as a process. I can see it goes through the entirety of the source file once, then goes through some of its parts once and then it crashes (with a windows crash message rather than a staxrip one).

Staxrip 1.x works fine but the gui is missing some switches.

The source is an UHD mkv file.

[stax76]

@Vulpix

The latest test build is 2.0.2.3.

https://staxrip.readthedocs.io/intro.html#download

[Revan654]

I've not really had much success with Staxrip 2.0. I tried the latest (2.0.0.25 ?) by getting the latest compiled full release, and dropping the pipeline build into it, but both the original as well as the final version crash for me.

Demux is fine, indexing is fine but then the staxrip window disappears and I can only see it as a process. I can see it goes through the entirety of the source file once, then goes through some of its parts once and then it crashes (with a windows crash message rather than a staxrip one).

Staxrip 1.x works fine but the gui is missing some switches.

The source is an UHD mkv file.

You can add new Menu items to StaxRip if you wish, Buttons can't be added by the user.

It's likely ffmpeg being the root problem(Shocking :sly: ). ffmpeg doesn't get along with many audio types. It's more noticeable with HLG content.

[Forteen88]

Why isn't TemporalDegrain2 integrated into StaxRip? Isn't it the most used and recommended degrainer?

EDIT: Thanks stax76!

[stax76]

Why isn't TemporalDegrain2 integrated into StaxRip? Isn't it the most used and recommended degrainer?

I hope it can be included in the next build.

https://github.com/staxrip/staxrip/issues/7

Meanwhile, it can be integrated manually:

https://github.com/staxrip/staxrip/issues/2#issuecomment-501064185

[jlw_4049]

Latest (stable)build has been super stable/quick for me so far.

[stax76]

Latest (stable)build has been super stable/quick for me so far.

Thanks for the positive feedback! :thanks:

[jlw_4049]

Thanks for the positive feedback! :thanks:

No problem. This is the only GUI that properly does HDR encoding. Awesome program!


Question. How do I select the subtitles (specifically to not burn in forced subs by default) when encoding? I like to do all my muxing with mkvtoolnix.

Or for instance if I wanted English and Spanish subs from the source file, where would I choose that? I can't seem to find it. Unless I choose when I'm demuxing the source?

Thanks for the responses.

EDIT: I'm about 90% sure I got it figured out mostly. Will post back when I get the chance. Looks like you select what ever subs you want to be encoded in when the demux menu pops up.

I however still can't find the option to disable automatic burn in?

[Vulpix]

@Vulpix

The latest test build is 2.0.2.3.

https://staxrip.readthedocs.io/intro.html#download

Oh, that explains a few things. I was getting it from here: https://github.com/Revan654/staxrip !

I've tried this 2.0.2.3 version and everything works again, yaay :D

:thanks:

[NikosD]

FYI

QSVEnc v3.21
NVEnc v4.42

For your next build.

[stax76]

FYI

QSVEnc v3.21
NVEnc v4.42

For your next build.

Are these available as binary or only as source code? I'm too stupid to compile C++ code. ;)

[Zetti]

NVEnc v4.42: https://github.com/rigaya/NVEnc/releases
QSVEnc v3.21: https://github.com/rigaya/QSVEnc/releases

[NikosD]

I have never seen rigaya posting the source code only.

He always releases binaries too.

[mcjordan]

Source code ->
https://github.com/rigaya/NVEnc/releases/tag/4.42
https://github.com/rigaya/QSVEnc/releases/tag/3.21

[Andy]

Hello, today I updated windows to version 1903 and since then I have a problem with KNLMeansCL. I also use QTGMC as a very good denoiser and now it doesn't work. Nothing but update I did.
The KNLMeansCL.dll in the folder is and the path in the script is also correct. Don't know where the problem is? Thank you.

[Natty]

install gpu drivers

install c++ pack maybe from here
https://github.com/abbodi1406/vcredist/releases

if it still doesn't work, delete this file staxrip/apps/plugins/knlmeans/knlmeans.dll

[stax76]

Hello, today I updated windows to version 1903 and since then I have a problem with KNLMeansCL. I also use QTGMC as a very good denoiser and now it doesn't work. Nothing but update I did.
The KNLMeansCL.dll in the folder is and the path in the script is also correct. Don't know where the problem is? Thank you.

I'm also on 1903 and QTGMC and KNLMeansCL are still working here.

Card: GT 1030
Driver: 26.21.14.3064

[Andy]

if it still doesn't work, delete this file staxrip/apps/plugins/knlmeans/knlmeans.dll

This worked, but without KNLMeans it didn't seem good to me. I made a copy of the disk before the update, so I returned to the original version of 1809. There everything worked again. I tried updating again and again wrong.
Then I thought it might cause an old gpu driver - I had 399.24, I got an Asus Strix 1080Ti. After installing the latest version of 430.86 KNLMeans works as before.
Thank you both for your advice! :D

[MrBrownCow]

Really hope I'm asking in the right place. Sorry if this isn't the spot, please just tell me where to go.

I wanted to ask if anyone can verify I did this right before spending weeks or months doing this wrong. Is it possible to look at my sample and log to make sure I encoded this 1080p copy from a 4K source correctly and that the HDR info was converted to SDR correctly? This is just one chapter from the movie and I ran tests for that last 24 hours using different filters because I wanted a light degrain and I didn't have much experience with filters. I made 12 different copies each with different filters but I think this one might be the one I like best.

Did HDR convert correctly?
Does anyone recommend a different filter than KNLMeansCL Medium?

StaxRip : 2.0.2.3
Windows : Windows 10 Pro 1903

104 MB chapter 1 file here: https://www58.zippyshare.com/v/pTNgOOPo/file.html
Log file: https://www70.zippyshare.com/v/6n2NkxGO/file.html
MediaInfo from result:https://www31.zippyshare.com/v/I5VsTDT5/file.html

[Atak_Snajpera]

I wanted to ask if anyone can verify I did this right before spending weeks or months doing this wrong. Is it possible to look at my sample and log to make sure I encoded this 1080p copy from a 4K source correctly and that the HDR info was converted to SDR correctly?
Looks like HDR is still there

Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : R: x=0.708000 y=0.292000, G: x=0.170000 y=0.797000, B: x=0.131000 y=0.046000, White point: x=0.312700 y=0.329000
Mastering display luminance : min: 0.0001 cd/m2, max: 1000.0000 cd/m2
Maximum Content Light Level : 992 cd/m2
Maximum Frame-Average Light Level : 518 cd/m2

[videoh]

Does anyone recommend a different filter than KNLMeansCL Medium? if you have an nVidia graphics card there is DGDenoise (part of DGDecNV). It is a CUDA implementation of NL means denoising.

You can also use DGHDRtoSDR() for your HDR->SDR work.

[MrBrownCow]

if you have an nVidia graphics card there is DGDenoise (part of DGDecNV). It is a CUDA implementation of NL means denoising.

You can also use DGHDRtoSDR() for your HDR->SDR work.

Thank you both. It looks like I'm making a 1080p HDR copy which might not be what I want.

I don't see DGDecNV as an option so I assume its something I have to download and add? Is it downloaded from here?
http://rationalqm.us/dgdecnv/dgdecnv.html

[videoh]

That's correct for DGDecNV and DGDenoise. For DGHDRtoSDR go here:

http://rationalqm.us/hdr/

DGDecNV requires a donation. DGHDRtoSDR is freeware. If you use the latter stand-alone then you will need a source filter that delivers high bit depth. DGSource() is the natural choice (part of DGDecNV). ;)

[MrBrownCow]

That's correct for DGDecNV and DGDenoise. For DGHDRtoSDR go here:

http://rationalqm.us/hdr/

DGDecNV requires a donation. DGHDRtoSDR is freeware. If you use the latter stand-alone then you will need a source filter that delivers high bit depth. DGSource() is the natural choice (part of DGDecNV). ;)

I got both downloaded and think I set DGDecNV correctly in the apps section so it says OK for the status but I still don't see DGDenoise as an option in the filters. Not sure how to load the DGHDRtoSDR dll either....

GPU is GTX1060

[videoh]

StaxRip guys will have to help you with that.

[stax76]

@MrBrownCow

The filter menu can be customized by selecting 'Profiles' in the menu, the format is INI/TOML like, you would add something like this:


[Noise]

DGDenoise = DGDenoise()


Following uses a sub/cascading menu and multi line code that loads a plugin DLL:


[Filter category]

Filter name | sub menu =
LoadPlugin("DLL path")
Filter()

[MrBrownCow]

@MrBrownCow

The filter menu can be customized by selecting 'Profiles' in the menu, the format is INI/TOML like, you would add something like this:


[Noise]

DGDenoise = DGDenoise()


Following uses a sub/cascading menu and multi line code that loads a plugin DLL:


[Filter category]

Filter name | sub menu =
LoadPlugin("DLL path")
Filter()



Thank you stax76. I added the following under the [Noise] section but I'm not sure if I did this right.


[Noise]
DGHDRtoSDR | sub menu =
LoadPlugin("C:\StaxRip-x64-2.0.2.3-test\Apps\DGHDRtoSDR_1.12\DGHDRtoSDR.dll")
DGDHDRtoSDR()

DGDenoise = DGDenoise()

[Atlantis]

I have a question about resize.

My video is 4K 3840 x 2160.
I want to resize to normal HD 1920 x 1080.

When I slide the Staxrip resize bar to left, it can go to 1924 x 1084 and not 1920 x 1080. Why? My Output Mod is set to 4.

[stax76]

Either use the arrow keys or the menu. :)

[Atlantis]

The arrow keys do not work, at least in staxrip 2.0.2.0.

What do you mean use the menu? Do you mean change it by hand in the boxes? In that case it does not respect the aspect ratio. If you change one number by hand, the other does not change accordingly.

Also the resize target is not always 1920 x 1080. Sometimes it's some other aspect ratio and you can't currently resize by slider or hand correctly in staxrip user interface.

Something is broken in staxrip user interface for resizing.

[stax76]

The menu shows when you click on the resize group box header, when you mouse hover over text and the text gets bold then this is an indication that there is a menu.

What will also work is click on the slider to give the slider focus and then use the left right keys.

I don't know what else can be done to make it more intuitive.

[Atlantis]

Thank you very much. I found the menu when it gets bolder and was able to choose 1920 x auto. That's good enough for me.

One last thing, how to crop visually? I want to crop after resize and not before. When I click on the crop menu on the top, the preview shows the original 4K resolution to crop.
Even when I move down the Crop in the AVS Filters menu under Resize, the crop menu shows the original 4K image and not the resized 1080p.

How can I crop visually the resized video in Staxrip?

Update: The arrows work! Because it is 4K it takes a long time, that's why I didn't notice. When I hit left on the resize bar, I have to wait 8-9 secs for it to go one step.

[stax76]

One last thing, how to crop visually? I want to crop after resize and not before.

The crop dialog uses the source filter as source because it's usually best to crop after the source filter.

Nobody ever requested to change it to use all filters before/until crop instead, it should be considered to change this I guess.

[Atlantis]

I was thinking because depending of what output mod you have 4 or 8 or 16, it makes more sense to crop after resize to achieve your output mod.

After the resize you can crop less and keep some black lines to match your output mod. Before resizing you don't know how much to crop.

[stax76]

Maybe create an issue on the tracker, there is a chance that at some time somebody likes to implement this.

[Natty]

you can drag and drop crop filter to be after resize filter

[K.i.N.G]

Since a yuv420 source only has half resolution for the chroma information, how would one resize a 4K yuv420 source to 2K yuv444 in a way that it only resizes the luma and keeps the resolution of the chroma?
Would it work if i just convert the yuv420 to yuv444 before resizing?

[StainlessS]

@K.i.N.G
Assuming that StaxRip uses avisynth (think it does), then maybe below of use


Colorbars(pixel_type="YV12")
ConvertBits(10)
###
U=UtoY
V=VtoY
Y=Spline36Resize(Width /2,Height/2).ConvertToYUV444 # convertToY/Y8 is currently broken [EDIT: for non 8 bit]:- https://forum.doom9.org/showthread.php?p=1877985#post1877985
YtoUV(U,V,Y)
info

Mainly pointing out the problem with convertToY/Y8, and a way around the problem.

EDIT: Not sure if technically correct to just re-use raw UV without some kind of chroma shift for YUV444, maybe post in Avisynth usage to find out.

[Revan654]

Not sure what magic has happened from 3.0 to 3.1. But Encoding has doubled, My speed went from 20fps to 40fps on my last encoding.

----

Also The Pipeline has tweaked a bit, Anytime a new Build Number is Pushed in the Source code it will also build a new version.

[Revan654]

Staxrip 2.0.2.4



Tweaked the VUI Code, If video you import video has Metadata for ColorSpace.
It Will AutoSelect the proper values.
Slight Tweak to HDR VUI as well.
Updated x265 & Nvencc Encoder Settings.
x265 will now Targets 3.1.
Tweaked the VS startup filters.
Included Two versions of exe file, One targets 4.7.2 framework and other
targets the newer 4.8 framework.
Updated FFMpeg, NVEnc, QSVEnc, x265, MKVTool, MTN and few other Files.



Link: https://ci.appveyor.com/project/Revan654/staxrip
Link: https://github.com/Revan654/staxrip/releases/tag/2.0.2.4
Link: https://github.com/staxrip/staxrip/releases/tag/2.0.2.4

Some Small Tweaks and Fixed the VUI Import Function for Non-HDR Content(If the Video you Import has ColorSpace Metadata). It will apply the VUI automatically(Only x265 / x264 Was Tested).

[Natty]

thanks revan, i will test it tomorrow

[MrBrownCow]

I'm still trying to get the DGHDRtoSDR dll installed. I made some progress when I saw on another forum thread that you need to put the dll in the AviSynth+ directory. I think I have that loaded now but still get the below error. Can anyone tell me what I might be missing here?

Error: "Script error: the named argument "tm" to DGHDRtoSDR had the wrong type"
https://imgur.com/a/ljCkc6Y

Profile change:
https://imgur.com/a/v496oNf


AVSMeter 2.9.0 (x64) - Copyright (c) 2012-2019, Groucho2004

VersionString: AviSynth+ 0.1 (r2772, MT, x86_64)
VersionNumber: 2.60
File / Product version: 0.1.0.0 / 0.1.0.0
Interface Version: 5
Multi-threading support: Yes
Avisynth.dll location: C:\WINDOWS\SYSTEM32\avisynth.dll
Avisynth.dll time stamp: 2018-12-20, 20:55:16 (UTC)
PluginDir2_5 (HKLM, x64): C:\Program Files (x86)\AviSynth+\plugins64
PluginDir+ (HKLM, x64): C:\Program Files (x86)\AviSynth+\plugins64+


[CPP 2.6 Plugins (64 Bit)]
C:\Program Files (x86)\AviSynth+\plugins64+\ConvertStacked.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64+\DGHDRtoSDR.dll [1.0.0.12]
C:\Program Files (x86)\AviSynth+\plugins64+\DirectShowSource.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64+\ImageSeq.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64+\Shibatch.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64+\TimeStretch.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64+\VDubFilter.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64\DGHDRtoSDR.dll [1.0.0.12]

[Scripts (AVSI)]
C:\Program Files (x86)\AviSynth+\plugins64+\colors_rgb.avsi [2016-07-05]

[Uncategorized files]
C:\Program Files (x86)\AviSynth+\plugins64+\colors_rgb.txt [2016-07-05]

[stax76]

@MrBrownCow

Try changing

tm="gamma"

to

tm=1.0

When you use quotes then AviSynth creates a string type but the filter expects the tm parameter to be of type float.

from the filter docs:

tm=1.0 Strength of tonemapping. Reduce this towards 0.0 to smoothly transition
to blowout (clipping) of highlights. This value controls a LERP between Reinhard
tonemapping and no tonemapping. Default is 1.0.

[videoh]

tm is now a float. Somebody or something is generating parameters for an earlier verion of DGHDRtoSDR.

BTW, you should obscure your download names to avoid running afoul of forum rule 6.

[MrBrownCow]

@MrBrownCow

Try changing

tm="gamma"

to

tm=1.0

When you use quotes then AviSynth creates a string type but the filter expects the tm parameter to be of type float.

from the filter docs:


Thank you. I was just looking at the txt file associated to DGHDRtoSDR and saw some of the default settings. I changed it to this:


HDRtoSDR = DGHDRtoSDR(impl="255",tm=1.0,light=300,gamma=0.42,fulldepth=true,r=1.0,g=1.0,b=1.15)


then restarted staxrip, tried again and i get this script error now:

DGHDRtoSDR: input must be CS_YUV420P16

[MrBrownCow]

tm is now a float. Somebody or something is generating parameters for an earlier verion of DGHDRtoSDR.

BTW, you should obscure your download names to avoid running afoul of forum rule 6.

Thank you, updated my post to hopefully comply with rule 6

[stax76]

@MrBrownCow

To make it a little easier for us better post the full script as text and obscure the file path if necessary.

[MrBrownCow]

@MrBrownCow

To make it a little easier for us better post the full script as text and obscure the file path if necessary.

I only had this in the profile section:


[Misc]
Histogram = Histogram("levels", Bits=$select:msg:Select BitDepth;8;10;12$)
MTMode | Prefetch = Prefetch($enter_text:Enter the Number of Threads to Use$)
MTMode | Set Max Memory = SetMemoryMax($enter_text:Enter the Maximum Memory Avisynth Can use$)
MTMode | Set Threads = threads=$enter_text:Enter The Number of Threads to Use$
MTMode | SetMTMode Filter = SetFilterMTMode("$enter_text:Enter The FilterName$",$enter_text:Enter Mode You Wish to Use$)
SplitVertical = Splitvertical=True
HDRtoSDR = DGHDRtoSDR(impl="255",tm=1.0,fulldepth=true,light=300,gamma=0.42,r=1.0,g=1.0,b=1.15)


I dont have any script yet so I guess thats my issue. Looking at the DGHDRtoSDR_1.12.txt document it gives some sample scripts but I dont have too much experience with this. Do I need to make a powershell script with this info somehow for this to work?

[stax76]

You can choose 'Preview Code' in the filters menu to get the full avs/vs script.

[MrBrownCow]

You can choose 'Preview Code' in the filters menu to get the full avs/vs script.


LoadPlugin("C:\StaxRip-x64-2.0.2.3-test\Apps\Plugins\avs\ffms2\ffms2.dll")
FFVideoSource("C:\The Matrix 2160p.mkv", colorspace = "YV12", \
cachefile = "C:\The Matrix 2160p_temp\The Matrix 2160p.ffindex")
DGHDRtoSDR(impl="255",tm=1.0,fulldepth=true,light=300,gamma=0.42,r=1.0,g=1.0,b=1.15)


I'm guessing I need to refrence the other dll files somehow like the example notes?


Here is a typical Avisynth+ script using default parameters:

loadplugin("dgdecodenv.dll")
loadplugin("dghdrtosdr.dll")
DGSource("hdr_sample.dgi",fulldepth=true)
DGHDRtoSDR()
prefetch(6)

[stax76]

DGHDRtoSDR: input must be CS_YUV420P16

I think you need some format conversion, I don't remember it because I gave up encoding, ConvertBits() maybe.

http://avisynth.nl/index.php/ConvertBits

[videoh]

Thank you for the guidance, stax76!

MrBrownCow, your source filter must deliver high bit depth (i.e., greater than 8-bit; most HDR is 10-bit). DGSource() does that when fulldepth=true. If you have another source filter delivering high bit depth it may be necessary to convert its output to YUV420P16 using an Avisynth conversion function (e.g., if the source filter delivers 10-bit).

For FFVideoSource you definitely do not want colorspace = "YV12", because that is only 8-bit.

[MrBrownCow]

Thank you for the guidance, stax76!

MrBrownCow, your source filter must deliver high bit depth (i.e., greater than 8-bit; most HDR is 10-bit). DGSource() does that when fulldepth=true. If you have another source filter delivering high bit depth it may be necessary to convert its output to YUV420P16 using an Avisynth conversion function (e.g., if the source filter delivers 10-bit).

For FFVideoSource you definitely do not want colorspace = "YV12", because that is only 8-bit.

Tried a few things here but still get the same error. I updated to staxrip 2.0.2.4, moved over all the dll files and made sure they say OK in the apps section, changed my source to DGSource and then tried adding HDRtoSDR again but it still says "DGHDRtoSDR: input must be CS_YUV420P16"


LoadPlugin("C:\Staxrip.2.0.2.4.x64\Apps\dgdecnv2053\DGDecodeNV.dll")
DGSource("C:\The Matrix 2160p_temp\The Matrix 2160p.dgi")
DGHDRtoSDR(impl="255",tm=1.0,fulldepth=true,light=300,gamma=0.42,r=1.0,g=1.0,b=1.15)


Error:
https://imgur.com/a/tqpbMLS

[stax76]

@MrBrownCow

To copy the error to the clipboard you can click on the preview which shows an error message box that has a copy button.

I think fulldepth is a parameter in DGSource.

[MrBrownCow]

@MrBrownCow

To copy the error to the clipboard you can click on the preview which shows an error message box that has a copy button.

I think fulldepth is a parameter in DGSource.

Looks like it just says the same thing, not much more detail. You want me to try adding something to the profile section?

DGHDRtoSDR: input must be CS_YUV420P16
(C:\Movies\The Matrix 2160p_temp\The Matrix 2160p.avs, line 4)

[stax76]

I think you have to move the fulldepth parameter.

DGSource("C:\The Matrix 2160p_temp\The Matrix 2160p.dgi", fulldepth=true)
DGHDRtoSDR(impl="255",tm=1.0,fulldepth=true,light=300,gamma=0.42,r=1.0,g=1.0,b=1.15)

[videoh]

Quite right, stax76. Thanks!

[MrBrownCow]

I think you have to move the fulldepth parameter.

DGSource("C:\The Matrix 2160p_temp\The Matrix 2160p.dgi", fulldepth=true)
DGHDRtoSDR(impl="255",tm=1.0,fulldepth=true,light=300,gamma=0.42,r=1.0,g=1.0,b=1.15)

Whoa, that might have done it. I changed it and reloaded staxrip, this time no error.


LoadPlugin("C:\Staxrip.2.0.2.4.x64\Apps\dgdecnv2053\DGDecodeNV.dll")
DGSource("C:\Movies\The_Matrix_2160p_temp\The_Matrix_2160p.dgi", fulldepth=true)
DGDenoise()
DGHDRtoSDR(impl="255",tm=1.0,light=300,gamma=0.42,r=1.0,g=1.0,b=1.15)


I dont need to have the fulldepth=true in both spots do I?

TY!

[videoh]

I dont need to have the fulldepth=true in both spots do I? Did you read the document?

If you want DGHDRtoSDR to output 8 bit (YV12) then omit fulldepth or include fulldepth=false. If you want YUV420P16 output then include fulldepth=true. DGSource must always have fulldepth=true when using DGHDRtoSDR after it.

[mparade]

How are DTS X, Dolby Atmos, and E-AC3 formats being handled in StaxRip? I want to reencode them to some lossy format while keeping most of the quality.
Thanks for any help.

[stax76]

Just try it and if it's not working or anything is unclear then post a full log file on pastebin.

[Revan654]

If @Videoh is reading this. There seems to be a small issue with DGIndexNV(Can't really Upload the Sample). I can Post the metadata if needed. It's not parse some mp4 formats. I believe it was mp42 format(id MediaiInfo Lists). The video was not mine, It was Encoded by HandBrake(aka ffmpeg). It would not open the file. My mp4 created files seem to fine.

[videoh]

Without a sample what can I do?

[Revan654]

Without a sample what can I do?

Not sure you can do anything, I was more looking for if you knew if the tool has support for mp42?

If it helps I can pull out the Encoding Settings from the Metadata.

Here:

cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=9 / psy_rd=1.0:1.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / chroma_qp_offset=-4 / threads=12 / nr=150 / decimate=1 / mbaff=0 / bframes=6 / b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=3 / wpredb=1 / keyint=30 / keyint_min=16 / scenecut=40(pre) / rc=abr / bitrate=3872 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / ip_ratio=1.40 / pb_ratio=1.30 / aq=1:1.00

Codec ID: avc1
AVC Form: avcC
x264 Core 65.
Framerate: VFR (This could where the issue is at. Not sure why VFR Exists in lower resolutions.)

[Atlantis]

I hope the speed increase you talked about is right. I just spent 30 hours for just one file.

So how to install 2.0.2.4? First I don't understand the two version framework 4.7 and 4.8. It's what framework? Should we extract the content of the 4.8 and put it in the root? It's with 4.8 that you see double speed increase?

[frenchfries]

I hope the speed increase you talked about is right. I just spent 30 hours for just one file.

So how to install 2.0.2.4? First I don't understand the two version framework 4.7 and 4.8. It's what framework? Should we extract the content of the 4.8 and put it in the root? It's with 4.8 that you see double speed increase?

.NET framework

Install the version you want and then download the 2.0.2.4 version of staxrip.

[Andy]

Win10 version 1903 has a Framework of 4.8.

[Atlantis]

I have Win10 1903 and Framework 4.8. I installed StaxRip 2.0.2.4 4.8 and here are my findings.

First it didn't work. The system cannot find the file specified File: ffmsindex.exe. In the log the command is ffmsindex.exe Z:\New\test.mkv Z:\New\test_temp\test.ffindex. It does not have the absolute path. After solving that I found these results.

x265 1080p SDR encoding is faster.
x265 2160p HDR encoding is slower.

I give more details in a post below.

[Atlantis]

I used the same files for each resolution.

1920 x 1080 - SDR - CRF-22

StaxRip 2.0.2.0 - (18.33 fps), 1835.77 kb/s
StaxRip 2.0.2.4 - (22.74 fps), 1737.10 kb/s

3840x2160 - HDR - CRF-23

StaxRip 2.0.2.0 - (1.80 fps), 45412.83 kb/s
StaxRip 2.0.2.4 - (1.72 fps), 44538.53 kb/s

In both cases the file size is a little smaller.
In the second case I don't understand why it is slower when the first case is faster.
I don't know if it's because it's 4K or HDR and how come that 1080P SDR is faster.

[frenchfries]

I used the same files for each resolution.

1920 x 1080 - SDR - CRF-22

StaxRip 2.0.2.0 - (18.33 fps), 1835.77 kb/s
StaxRip 2.0.2.4 - (22.74 fps), 1737.10 kb/s

3840x2160 - HDR - CRF-23

StaxRip 2.0.2.0 - (1.80 fps), 45412.83 kb/s
StaxRip 2.0.2.4 - (1.72 fps), 44538.53 kb/s

In both cases the file size is a little smaller.
In the second case I don't understand why it is slower when the first case is faster.
I don't know if it's because it's 4K or HDR and how come that 1080P SDR is faster.

4% is well within a normal error margin, particularly given that I doubt you tested very scientifically, ie. controlling all of the other variables such as services running etc.

[chipxtreme]

I have Win10 1903 and Framework 4.8. I installed StaxRip 2.0.2.4 4.8 and here are my findings.

First it didn't work. The system cannot find the file specified File: ffmsindex.exe. In the log the command is ffmsindex.exe Z:\New\test.mkv Z:\New\test_temp\test.ffindex. It does not have the absolute path. After solving that I found these results.

How did you fix this, I haven't been able to use new version for same reason.

[Atlantis]

go to Apps->Manage->AviSynth->ffms2.

It says app not found. Hit F11 and browse to
...StaxRip\Apps\Plugins\Both\FFMS2

[Ruriko]

How do I add a watermark logo in batch mode?

[AMED]

Something very minor I found using dotnet 4.8 build of v2.0.2.4 (Revan654).

When i have minimize processing dialog to tray enabled in the settings and then minimise StaxRip in a batch run it just disappears from the taskbar and doesn't appear in the system tray. I couldn't find any way to get focus of the StaxRip processing window so i had to kill tasks and then rerun it again with that setting disabled.

[Exaris]

NvEnc will not encode with Vapoursynth R46 because it expects to find vsscript.dll in the system directory. But it works fine with x265.

staxrip.log
vpy: Failed to load vsscript.dll.
Failed to open input file.

https://github.com/vapoursynth/vapoursynth/blob/master/ChangeLog
Line 6: "the windows installer no longer puts a copy of vsscript.dll in the system directory and no longer writes the legacy registry entries, deprecated since r31"

[BetA13]

i have a tiny question.

Is it still the case, that NVIDIA gpu´s are better for encoding movies, etc, then AMD ones?
Is AMD still behind when it comes to encode, etc speed and quality?

I need to upgrade my GPU and im thinking about what would be the best pic for me..
Stay NVidia or go Team Red? the only benchmarks i see are with adpbe premiere and such, but i use staxrip 100% for the time so, can u compare adobe premier benchmarks also with staxrip? I didnt find any staxrip benchmarks sadly, they would tell me wich is best..

If any experienced user knows what i mean and has a good answer for me, please do :)

THX

[Groucho2004]

i have a tiny question.There are no tiny questions, there are only tiny answers.

Sorry, could not help myself. :D

[stax76]

i have a tiny question.

Is it still the case, that NVIDIA gpu´s are better for encoding movies, etc, then AMD ones?
Is AMD still behind when it comes to encode, etc speed and quality?

I need to upgrade my GPU and im thinking about what would be the best pic for me..
Stay NVidia or go Team Red? the only benchmarks i see are with adpbe premiere and such, but i use staxrip 100% for the time so, can u compare adobe premier benchmarks also with staxrip? I didnt find any staxrip benchmarks sadly, they would tell me wich is best..

If any experienced user knows what i mean and has a good answer for me, please do :)

THX

As far as I can see, NVIDIA is still on top.

[BetA13]

oki doki, Thank you for the quick response..

hopefully AMD manages to make Nvidia drop theyr prices even more.. :)

[Andy]

Nvidia is better than AMD in that, but the quality of gpu encoding is still not cpu encoding, video is losing little detail, sharpness.
I do not know how it is on NVidia cards with Turing chip (RTX 20xx), where NVenc can already insert B-frames, there is maybe better quality.

[martynuzza]

I'm using StaxRip-x64-2.0.2.0-stable.
When i enable QTGMC an error occour:

The error:


Cannot load file 'C:/Users/utente/App/StaxRip-x64-2.0.2.0-stable/Apps/Plugins/avs/DFTTest/dfttest.dll'. Platform returned code -1073741795:
Unknown error
(C:\Users\utente\Desktop\clip_temp\clip.avs, line 5)




The content of "C:\Users\utente\Desktop\clip_temp\clip.avs": (line 5 colored in red)
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\AddGrainC\AddGrainC.dll")
Import("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\AnimeIVTC\AnimeIVTC.avsi")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\Average\Average.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\Decomb\Decomb.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\DFTTest\dfttest.dll")
Import("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\AVS\Dither\dither.avsi")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\AVS\Dither\dither.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\EEDI2\EEDI2.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\EEDI3\EEDI3.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\FFT3DFilter\fft3dfilter.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\JPSDR\Plugins_JPSDR.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\both\KNLMeansCL\KNLMeansCL.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\masktools2\masktools2.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\modPlus\modPlus.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\MPEG2DecPlus\MPEG2DecPlus.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\mvtools2\mvtools2.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\RgTools\RgTools.dll")
Import("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\SMDegrain\SMDegrain.avsi")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\AVS\TDeint\TDeint.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\yadifmod2\yadifmod2.dll")
LoadPlugin("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\ffms2\ffms2.dll")
Import("C:\Users\utente\App\StaxRip-x64-2.0.2.0-stable\Apps\Plugins\avs\QTGMC\QTGMC.avsi")
FFVideoSource("C:\Users\utente\Desktop\clip.avi", colorspace = "YV12", \
cachefile = "C:\Users\utente\Desktop\clip_temp\clip.ffindex")
#AssumeFPS(25)
QTGMC(Preset = "Placebo", InputType=3, SourceMatch=3, Sharpness=0.2, TR2=2, EdiThreads=8)


What's wrong?

[stax76]

@martynuzza

I think this was reported before and I was not able to reproduce it, just tried it and it loads.

I'm on Win 10 1903 and have following runtimes:

https://postimg.cc/9RMP25kn

If I remember right then I had tried to reproduce it on Win 7 (vmware) and it was working there as well.

Maybe try VapourSynth, sorry but I don't have a better idea.

[martynuzza]

The dependancies are satisfied like you. With VapourSynth complain another error "EEDI3m.dll. GetLastError() returned 126. A DLL dependency is probably missing."

However even with the lastest 2.0.2.4 the error (with avisynth) still remains.

May be a problem with instruction set of my old CPU i3 2120 ?

(i've tried also with my old laptop, with even less instruction set, same win7 x64 clean install and all requirements, same error).

Currently i can get everything to work perfectly using only the old version of staxrip 1.7.0.0 :(

[ChaosKing]

Dependencies of EEDI3m.dll (vapoursynth):
- OpenCL.dll
- msvcrt.dll

[martynuzza]

Dependencies of EEDI3m.dll (vapoursynth):
- OpenCL.dll
- msvcrt.dll

:( I can't satisfy opencl.dll, i've only integrated gpu

[ChaosKing]

It seems that you need to install opencl drivers separately https://www.intel.com/content/www/us/en/support/articles/000005524/graphics-drivers.html

EDIT hmm it seems HD 2000 doesn't support opencl (if you look at the table below)

[Atlantis]

Another thing I noticed in StaxRip 2.0.2.4 - 4.8.

When you have several jobs in StaxRip and one ends, the handles inside StaxRip to that finished job are not closed.

When a job is finished and I want to move or rename the folder, I can not. It says it's still open in StaxRip. This did not happen before.

[stax76]

Another thing I noticed in StaxRip 2.0.2.4 - 4.8.

When you have several jobs in StaxRip and one ends, the handles inside StaxRip to that finished job are not closed.

When a job is finished and I want to move or rename the folder, I can not. It says it's still open in StaxRip. This did not happen before.

Maybe it's the source filter.

[frenchfries]

Maybe it's the source filter.

I doubt it as it happens to me and I only really use libav.

[stax76]

I'm able to reproduce it and will debug it later today.

[stax76]

ffms2 from staxrip 2024 is from january and has both a file lock and memory leak
ffms2 from staxrip 2023 is from june and is stable

[stax76]

ffms2 and l-smash have a long history of memory issues so it's necessary to test new builds by opening a 4K source file, open the preview and move around the position, look in task manager to see how much memory is used, close preview and check if the memory is released after closing the preview.

[mparade]

------- Convert MKA to FLAC 2 using ffmpeg 2019-05-29 Wolfberry -------

C:\StaxRipV2023x64\Apps\Encoders\ffmpeg\ffmpeg.exe -i "C:\Temp\x\x.mka" -y -hide_banner -ac 2 "C:\Temp\x\x.flac"

Input #0, dts, from 'C:\Temp\x\x.mka':
Duration: N/A, start: 0.000000, bitrate: N/A
Stream #0:0: Audio: dts (DTS-HD MA), 48000 Hz, 7.1, s32p (24 bit)
Stream mapping:
Stream #0:0 -> #0:0 (dts (dca) -> flac (native))
Press [q] to stop, [?] for help
Output #0, flac, to 'C:\Temp\x\x.flac':
Metadata:
encoder : Lavf58.27.103
Stream #0:0: Audio: flac, 48000 Hz, stereo, s32 (24 bit), 128 kb/s
Metadata:
encoder : Lavc58.52.102 flac
video:0kB audio:1224817kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000661%

Start: 8:44:22
End: 8:47:10
Duration: 00:02:47

source is 7.1 DTS-X, ffmpeg converted to stereo, however my settings correct for keeping number of channels etc. I thought ffmpeg can decode DTS-X as DTS-HD MA.
Anyone knows why?

[Natty]

ColorMatrix(Mode="Rec.601->Rec.709")

whenever I use this, staxrip just hangs and then crashes

http://avisynth.nl/index.php/External_filters#Chroma_correction

[AMED]

source is 7.1 DTS-X, ffmpeg converted to stereo, however my settings correct for keeping number of channels etc. I thought ffmpeg can decode DTS-X as DTS-HD MA.
Anyone knows why? Its the -ac 2 in your log that is causing it. Have you accidentally set a custom parameter somewhere in the audio profile?

[stax76]

source is 7.1 DTS-X, ffmpeg converted to stereo, however my settings correct for keeping number of channels etc. I thought ffmpeg can decode DTS-X as DTS-HD MA.
Anyone knows why?

Can you upload a short sample or post mediainfo using the built in mediainfo gui in developer mode.

ColorMatrix(Mode="Rec.601->Rec.709")

whenever I use this, staxrip just hangs and then crashes

http://avisynth.nl/index.php/Externa...oma_correction

I cannot find a x64 plugin named ColorMatrix.

Something very minor I found using dotnet 4.8 build of v2.0.2.4 (Revan654).

When i have minimize processing dialog to tray enabled in the settings and then minimise StaxRip in a batch run it just disappears from the taskbar and doesn't appear in the system tray. I couldn't find any way to get focus of the StaxRip processing window so i had to kill tasks and then rerun it again with that setting disabled.

I committed a change that might fix it.

NvEnc will not encode with Vapoursynth R46 because it expects to find vsscript.dll in the system directory. But it works fine with x265.

staxrip.log
vpy: Failed to load vsscript.dll.
Failed to open input file.

https://github.com/vapoursynth/vapou...ster/ChangeLog
Line 6: "the windows installer no longer puts a copy of vsscript.dll in the system directory and no longer writes the legacy registry entries, deprecated since r31"

I believe it's a problem in nvencc, maybe you can report it to the nvencc tracker.

[Natty]

I cannot find a x64 plugin named ColorMatrix.


https://forum.doom9.org/showthread.php?p=1374605#post1374605


https://github.com/sorayuki/ColorMatrix/releases

[stax76]

does not work for me.

Cannot load a 32 bit DLL in 64 bit Avisynth: 'C:/Users/jd/Desktop/colormatrix_v2_6/colormatrix.dll'.

(D:\Samples\aaa_temp\aaa_new.avs, line 5)

[lasa]

With the Version 2.0.2.4 I get an error when I trie to open a VC1 File.

Video format VC-1 is not supported.

What can I do, to open it correct?

[stax76]

You mean the file extension is VC1? Does that play in mpc or mpv?

[Groucho2004]

I cannot find a x64 plugin named ColorMatrix.I made a 64 bit version (https://forum.doom9.org/showthread.php?t=173259).

[lasa]

You mean the file extension is VC1? Does that play in mpc or mpv?

I have a demuxed MKV file with VC1 codec. MPC plays the file.

[stax76]

So you had a MKV file that was containing VC1 and you demuxed this into a raw VC1 file?

[Natty]

can i somehow put all stax bundled dlls/avsi files located in subfolders of staxrip/apps/plugins/avs in one single folder (not program files/avisynth)? it will make it easier to manual update them, keep a track of versions and scan via avsmeter64 in case of some issues.

[stax76]

can i somehow put all stax bundled dlls/avsi files located in subfolders of staxrip/apps/plugins/avs in one single folder (not program files/avisynth)? it will make it easier to manual update them, keep a track of versions and scan via avsmeter64 in case of some issues.

You can do that using the custom path option in the toolbar of the app manage dialog.

[Santojob]

I'm doing tests with StaxRip, compressing videos in x265 + nVENC, the quality is good and especially the speed very fast. Could you recommend the implementation of a filter that improves the final quality of the x265 video and does not consume or reduce compression times too much?

[videoh]

Look for the MakeAnyVideoBetter() filter.

[ChaosKing]

I'm doing tests with StaxRip, compressing videos in x265 + nVENC, the quality is good and especially the speed very fast. Could you recommend the implementation of a filter that improves the final quality of the x265 video and does not consume or reduce compression times too much?

removegrain(1) helps a bit with compressibility(2-3%) and is usually a safe and very fast option.

[AMED]

There is an update to the VS script ResampleHQ.

https://gist.github.com/4re/64642122e359c37543fe

Looks like calling the script has been renamed to Resample_HQ now

[Natty]

:goodpost::DLook for the MakeAnyVideoBetter() filter.

[Trench]

I like the new black icon, and would vote to keep that. It did need the white outline that was added. The resampling done to create the lower-resolution versions in the .ico file didn't always maintain the needed amount of white outline, though, as shown in attached screen shot.

The attached .ico file contains updated lower resolutions, which "do better" at this. Its still not perfect nor a hand-tuned version (yet) for those lower resolutions, but might do better as the placeholder until more icon decisions or improvements are made.

For what it's worth.

[Santojob]

removegrain(1) helps a bit with compressibility(2-3%) and is usually a safe and very fast option.

Thank you very much for your advice ChaosKing that I will definitely try. I do not have much knowledge and time to try other things.

videoh Thank you very much for nothing.

[gonca]

Look for the MakeAnyVideoBetter() filter.

When are you releasing the MakeAnyVideoBetterNV filter
I could use it

[gonca]

Thank you very much for your advice ChaosKing that I will definitely try. I do not have much knowledge and time to try other things.

videoh Thank you very much for nothing.

Before you thank someone for nothing look carefully at your question.
You want "a filter" that improves the "final video quality" without increasing size or encode time.
Exactly what is it about your video that requires improvement
Denoising doesn't work on all videos.
In fact there is NO ONE SIZE FITS ALL filters.
Tell us what the issue is and then we can attempt to help you

[Santojob]

Before you thank someone for nothing look carefully at your question.
You want "a filter" that improves the "final video quality" without increasing size or encode time.
Exactly what is it about your video that requires improvement
Denoising doesn't work on all videos.
In fact there is NO ONE SIZE FITS ALL filters.
Tell us what the issue is and then we can attempt to help you

Do you perhaps mean setting(s)?

gonca no doubt you are right in your comments. My English is not good and the translator sometimes does not reflect exactly what I want to say. I usually compress some movie that I like and then store it in a backup HD. I have been compressing lately with Handbrake, but I see that I get a similar quality with StaxRip, but with a very important time reduction in the coding process (currently I use x265 + Nvenc + 10 bit) that I think has very good results.

Currently I only have the encoder (x265-Nvidia) configured in StaxRip and I only use the CROP filter. This configuration compresses fast (I use a bitrate of 4500 VBR).

My question is that filters could improve the final quality of the video, with the configuration mentioned above, without the coding time increasing very much .....

That was the question friends ...

[videoh]

My question is that filters could improve the final quality of the video It seems you miss the point entirely. Never mind, sorry for the snark and good luck with your projects.

"very much" is also highly nebulous.

[frenchfries]

gonca no doubt you are right in your comments. My English is not good and the translator sometimes does not reflect exactly what I want to say. I usually compress some movie that I like and then store it in a backup HD. I have been compressing lately with Handbrake, but I see that I get a similar quality with StaxRip, but with a very important time reduction in the coding process (currently I use x265 + Nvenc + 10 bit) that I think has very good results.

Currently I only have the encoder (x265-Nvidia) configured in StaxRip and I only use the CROP filter. This configuration compresses fast (I use a bitrate of 4500 VBR).

My question is that filters could improve the final quality of the video, with the configuration mentioned above, without the coding time increasing very much .....

That was the question friends ...

A couple of things.

1. Technically you should be referring to the NVENC implementation of HEVC as H.265, HEVC or MPEG-H Part 2 rather than X265 as that's a very different project and leads to potential confusion in your post.

2. To address your question, rather than filters perhaps you can change some settings in NVENC to have the same final bitrate but a quality improvement such as setting the CRF to 17 or 18, I have no idea what you use, which will make your files larger and then adjust B frames and reference frames up a bit to bring the file back down to the same bitrate hopefully.

I find that quicksync doesn't slow down a lot, if at all, even with 6 B frames and 9 reference frames but it works wonders on some footage, particularly animation.

I haven't really played with NVENC but it may also not suffer from tweaked settings.

Quicksync with the following settings seems to do wonders for me

--codec hevc --quality best --profile main10 --la-quality slow --la-window-size 15 --bframes 6 --ref 9 --b-pyramid --fallback-rc --icq 17

Quality is better than x265 slow or slower, always results in a smaller file size and encodes 4k material at ~12-14fps on my laptop with UHD620 graphics.

EDIT - I just reread your post and you use VBR 4500. I would highly recommend going to some form of constant rate factor rather than VBR.

[gonca]

Try this command line and adjust as necessary
"C:\Program Files (Portable)\NVEncC\NVEncC64.exe" --vbrhq 38400 --codec h265 --preset quality --profile main10 --level 5.1 --output-depth 10 --ref 5 --gop-len 24 --lookahead 32 --qp-init 1 --max-bitrate 38400 --vbr-quality 25 --aq --cuda-schedule auto --mv-precision q-pel --cabac
Note that different NVidia cards have different capabilities
If you a RTX 20xx type you can use b frames

[maupassant]

Problem using mClean with VS Filters (StaxRip 2.0.2.4)

Script Error :
Python Exception: name 'hnwvsfunc' is not defined
Traceback (most recent call last):
File "src\cython\vapoursynth.pyx", line 1927, in vapoursynth.vpy_evaluateScript

[Santojob]

Thanks frenchfries for your advice on VBR and gonca for its command line. The tests I have done have been very good quality. I have had problems compressing m2ts files coming from Bluray with audio & video sync, and I do not know how to solve it. I'm still looking for information on how to fix it ...

[frenchfries]

Thanks frenchfries for your advice on VBR and gonca for its command line. The tests I have done have been very good quality. I have had problems compressing m2ts files coming from Bluray with audio & video sync, and I do not know how to solve it. I'm still looking for information on how to fix it ...

Sync info is embedded within the container and staxrip and mediainfo extract it out for you.

I'm not sure what you're doing but I'd advise you to do a very standard run, ie. with no customistation and see if the output is right. Try a software only transcode and see if it syncs properly. If it does the problem is porbably to do with how you've configured NVENC.

[Santojob]

As it seems, the problem was in the structure of the Bluray that tried to compress (Star Wars I). The process I have done to correct the delay has been to read the structure of the bluray with the GUI MKVToolNix and after selecting the tracks that I have generated an MKV, with this MKV has worked well the compression and synchronization of video and audio.

[Zetti]

NVEncC v4.43 is released.

[ChaosKing]

Problem using mClean with VS Filters (StaxRip 2.0.2.4)

Script Error :
Python Exception: name 'hnwvsfunc' is not defined
Traceback (most recent call last):
File "src\cython\vapoursynth.pyx", line 1927, in vapoursynth.vpy_evaluateScript


hnwvsfunc is dead. Should be replaced with https://github.com/Helenerineium/G41Fun

[Andy]

I'm doing tests with StaxRip, compressing videos in x265 + nVENC, the quality is good and especially the speed very fast. Could you recommend the implementation of a filter that improves the final quality of the x265 video and does not consume or reduce compression times too much?

If you want a good picture, you have to use cpu encoding, not gpu. It has a lot of original details that the image made by graphics does not have. It rather smooths it.
Playing with the psychovisual capabilities of the codec (psy-rd, psy-rdog) often helps. If the source has grain, so it is longer ....
But I convert UHD over NVenc with time reasons, if it's not grain, I add Finesharp (Light) and sometimes MSharpen (50-60%) and the result is excellent. :)

[Atlantis]

Question. Just noticed this.

When I encode an AVC 8bit video with x265 10bit, the result is a little brighter and yellower than the original colors.
If I encode the same AVC 8bit video with x265 8bit, the colors look the same.

So how can I encode an AVC 8bit video into x265 10bit and keep the original colors?

I capture images of the same frames and that's how I see that encoding an 8bit source into 10bit changes the colors slightly.

[sneaker_ger]

Is the video using SD resolution? Those often use BT.601 colors. Some players may assume BT.709 colors with 10 bit files. So it's more of a problem of the player or you not setting the proper color flags (if the player can understand and obey those - most do not).

[Atlantis]

They are all standard blurays. And all HD.

https://i.postimg.cc/hP5MzVKq/test-mkv-compare.jpg

original video - 8bit encoding - 10bit encoding

You see the image on the far right (10bit) has different colors. When you have the full image and switch between them, the difference is more visible.

[Atlantis]

You can do it yourself, it is very easy and very fast. Take an 8bit AVC short clip and use Staxrip to do 2 encodings. x265 8bit and x265 10bit. Take 3 screenshots and compare them.

In the past I was inclined to do all my encoding in 10bits because of better compression and less banding, but the colors are not accurate and not the original colors.

[Atlantis]

Here are the file info

original video

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings : CABAC / 5 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 5 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 18 s 561 ms
Bit rate : 6 326 kb/s
Width : 1 920 pixels
Height : 808 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 23.976 (23976/1000) FPS
Original frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.170
Stream size : 14.0 MiB (100%)
Language : English
Default : Yes
Forced : No

-----------------------------------------------------------------

8bit encoding

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 18 s 560 ms
Bit rate : 662 kb/s
Width : 1 920 pixels
Height : 808 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Bits/(Pixel*Frame) : 0.018
Stream size : 1.46 MiB (99%)
Writing library : x265 3.1_RC1+3-3bdf06e3c628:[Windows][MSVC 1921][64 bit] 8bit+10bit+12bit
Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=8 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=1920x808 / interlace=0 / total-frames=445 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=250 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=5 / scenecut=40 / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=3 / early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=22.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 / chromaloc=0 / display-window=0cll=0,0 / min-luma=0 / max-luma=255 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr / no-hdr-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=0 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00
Default : Yes
Forced : No

-----------------------------------------------------------------

10bit encoding

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 18 s 560 ms
Bit rate : 649 kb/s
Width : 1 920 pixels
Height : 808 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.017
Stream size : 1.44 MiB (99%)
Writing library : x265 3.1_RC1+3-3bdf06e3c628:[Windows][MSVC 1921][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=8 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=1920x808 / interlace=0 / total-frames=445 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=3 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=250 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=20 / lookahead-slices=5 / scenecut=40 / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=0 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / temporal-mvp / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / sao / no-sao-non-deblock / rd=3 / early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=0.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=crf / crf=22.0 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=0 / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 / chromaloc=0 / display-window=0cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr / no-hdr-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=0 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00
Default : Yes
Forced : No

[sneaker_ger]

You can do it yourself, it is very easy and very fast.
I doubt I can reproduce it that way because I believe it's a problem of your player or the way you take screenshots. If you upload both your 8 bit as well as your 10 bit encode I can take screenshots on my PC to confirm this.
Only way StaxRip could be at fault would be if it would do any color(space) conversion. That is usually not the case with YUV source and output (the StaxRip log should confirm this).

[Atlantis]

I'm not saying it is staxrip, it could be x265. I'm going to do several more tests to find more information and report. I'm going to try taking screenshots with different player, going to try using MeGUI to encode and also try using x265 directly.

[Atlantis]

So I did more tests and it turns out it's the video player. I use PotPlayer to watch and take snapshots and it seems PotPlayer shows 10bit video a little different than 8bit video. Slightly brighter and more yellow.

I used VLC to take snapshots and it seems VLC shows more accurate colors. Snapshots taking with VLC from 8bit and 10bit show the same colors.

What other software do you recommend for taking accurate snapshots from videos?

[Andy]

Bluray encoded with 10bit is, imho, more saturated colors, because max-luma is 1023 and not 255 as 8bit.

[sneaker_ger]

What other software do you recommend for taking accurate snapshots from videos?
MPC-HC/LAV/madVR or mpv.

[stax76]

Next mpv.net to be released this weekend has config editor support for all of mpv's screenshot settings.

https://mpv.io/manual/master/#options-screenshot-format

[Exaris]

I've found that MPC-BE+MadVR gives the best overall results for 10bit->8bit conversion for watching HDR on an SDR display.

[MrBrownCow]

Anyone built a Ryzen 3xxx machine yet like 3900X? Curious how staxrip performs on intel i9-9900k vs AMD 3900X. All the benchmark guys always use handbrake and I assume the results would be similar for staxrip. Just curious if anyone's built a new ryzen machine and tested or not.

[stax76]

Anyone built a Ryzen 3xxx machine yet like 3900X? Curious how staxrip performs on intel i9-9900k vs AMD 3900X. All the benchmark guys always use handbrake and I assume the results would be similar for staxrip. Just curious if anyone's built a new ryzen machine and tested or not.

Some options that might help with benchmarks are:

x265 > Other > Decoder

and:

x265 > Other > Piping Tool

[Natty]

its been a while since aq 4 and hme was added in x265
mediainfo, mkvtoolnix and many avs plug-ins were updated.
maybe stax needs an update for it.
thanks.

[jlw_4049]

Tried the latest version. I've re-extracted a few times, regardless if I run the .exe from the 4.7 or 4.8 I get this same error.

DirectoryNotFoundException (2.0.2.4)

Could not find a part of the path 'C:\Encoding Tools\Staxrip.2.0.2.4.x64\v4.8\Apps\Versions.txt'.

System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Encoding Tools\Staxrip.2.0.2.4.x64\v4.8\Apps\Versions.txt'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
at System.IO.StreamReader..ctor(String path, Encoding encoding)
at System.IO.File.InternalReadAllLines(String path, Encoding encoding)
at StaxRip.Package..cctor()"


EDIT
Apparently you just take the contents from 4.8 and bring it into the root folder and it runs perfectly! My apologies.

Where can I get the correct FFMS2 version? It's saying the latest version here isn't supported? (https://github.com/FFMS/ffms2)

So the program is calling for FFMS2 version 2.3.0 but that doesn't exists? I can't find it on google/github anywhere? The only version I can find is 2.23.1 and it was made a good while ago. What am I missing here?

[stax76]

its been a while since aq 4 and hme was added in x265
mediainfo, mkvtoolnix and many avs plug-ins were updated.
maybe stax needs an update for it.
thanks.

I'm using staxrip maybe three times a year, it's really sad.

mpv.net is my new favorite project, using it every day, it's been great fun working on it.

Anyway, I'm trying not to code some days and then I think I can write a little code for staxrip and upload an executable, but no tools, Revan does manage that. It would probably be possible to manage this together but it would need some server technique and it's not the kind of stuff I know much about.

[Natty]

I'm using staxrip maybe three times a year, it's really sad.

mpv.net is my new favorite project, using it every day, it's been great fun working on it.

Anyway, I'm trying not to code some days and then I think I can write a little code for staxrip and upload an executable, but no tools, Revan does manage that. It would probably be possible to manage this together but it would need some server technique and it's not the kind of stuff I know much about.

no problem. i understand.

i update avs/vs plug-ins, and other integrated tools manually, no problem in that. just sometimes i make mistakes if some x265 options are not in GUI. I'll try to be more careful with that. :thanks:

[chipxtreme]

I'm trying to convert an x264 file to x265 and downsampling audio from dts to aac. It keeps crashing with STATUS_WAIT_1 on audio.

What am I doing wrong?

[videoh]

I'm trying to convert a tv series from x264 to x265 and downsampling audio from dts to aac. It keeps crashing with STATUS_WAIT_1 on audio.

What am I doing wrong? Violating forum rule 6 perhaps?

EDIT: Poster edited out the torrent file name. ;)

[jlw_4049]

Latest version of StaxRip. I notice that after you index a source (specifically 4K with ffvidesource) it minimizes StaxRip and does something in the background for about 5 to 10 minutes before it comes back up and you are able to make changes with the UI etc.

However, on the last release it didn't seem to do this.

https://i.imgur.com/q8STNN8.png

[Exaris]

I can do the 9900k part for you. I don't have a 3900 build though.

P.S. To the people wanting new x265 features go to msystem.waw.pl/x265/ and get the latest VS 2019 AVX2 under the stable branch (use the ~15MB exe it contains 8+10+12 bit) and replace the old x265 in [StaxRip Folder]\Apps\Encoders\x265

[NikosD]

@stax76

Hello Frank.

Are there two versions maintained by you and Revan654 or just one and where can someone find it/them ?

I can see a numbering of latest official build of 2.0.2.4 here https://github.com/Revan654/staxrip/releases/tag/2.0.2.4 but the same version has also a different number of 2.0.0.30 here https://ci.appveyor.com/project/Revan654/staxrip/history

The latest build is 2.0.0.33 here https://ci.appveyor.com/project/Revan654/staxrip/builds/26460900/artifacts

Thanks.

[XPEHOPE3]

I'd like to know what's the preferred way of rotating a video using StaxRip (2.0.2.4). My sources come from Ipads and Android phones and sometimes are long enough for me to be willing to use GPU encoding so I use StaxRip for that. But sometimes the sources have improper rotation.
No immediately helpful information about this was found in the help, site or this thread. Or maybe I'm just blind...

[stax76]

@NikosD

You have to ask Revan about his builds, Revan is now project lead.

[NikosD]

@NikosD



You have to ask Revan about his builds, Revan is now project lead. Ok. Do you have any builds on your own, regarding StaxRip and where can I find them ?

Thanks.

[stax76]

Ok. Do you have any builds on your own, regarding StaxRip and where can I find them ?

Thanks.

I don't have own new builds. I just made a commit (https://github.com/staxrip/staxrip/commit/763a60c692d52beb1175a0442e5c708f08c34c6a), let's see if it appears in Revan's auto build pipeline.

[Natty]

http://ffmpeg.org/index.html#pr4.2

[Arbelisk]

Hey all! I'm currently using StaxRip 2.0.2.4 Beta and encoding a 4K movie using NVEnc. But for some reason, it will output two files after the encoding is finished. One has the original name that i set, and the other has _HDR10 at the end. Is there an option I'm missing to keep it from doing this? Thanks!

[hamdanof]

Request: I want to add mkv files in batch, but it selects automatically the .ass embedded files (from the extracted folder) as hardcoded

is it possible?

[stax76]

From my side both staxrip and mpv.net are paused at least until end of summer, sorry.

[stax76]

Request: I want to add mkv files in batch, but it selects automatically the .ass embedded files (from the extracted folder) as hardcoded

is it possible?

You can try:

Options > Subtitles > Preferred Languages

and

Options > Subtitles > Add Hardcoded Subtitle

[hamdanof]

You can try:

Options > Subtitles > Preferred Languages

and

Options > Subtitles > Add Hardcoded Subtitle

tried already, doesn't do the trick (all my subs .ass) = shows warning, not accepting
plz reply to my private msg

[Santojob]

What filters should I use to improve compression quality in animation movies? I am using nvidia h265 profiles in Staxrip.

Thanks

[jlw_4049]

What filters should I use to improve compression quality in animation movies? I am using nvidia h265 profiles in Staxrip.

ThanksStop using nvidia as an encoder. If you want smaller size/better quality use x264 CPU encoding at least slow.

Sent from my SM-G965U1 using Tapatalk

[Natty]

2.0.3.0 stops responding for a long time with 99% disk usage in preview window. check using no filters. just during one click x265 encode. so nothing is wrong with filters. only ffms2 or ffvideosource was loaded while using preview window

[jlw_4049]

2.0.3.0 stops responding for a long time with 99% disk usage in preview window. check using no filters. just during one click x265 encode. so nothing is wrong with filters. only ffms2 or ffvideosource was loaded while using preview windowThere is a newer stable version out.

Sent from my SM-G965U1 using Tapatalk

[stax76]

2.0.3.0 stops responding for a long time with 99% disk usage in preview window. check using no filters. just during one click x265 encode. so nothing is wrong with filters. only ffms2 or ffvideosource was loaded while using preview window

Here it works, maybe it happens only with certain source types, what does mediainfo look like?

Maybe there is a problem with HolyWu's ffms2 build, you can try a StvG build.

https://forum.doom9.org/showthread.php?p=1880545#post1880545

There is a newer stable version out.

2.0.3.0 is the last/stable

[ChaosKing]

2.0.3.0 stops responding for a long time with 99% disk usage in preview window. check using no filters. just during one click x265 encode. so nothing is wrong with filters. only ffms2 or ffvideosource was loaded while using preview window

Try to remove the index file, sometimes it helps if you're switching ffms2 versions.

[jlw_4049]

Here it works, maybe it happens only with certain source types, what does mediainfo look like?

Maybe there is a problem with HolyWu's ffms2 build, you can try a StvG build.

https://forum.doom9.org/showthread.php?p=1880545#post1880545



2.0.3.0 is the last/stableYes I was wrong Haha. I am using 2.0.2.4 I believe.

Sent from my SM-G965U1 using Tapatalk

[proper88]

here version 2.0.3.0 is working ( update from 2.0.2.3-test)
thank's for your work


//proper88

[Natty]

Here it works, maybe it happens only with certain source types, what does mediainfo look like?

Maybe there is a problem with HolyWu's ffms2 build, you can try a StvG build.

https://forum.doom9.org/showthread.php?p=1880545#post1880545



2.0.3.0 is the last/stable

just usual BD50.

i had some older version of ffvideosource which was working fine in 2.0.2.2 but i accidentally deleted that installation now i forgot which version was that. but i remember that i took that ffvideosource file from older staxrip. do u have any idea what was that?

and 1 more question. does --normalize even work in audio encoding?
i used a wav file. qaac q127. piping - w64... couldnt see normalizing in cli when audio was getting encoded. :thanks:

[chipxtreme]

I've tried to update VapourSynth from inside Staxrip folder and now i'm getting an error setup on my computer than Python is only installed or the current user and that I should install for all users. My PC only has one user but when I installed Python I made sure I clicked the install for all users box. Anyone else have this issue and how do I get around it?

[stax76]

just usual BD50.

i had some older version of ffvideosource which was working fine in 2.0.2.2 but i accidentally deleted that installation now i forgot which version was that. but i remember that i took that ffvideosource file from older staxrip. do u have any idea what was that?

and 1 more question. does --normalize even work in audio encoding?
i used a wav file. qaac q127. piping - w64... couldnt see normalizing in cli when audio was getting encoded.

I don't remember exactly which version was used at a given time. I think I was using a StvG version from June at one time, it was hard to find that because at that time many builds had this file lock memory issue, I had posted it and HolyWu found and fixed the issue.

Later then I think Revan released a stabel release with ffms2 from January and I think this ffms2 had a file lock and memory issue and it's not clear if it really was from January because all Revan's apps lost all timestamps due to his RAR achieve not containing timestamps. I wrote a script that did compare CRC checksum against staxrip 1.7 apps to at least recover the timestamps partly, all the files that Revan added after 1.7 that wasn't updated meanwhile still have incorrect timestamps.

Before I made this stable release I was doing quite many tests with different sources.

For normalizing you have to look at the log file and post it if in doubt.

timestamps still incorrect:

Apps> (get-content versions.txt) | findstr 2019-01-01
AddGrainC avs = 2019-01-01; 1.7.1
adjust vs = 2019-01-01; 2015-03-22
AnimeIVTC avs = 2019-01-01; 2.20
Average avs = 2019-01-01; 0.94
AvsResize avs = 2019-01-01; r1d
AVSTP avs = 2019-01-01; 1.0.3.0
aWarpSharp2 avs = 2019-01-01; 2.0.1.7
AWarpSharp2 vs = 2019-01-01; 2018-06-18
BM3D vs = 2019-01-01; 2016-08-16
CNR2 avs = 2019-01-01; 2.6.1
CNR2 vs = 2019-01-01; 2016-07-02
CTMF vs = 2019-01-01; 2017-06-02
DAA3Mod avs = 2019-01-01; 3.3
DCTFilter avs = 2019-01-01; 0.5.0
DCTFilter vs = 2019-01-01; 2016-08-17
DCTFilter-f vs = 2019-01-01; r2
Deblock avs = 2019-01-01; 2013-12-03
Deblock_QED avs = 2019-01-01; 2011-11-29
DeblockPP7 vs = 2019-01-01; 2018-04-28
DeGrainMedian avs = 2019-01-01; 0.8.2
DegrainMedian vs = 2019-01-01; 2016-08-07
DehaloAlpha avs = 2019-01-01; MT2
DeNoise Histogram avs = 2019-01-01; 2018-05-15
DeNoiseMD avs = 2019-01-01; 2018-05-15
DeNoiseMF avs = 2019-01-01; 2018-05-15
DFTTest avs = 2019-01-01; 1.9.4.1
DFTTest vs = 2019-01-01; 2017-12-21
DGTonemap avs = 2019-01-01; 1.2
Dither AVSI avs = 2019-01-01; 1.27.2
Dither DLL avs = 2019-01-01; 1.27.2
Dither vs = 2019-01-01; 2018-02-23
DSS2mod avs = 2019-01-01; 2014-11-13
edi_rpow2 AVSI avs = 2019-01-01; 0.9.2.0
EEDI2 avs = 2019-01-01; 0.9.2.0
EEDI2 vs = 2019-01-01; 2017-03-04
EEDI3 avs = 2019-01-01; 0.9.2.3
eedi3_resize avs = 2019-01-01; 0.11
EEDI3m vs = 2019-01-01; 2017-12-23
FFT3DFilter avs = 2019-01-01; 2.4.7
FFT3DFilter vs = 2019-01-01; 2018-07-11
FineDehalo avs = 2019-01-01; 1.1
FineSharp avs = 2019-01-01; 2012-04-12
finesharp vs = 2019-01-01; 2018-06-30
flash3kyuu_deband avs+vs = 2019-01-01; 5.0
FluxSmooth vs = 2019-01-01; 2.0
FrameRateConverter AVSI avs = 2019-01-01; 1.2.1
fvsfunc vs = 2019-01-01; 2018-10-28
G41Fun vs = 2019-01-01; 1.0
GradFun2DB avs = 2019-01-01; 2010-03-29
GradFun2DBmod avs = 2019-01-01; 1.5
havsfunc vs = 2019-01-01; 31
HQDeringmod avs = 2019-01-01; 2018-01-18
HQDN3D avs = 2019-01-01; 0.11
HQDN3D vs = 2019-01-01; 2018-07-01
InterFrame avs = 2019-01-01; 2.0
IT vs = 2019-01-01; 1.2
JincResize avs = 2019-01-01; r44
JPSDR avs = 2019-01-01; 3.0.0
KNLMeansCL avs+vs = 2019-01-01; 1.1.1
Lazy Utilities avs = 2019-01-01; 0.12
MAA2Mod avs = 2019-01-01; 0.431
masktools2 avs = 2019-01-01; 2.2.18
mcdegrainsharp vs = 2019-01-01; 2016-10-20
mClean avs = 2019-01-01; 3.2
MCTemporalDenoise avs = 2019-01-01; 1.4.20
MiniDeen vs = 2019-01-01; 1.0
MipSmooth avs = 2019-01-01; 1.1.2
modPlus avs = 2019-01-01; 2017-10-17
MPEG2DecPlus avs = 2019-01-01; 1.5.8.0
MT Expand Multi avs = 2019-01-01; 2018-05-19
MultiSharpen avs = 2019-01-01; 1.0
mvmulti vs = 2019-01-01; 20
mvtools2 avs = 2019-01-01; 2.7.38
NicAudio avs = 2019-01-01; 1.1
nnedi3 AVSI avs = 2019-01-01; 3.0
nnedi3 vs = 2019-01-01; v12
nnedi3cl vs = 2019-01-01; 7.2
nnedi3x AVSI avs = 2019-01-01; 3.0
Oyster vs = 2019-01-01; 2017-02-10
Plum vs = 2019-01-01; 2017-06-24
PNGopt = 2019-01-01; 1.4
pSharpen avs = 2019-01-01; 2016-03-16
psharpen vs = 2019-01-01; 1.0
QTGMC avs = 2019-01-01; 3.361s
resamplehq vs = 2019-01-01; 1.0
ResizeX avs = 2019-01-01; 1.0.1
RgTools avs = 2019-01-01; 0.97
Sangnom vs = 2019-01-01; 2016-08-31
Shader AVSI avs = 2019-01-01; 1.6.5
Shader DLL avs = 2019-01-01; 1.0
SmoothD2 avs = 2019-01-01; a2
SmoothD2c avs = 2019-01-01; a2
SVPFlow 1 avs = 2019-01-01; 4.2.0.133
SVPFlow 1 vs = 2019-01-01; 4.2.0.133
SVPFlow 2 avs = 2019-01-01; 4.2.0.142
SVPFlow 2 vs = 2019-01-01; 4.2.0.142
taa vs = 2019-01-01; 0.8.0
TCanny vs = 2019-01-01; 2017-07-30
TDeintMod vs = 2019-01-01; r10
TEMmod avs = 2019-01-01; 0.2.1
TemporalMedian vs = 2019-01-01; v1
TimeCube vs = 2019-01-01; 2.0
TIVTC avs = 2019-01-01; 1.0.11
TMM2 avs = 2019-01-01; 2016-07-05
TNLMeans avs = 2019-01-01; 1.0.3
TTempSmooth vs = 2019-01-01; 2018-05-08
VagueDenoiser avs = 2019-01-01; 0.35.1.0
VagueDenoiser vs = 2019-01-01; 2015-06-08
VapourSource avs = 2019-01-01; 2018-09-21
vcfreq vs = 2019-01-01; 2016-05-12
vcmod vs = 2019-01-01; 2017-10-17
vcmove vs = 2019-01-01; 2016-04-10
Vine vs = 2019-01-01; 2017-03-16
vsCube avs = 2019-01-01; 1.0
VSFilterMod avs+vs = 2019-01-01; 5.2
W3FDIF vs = 2019-01-01; r1
xNLMeans avs = 2019-01-01; 0.03
YFRC avs = 2019-01-01; 2015-10-01
znedi3 vs = 2019-01-01; 2018-01-11
Apps>

I've tried to update VapourSynth from inside Staxrip folder and now i'm getting an error setup on my computer than Python is only installed or the current user and that I should install for all users. My PC only has one user but when I installed Python I made sure I clicked the install for all users box. Anyone else have this issue and how do I get around it?

Even experienced people including me had issues installing it. There are many setup related posts in the VapourSynth thread. I prefer having Python installed per user!

[jlw_4049]

I thought the releases was announced on here. That's why I didn't notice there was a new release.

@Stax76
What is the difference between your release and Revan654? After I index a 4k movie, it takes his version of the app like 5 to 10 minutes after indexing hits 100% and opening the GUI again. Where yours takes maybe 5 seconds.

Just curious.

Tested again, another source is taking a while, about 2 minutes. However, not nearly as long as older version of the program.

Upon further testing, 1 4k source opened okay, another 4k remux I have just got stuck on a loading symbol after indexing for about 20 minutes until I killed the task.

Used ffm2 from version 2.0.2.4 and it's working perfect.

[Natty]

For normalizing you have to look at the log file and post it if in doubt.


https://pastebin.com/raw/iDEQtQah

FLAC audio, piping method - FLAC, normalizing option was ticked, right clicked on audio tab in staxrip -> execute

[Natty]

What is the difference between your release and Revan654? After I index a 4k movie, it takes his version of the app like 5 to 10 minutes after indexing hits 100% and opening the GUI again. Where yours takes maybe 5 seconds.



Used ffm2 from version 2.0.2.4 and it's working perfect.

"his" version is 2.0.2.4 :stupid:

[jlw_4049]

"his" version is 2.0.2.4 :stupid:The ffms2 indexer was different.

[stax76]

@jlw_4049

I used HolyWu's last ffms2 build, the changelog and apps dialog show detailed version info:

ffms2 r1275+2-2019-08-11 HolyWu

I had also changed the indexing code in order to support the new progress feature of l-smash, it could make a difference but unlikely. If you encode much then l-smash and DGDecNV are worth a try. StaxRip has a sub optimal preview implementation and DGDecNV gives a nice performance boost in the preview, for encoding with 6 cores it don't help, 60 vs 61 fps in my test.


@Natty

I would need a full log file.

[jlw_4049]

@jlw_4049

I used HolyWu's last ffms2 build, the changelog and apps dialog show detailed version info:

ffms2 r1275+2-2019-08-11 HolyWu

I had also changed the indexing code in order to support the new progress feature of l-smash, it could make a difference but unlikely. If you encode much then l-smash and DGDecNV are worth a try. StaxRip has a sub optimal preview implementation and DGDecNV gives a nice performance boost in the preview, for encoding with 6 cores it don't help, 60 vs 61 fps in my test.


@Natty

I would need a full log file.

I used your version (the latest staxrip version) but I had to remove "ffms2 r1275+2-2019-08-11 HolyWu"s build. When it wouldn't load up at all after indexing 4k files. Had to go back to the previous ffms2 build from an earlier version.

[stax76]

I used your version (the latest staxrip version) but I had to remove "ffms2 r1275+2-2019-08-11 HolyWu"s build. When it wouldn't load up at all after indexing 4k files. Had to go back to the previous ffms2 build from an earlier version.

If you use the build of 2.0.2.4 then there might be a problem with file lock and memory, see if the preview releases the memory when closed. I don't know what Revan used in 2.0.2.4, IIRC I was using a StvG build from June in 2.0.2.0, StvG has also a newer build you could try:

https://forum.doom9.org/showthread.php?p=1880545#post1880545

You also have to be careful because failures might be random, all my tests were successful with HolyWu's build, so I won't replace it until I'm sure that there is a issue.

[jlw_4049]

If you use the build of 2.0.2.4 then there might be a problem with file lock and memory, see if the preview releases the memory when closed. I don't know what Revan used in 2.0.2.4, IIRC I was using a StvG build from June in 2.0.2.0, StvG has also a newer build you could try:

https://forum.doom9.org/showthread.php?p=1880545#post1880545

You also have to be careful because failures might be random, all my tests were successful with HolyWu's build, so I won't replace it until I'm sure that there is a issue.

With the HolyWu build I tried 3 different 4k remux's (hdr/uhd) 2 of the 3 failed.

I then indexed in version 2.0.2.4 and saved the job to a srip file. Tried to open the srip file with latest stable StaxRip (with 2 of the ones that didn't work) and it would just get stuck loading. It doesn't fail but it never loads.

So I then just used the ffms2 version in 2.0.2.4 and it worked great. I haven't noticed a memory leak, but it does take it 5 to 10 minutes after indexing the file to open the GUI again where I can make changes.

The last stable release you released (not sure which version) didn't have either of these problems. I'm assuming it was on an older ffms2 build.

EDIT: The last version where the file would load instantly after using ffvideosource to index was 2.0.2.0.

StvG's build won't index in StaxRip latest version at all. Although I'm currently near the end of a 4k encode that's been going for about 16 hours. So i'm going to wait to test again after this is done. I'll report back.

[stax76]

I'll run a couple of tests tonight. Which kind of files caused the issue? Was it located on a SSD or on a HDD?

First test with 40GB MakeMKV 4K HEVC file, SSD drive, indexing Window being active, after indexing maybe one second wait time, no problem at all.

Second test same as before but minimized to tray, indexing 40 GB took only 50 seconds, no wait time after indexing, no problem.

Third test using l-smash, 70 seconds indexing, no wait time after indexing, no problem.

4. same movie using HDD and ffms2, indexing took 7 minutes, no wait time after indexing, no problem.

Maybe the issue happens only with certain source file types or it happens randomly, might as well be an issue caused by staxrip because there is some threading happening and this can potentially cause a randomly occurring issue.

[jlw_4049]

I'll run a couple of tests tonight. Which kind of files caused the issue? Was it located on a SSD or on a HDD?

First test with 40GB MakeMKV 4K HEVC file, SSD drive, indexing Window being active, after indexing maybe one second wait time, no problem at all.

Second test same as before but minimized to tray, indexing 40 GB took only 50 seconds, no wait time after indexing, no problem.

Third test using l-smash, 70 seconds indexing, no wait time after indexing, no problem.

4. same movie using HDD and ffms2, indexing took 7 minutes, no wait time after indexing, no problem.

Maybe the issue happens only with certain source file types or it happens randomly, might as well be an issue caused by staxrip because there is some threading happening and this can potentially cause a randomly occurring issue.Its 4k remuxes. Coming off of an 8TB wd red.

Staxrip runs from the SSD.

I'll test again when I get home to give you as much detail as possible.

EDIT:

Just got home doing some tests now. Test 1 after it was done indexing on a 5200 RPM 8tb WD RED the app minimizes for about 6 minutes and 50 seconds. It finally comes back up and I am able to use the GUI.

A fresh install of the latest StaxRip build with the included ffms2 was able to open the file however for me to work with. I'll post back with more.

Is it normal to get this error
"https://i.imgur.com/sx6CGlB.png"

It happens sometimes when the movie file is on 1 of my drives. Maybe it's the folder character length to large?

[Natty]

@jlw_4049,after indexing please try using preview window too and keep an eye on task manager

[stax76]

the app minimizes for about 6 minutes and 50 seconds. It finally comes back up and I am able to use the GUI.

Sounds awful, unfortunately problems I cannot reproduce are difficult to fix and I have no idea what to do about it at the moment. I try to use staxrip more often and also try to use HDDs, hopefully I will be able to reproduce it.

[NikosD]

Test 1 after it was done indexing on a 5200 RPM 8tb WD RED the app minimizes for about 6 minutes and 50 seconds. It finally comes back up and I am able to use the GUI.

A fresh install of the latest StaxRip build with the included ffms2 was able to open the file however for me to work with. So, after using a fresh install did you see again that behavior of minimizing so long ?

I have never installed, not even once, StaxRip and I have never used SSD for it.

Portable version works perfectly fine and I always use it from my HDD, just a 7200 RPM - 2TB disk.

Don't mess with installations.

[lifta19]

2.0.3.0 Stable

1) Input: 10-bit BluRay Source (FFVideoSource , LWLibavVideoSource )
Setting: x265 10bit
Piping Tool - ffmpeg (x265 official build)
changed: Wolfberry building --> official building
(The user must be able to replace the version they want.)
Result : not working

2) Input: 10-bit BluRay Source (FFVideoSource , LWLibavVideoSource )
Setting: x265 10bit
AVS: LSFMode (this is not an YV12 clip!)
Result : not working

1) 2) The 8-bit source works.

I think the probe is that the FFVideoSource (colorspace = "YV12") , LSMASHVideoSour (format = "YUV420P8") option was deleted.

PS:
2.0.2.0 Stable - All Work

[stax76]

I don't see a problem, you can edit the filter profiles if you prefer the old defaults.

[lifta19]

Thank you for the good encoder.
So why do you think there's no problem?
LSFMode filter error on apparent 10-bit source
Also, the Piping Tool - ffmpeg does not work when the user replaces the x265 file I gave feedback.
It works well with 2.0.2.0 Stable version.
Thank you all the time.

[sneaker_ger]

If a filter you want to use only supports 8 bit add ConvertBits (http://avisynth.nl/index.php/ConvertBits)(8, dither=0) above it as a simple workaround. (There are other ways.)

[lifta19]

If a filter you want to use only supports 8 bit add ConvertBits (http://avisynth.nl/index.php/ConvertBits)(8, dither=0) above it as a simple workaround. (There are other ways.)

I know, but the encoder settings allow you to change FFmpeg, x265, filters, right?
But in a 10-bit source, it's a problem with the piping tool.
So I'm telling the manager because it worked well in version 2.0.2.0.
It's because the UHD Blu-ray is all 2160p 10-bit

[stax76]

just tested:


8 bit source > avs > no piping tool > x265: works fine
8 bit source > avs > avs2pipemod > x265: works fine
8 bit source > avs > ffmpeg > x265: works fine

10 bit source > avs > no piping tool > x265: works fine
10 bit source > avs > avs2pipemod > x265: works fine
10 bit source > avs > ffmpeg > x265: works fine

[jlw_4049]

@jlw_4049,after indexing please try using preview window too and keep an eye on task managerI'll do that when I get home from work. Probably be about 6pm est. I plan on getting to the bottom or this.

I have a standard of a high bitrate i encode at, so I generally dont use the preview window. I'll report back.Sounds awful, unfortunately problems I cannot reproduce are difficult to fix and I have no idea what to do about it at the moment. I try to use staxrip more often and also try to use HDDs, hopefully I will be able to reproduce it.I'm going to test it on multiple drives and my ssd. I might even try the some 4k files on my gaming PC to see if it happens on there as well. I'll report back and I appreciate you checking into these things. I love the software! Wished I knew how to code.So, after using a fresh install did you see again that behavior of minimizing so long ?

I have never installed, not even once, StaxRip and I have never used SSD for it.

Portable version works perfectly fine and I always use it from my HDD, just a 7200 RPM - 2TB disk.

Don't mess with installations.I dont actually install it. I meant a fresh extracted version of stax. I always put it in a folder on the root of my C drive. So it's on my SSD and not on 1 of my servers storage drive.



Sent from my SM-G965U1 using Tapatalk

[lifta19]

10 bit source > avs LSFMode> no piping tool > x265(official, Wolfberry): not work
(Of course, only Wolfberry build works here.)
10 bit source > avs LSFMode> avs2pipemod > x265: (official, Wolfberry) not work
10 bit source > avs LSFMode> ffmpeg > x265: (official) not work

10 bit source > avs (No filter)> no piping tool > x265(Wolfberry): works fine
(Of course, only Wolfberry build works here.)
10 bit source > avs (No filter)> no piping tool > x265(official): not work
10 bit source > avs (No filter)> avs2pipemod > x265: (official, Wolfberry) works fine
10 bit source > avs (No filter)> ffmpeg > x265: (Wolfberry) works fine
10 bit source > avs (No filter)> ffmpeg > x265: (official) not work

2.0.2.0 Stable - All Work

[stax76]

@lifta19

If the problem is that you miss that the source filters output 8 bit then modifying the filter profiles is your solution. Right-click the filters and choose 'Profiles'. This is your old profiles:


FFVideoSource =
FFVideoSource("%source_file%", colorspace = "YV12", \
cachefile = "%source_temp_file%.ffindex")
#AssumeFPS(25)

LSMASHVideoSource =
LSMASHVideoSource("%source_file%", format = "YUV420P8")
#AssumeFPS(25)

LWLibavVideoSource =
LWLibavVideoSource("%source_file%", format = "YUV420P8")
#AssumeFPS(25)


That's what it was before, it will force YUV420P8 for both ffms2 and l-smash. If you want the old defaults back, you can create a ticket on the tracker.

[Natty]

update your lsfmod https://pastebin.com/NEyPaAig

it will take 10bit source and process and output 10bit clip. dont let source filters change color space or bitdepth

[jlw_4049]

Update:

Tried the same 49.5 GB file on 3 different WD Red Drives. Took approximately 7 minutes after indexing for it the UI to come back up to where I could make changes.

The app goes into background processes here
https://i.imgur.com/Mw7fUIN.png

I will try a little more.

EDIT: Same file, another machine, same version of StaxRip, does the same thing.

I use manual input. Drag the movie into the program, select FFVideoSource. I deselect everything, audio, chapters, everything. I only index the file, it doesn't take long, a couple minutes, the window goes away (not anywhere visible but in the task manager) for about 6 to 7 minutes and then it comes back up.|

EDIT: Moved video files to an SSD. Takes exactly 6 to 7 minutes before the GUI is usable again (meaning it has nothing to do with the storage medium). Going to try a couple more things.

Also tried 3 more HEVC Remux's HDR UHD. Even extracted 1 of them with MKVExtract to a hevc/x265 file and it does the same thing. Not quite sure what it is, but I can't find anything in the log.

Also, is there a folder name length limit that gives an error? Because when I open a file with a lot of characters after trying to index it fails. Once I lower it to a smaller name it seems to work.

[lifta19]

update your lsfmod https://pastebin.com/NEyPaAig

it will take 10bit source and process and output 10bit clip. dont let source filters change color space or bitdepth

avisynth+ 2772
10bit Source

https://i.postimg.cc/FswhSQHR/Screen-Shot00001.jpg

[NikosD]

Tried the same 49.5 GB file on 3 different WD Red Drives.
Took approximately 7 minutes after indexing for it the UI to come back up to where I could make changes.
...
Moved video files to an SSD.
Takes exactly 6 to 7 minutes before the GUI is usable again (meaning it has nothing to do with the storage medium) It seems it's not a bug eventually, it's a feature.

We have probably never encountered 50GB files like you and we hadn't noticed.

I don't know if the developers can do something about it.

[Natty]

Update:

Tried the same 49.5 GB file on 3 different WD Red Drives. Took approximately 7 minutes after indexing for it the UI to come back up to where I could make changes.

The app goes into background processes here
https://i.imgur.com/Mw7fUIN.png

I will try a little more.

EDIT: Same file, another machine, same version of StaxRip, does the same thing.

I use manual input. Drag the movie into the program, select FFVideoSource. I deselect everything, audio, chapters, everything. I only index the file, it doesn't take long, a couple minutes, the window goes away (not anywhere visible but in the task manager) for about 6 to 7 minutes and then it comes back up.|

EDIT: Moved video files to an SSD. Takes exactly 6 to 7 minutes before the GUI is usable again (meaning it has nothing to do with the storage medium). Going to try a couple more things.

Also tried 3 more HEVC Remux's HDR UHD. Even extracted 1 of them with MKVExtract to a hevc/x265 file and it does the same thing. Not quite sure what it is, but I can't find anything in the log.

Also, is there a folder name length limit that gives an error? Because when I open a file with a lot of characters after trying to index it fails. Once I lower it to a smaller name it seems to work.

check how crop and preview windows are behaving after file is indexed

[Natty]

avisynth+ 2772
10bit Source

https://i.postimg.cc/FswhSQHR/Screen-Shot00001.jpg

hmm u need latest smdegrain , rgtools and masktools

put them in \AviSynth+\plugins64+\

https://pastebin.com/4y4Zw2xG

https://github.com/pinterf/RgTools/releases/

https://github.com/pinterf/masktools/releases/

and delete them from StaxRip/Apps/Plugins

because it does not auto load correctly from there. all needed plugins should be in 1 single auto load folder.

[jlw_4049]

check how crop and preview windows are behaving after file is indexedI will check after work. Around 5pm est and will get back to you.

Sent from my SM-G965U1 using Tapatalk


EDIT: Got an encode finishing up 4K, it's been going for 14 hours, so I don't wanna risk locking it up. I'll wait until it's done, about 3 hours.

Sooo, indexing still takes about 6 to 7 minutes. When I press preview it takes about 10 seconds before I can use it. Works normally. When I close preview it takes about 7 seconds to close.

Cropping takes about 7 seconds to open up. It works like it's supposed to it seems like.

UPDATE: Testing a 1080p remux now. Well apparently 1080p remux's are doing the exact same thing. Hmmmm. Going to reinstall AviSynth etc to see if it fixes it by chance.

Reinstalled AviSynth, Reinstalled VapSynth (i know I'm not using it), reinstalled LAV filters, reinstalled Python. Trying StaxRip on another HDD in the machine.

[Natty]

same behaviour here. using older ffms2 build and it works snappy. i will post that old ffms2 here later today.

[jlw_4049]

FFMS2 version 2.23.1 (old version that's on github) indexes and the GUI is usable again in about 50 seconds. FFMS2 latest version included in StaxRip takes about 7 minutes before GUI is usable each time.


I'm really not sure if it's a bug or not. Maybe its supposed to take that long?

I just spent a bunch of time trying different versions of staxrip, extracted to different places, with different ffms2 versions.

I've got my smaller 1080p remuxs opening pretty much instant. However, when I get to the bigger 1080p remuxs like avengers end game or 4k avengers endgame, it seems to take about 2 minutes and 7 minutes.

I really wish I knew why. I assumed after it was done indexing the file the ffms2 had nothing else to do. But staxrip minimizes completely for 7 minutes, the hard drive stops working after 10 seconds, CPU usage is at 3% and memory around 650mbs.

It just pops back up around 7 minutes. It seems to me something is caught in a loop. Idk if it's the indexer or staxrip.

[NikosD]

FFMS2 version 2.23.1 (old version that's on github) indexes and the GUI is usable again in about 50 seconds.
FFMS2 latest version included in StaxRip takes about 7 minutes before GUI is usable each time.
...
Idk if it's the indexer or staxrip. So, on the exact same ~50 GB file, the old version of ffms2 takes 50 sec and the new one takes 8 times more (!) for indexing.

That's interesting and worths an investigation from the developers, if it's StaxRip or FFMS2.

[Natty]

this ffms2 version works fine for indexing, cropping and previewing

https://www84.zippyshare.com/v/9itzqrGo/file.html

please test

[Taurus]

@Natty
Please use another filesharer.
Zippyshare is the worst spammer around and just gave me "403 forbidden"....

[lifta19]

hmm u need latest smdegrain , rgtools and masktools

put them in \AviSynth+\plugins64+\

https://pastebin.com/4y4Zw2xG

https://github.com/pinterf/RgTools/releases/

https://github.com/pinterf/masktools/releases/

and delete them from StaxRip/Apps/Plugins

because it does not auto load correctly from there. all needed plugins should be in 1 single auto load folder.

Hi, Natty. What version are you using?
Because of the error, I just deleted version 2.0.3 and rolled back to version 2.0.2.0.
I'll just keep using 2.0.2.0 version.
Thank you

PS:
Aren't you the QXR encoder? LOL

[jlw_4049]

this ffms2 version works fine for indexing, cropping and previewing

https://www84.zippyshare.com/v/9itzqrGo/file.html

please testJust waking up. Off of work today, I'll report back when I get on my PC to access my server here soon.

This version of FFMS2 took about 75 seconds on my 5400RPM 8tb storage drive. Latest version FFMS2 takes about 7 minutes and 30 seconds(I'm sure the latest version has better/more features).

The funny thing is, the hard drive is pretty much doing nothing. Meaning the indexer/program isn't utilizing it quickly/or barely at all, hence why it's taking so long.

StvG's version (which is newish only takes the 75 seconds on larger files. So i'm assuming it's not an issue with staxrip, but more of an issue with the indexer. (could be both) You can get it here https://forum.doom9.org/showpost.php?p=1880545&postcount=2505)

[stax76]

@jlw_4049

I just tried more than 20 test runs and the main dialog appeared instantly every time. There must be a special condition on your PC.

Is this PC under load when it happens?
Which Windows version is used?
Anitmalware software installed or a system tool like clipboard manager, shell extension or automation tool?
Is staxrip minimized while indexing and if so is it minimized to tray or to task bar?
Does it also happen with short files like a minute or only with 50GB files?
Please post mediainfo.

[jlw_4049]

@jlw_4049

I just tried more than 20 test runs and the main dialog appeared instantly every time. There must be a special condition on your PC.

Is this PC under load when it happens?
Which Windows version is used?
Anitmalware software installed or a system tool like clipboard manager, shell extension or automation tool?
Is staxrip minimized while indexing and if so is it minimized to tray or to task bar?
Does it also happen with short files like a minute or only with 50GB files?
Please post mediainfo.



PC is a ryzen 7 1700. It's not under any loads when this is happening.
It's Windows 10 Enterprise v.1903 (also tested on my gaming rig Windows 10 Pro v1903)
Only antivirus I use is Windows Defender.
I don't have any other tools. I keep my system pretty bare.
It runs PLEX/QBitorrent full time though.

It only happens with larger files now. It WAS happening with shorter files, but I re-extracted the latest version of StaxRip and that seemed to fix it on all files that are under 25gbs.

I'll post media info to the larger one I have been testing right now.

Also @Natty is having the same exact problem as me.

Also to clarify, the Index window is there. It shows a progress bar from 0 to 100% like it's supposed to. Once it completes the entire program closes out, you can't see it on task bar, you can't see it anywhere, but in the process tab of Task Manger. This is happening on 3 of my computers at home.

That's when it takes its time 70 seconds to almost 8 minutes depending on which FFMS2 I have on the program at the time. When this happens PC is chilling, hard drive is at 0, CPU is at 0, and Ram is still using the same amount for StaxRip.

IDK if this helps, but I usually use StaxRip for 4k files and MeGui for 1080p. MeGui doesn't have this issue when I index with FFMS2. It takes it about 5 to 10 seconds after Indexing is to complete for the GUI to come up and work again (It is using the version 2.23.1 FFMS2 filter).

MediaInfo:

Format : Matroska
Format version : Version 4
File size : 47.3 GiB
Duration : 2 h 10 min
Overall bit rate mode : Variable
Overall bit rate : 51.8 Mb/s
Movie name : Iron Man 3 4K
Encoded date : UTC 2019-08-07 02:14:53
Writing application : mkvmerge v35.0.0 ('All The Love In The World') 64-bit
Writing library : libebml v1.3.9 + libmatroska v1.5.2

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 2 h 10 min
Bit rate : 44.1 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.222
Stream size : 40.2 GiB (85%)
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0050 cd/m2, max: 4000 cd/m2
Maximum Content Light Level : 572 cd/m2
Maximum Frame-Average Light Level : 565 cd/m2

Audio #1
ID : 2
Format : MLP FBA 16-ch
Format/Info : Meridian Lossless Packing FBA with 16-channel presentation
Commercial name : Dolby TrueHD with Dolby Atmos
Codec ID : A_TRUEHD
Duration : 2 h 10 min
Bit rate mode : Variable
Bit rate : 4 826 kb/s
Maximum bit rate : 7 887 kb/s
Channel(s) : 8 channels
Channel layout : L R C LFE Ls Rs Lb Rb
Sampling rate : 48.0 kHz
Frame rate : 1 200.000 FPS (40 SPF)
Compression mode : Lossless
Stream size : 4.40 GiB (9%)
Title : TrueHD Atmos 7.1
Language : English
Default : Yes
Forced : No
Number of dynamic objects : 13
Bed channel count : 1 channel
Bed channel configuration : LFE

Audio #2
ID : 3
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 2 h 10 min
Bit rate mode : Constant
Bit rate : 640 kb/s
Channel(s) : 6 channels
Channel layout : L R C LFE Ls Rs
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 597 MiB (1%)
Title : AC3 5.1
Language : English
Service kind : Complete Main
Default : No
Forced : No

Audio #3
ID : 4
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 2 h 10 min
Bit rate mode : Constant
Bit rate : 192 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 179 MiB (0%)
Title : Commentary by Director/Writer Shane Black/Writer Drew Pearce
Language : English
Service kind : Complete Main
Default : No
Forced : No

Text #1
ID : 5
Format : PGS
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 2 h 10 min
Bit rate : 36.1 kb/s
Count of elements : 3480
Stream size : 33.5 MiB (0%)
Title : English
Language : English
Default : No
Forced : No

I deleted like 50 texts from the media info. As the post would have been too long.

You're version StaxRip 2.0.2.0 opens the GUI after indexing in 40 seconds. Latest almost 8 minutes. None of them are instant so far.

[stax76]

Is the crop filter enabled? Maybe it's the auto crop feature.

[jlw_4049]

Is the crop filter enabled? Maybe it's the auto crop feature.

I don't do anything with the program but launch it. I set the template from automatic to manual.

I drag my video file in. I choose FFVideoSource. The index selection comes up, which I de-select everything. I don't want to demux anything just index the file. It indexes from 0 to 100% (time takes 1-7 mins depending on size, which is normal)
The problem comes in, once that is done, the entire program goes away. It won't come back from 70 seconds to 8 minutes depending on filter version.

I never get a chance to crop/preview or anything else until StaxRip comes back up after the 8 minutes.

Currently running 2 more tests. One on my gaming PC with the file stored locally on it. One on my server with the file moved/stored locally on it. Going to see what happens, indexing is almost done.

EDIT: Just tested the same file on 2 different machines. One with latest version of StaxRip using FFMS2, it's been 4 minutes still hasn't opened.

The other program with VapourSynth (staxrip v2.0.1.0) after it was done indexing program opens instantly like it's supposed to. It definitely has something to do with the AviSynth ffms2, IDK if it's Stax or the filter though.

[stax76]

Before you open a file, is the crop filter checked?

[jlw_4049]

Before you open a file, is the crop filter checked?

https://i.imgur.com/C7OumRU.png

This is what it looks like when I launch it. I drag the file in immediately after words.

Also a little update:
VapourSynth ffms2 works instantly in Stax.
AviSynth ffms2 just took 8 minutes for GUI to become usable afterwords.

Same file, 2 different machines.

[jlw_4049]

Before you open a file, is the crop filter checked?


I'm willing to let you teamview in my machine to see this first hand if you'd like.

[stax76]

I'll add debug logging in the next release, issues that cannot be reproduced sometimes happen, and they are typically very hard to fix.

[jlw_4049]

I'll add debug logging in the next release, issues that cannot be reproduced sometimes happen, and they are typically very hard to fix.

I'm pretty adept when it comes to PC's. I've spent the last 2 days on and off working on this and testing it on multiple machines. I have 4 in my house, I have tested it on 2.

I've tested multiple staxrip versions and ffms2 indexers. I can't quite figure this out. Hopefully you can!

If you'd like to teamview into my machine and take a look? Send me a PM really quick and check it out! I'm willing to help in anyway I can, although I have no knowledge of coding.

EDIT: Testing on a 3rd computer now. It's never had any encoding software, avisynth or anything installed to it. Going to see if that makes a difference. So 3rd machine, that has never had any encoding software installed, worked Instantly. Indexing again to make sure it isn't a fluke (NOT A FLUKE, WORKS PERFECT). Also, i'm assuming it has something to do with previous AviSynth installs or something of that nature. Going to attempt to track this down.

[stax76]

Actually this was an issue for weeks after the parallel processing feature was added, it was very difficult to solve, debug logging was used to solve it but apparently it isn't completely solved, it's most likely related to thread synchronization. I don't know if remote access could help. If you code an app and there is an issue the one important thing you do is trying to reproduce it, after that it's usually easy to fix but if you cannot reproduce it then you have a great problem! All the logging code is still present in the relevant locations, it needs a bit work to re-enable it so that it creates a log file.

[jlw_4049]

Actually this was an issue for weeks after the parallel processing feature was added, it was very difficult to solve, debug logging was used to solve it but apparently it isn't completely solved, it's most likely related to thread synchronization. I don't know if remote access could help. If you code an app and there is an issue the one important thing you do is trying to reproduce it, after that it's usually easy to fix but if you cannot reproduce it then you have a great problem! All the logging code is still present in the relevant locations, it needs a bit work to re-enable it so that it creates a log file.

Read my last post, under the EDIT: section. I figured it out, IDK if it's an issue that you can fix or not. I'm trying to "clean" my avisynth now and do a retest.

[stax76]

Some things are difficult to find, I got some issues too:

My shell extension 'Open with++' breaks the Win+X menu, trying to debug this turned out that lot's of shell extensions break it and nobody knows why, fortunately I don't find the Win+x menu useful at all.

I invested lot's of time telling the Visual Studio team that my text caret is only one pixel wide not only in Visual Studio but also in any Win32 and WPF app, only UWP (store) apps use 3 pixel as it should be on 288 DPI. At the end they were telling me that they cannot reproduce it, even proved it with a screenshot, and they said that they have a priority system where my issue will be at the bottom. Next time I install Windows I hope I can find the reason.

Very often when apps show the file open dialog it is so tiny that I have to enlarge it before I can use it. Also high DPI related. I did not yet try to do anything about it.

[jlw_4049]

Some things are difficult to find, I got some issues too:

My shell extension 'Open with++' breaks the Win+X menu, trying to debug this turned out that lot's of shell extensions break it and nobody knows why, fortunately I don't find the Win+x menu useful at all.

I invested lot's of time telling the Visual Studio team that my text caret is only one pixel wide not only in Visual Studio but also in any Win32 and WPF app, only UWP (store) apps use 3 pixel as it should be on 288 DPI. At the end they were telling me that they cannot reproduce it, even proved it with a screenshot, and they said that they have a priority system where my issue will be at the bottom. Next time I install Windows I hope I can find the reason.

Very often when apps show the file open dialog it is so tiny that I have to enlarge it before I can use it. Also high DPI related. I did not yet try to do anything about it.

So 3rd computer. Program works perfectly. It has never had any video encoding software/filters or anything on it. It's purely just for gaming from my bed on a controller.

1st computer and server, even after cleaning AviSynth I cannot get them to open immediately. The file is indexing on my 1st computer on a NVME 3.5gb's drive, so it indexes in like 10 seconds and still the program takes 8 minutes to open. I'm not sure what staxrip leaves behind on old installs or avisynth. I've deleted what I could find out of the registry.

Just rebooted to safe mode to try again. Same issue. After indexing wants to hang (wait for 8 minutes before it comes back up) Really trying to figure this out. Tried the program on my wifes computer, works perfectly. It has to do something with old Staxrip installs/AviSynth installs. Which both of those computers have never had.

[Natty]

Just waking up. Off of work today, I'll report back when I get on my PC to access my server here soon.

This version of FFMS2 took about 75 seconds on my 5400RPM 8tb storage drive. Latest version FFMS2 takes about 7 minutes and 30 seconds(I'm sure the latest version has better/more features).

The funny thing is, the hard drive is pretty much doing nothing. Meaning the indexer/program isn't utilizing it quickly/or barely at all, hence why it's taking so long.

StvG's version (which is newish only takes the 75 seconds on larger files. So i'm assuming it's not an issue with staxrip, but more of an issue with the indexer. (could be both) You can get it here https://forum.doom9.org/showpost.php?p=1880545&postcount=2505)

surely the newer 4.2 is much better, but painfully slow. it takes 100% disk usage while cropping and previewing for me. so I'll just use that older version.
i remember recent versions of ffms2 do 2 passes of indexing, that's why stax window disappears.

[jlw_4049]

surely the newer 4.2 is much better, but painfully slow. it takes 100% disk usage while cropping and previewing for me. so I'll just use that older version.
i remember recent versions of ffms2 do 2 passes of indexing, that's why stax window disappears.

Stax doesn't disappear on my computers in my house that have never had it on it. However, the ones that I actually need it on it messes up.

[jlw_4049]

@stax76 Wanted to update. Clean install of Windows 10 on my gaming computer, program still does the exact same thing. So, it's for sure on the programs side of things.

Now to set my gaming machine back up. Let me know when you get that debugging in, I'll be watching this thread.

[lifta19]

StaxRip Error

Input : 8bit Source

Piping Tool : ffmpeg
x265: 3.1+11-de920e0 (Wolfberry and official)
(http://msystem.waw.pl/x265/)

AVS : ConvertBits(10)

It works : RipBot264, MeGUI, Hybrid
ffmpeg.exe -loglevel panic -i input.avs -strict -1 -f yuv4mpegpipe - | x265--crf 22 --preset slow --output-depth 10 --aq-mode 3 --frames 189956 --y4m --output Video_out.hevc -
--------------------------------------
error : StaxRip (2.0.2.0 ~ 2.0.3)
ffmpeg.exe -i input.avs -f yuv4mpegpipe -loglevel fatal -hide_banner - | x265.exe --crf 22 --preset slow --output-depth 10 --aq-mode 3 --frames 189956 --y4m --output Video_out.hevc -
(x265 [error]: unable to open input file <->)
--------------------------------------

Piping Tool : none - x265 Wolfberry(work)

x265 is frequently updated
We'll need to make sure there's no error after the replacement.

[stax76]

@lifta19

ffmpeg pipe needs -strict -1 for 10 bit, this will be available in the next release. Choosing 'None' under 'Piping Tool' is probably the best option using a Wolfberry build.

[stax76]

@jlw_4049

There is a file called StaxRip.exe.config in the startup folder, currently it has the trace section disabled, enable it.

After that you can enable debug printing under:

Tools > Settings > General > Enable Debug Logging

It should then create a debug.log file in the startup folder. If it happens again post both the debug log file and the regular log file. A few test builds might be necessary.

[jlw_4049]

@jlw_4049

There is a file called StaxRip.exe.config in the startup folder, currently it has the trace section disabled, enable it.

After that you can enable debug printing under:

Tools > Settings > General > Enable Debug Logging

It should then create a debug.log file in the startup folder. If it happens again post both the debug log file and the regular log file. A few test builds might be necessary.


Just reproduced it again. There is no log even with debugging mode ticked. You are talking about the root of the StaxRip folder correct?

If so there is no log that I can see.

[stax76]

Please wait a second, I'll upload a new build.

[jlw_4049]

Please wait a second, I'll upload a new build.Okay I'm going to work for 5 hours. Was home on break. I'll use new build and post as soon as I get home! Thanks, I'm down to try what ever!

Sent from my SM-G965U1 using Tapatalk

[stax76]

2.0.3.1 Beta

piping tool option added to x264 encoder
piping with ffmpeg supports 10 bit now
the track title wasn't detected from demuxed audio and subtitle tracks
closing the settings dialog was setting the icon location as last source directory
debug logging was improved, more debug info is included, it's no longer
needed to edit the config file to enable debug logging, it's sufficient
to enable it in the settings: Tools > Settings > General > Enable Debug Logging


https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

[lifta19]

@lifta19

ffmpeg pipe needs -strict -1 for 10 bit, this will be available in the next release. Choosing 'None' under 'Piping Tool' is probably the best option using a Wolfberry build.

2.0.3.1 Beta

Input : 8bit, 10bit
output: 10bit
Piping Tool : ffmpeg
x265: 3.1+11-de920e0 (Wolfberry or official)

Result:
Everything works fine.
Thank you, thank you. Thank you.

[jlw_4049]

2.0.3.1 Beta

piping tool option added to x264 encoder
piping with ffmpeg supports 10 bit now
the track title wasn't detected from demuxed audio and subtitle tracks
closing the settings dialog was setting the icon location as last source directory
debug logging was improved, more debug info is included, it's no longer
needed to edit the config file to enable debug logging, it's sufficient
to enable it in the settings: Tools > Settings > General > Enable Debug Logging


https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

Here are the log files. It hangs for about 8 minutes. Let me know if you need anything else.

[sneaker_ger]

Choosing 'None' under 'Piping Tool' is probably the best option using a Wolfberry build.
What is the purpose of offering the user a choice between several piping tools instead of just hardcoding one that works?

[stax76]

What is the purpose of offering the user a choice between several piping tools instead of just hardcoding one that works?

Maybe if somebody is used to do things in a certain way or want to try out a different way, maybe just for fun.

I like Wolfberry's builds because they support avs input, for that it's good that the piping tool can be disabled. Some people might want to use another x265 build that don't has avs input support or maybe Wolfberry stops making builds.

Maybe one of the piping tools has a rare bug, people can then try another piping tool then.

I think it's always good when an application is feature rich, of course when an application has many features some care has to be taken to structure everything and add some search features so users can find the features easily.

If I recall correctly then the default in staxrip is avs2pipemod for x264 and x265 using AviSynth and for VapourSynth it's vspipe.

What's new is that x264 avs input use avs2pipemod, before it was using direct avs input, I changed it in order to support 10 bit.

I remember the reason why I first added avs2pipemod was because something with ffmpeg was not working, I don't remember what it was, maybe I just missed a setting like strict -1, today maybe ffmpeg would be sufficient but since everything works very well since a long time I just leave the old defaults.

I think megui and ribbot use other piping tools, can't remember the name, there are many solutions it seems. Not sure what is most popular or fastest or most stable. What's your favorite way these days?

[Atak_Snajpera]

I just use ffmpeg as piping tool. Works without any issues so far.
Piping in general is better than direct support in encoder.
Reasons:
1) decoding/encoding overlapping ( https://forum.doom9.org/showthread.php?t=175258 )
2) separation of processes on diffrent NUMA nodes ( decoding can run on NUMA 0 while encoding on NUMA 1 )

[jlw_4049]

My log files are pending approval apparently. Maybe I didn't add them correctly?

I went ahead and put them on a pastebin. Here are the pastebin links!

https://pastebin.com/EgM0pat8
https://pastebin.com/tL61JyXM

[stax76]

My log files are pending approval apparently. Maybe I didn't add them correctly?

I went ahead and put them on a pastebin. Here are the pastebin links!

https://pastebin.com/EgM0pat8
https://pastebin.com/tL61JyXM

Thanks for helping to debug this, I hope it can be fixed.

[jlw_4049]

Thanks for helping to debug this, I hope it can be fixed.

No problem man! I love the program for 4K encoding.

It seems to hang and slowly build the AVS file 1 at a time between like 3 minute segments. I know that sounds crazy since they are >1kbs.

Let me know if I can help more/test more builds. I glanced over the debugging log, granted I have no knowledge of code, but I didn't see anything that stood out.

EDIT: Going to be out for a bit. If you would like to download this source file from me to test yourself, let me know and I'll set you up a login to my ftpServer with access to that file.

[lifta19]

Maybe if somebody is used to do things in a certain way or want to try out a different way, maybe just for fun.

I like Wolfberry's builds because they support avs input, for that it's good that the piping tool can be disabled. Some people might want to use another x265 build that don't has avs input support or maybe Wolfberry stops making builds.

Maybe one of the piping tools has a rare bug, people can then try another piping tool then.

I think it's always good when an application is feature rich, of course when an application has many features some care has to be taken to structure everything and add some search features so users can find the features easily.

If I recall correctly then the default in staxrip is avs2pipemod for x264 and x265 using AviSynth and for VapourSynth it's vspipe.

What's new is that x264 avs input use avs2pipemod, before it was using direct avs input, I changed it in order to support 10 bit.

I remember the reason why I first added avs2pipemod was because something with ffmpeg was not working, I don't remember what it was, maybe I just missed a setting like strict -1, today maybe ffmpeg would be sufficient but since everything works very well since a long time I just leave the old defaults.

I think megui and ribbot use other piping tools, can't remember the name, there are many solutions it seems. Not sure what is most popular or fastest or most stable. What's your favorite way these days?

I've used several encoders.
But I liked the StaxRip the best. It's because the GUI is very intuitive and easy to use It's a great encoder with a user-centered signature. So I only use the staxrip.
Thank you so much for providing me with a good encoder.
I'm sorry for my poor English.

ps:
And I tested it.
ffmpeg pipe was faster than x265 none

[stax76]

@lifta19, jlw_4049

Thanks for the positive feedback, it's very helpful for motivation.

@jlw_4049

I can see now that the issue is probably related to AviSynth, the main thread (thread of the main dialog) is opening the avs file to retrieve information from it, the opening happens at 20:55:44 and the closing happens minutes after at 20:59:09, here with an 18 GB file it was taking 0.5 seconds. Why it takes so long is unclear, I can try to analyze the code, maybe make some changes and add some more trace printing. It would be helpful to know if the issue persists when VapourSynth is used instead of AviSynth.

[jlw_4049]

@lifta19, jlw_4049

Thanks for the positive feedback, it's very helpful for motivation.

@jlw_4049

I can see now that the issue is probably related to AviSynth, the main thread (thread of the main dialog) is opening the avs file to retrieve information from it, the opening happens at 20:55:44 and the closing happens minutes after at 20:59:09, here with an 18 GB file it was taking 0.5 seconds. Why it takes so long is unclear, I can try to analyze the code, maybe make some changes and add some more trace printing. It would be helpful to know if the issue persists when VapourSynth is used instead of AviSynth.The issue doesn't happen with vapoursynth. Its instant.

Sent from my SM-G965U1 using Tapatalk

[stax76]

Is the source file on a fixed local drive or on a network drive? Maybe it takes so long because it's again indexing.

edit:

To find out if it was indexing again you can look at the last write date of the index file (.ffindex).

[jlw_4049]

Is the source file on a fixed local drive or on a network drive? Maybe it takes so long because it's again indexing.

edit:

To find out if it was indexing again you can look at the last write date of the index file (.ffindex).I've tried it with my 2nd PC locally and on the network drive. I have tried it on 3 local drives a nvme ssd and another ssd.

It's not just 1 file, it's like almost every 4k hdr remux.

Going to record what it does, so you can see. Give me a few minutes.

Sent from my SM-G965U1 using Tapatalk

[stax76]

After the main dialog comes back please check the last write time of the ffindex file, it must match with the end time of the index process found in the log file. If there is a difference of minutes then we know that the problem is that it indexes a second time.

----------------------- Indexing using ffmsindex -----------------------

"C:\Users\jlwServer\Desktop\Stax 2.0.3.1 test\Apps\Plugins\both\ffms2\ffmsindex.exe" "E:\temp\iron man 3 UHD\Iron man 3 UHD.mkv" "E:\temp\iron man 3 UHD\Iron man 3 UHD_temp\Iron man 3 UHD.ffindex"

Writing index... done.

Start: 4:50:31 PM
End: 4:55:44 PM

[jlw_4049]

After the main dialog comes back please check the last write time of the ffindex file, it must match with the end time of the index process found in the log file. If there is a difference of minutes then we know that the problem is that it indexes a second time.

----------------------- Indexing using ffmsindex -----------------------

"C:\Users\jlwServer\Desktop\Stax 2.0.3.1 test\Apps\Plugins\both\ffms2\ffmsindex.exe" "E:\temp\iron man 3 UHD\Iron man 3 UHD.mkv" "E:\temp\iron man 3 UHD\Iron man 3 UHD_temp\Iron man 3 UHD.ffindex"

Writing index... done.

Start: 4:50:31 PM
End: 4:55:44 PM


Here is the video. It's processing, but it should be done soon. Pretty compressed video file.

https://youtu.be/PEzNkNW0Zi8

Will add new log files in just a second

Here you go:
https://pastebin.com/5pb5a20M
https://pastebin.com/dXgKEzXD

Also, index times look accurate. There is no HDD activity/or updated index file while it's waiting the additional 8 minutes.

[stax76]

If there is no hdd activity then a second indexing is probably not happening. Maybe check the timestamps anyway after the waiting, the index file isn't written while indexing, it's only written after the indexing.

[jlw_4049]

If there is no hdd activity then a second indexing is probably not happening. Maybe check the timestamps anyway after the waiting, the index file isn't written while indexing, it's only written after the indexing.

It's not indexing that is the issue. :/

Watch the video and take a look!

[stax76]

I'll watch it. To be sure that it's not indexing only the HDD activity or the timestamps can tell. The filter can index using the staxrip process not using ffmsindex.exe

[stax76]

I've watched the video, there is about 7% CPU time, that would be about that same what indexing uses. :-) I'll watch it again.

[jlw_4049]

I've watched the video, there is about 7% CPU time, that would be about that same what indexing uses. :-) I'll watch it again.


Let me know what you think it is.

EDIT: Also, wouldn't the HDD be under load though if it was indexing a 2nd time? Like I said, I've done a lot of tests and IDK what it is.

I am pretty sure it does it with this file on 3 out of the 4 computers I have tested it on. I even reinstalled Windows 10 on my gaming machine to try with fresh avisynth etc, still does the same thing. Takes about 7-8 minutes each time after the index. Usually the Index takes about 5 minutes.

(Just double checked. No HDD usage during the 8 minute period where StaxRip isn't there)

[jlw_4049]

I've watched the video, there is about 7% CPU time, that would be about that same what indexing uses. :-) I'll watch it again.


Just noticed, on the build I'm using, I went to go ahead and try another file (which did take the 8 minutes exta), however I was going to do a 4K encode, I clicked crop and it's doing the exact same thing that the Indexer is doing. I'm going to wait and see if it's waiting for the 8 minutes before the crop window comes up for me to crop.

Just took the program about 7 minutes to open the cropping window.

[stax76]

If the preview or cropping dialog takes minutes to load then it's an indication that's a general avs issue, maybe try to load the avs scripts generated by staxrip in another app like VirtualDub2, if that takes also minutes to load then it's a general avs issue out of the control of staxrip.

[jlw_4049]

If the preview or cropping dialog takes minutes to load then it's an indication that's a general avs issue, maybe try to load the avs scripts generated by staxrip in another app like VirtualDub2, if that takes also minutes to load then it's a general avs issue out of the control of staxrip.

I'll uninstall/reinstall AviSynth. Have you made any head way on that issue after indexing?

[Atlantis]

I just installed 2.0.3 and want to thank you. This is not just an improvement, this is a huge first step. For the very first time Staxrip (or at least me) is encoding H265 10bit sources correctly.

For many years, don't remember maybe since 1.0.7 or 1.0.6 I have been encoding H265 10bit HDR sources incorrectly. I was always dissatisfied with the results and I knew something was wrong but did not know what.

Now I have discovered that before 2.0.3 I got

avs2pipemod[info]: writing 1146 frames of 24000/1001 fps, 3840x2160,
sar 0:0, YUV-420-planar-8bit progressive video.
y4m [info]: 3840x2160 fps 24000/1001 i420p8 unknown frame count

now I get this
avs2pipemod[info]: writing 1146 frames of 24000/1001 fps, 3840x2160,
sar 0:0, YUV-420-planar-10bit progressive video.
y4m [info]: 3840x2160 fps 24000/1001 i420p10 unknown frame count

So I'm suspecting that for the past few years, staxrip was converting H265 10bit HDR sources to 8bit and again to 10bit H265 for encoding.

Now my encodes with H265 10bit sources, finally look acceptable to my eyes.

The side-effect is that my encodes have gone extremely slower. A 16hr encode now takes 25 hours. I suspect that in the past when it was sending 8bit information, there was less information to encode and it was faster. Now for the first time it is sending the correct full 10bit information to encode and it is extremely slow. :o

[stax76]

@jlw_4049

So far I only found an unrelated bug and I realize that it's a lot of complicated multi threading code. At this time it appears that it's not staxrip that is blocking AviSynth but that it simply takes AviSynth awful long to execute. If your file is on a server I can try if it works better here, 50 GB is not a problem to download.

@Atlantis

Before the source filters had a parameter that was forcing 8 bit output (can be customized), don't ask me if this should have been changed long before. :-)

[Zetti]

NVEncC v4.46 is released.

[jlw_4049]

@jlw_4049

So far I only found an unrelated bug and I realize that it's a lot of complicated multi threading code. At this time it appears that it's not staxrip that is blocking AviSynth but that it simply takes AviSynth awful long to execute. If your file is on a server I can try if it works better here, 50 GB is not a problem to download.

@Atlantis

Before the source filters had a parameter that was forcing 8 bit output (can be customized), don't ask me if this should have been changed long before. :-)

@stax76 I'm about to PM you with FTP details.
PM sent. Let me know if you have any issues.

[stax76]

With that file it was reproducible, took minutes to load, I tried to open the avs file with VirtuaDub2, same problem, tried l-smash, same problem.

After I remuxed it using only 5 of the 45 subtitle streams, things were greatly improved. It seems more streams means more wait time and with 50 GB with 50+ streams the wait time is several minutes.

We've learned this the hard way, but we've learned something. :)

[jlw_4049]

With that file it was reproducible, took minutes to load, I tried to open the avs file with VirtuaDub2, same problem, tried l-smash, same problem.

After I remuxed it using only 5 of the 45 subtitle streams, things were greatly improved. It seems more streams means more wait time and with 50 GB with 50+ streams the wait time is several minutes.

We've learned this the hard way, but we've learned something. :)I'm glad you looked into it. So in other words it's not actually a problem?

Or is it something that can be sped up?

Also with the new piping options you added. Are they they to stay in the next stable release?

I focus primarily on 4k encodes with staxrip. Should I leave the piping tool on automatic or set it to something else?

P.S. glad you figured out I wasnt crazy with that file :)

EDIT: if I demux the video during the selection and nothing else. Will the Avs file be made from the raw demuxed video file or will it still base everything off of the original file.

If it was the first option that would solve my long wait times on files with a stupid amount of subtitles.

Sent from my SM-G965U1 using Tapatalk

[stax76]

I'm glad you looked into it. So in other words it's not actually a problem?

I don't know if there is much room for optimization, if so then it would happen in the source filter or in ffmpeg (Libavformat). The way this particular mkv file or the way mkv files are structured in general might play a role.

Also with the new piping options you added. Are they they to stay in the next stable release?

I focus primarily on 4k encodes with staxrip. Should I leave the piping tool on automatic or set it to something else?

I guess all methods will work equally well.

[jlw_4049]

I don't know if there is much room for optimization, if so then it would happen in the source filter or in ffmpeg (Libavformat). The way this particular mkv file or the way mkv files are structured in general might play a role.



I guess all methods will work equally well.Thanks for info! I have left it to automatic for now, which is default.

I read earlier someone some ffmpeg piping tool encoded faster. Since I'm doing large 4k encodes, might be something worth testing.

Also if I demux the video file does stax use the demuxed file as input?
Sent from my SM-G965U1 using Tapatalk

[stax76]

Thanks for info! I have left it to automatic for now, which is default.

I read earlier someone some ffmpeg piping tool encoded faster. Since I'm doing large 4k encodes, might be something worth testing.

Also if I demux the video file does stax use the demuxed file as input?
Sent from my SM-G965U1 using Tapatalk

I made a quick performance comparison between the 3 piping options without getting a notable difference.

Also if I demux the video file does stax use the demuxed file as input?

Normally only audio and subtitles are demuxed when a source is opened but demuxing can be disabled, in that case staxrip works with the streams, it's still possible to choose audio and subtitle streams.

[jlw_4049]

I made a quick performance comparison between the 3 piping options without getting a notable difference.







Normally only audio and subtitles are demuxed when a source is opened but demuxing can be disabled, in that case staxrip works with the streams, it's still possible to choose audio and subtitle streams.Thanks again!!

Sent from my SM-G965U1 using Tapatalk

[MrBrownCow]

Just noticed, on the build I'm using, I went to go ahead and try another file (which did take the 8 minutes exta), however I was going to do a 4K encode, I clicked crop and it's doing the exact same thing that the Indexer is doing. I'm going to wait and see if it's waiting for the 8 minutes before the crop window comes up for me to crop.

Just took the program about 7 minutes to open the cropping window.

Thank you. I was having all kinds of issues with the interface locking up and taking about 7 minutes to respond again. Always when i opened the crop interface it would lock up for 7 minutes. I changed the ffm2 version from what 2.0.3.0 had by default to what someone linked here. https://www.sendspace.com/file/wyefy3

I think the ffm2 version went from 8.11.2019 to 7.18.2019 or something so i cant be missing much can I? Either way the program is much more responsive and never seems to lock up at all now.

[jlw_4049]

Thank you. I was having all kinds of issues with the interface locking up and taking about 7 minutes to respond again. Always when i opened the crop interface it would lock up for 7 minutes. I changed the ffm2 version from what 2.0.3.0 had by default to what someone linked here. https://www.sendspace.com/file/wyefy3



I think the ffm2 version went from 8.11.2019 to 7.18.2019 or something so i cant be missing much can I? Either way the program is much more responsive and never seems to lock up at all now.The actual fix to this. Is to properly uninstall avisynth and reinstall it.

Look up universal avisynth installer. You can use that to get it all out.

Sent from my SM-G965U1 using Tapatalk

[Atlantis]

The process StaxRip.exe manifests ransomware behavior and was blocked. Your files have been protected from being altered.

With this new version 2.0.3, Bitdefender says that at the end of a job and causes many problems.

[jlw_4049]

The process StaxRip.exe manifests ransomware behavior and was blocked. Your files have been protected from being altered.

With this new version 2.0.3, Bitdefender says that at the end of a job and causes many problems.Exclude it from bitdefender. The app is fine.

Sent from my SM-G965U1 using Tapatalk

[MrBrownCow]

The actual fix to this. Is to properly uninstall avisynth and reinstall it.

Look up universal avisynth installer. You can use that to get it all out.

Sent from my SM-G965U1 using Tapatalk

I used the universal avisynth installer to uninstall and re-install avisynth but it didnt help. I tried three times to uninstall and do a clean install of r2772 but with that newer ffm2index version it causes all kinds of lock ups to the application every time i click on something. Takes me 40 minutes to queue up a new encode.

When i switch back to the older ffm2index files it takes me 4 minutes total to queue up a new encode. I spent two hours trying different things but this was the only thing that worked so i guess i just have to stick with the older ffm2index.exe files for now.

:confused:

[jlw_4049]

I used the universal avisynth installer to uninstall and re-install avisynth but it didnt help. I tried three times to uninstall and do a clean install of r2772 but with that newer ffm2index version it causes all kinds of lock ups to the application every time i click on something. Takes me 40 minutes to queue up a new encode.



When i switch back to the older ffm2index files it takes me 4 minutes total to queue up a new encode. I spent two hours trying different things but this was the only thing that worked so i guess i just have to stick with the older ffm2index.exe files for now.



:confused:Uninstall x86/64 and reinstall with the included AviSynth install files in the StaxRip folder.

Sent from my SM-G965U1 using Tapatalk

[Natty]

Uninstall x86/64 and reinstall with the included AviSynth install files in the StaxRip folder.

Sent from my SM-G965U1 using Tapatalk

so latest ffms2 4.2 is working fine for u?

[jlw_4049]

so latest ffms2 4.2 is working fine for u?Yes it is. It's about as slow as avspmod and megui avisynth filters.

EDIT: I am having issues with it being slow on and off. Takes FOREVER to open the crop window, about 4 minutes to open the crop window.

@stax76
There does seem to be a problem with ffms2 and this version of StaxRip. Uninstalling AviSynth and reinstalling it helps for 1 encode. After that the problem returns.

Crop/Preview window takes about 4 minutes to open or close. It goes either way. I'm going to do a test with VaporSynth in a moment to see if I get the same issues.

VaporSynth is not instant. However it's like 80% quicker. Opening the crop window took 35 seconds on VaporSynth vs 4 minutes for AviSynth.

EDIT: Dropping back to version 2.0.2.0 solved all of my issues I was having. @MrBrownCow and @Natty
EDIT 2: Testing 2.0.2.4 now."
EDIT 3: Problem lies in what ever changed from 2.0.2.0 to 2.0.2.4

@stax76 Where it was taking 8 minutes after indexing to open 2.0.2.0 opens it within the minute. The only downside, for long file names or file names with spaces it seems to get some sort of path error. However, I can deal with that.

I'll be sticking with 2.0.2.0 for now then.

[Natty]

ok i am using 2030 with old ffms2. seems to be frame accurate and updated all plugins. everything working smooth.

[jlw_4049]

ok i am using 2030 with old ffms2. seems to be frame accurate and updated all plugins. everything working smooth.


I'm going to just rock 2.0.2.0 for the time being. Over all seems a lot more stable. Everything is instant.
I'll test latest version with ffms2 and see if it fixes my issues.

I was able to do 2.0.3.0 with the older FFMS2. After re-extracting etc. Seems to be working alright. I'll stick with this version for sure, idk how or why the ffms2 plugin is causing lots of weird issues.

[stax76]

The only downside, for long file names or file names with spaces it seems to get some sort of path error. However, I can deal with that.

Next mpv.net release has a fix for it. For staxrip it will likely be difficult to support, I've created an issue on the tracker.

There were issues with the source filters that occurred only under special circumstances (source files with many audio/subtitle tracks) so I needed to make a stable release that is hopefully more stable than the previous one.

Still using source files with 50 tracks AviSynth/VapourSynth need about 30 seconds to load, on a SSD. In that time the application is unfortunately unresponsive or hidden, staxrip queries avs/vs whenever the script changes or the crop/preview is shown. There is no warning or progress indicator that says that avs/vs is currently loading.

2.0.4.0 Stable

update: ffms2 2019-08-30 StvG, successfully tested was the load time, memory usage and avs/vs compatibility
update: L-Smash-Works r935+34 2019-08-29 MeteorRain, successfully tested was the load time, memory usage and avs/vs compatibility
update: MediaInfo 19.07
update: ffmpeg 4.2 Wolfberry
update: nvenc 4.46
update: qsvenc 3.24


https://github.com/staxrip/staxrip/releases

[jlw_4049]

Next mpv.net release has a fix for it. For staxrip it will likely be difficult to support, I've created an issue on the tracker.



There were issues with the source filters that occurred only under special circumstances (source files with many audio/subtitle tracks) so I needed to make a stable release that is hopefully more stable than the previous one.



Still using source files with 50 tracks AviSynth/VapourSynth need about 30 seconds to load, on a SSD. In that time the application is unfortunately unresponsive or hidden, staxrip queries avs/vs whenever the script changes or the crop/preview is shown. There is no warning or progress indicator that says that avs/vs is currently loading.



2.0.4.0 Stable



update: ffms2 2019-08-30 StvG, successfully tested was the load time, memory usage and avs/vs compatibility

update: L-Smash-Works r935+34 2019-08-29 MeteorRain, successfully tested was the load time, memory usage and avs/vs compatibility

update: MediaInfo 19.07

update: ffmpeg 4.2 Wolfberry

update: nvenc 4.46

update: qsvenc 3.24





https://github.com/staxrip/staxrip/releasesYou're the man! I'll try this out tomorrow after work and see how she works!!

:)

Sent from my SM-G965U1 using Tapatalk

[Natty]

staxrip queries avs/vs whenever the script changes or the crop/preview is shown.


https://forum.doom9.org/showthread.php?p=1872314#post1872314

maybe this is reducing load time of crop window. please check.

[Patman]

Next mpv.net release has a fix for it. For staxrip it will likely be difficult to support, I've created an issue on the tracker.

There were issues with the source filters that occurred only under special circumstances (source files with many audio/subtitle tracks) so I needed to make a stable release that is hopefully more stable than the previous one.

Still using source files with 50 tracks AviSynth/VapourSynth need about 30 seconds to load, on a SSD. In that time the application is unfortunately unresponsive or hidden, staxrip queries avs/vs whenever the script changes or the crop/preview is shown. There is no warning or progress indicator that says that avs/vs is currently loading.

2.0.4.0 Stable

update: ffms2 2019-08-30 StvG, successfully tested was the load time, memory usage and avs/vs compatibility
update: L-Smash-Works r935+34 2019-08-29 MeteorRain, successfully tested was the load time, memory usage and avs/vs compatibility
update: MediaInfo 19.07
update: ffmpeg 4.2 Wolfberry
update: nvenc 4.46
update: qsvenc 3.24


https://github.com/staxrip/staxrip/releases

Hello Stax,

the changelog says that you have tested the ffms2 build by STvG or do you mean that from HolyWu?

https://forum.doom9.org/showthread.php?p=1883750#post1883750

[lifta19]

2.0.4.0 Stable Link is missing

[stax76]

the changelog says that you have tested the ffms2 build by STvG or do you mean that from HolyWu?

Both uploaded a ffms2 build yesterday, I've tested both and both worked well.

2.0.4.0 Stable Link is missing

It's there (expand assets).

https://github.com/staxrip/staxrip/releases

https://forum.doom9.org/showthread.p...14#post1872314

maybe this is reducing load time of crop window. please check.

That is needed for the current drawing method.

[lifta19]

Am I stupid?
I'm sorry. I can't find

https://github.com/staxrip/staxrip/releases

https://i.postimg.cc/26rKJV8F/1.jpg

[shodan5000]

Am I stupid?
I'm sorry. I can't find

https://github.com/staxrip/staxrip/releases

https://i.postimg.cc/26rKJV8F/1.jpg

That makes two of us. I only see 2.0.3.0 available for actual download.

[shodan5000]

Boom. The link is updated now. Thanks Stax!

[stax76]

I'm sorry, wrong button pushed which made it only a draft instead of a release.

https://github.com/staxrip/staxrip/releases

[Atlantis]

Can we change the CRF 18 of the compressibility check to another CRF?

I also want to manually add SelectRangeEvery() to some of my encodes and not use compressibility check.
Is there an easy way to add SelectRangeEvery() inside staxrip? I can't find it in the Field AVS filters.

[jlw_4049]

Can we change the CRF 18 of the compressibility check to another CRF?

I also want to manually add SelectRangeEvery() to some of my encodes and not use compressibility check.
Is there an easy way to add SelectRangeEvery() inside staxrip? I can't find it in the Field AVS filters.You just click on avs filters. Select edit script. Right underneath the first line you can add that line of code.

selectrangeevery(x,x)

Press okay and give it 2 seconds and itll update on the top right of the program and show the time.

Sent from my SM-G965U1 using Tapatalk

[Atlantis]

Thank you. That works.

However it's only for the current project. I want to have SelectRangeEvery(280,14) as a permanent option in the Fields to select in any project.
Is that possible? How can I save it to Field?

[lifta19]

What happened?
Crop, very fast. Nice Good

[Natty]

What happened?
Crop, very fast. Nice Good

yes. everything smooth and stable now. thanks revan & stax76.

[proper88]

QSVEnc is not working with the latest version

------------------------------------------------------------
Max GOP Length 240 frames
Ext. Features WeightP WeightB ctu:32 sao:none
DecodeFrameAsync error: unknown error..
Error in encoding pipeline. : unknown error.
error at encode thread.
encoded 0 frames, 0.00 fps, 0.00 kbps, 0.00 MB
encode time 0:00:00, CPULoad: 0.0
QSVEncC.exe finished with error!
------------------------------------------------------------

it is not a problem of QSVEncC 3.24, because i also tried old Version 3.23, same

[proper88]

I changed in the QSVENC Options window
Decoder from <QSVENC Intel> to <AviSynth/Vapour>
then all is working(source is a VC1 video, maybe this is a problen for QSVENC

Sorry for the confusion

QSVEnc is not working with the latest version

------------------------------------------------------------
Max GOP Length 240 frames
Ext. Features WeightP WeightB ctu:32 sao:none
DecodeFrameAsync error: unknown error..
Error in encoding pipeline. : unknown error.
error at encode thread.
encoded 0 frames, 0.00 fps, 0.00 kbps, 0.00 MB
encode time 0:00:00, CPULoad: 0.0
QSVEncC.exe finished with error!
------------------------------------------------------------

it is not a problem of QSVEncC 3.24, because i also tried old Version 3.23, same

[Atlantis]

Thank you very much for 2.0.4.0. Everything is very fast for manipulating 4K sources now.

Before, it took me minutes to crop, change CRF, seek and many other things was so slow.

[Khun_Doug]

Using the new 2.0.4.0 I get an error that MediaInfo.dll cannot be found. I don't get this on rev 2.0.3.0 and the much older 1.7.0.6. I believe the relevant text of the error is this:

System.DllNotFoundException: Unable to load DLL 'MediaInfo.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at StaxRip.MediaInfo.MediaInfo_New()
at StaxRip.MediaInfo..ctor(String path) in D:\Projekte\VB\staxrip\General\MediaInfo.vb:line 17
at StaxRip.MediaInfo.GetMediaInfo(String path) in D:\Projekte\VB\staxrip\General\MediaInfo.vb:line 371
at StaxRip.MediaInfo.GetSummary(String path) in D:\Projekte\VB\staxrip\General\MediaInfo.vb:line 205
at StaxRip.Audio.Process(AudioProfile ap) in D:\Projekte\VB\staxrip\General\Audio.vb:line 11
at StaxRip.GlobalClass._Closure$__31-0._Lambda$__2() in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 125
at System.Threading.Tasks.Parallel.<>c__DisplayClass4_0.<Invoke>b__0()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at StaxRip.GlobalClass.ProcessJob(String jobPath) in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 137
at StaxRip.GlobalClass.ProcessJobs() in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 36

I never had a folder or path that is D:\Projekte\VB\staxrip\General\... This looks to be German and my system is English. The header of the log shows:

StaxRip : 2.0.4.0
Windows : Windows 10 Education 1903
Language : English (United States)
CPU : Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz
GPU : AMD Radeon VII
Resolution : 2560 x 1440
DPI : 120

Have I done something wrong with the setup? I made the 2.0.4.0 folder the exact same way I made every other version of StaxRip.

[Khun_Doug]

Some additional information. When using rev 2.0.4.0 on a five minute test encode there is a warning that VapourSynth script memory limit exceeded and to consider increasing cache size. I am encoding HD to x265. At the end of the test encode I get the same error as indicated above. I then deleted the temporary folder and tried the five minute encode with rev 2.0.3.0. There was no memory limit warning and the encode runs properly to completion. The PC has VapourSynth 64 bit rev 47.2 installed. The PC has 48 GB free memory and during encodes I never see free memory go lower than 36 GB, so I believe the memory limit warning/error is something isolated to StaxRip 2.0.4.0.

I can work around this by going back to rev 2.0.3.0 for the failed encodes. But something seems amiss with the newer version.

[jlw_4049]

Using the new 2.0.4.0 I get an error that MediaInfo.dll cannot be found. I don't get this on rev 2.0.3.0 and the much older 1.7.0.6. I believe the relevant text of the error is this:

System.DllNotFoundException: Unable to load DLL 'MediaInfo.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at StaxRip.MediaInfo.MediaInfo_New()
at StaxRip.MediaInfo..ctor(String path) in D:\Projekte\VB\staxrip\General\MediaInfo.vb:line 17
at StaxRip.MediaInfo.GetMediaInfo(String path) in D:\Projekte\VB\staxrip\General\MediaInfo.vb:line 371
at StaxRip.MediaInfo.GetSummary(String path) in D:\Projekte\VB\staxrip\General\MediaInfo.vb:line 205
at StaxRip.Audio.Process(AudioProfile ap) in D:\Projekte\VB\staxrip\General\Audio.vb:line 11
at StaxRip.GlobalClass._Closure$__31-0._Lambda$__2() in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 125
at System.Threading.Tasks.Parallel.<>c__DisplayClass4_0.<Invoke>b__0()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at StaxRip.GlobalClass.ProcessJob(String jobPath) in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 137
at StaxRip.GlobalClass.ProcessJobs() in D:\Projekte\VB\staxrip\General\GlobalClass.vb:line 36

I never had a folder or path that is D:\Projekte\VB\staxrip\General\... This looks to be German and my system is English. The header of the log shows:

StaxRip : 2.0.4.0
Windows : Windows 10 Education 1903
Language : English (United States)
CPU : Intel(R) Core(TM) i7-6850K CPU @ 3.60GHz
GPU : AMD Radeon VII
Resolution : 2560 x 1440
DPI : 120

Have I done something wrong with the setup? I made the 2.0.4.0 folder the exact same way I made every other version of StaxRip.

Have you attempted to select the path for the mediainfo app?

@stax76
So far the latest stable version is working way way better in every way. If I come across something I'll let you know. So far everything that was giving me issues before is gone.

[stax76]

QSVEnc is not working with the latest version

I forgot to test it, unfortunately. It does not work here either but I don't think that it's a problem in staxrip because I don't believe that I changed any relevant code. I'm not using the Intel GPU so maybe I just miss a setting or driver.

Using the new 2.0.4.0 I get an error that MediaInfo.dll cannot be found. I don't get this on rev 2.0.3.0 and the much older 1.7.0.6. I believe the relevant text of the error is this:

The stack trace shows that the error happens while job processing, mediainfo is however already needed for job preparation. The changelog don't has relevant changes except for the updated source filter so you could try LWLibavSource instead of ffms2. I've made a short test encode with VapourSynth, everything was working fine.

[Khun_Doug]

Whatever this is, it is something that crept in after 2.0.3.0 since that version is working properly. I do see that MediaInfo.dll is a different size between versions. I could copy over the version from 2.0.3.0 and try it. What's strange is that some encodes do work properly. For certain, the encodes that fail work properly using previous versions. But the other odd thing is the warning (or error) from VapourSynth that the script has exceeded the cache. That error does not happen on rev 2.0.3.0. I did look and VSpipe was approximately 4.4 GB during the encode that ultimately fails. There is plenty of RAM available so it is not as if the system is thrashing. And Python is a 64 bit install.

There was a question on whether I verified the path for MediaInfo.dll was correct. Yes it is the correct path. As I indicated above, some encodes are working. This fault crept in after 2.0.3.0 as it that version works properly.

[jlw_4049]

I forgot to test it, unfortunately. It does not work here either but I don't think that it's a problem in staxrip because I don't believe that I changed any relevant code. I'm not using the Intel GPU so maybe I just miss a setting or driver.



The stack trace shows that the error happens while job processing, mediainfo is however already needed for job preparation. The changelog don't has relevant changes except for the updated source filter so you could try LWLibavSource instead of ffms2. I've made a short test encode with VapourSynth, everything was working fine.

@stax76
I never encode with QSV. However, I went ahead and did a short test and it's pretty much an instant error when you try to start the encode. So it's not working here either.

EDIT:
I've never really payed attention. Is a slower Muxing process normal here? It seems like the new version might be taking a lot longer to mux. (This is on smaller files where I'm only doing selectrangeevery(x,x) around 50mb's.)

[stax76]

I never encode with QSV. However, I went ahead and did a short test and it's pretty much an instant error when you try to start the encode. So it's not working here either.

I hope a qsvenc user like Nikos can tell what could be wrong.

@Khun_Doug

There are only three changes since 2.0.3.0 that I think are relevant.

2.0.4.0 Stable

update: ffms2 2019-08-30 StvG, successfully tested was the load time, memory usage and avs/vs compatibility
update: L-Smash-Works r935+34 2019-08-29 MeteorRain, successfully tested was the load time, memory usage and avs/vs compatibility
update: MediaInfo 19.07
update: ffmpeg 4.2 Wolfberry
update: nvenc 4.46
update: qsvenc 3.24

2.0.3.1 Beta

piping tool option added to x264 encoder
piping with ffmpeg supports 10 bit now
the track title wasn't detected from demuxed audio and subtitle tracks
closing the settings dialog was setting the icon location as last source directory
debug logging was improved, more debug info is included, it's no longer needed to edit the config file to enable debug logging, it's sufficient to enable it in the settings: Tools > Settings > General > Enable Debug Logging

I've never really payed attention. Is a slower Muxing process normal here? It seems like the new version might be taking a lot longer to mux. (This is on smaller files where I'm only doing selectrangeevery(x,x) around 50mb's.)

You can try to paste the command line found in the changelog to cmd and compare it to older mkvmerge versions.

[Khun_Doug]

It appears MediaInfo.dll is the culprit. I already have MediaInfo (64 bit) installed on the PC. I renamed the file in the 2.0.4.0 tree to a different name to save it, and then copied in the MediaInfo.dll from the C:\Program Files folder. They appear to have the same date and file size. I deleted the temporary folder and tried the problem encode again. This time no error from VapourSynth and the encode went all the way through without faulting.

Possible dirty download? Hard to think 7z didn't complain about the archive being corrupted.

[Patman]

Hi all,

i've tested the QSVEnc version 3.24 and it works. Here is a part of my log-file.


------------------- Video encoding using QSVEnc 3.24 -------------------

F:\VideoProgz\Staxripx64\Apps\Encoders\QSVEnc\QSVEncC64.exe --quality high --profile high --level 4.1 --trellis all --fallback-rc --icq 18 --crop 4,136,4,136 --output-res 720x304 -i "E:\x264\_\_.Title1.mkv" -o "E:\x264\_\_.Title1_temp\_.Title1_new_out.h264"

QSVEncC (x64) 3.24 (r1632) by rigaya, Jul 5 2019 14:46:37 (VC 1916/Win/avx2)
OS Windows 10 x64 (18362)
CPU Info Intel Core i7-4790K @ 4.00GHz [TB: 4.40GHz] (4C/8T) <Haswell>
GPU Info Intel HD Graphics 4600 (20EU) 1300MHz (20.19.15.4531)
Media SDK QuickSyncVideo (hardware encoder) PG, 2nd GPU, API v1.19
Async Depth 6 frames
Buffer Memory d3d11, 1 input buffer, 32 work buffer
Input Info avqsv: H.264/AVC, 1920x1080, 24000/1001 fps
Crop 4,136,4,136 (1920x1080 -> 1912x808)
VPP Enabled Resizer, 1920x1080 -> 720x304
AVSync cfr
Output H.264/AVC High @ Level 4.1
720x304p 1:1 23.976fps (24000/1001fps)
Target usage 3 - high
Encode Mode ICQ (Intelligent Const. Quality)
ICQ Quality 18
QP Limit min: none, max: none
Trellis for All frames
Ref frames 3 frames
Bframes 3 frames, B-pyramid: on
Max GOP Length 240 frames
Ext. Features PerMBRC
encoded 156854 frames, 359.42 fps, 1223.39 kbps, 954.10 MB
encode time 0:07:16, CPULoad: 7.0
frame type IDR 654
frame type I 1308, total size 34.53 MB
frame type P 39214, total size 452.31 MB
frame type B 116986, total size 484.53 MB
[matroska,webm @ 000001d0436140c0] Element at 0x672ace4dc ending at 0x672b0232f exceeds containing master element ending at 0x672ace4d5

Start: 18:30:39
End: 18:37:57
Duration: 00:07:18

What are your settings?

[NikosD]

@stax76
I have become a NVEncC user lately due to my GTX 1660 Turing card, but I can try QSVEncC with my Skylake work PC [emoji2]

@jiw_4049
The default decoder of QSVEncC is always avisynth in StaxRip
Can you change that to Intel QSV ?

@patman
I can see that you are using Intel QSV as decoder.
Can you change that to the default avisynth ?

Thanks.

[Patman]

@patman
I can see that you are using Intel QSV as decoder.
Can you change that to the default avisynth ?


Here is a part of log file with avisynth as decoder. Works well too.

------------------- Video encoding using QSVEnc 3.24 -------------------

F:\VideoProgz\Staxripx64\Apps\Encoders\QSVEnc\QSVEncC64.exe --quality high --profile high --level 4.1 --trellis all --fallback-rc --icq 18 -i "E:\x264\_\_.Title1_temp\_.Title1_new2.avs" -o "E:\x264\_\_.Title1_temp\_.Title1_new2_out.h264"

QSVEncC (x64) 3.24 (r1632) by rigaya, Jul 5 2019 14:46:37 (VC 1916/Win/avx2)
OS Windows 10 x64 (18362)
CPU Info Intel Core i7-4790K @ 4.00GHz [TB: 4.40GHz] (4C/8T) <Haswell>
GPU Info Intel HD Graphics 4600 (20EU) 1300MHz (20.19.15.4531)
Media SDK QuickSyncVideo (hardware encoder) PG, 2nd GPU, API v1.19
Async Depth 4 frames
Buffer Memory d3d11, 3 input buffer, 14 work buffer
Input Info Avisynth+ 2.60(yv12)->nv12 [AVX2], 720x304, 24000/1001 fps
AVSync cfr
Output H.264/AVC High @ Level 4.1
720x304p 1:1 23.976fps (24000/1001fps)
Target usage 3 - high
Encode Mode ICQ (Intelligent Const. Quality)
ICQ Quality 18
QP Limit min: none, max: none
Trellis for All frames
Ref frames 3 frames
Bframes 3 frames, B-pyramid: on
Max GOP Length 240 frames
Ext. Features PerMBRC
encoded 156854 frames, 228.16 fps, 1274.41 kbps, 993.89 MB
encode time 0:11:27, CPULoad: 81.5
frame type IDR 654
frame type I 1308, total size 36.13 MB
frame type P 39214, total size 474.50 MB
frame type B 116986, total size 501.32 MB

Start: 19:52:22
End: 20:03:51
Duration: 00:11:28

@Stax

To issue #37 i have leaved a comment.

[stax76]

@NikosD
@Patman

I probably miss installing the driver or miss to enable something, for now it's OK for me that I don't test qsvencc or nvencc.

@Khun_Doug

Weird things happen, I hope your hardware is fine.

[Patman]

Hi Stax,

the progress bar is shown with a delay during the muxing process (at 47 percent) when i've used QSVEnc or NVEnc. During indexing with DGIndexNV only percents are shown without progress bar.

[proper88]

I changed the QSVENC encoder options.
Decoder from <QSVENC Intel> to <AviSynth/Vapour> or <QSVENC Intel Software> then all is working, source is a VC1 video, maybe this is a problen for QSVENC.

If source video is MPEG4-AVC then i can use the <QSVENC Intel> encoder

So this is ok for me, maybe there is a hardware limitation for my GPU(i8400)

Thank you to all for their great support !!

[NikosD]

Decoder from QSVENC Intel to AviSynth/Vapour or QSVENC Intel Software then all is working, source is a VC1 video, maybe this is a problen for QSVENC.
Hello.
QSVENC Intel should decode VC-1 in hardware but maybe the specific VC-1 is incompatible with QSV decoder.

Generally speaking, you could try different decoders provided by StaxRip like ffmpeg DXVA2 or ffmpeg Intel or any other listed there.

If you want, you could even report that specific VC-1 file to rigaya, the developer of QSVENCC (and all the other hardware encoders)

[Patman]

Hello.
QSVENC Intel should decode VC-1 in hardware but maybe the specific VC-1 is incompatible with QSV decoder.

Generally speaking, you could try different decoders provided by StaxRip like ffmpeg DXVA2 or ffmpeg Intel or any other listed there.

If you want, you could even report that specific VC-1 file to rigaya, the developer of QSVENCC (and all the other hardware encoders)

Hey NikosD,

you're right, VC-1 isn't supported for now:

https://github.com/rigaya/QSVEnc/blob/master/QSVEncC_Options.en.md

Under section "--avhw" are listed the supported codecs.

[stax76]

the progress bar is shown with a delay during the muxing process (at 47 percent) when i've used QSVEnc or NVEnc.

I don't understand it, maybe you can make a screenshot when it happens again. First the progress bar text is set, then the text is parsed and according to that the progress values of the progress bar and the taskbar button is set, everything happens in the same thread however.

edit:

You mean the entire bar/tab shows too late? I hope it's not bad because it's much complicated multi threading code, changing this would rather be difficult.

During indexing with DGIndexNV only percents are shown without progress bar.

Will be available in the next build.

I started however working on mpv.net again...

[Patman]

edit:

You mean the entire bar/tab shows too late? I hope it's not bad because it's much complicated multi threading code, changing this would rather be difficult.

I will post a screenshot or vid later.


I started however working on mpv.net again...

Sounds good.

[NikosD]

Hey NikosD,

you're right, VC-1 isn't supported for now:

https://github.com/rigaya/QSVEnc/blob/master/QSVEncC_Options.en.md

Under section "--avhw" are listed the supported codecs. TBH, I thought the specific VC-1 file wasn't supported by avqsv, not the entire VC-1 codec.

It's better to run --check-features command from inside StaxRip GUI or from a command line window in order to find out for sure and in real-time using your specific driver and QSVEncC version, if VC-1 is supported or not.

The HW can definitely support VC-1 decoding and I think the above documentation could be old.

[Patman]

TBH, I thought the specific VC-1 file wasn't supported by avqsv, not the entire VC-1 codec.

It's better to run --check-features command from inside StaxRip GUI or from a command line window in order to find out for sure and in real-time using your specific driver and QSVEncC version, if VC-1 is supported or not.

The HW can definitely support VC-1 decoding and I think the above documentation could be old.

I ran --check-features and the result indicates that the vc-1 codec is supported. I loaded MKV files based on VC-1 codec and wanted to decode with Intel hardware, but nothing happened. After a few minutes, I have an error message in the Staxrip GUI, but if I used the command line, only the Matroska Webm message will be displayed and the process will be stopped.

[NikosD]

I loaded MKV files based on VC-1 codec and wanted to decode with Intel hardware, but nothing happened. I'm afraid that StaxRip's thread will become QSVENC's thread, so as my last advice I would say to check also both ffmpeg HW decoders provided by StaxRip.

I'll check tomorrow the Skylake at work.

[Patman]

I mainly use CPU encoding with x264. Staxrip is a great application, and the tools on board should work with all options. From time to time, I like to test the other encoders and then things like that come to mind.

It's great to see the great involvement of the Staxrip community.

[NikosD]

Using a Skylake Core i5-6500 under Win 10 x64 (17763) with 6951 drivers (API v1.29) and StaxRip v2.0.4.0 (QSVEncC v3.24), everything seems to work fine regarding HW support of VC-1.
It's supported by the GPU/Driver/QSVenc and it works when tested on a few VC-1 files using QSVEnc Intel (--avqsv) decoder which uses the least CPU usage (~7%) and it's the fastest, as a completely HW based implementation.
But I found a VC-1 clip that started OK and finished with error (incorrect function) crashing StaxRip.
The same clip works fine using Avisynth/QSVEnc Software/ffmpeg Intel as decoders.
So, you could find some incompatibilities using a HW decoder like QSVEnc Intel, but not only for VC-1, the same thing can happen to any other supported codec.
The only solution, is to report this specific clip to the developer of the HW encoders, hoping that he could fix it, here:
https://rigaya34589.blog.fc2.com/

[Patman]

Using a Skylake Core i5-6500 under Win 10 x64 (17763) with 6951 drivers (API v1.29) and StaxRip v2.0.4.0 (QSVEncC v3.24), everything seems to work fine regarding HW support of VC-1.
It's supported by the GPU/Driver/QSVenc and it works when tested on a few VC-1 files using QSVEnc Intel (--avqsv) decoder which uses the least CPU usage (~7%) and it's the fastest, as a completely HW based implementation.
But I found a VC-1 clip that started OK and finished with error (incorrect function) crashing StaxRip.
The same clip works fine using Avisynth/QSVEnc Software/ffmpeg Intel as decoders.
So, you could find some incompatibilities using a HW decoder like QSVEnc Intel, but not only for VC-1, the same thing can happen to any other supported codec.
The only solution, is to report this specific clip to the developer of the HW encoders, hoping that he could fix it, here:
https://rigaya34589.blog.fc2.com/

Hi NikosD,

thanks for doing a test. Then it can either be the file or a compatibility issue with the hardware. I reported the problem.

[NikosD]

Then it can either be the file or a compatibility issue with the hardware. I reported the problem. It's never (almost) the hardware!
But you can always check hardware decoding using LAV filters and a suitable player like MPC-HC or internal HW decoder of MPC-BE player.
They use DXVA2 or D3D11 instead of QSV Intel to access the hardware decoder and they are extremely tested and optimized for HW decoding.

So, most of the times it's just rigaya's implementation of QSV Intel decoder.

[proper88]

Hi Patman,
thank you very much for reporting this problem to rigaya !!!

[Zetti]

MediaInfo v19.09 is released.

NVEncC v4.47 is released some days ago.

[stax76]

@Zetti

Thanks for posting, I'm currently working on a new beta build.

[stax76]

What are common file extensions for MKV attachments?

So far I got:

"ttf", "txt", "jpg", "png"

[frenchfries]

What are common file extensions for MKV attachments?

So far I got:

"ttf", "txt", "jpg", "png"

That seems pretty right to me. TBH other file/MIME types are probably added for their attack vector potential such as PDFs

[stax76]

2.0.4.1 Beta


nvenc switch --avhw updated (Patman86), --sub-source added

qsvenc switches added: --data-copy, --adapt-ltr

progress display support added for DGIndexNV, MP4Box and ffmpeg audio encoding

L-Smash Works parameters prefer_hw and format have menu support in the avs/vs code editor

the container/muxer dialog has a new tab for MKV attachments

fix: vpy import did not work when the output variable isn't named 'clip'

fix: a format exception was fixed, it was happening when the cut/trim feature was used

update: nvenc 4.47

update: L-Smash Works 2019-09-10 HolyWu

update: MediaInfo 19.09

update: mpv.net 5.4.1.1



https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

[sneaker_ger]

What are common file extensions for MKV attachments?

So far I got:

"ttf", "txt", "jpg", "png"
otf (OpenType Font), jpeg

[Havokdan]

Is it possible to have StaxRip import .nfo files into mkv format? In this case, the .nfo would be the format used by Kodi to create mkv tags with history, actors, producers and additional data, xvid4psp 6 onwards did that, and it seems to be the only one that did it, but it stopped be free.

[suarsg]

Can someone clue me in why the ordering of the parameters in the "Encoding settings"-field for x265 (visible with MediaInfo for example) changed all of a sudden? For years and with Stax 2.0.2 (x265 v3.1 RC1+3) it looked like this:
cpuid=1111039 / frame-threads=4 / numa-pools=16 / wpp / no-pmode / no-pme / no-psnr / no-ssim / ...

Now I've updated to Stax 2.0.4 (x265 3.1+11) it suddenly has this ordering:
rc=crf / crf=17.0000 / qcomp=0.60 / qpstep=4 / vbv-maxrate=160000 / vbv-bufsize=160000 / vbv-init=0.9 / ...

For as long as I can remember, all x265 encodes everywhere looked like the first one. I don't think it's from x265 itself (version barely changed) and I've seen other "x265 3.1+11" encodes where it still looks like the first one.

Did I accidentally change something in StaxRip for this to happen and didn't even notice? Was it a change in StaxRip itself after 2.0.2? I can't find any info on such a change in the changelogs of StaxRip or x265.

[stax76]

Is it possible to have StaxRip import .nfo files into mkv format? In this case, the .nfo would be the format used by Kodi to create mkv tags with history, actors, producers and additional data, xvid4psp 6 onwards did that, and it seems to be the only one that did it, but it stopped be free.

StaxRip allows adding attachments, I hope that's everything needed.

Did I accidentally change something in StaxRip for this to happen and didn't even notice? Was it a change in StaxRip itself after 2.0.2? I can't find any info on such a change in the changelogs of StaxRip or x265.

All what StaxRip does is running a command line, by default the command line is very simple, all can be seen in the log file (Tools > Log File).

[Patman]

Hey Stax you saw?

https://github.com/staxrip/staxrip/issues/51 (https://github.com/staxrip/staxrip/issues/51#issuecomment-530669760)

[Patman]

Can someone clue me in why the ordering of the parameters in the "Encoding settings"-field for x265 (visible with MediaInfo for example) changed all of a sudden? For years and with Stax 2.0.2 (x265 v3.1 RC1+3) it looked like this:
cpuid=1111039 / frame-threads=4 / numa-pools=16 / wpp / no-pmode / no-pme / no-psnr / no-ssim / ...


Some of these settings are default settings, so they are no longer listed separately. These can be found under Performance at the x265 options.

[suarsg]

Some of these settings are default settings, so they are no longer listed separately. These can be found under Performance at the x265 options.
That's not what I'm talking about.

All what StaxRip does is running a command line, by default the command line is very simple, all can be seen in the log file (Tools > Log File).
I've done some digging in x265's source code. The ordering has never officially changed (https://bitbucket.org/multicoreware/x265/src/c4b098f973e6b0ee4aee3bf0d7b54da4e2734d42/source/common/param.cpp#lines-1903), like I suspected. So whoever compiled the x265.exe you shipped 2.0.4.0 with, has done so with his own custom function for x265_param2string(). I've confirmed this by replacing the x265.exe in Apps/Encoders/x265 with one from here (http://msystem.waw.pl/x265/) for the exact same x265 version. I then ran StaxRip with a test clip back to back, first with the old and then with new x265.exe. The replacement-exe writes the correct metadata, the x265.exe StaxRip is shipped with does not. I don't know where you got it from but it's definitely not compiled from the original official source code.

[Patman]

That's not what I'm talking about.


Sorry, my fault. I've build a x265 from official git and the settings info shows "cpuid=1111039 / frame-threads=4 / numa-pools=16 / wpp / no-pmode / no-pme / no-psnr / no-ssim / ..."

As far as i know staxrip uses x265 build from Wolfberry. Maybe there is used a custom param.cpp for this build.

[stax76]

Hey Stax you saw?

https://github.com/staxrip/staxrip/issues/51 (https://github.com/staxrip/staxrip/issues/51#issuecomment-530669760)

Sorry Patman, I had missed it. I've updated now x265, ffmpeg and MP4Box so it will be available in the next beta.

I've done some digging in x265's source code. The ordering has never officially changed, like I suspected. So whoever compiled the x265.exe you shipped 2.0.4.0 with, has done so with his own custom function for x265_param2string(). I've confirmed this by replacing the x265.exe in Apps/Encoders/x265 with one from here for the exact same x265 version. I then ran StaxRip with a test clip back to back, first with the old and then with new x265.exe. The replacement-exe writes the correct metadata, the x265.exe StaxRip is shipped with does not. I don't know where you got it from but it's definitely not compiled from the original official source code.

Maybe ask in the x265 thread, I don't know if Wolfberry follows the staxrip thread.

[Havokdan]

StaxRip allows adding attachments, I hope that's everything needed.

Hopefully in the future we will have this feature, initially at least importing from the format used by Kodi, parsing and placing in mkv tags.

https://kodi.wiki/view/NFO_files/TV_shows
https://kodi.wiki/view/NFO_files/Movies

[stax76]

Hopefully in the future we will have this feature, initially at least importing from the format used by Kodi, parsing and placing in mkv tags.

https://kodi.wiki/view/NFO_files/TV_shows
https://kodi.wiki/view/NFO_files/Movies

It's tricky, tricky (Tricky) tricky, sorry but I don't understand much about Kodi.

edit:

So I was looking if some of my 'samples' has nfo mediainfo, full text search unfortunately don't work because nfo is part of info, is there a certain mediainfo property I can look for or does mediainfo not support this info?

This is my full text search command:

get-childitem | foreach { (mediainfo $_.fullname) | out-string } | where { $_ -match 'nfo' }

edit2:

The match operator in powershell uses regex, non of my files have an attachment with nfo file extension. As I understand it such nfo files have xml content that can be created and edited with external applications, the nfo file is then added as mkv attachment which staxrip supports, I can add nfo support to the file open dialog extension filter but apart from that I don't see a need for improvement in staxrip.

[Havokdan]

It's tricky, tricky (Tricky) tricky, sorry but I don't understand much about Kodi.

edit:

So I was looking if some of my 'samples' has nfo mediainfo, full text search unfortunately don't work because nfo is part of info, is there a certain mediainfo property I can look for or does mediainfo not support this info?

This is my full text search command:

get-childitem | foreach { (mediainfo $_.fullname) | out-string } | where { $_ -match 'nfo' }

I don't know if I understand correctly, but kodi looks for info about the web media file for its media center function, but it has the option to read local nfo files, you can manually create nfo files, or use tools like MediaElch, Media Companion and TinyMediaManager (which is what I use), I wanted to import the information from this nfo which has a schema that looks like xml as tags in mkv, example of how it looked in xvid4psp:


General
Unique ID : 109171765302595762700583546447705430305 (0x5221B7999E7089240A3F1143861C5921)
Complete name : E:\Videos\Filmes\[REC] (2007)\[REC] (2007).mkv
Format : Matroska
Format version : Version 4
File size : 620 MiB
Duration : 1 h 15 min
Overall bit rate : 1 152 kb/s
Movie name : [REC]
Description : Uma equipa de repórteres de TV decide documentar em direto, uma patrulha de bombeiros em serviço durante a noite. O objetivo é registar a vida destes profissionais, incluindo as situações mais arriscadas. A primeira missão da noite, é resgatar uma senhora idosa que se encontra fechada no seu apartamento por razões desconhecidas. Durante esta missão algo corre terrivelmente mal… O que parecia de rotina, torna-se num verdadeiro inferno. Algo maléfico e sinistro está fora de controlo e ameaça a corporação e a equipa de TV. Os papéis invertem-se. A sobrevivência e a fuga terão de se sobrepor ao medo e, custe o que custar, a câmara não é para desligar… até ao último momento.
Writing application : XviD4PSP 7.0.455 DAILY
Writing library : Lavf57.71.100
ErrorDetectionType : Per level 1
Attachments : poster.jpg / backdrop.jpg
ACTORS : Manuela Velasco, Ferran Terraza, Martha Carbonell, David Vert, Carlos Lasarte, Pablo Rosso, Vicente Gil, Carlos Vicente, Jorge Yamam, María Teresa Ortega, Manuel Bronchud, Maria Lanau, Claudia Silva, Javier Botet, Ben Temple, Akemi Goto, Kao Chen-Min, Ana Isabel Velásquez, Javier Coromina, Pep Sais
COUNTRY : Spain
DATE : 2007-04-10
DIRECTOR : Jaume Balagueró, Paco Plaza
ENCODING_INFO : MATROSKA,WEBM > MKV MKV / H264 > COPY Smart / AAC-LC > COPY Smart
GENRE : Terror, Mistério
HD_VIDEO : 1
Language : und
MEDIA_TYPE : 9
PRODUCER : Julio Fernández, Alberto Marini
PUBLISHER : Filmax
RATING : 7.10
WRITER : Jaume Balagueró, Paco Plaza, Luis Berdejo

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 5 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference : 5 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 15 min
Nominal bit rate : 1 024 kb/s
Width : 1 280 pixels
Height : 688 pixels
Display aspect ratio : 1.85:1
Frame rate mode : Constant
Frame rate : 25.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.047
Writing library : x264 core 130 r2273 b3065e6
Encoding settings : cabac=1 / ref=5 / deblock=1:-1:-1 / analyse=0x3:0x133 / me=umh / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=3 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=1024 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00
Default : Yes
Forced : Yes
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : A_AAC-2
Duration : 1 h 15 min
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 44.1 kHz
Frame rate : 43.066 FPS (1024 SPF)
Compression mode : Lossy
Title : _audio.aac - Imported with GPAC 0.5.1-DEV-rev4246
Default : Yes
Forced : No



In short, in practice, I wanted to pull the files into mkv with these tags with additional information about the file, in this case getting them from an external nfo file that contained them, in this case in the Kodi standard.

[stax76]

@Havokdan

Maybe I understand now what is needed. Currently, there is a text box where you can enter tags in a certain format:

tag name: tag value;...

This feature is better than nothing but it's not powerful nor intuitive, what would be better is a text box with open file dialog picker to define a tag xml file, that's how it works in the mkvtoolnix GUI. Furthermore staxrip could show a grid view where the content of the tag XML file can be edited and last staxrip could automatically convert a found nfo file to a tag xml file. I think that's the right way to do it, what do you think?

[Havokdan]

@Havokdan

Maybe I understand now what is needed. Currently, there is a text box where you can enter tags in a certain format:

tag name: tag value;...

This feature is better than nothing but it's not powerful nor intuitive, what would be better is a text box with open file dialog picker to define a tag xml file, that's how it works in the mkvtoolnix GUI. Furthermore staxrip could show a grid view where the content of the tag XML file can be edited and last staxrip could automatically convert a found nfo file to a tag xml file. I think that's the right way to do it, what do you think?

Well, I'm a humble beggar, whatever can be implemented would be happy and thankful. I just wanted to facilitate this operation, because in my particular situation I have several files that I organized with Tmm (tinymediamanager) that would like to import the covers and information into the file itself. Perhaps by implementing an option that StaxRip would do this automatically, based on criteria, such as being in the same folder and with some names, that would have some default values ​​and could be edited by the user, including using ReGex. :thanks:

[FreaQ]

Hi stax76,

don't know if it was mentioned before, but if I try to encode a file with special characters (ä, ö, ü, ß) the encode fails since 2.0.3.0. In 2.0.2.4 everything is fine.
In 2.0.3.0 the status window freezes but x264 starts but never finishes encoding utilizing 99% of CPU. In 2.0.4.0 i get the following error.

https://abload.de/img/stax2040a8k6w.jpg

As you can see in the log, the special character gets wornlgy converted.


-------------------------- System Environment --------------------------

StaxRip : 2.0.4.0
Windows : Windows 10 Pro 1903
Language : German (Germany)
CPU : Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
GPU : Intel(R) HD Graphics 530, NVIDIA GeForce GTX 950M
Resolution : 1920 x 1080
DPI : 96

------------------------ MediaInfo Source File ------------------------

D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All.ts

General
ID : 1039 (0x40F)
Complete name : D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All.ts
Format : MPEG-TS
File size : 496 MiB
Duration : 14 min 23 s
Overall bit rate mode : Variable
Overall bit rate : 4 819 kb/s

Video
ID : 5421 (0x152D)
Menu ID : 10377 (0x2889)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 4 Ref Frames
Format, CABAC : Yes
Format, Reference frames : 4 frames
Codec ID : 27
Duration : 14 min 23 s
Bit rate : 4 128 kb/s
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 50.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.090
Stream size : 425 MiB (86%)

Audio
ID : 5426 (0x1532)
Menu ID : 10377 (0x2889)
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : 6
Duration : 14 min 22 s
Bit rate mode : Constant
Bit rate : 448 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Delay relative to video : 90 ms
Stream size : 46.1 MiB (9%)
Language : German
Service kind : Complete Main

--------- ffmpeg: Re-mux TS to MKV using ffmpeg 4.2 Wolfberry ---------

D:\_Programme\_Portable\StaxRip.2.0.4.0\Apps\Encoders\ffmpeg\ffmpeg.exe -i "D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All.ts" -c copy -map 0 -ignore_unknown -sn -y -hide_banner "D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All_temp\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All.mkv"

[h264 @ 000001ec3c2ee800] Increasing reorder buffer to 1
[h264 @ 000001ec3c2ee800] Increasing reorder buffer to 2
[mpegts @ 000001ec3c2e7f00] start time for stream 2 is not set in estimate_timings_from_pts
Input #0, mpegts, from 'D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All.ts':
Duration: 00:14:23.00, start: 90545.858756, bitrate: 4820 kb/s
Program 10377
Stream #0:0[0x152d]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], 50 fps, 50 tbr, 90k tbn, 100 tbc
Stream #0:1[0x1532](deu): Audio: ac3 ([6][0][0][0] / 0x0006), 48000 Hz, stereo, fltp, 448 kb/s
Stream #0:2[0x1531](deu): Subtitle: dvb_subtitle ([6][0][0][0] / 0x0006) (hearing impaired)
Output #0, matroska, to 'D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All_temp\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All.mkv':
Metadata:
encoder : Lavf58.29.100
Stream #0:0: Video: h264 (High) (H264 / 0x34363248), yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 50 fps, 50 tbr, 1k tbn, 90k tbc
Stream #0:1(deu): Audio: ac3 ([0] [0][0] / 0x2000), 48000 Hz, stereo, fltp, 448 kb/s
Stream mapping:
Stream #0:0 -> #0:0 (copy)
Stream #0:1 -> #0:1 (copy)
Press [q] to stop, [?] for help
video:442133kB audio:47194kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.118997%

Start: 11:34:10
End: 11:34:14
Duration: 00:00:03

------------------ Demux MKV using mkvextract 37.0.0 ------------------

D:\_Programme\_Portable\StaxRip.2.0.4.0\Apps\Support\MKVToolNix\mkvextract.exe "D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All_temp\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All.mkv" tracks 1:"D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All_temp\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All ID1 89ms German.ac3" --ui-language en

Extracting track 1 with the CodecID 'A_AC3' to the file 'D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All_temp\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All ID1 89ms German.ac3'. Container format: Dolby Digital (AC-3)

Start: 11:34:14
End: 11:34:15
Duration: 00:00:00

General
Complete name : D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All_temp\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All ID1 89ms German.ac3
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
File size : 46.1 MiB
Duration : 14 min 22 s
Overall bit rate mode : Constant
Overall bit rate : 448 kb/s

Audio
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Duration : 14 min 22 s
Bit rate mode : Constant
Bit rate : 448 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 46.1 MiB (100%)
Service kind : Complete Main

------------------------- Error opening source -------------------------

System exception - Access Violation
(D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All_temp\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All_source.avs, line 2)

LoadPlugin("D:\_Programme\_Portable\StaxRip.2.0.4.0\Apps\Plugins\both\L-SMASH-Works\LSMASHSource.dll")
LWLibavVideoSource("D:\Video\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All_temp\Alpha Centauri - S04E13 - Woher kommt unser Wissen übers All.mkv", format = "YUV420P8")

[stax76]

Well, I'm a humble beggar, whatever can be implemented would be happy and thankful. I just wanted to facilitate this operation, because in my particular situation I have several files that I organized with Tmm (tinymediamanager) that would like to import the covers and information into the file itself. Perhaps by implementing an option that StaxRip would do this automatically, based on criteria, such as being in the same folder and with some names, that would have some default values ​​and could be edited by the user, including using ReGex.

I started to work on it.

don't know if it was mentioned before, but if I try to encode a file with special characters (ä, ö, ü, ß) the encode fails since 2.0.3.0. In 2.0.2.4 everything is fine.
In 2.0.3.0 the status window freezes but x264 starts but never finishes encoding utilizing 99% of CPU. In 2.0.4.0 i get the following error.

Hi FreaQ,

I'm not able to reproduce it:

https://pastebin.com/3bbA57M1

Maybe try 2.0.4.2, it uses a HolyWu L-Smash build instead of a MeteorRain build like in 2.0.4.0, if it persists maybe you can upload the file.

[FreaQ]

Hi FreaQ,

I'm not able to reproduce it:

https://pastebin.com/3bbA57M1

Maybe try 2.0.4.2, it uses a HolyWu L-Smash build instead of a MeteorRain build like in 2.0.4.0, if it persists maybe you can upload the file.

Strange.

Tried 2.0.4.2 and it crashed when I hit the start button.

Here is one file.
https://mega.nz/#F!bkkByaIa!6I5p9jkfXCT-oMQljTF9Rw

Happens also with all the others I have with ä, ö or ß.

[Havokdan]

I started to work on it.
:thanks:

[stax76]

Strange.

Tried 2.0.4.2 and it crashed when I hit the start button.

Here is one file.
https://mega.nz/#F!bkkByaIa!6I5p9jkfXCT-oMQljTF9Rw

Happens also with all the others I have with ä, ö or ß.

Thanks for the file, I was able to reproduce it and indeed it seem to be caused by Umlaute, I've reported it in the L-Smash thread.

[stax76]

@FreaQ

It seems it's not the filename but something else, you can still use ffms2 and dgdecnv, the latter is probably the most robust in regard of ts.


@Havokdan

The next build has following improvements:

- a Tag File option has been added to the container/muxer dialog
- container/muxer has a Tags tab with a grid view for tags

For further improvement please create an issue on the tracker, it's too complicated to discuss here.

[Havokdan]

@FreaQ

It seems it's not the filename but something else, you can still use ffms2 and dgdecnv, the latter is probably the most robust in regard of ts.


@Havokdan

The next build has following improvements:

- a Tag File option has been added to the container/muxer dialog
- container/muxer has a Tags tab with a grid view for tags

For further improvement please create an issue on the tracker, it's too complicated to discuss here.
Thank you, I will wait then.

[Patman]

https://github.com/staxrip/staxrip/issues/42#issuecomment-531414479

[stax76]

2.0.4.3 Beta

new AviSynth script CropResize added
update: x265 3.1+15-a092e82 Wolfberry
update: MP4Box 0.8.0-rev69-5fe3ec1 Wolfberry
update: ffmpeg 4.2.1 Wolfberry
update: L-Smash Works 2019-09-14 HolyWu
the filter list in the main dialog shows shorter filter names,
for example 'BicubicResize' instead of 'Resize BicubicResize'
SubtitleEdit is now included
chapterEditor has been integrated into the main menu and
into the container/muxer dialog
a Tag File option has been added to the container/muxer dialog
container/muxer has a Tags tab added with a grid view for editing tags
Kodi nfo files are imported into tags


https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

[Atlantis]

Could you please add a button to StaxRip Help to Check for Updates? Currently we don't get notified if a new stable version is released.

[stax76]

Could you please add a button to StaxRip Help to Check for Updates? Currently we don't get notified if a new stable version is released.

I'm not sure what is the best way to do this, I will look at other apps first to see how they do it.

You could register at github for notifications on stable releases.

https://i.postimg.cc/26HYcJ86/Screenshot-33.png

[NikosD]

2.0.4.1 Beta


nvenc switch --avhw updated (Patman86), --sub-source added Nice catch Patman!

It seems that from NVEncC v4.44 onwards the --avhw cuda switch has been removed, but rigaya forgot to update his help file and change log file in versions v4.44 and v4.45.

So, StaxRip versions 2.0.2.7, 2.0.3.0, 2.0.3.1 using NVEncC v4.44 crash when using NVEnc Cuda option (--avhw cuda switch) because it simply doesn't exist in NVEncC v4.44 .

From NVEncC v4.46 onwards, the help file has been fixed but still rigaya didn't mention anything in his change log, I think.

From StaxRip v2.0.4.1 onwards the NVEnc Cuda option (--avhw cuda switch) has been removed from GUI, so everything is back to normal.

[NikosD]

@stax76

Hey Frank,

I was wondering if there is an easy and not time consuming way for you to identify an Intel processor with disabled iGPU (like my Core i3 9100F) in order to prevent loading Intel based HW decoders like QSVEnc and ffmpeg (Intel) which obviously don't work.

It's a new trend of Intel with those F professors, but not a great deal if it's not feasible.

Thanks!

[Atlantis]

I'm not sure what is the best way to do this, I will look at other apps first to see how they do it.
Didn't the old version have it? Maybe 1.7? Or if I'm not remembering correctly, it had a link to the site. Maybe to put at least a link to the GitHub site in the software itself.

[stax76]

@stax76

Hey Frank,

I was wondering if there is an easy and not time consuming way for you to identify an Intel processor with disabled iGPU (like my Core i3 9100F) in order to prevent loading Intel based HW decoders like QSVEnc and ffmpeg (Intel) which obviously don't work.

It's a new trend of Intel with those F professors, but not a great deal if it's not feasible.

Thanks!

Hello Nikos,

it's possible to query which GPUs are present, I get a caption for each GPU from WMI, if there is only one caption and it contains AMD or NVIDIA than there can not be an Intel GPU.

If you are referring to the Decoder dropdown, I don't know if it is easy to hide or disable items in this dropdown, both together will be some work, I don't mind if you create a ticket for it.

Didn't the old version have it? Maybe 1.7? Or if I'm not remembering correctly, it had a link to the site. Maybe to put at least a link to the GitHub site in the software itself.

Nothing I remember (I have bad memory though), first steps would be 1. creating a ticket and 2. some discussion happening in this ticket.

An automatic update is probably not easy to build and maintain but a notification that opens the download page might not be so hard and very useful. I don't mind a ticket for this either and there are also not many open tickets, I mean issues.

[NikosD]

Hello Nikos,



it's possible to query which GPUs are present, I get a caption for each GPU from WMI, if there is only one caption and it contains AMD or NVIDIA than there can not be an Intel GPU.



If you are referring to the Decoder dropdown, I don't know if it is easy to hide or disable items in this dropdown, both together will be some work, I don't mind if you create a ticket for it. You can actually have both cards active (iGPU + discrete card) and use them easily in Windows 10.
But in this case you can obviously use QSVEncC, so no problem.
Yes, I'm talking about the decoder drop-down because my CPU has no iGPU but I can see QSVenc decoder.
I'll try to create a ticket.
Thanks!

[FreaQ]

@FreaQ

It seems it's not the filename but something else, you can still use ffms2 and dgdecnv, the latter is probably the most robust in regard of ts.

With FFVideoSource it worked.

[Patman]

Hello everybody. Unfortunately the dxva2 function can not be used in the current version of staxrip. This is due to the included Wolfberry version of ffmpeg. In this the hardware acceleration dxva2 is disabled. Here is a link to my version.

https://github.com/staxrip/staxrip/issues/43#issuecomment-531877274

[stax76]

Can someone with Intel GPU tell me what following PowerShell command prints:

Get-WmiObject -class Win32_VideoController | Select-Object Caption

[NikosD]

Can someone with Intel GPU tell me what following PowerShell command prints:



Get-WmiObject -class Win32_VideoController | Select-Object Caption On my Win 10 machine using a Core i5-6500 gave me this:
Caption
-------
Intel(R) HD Graphics 530
Perfect!

[stax76]

@NikosD

Thanks, the Intel drop down items should now be hidden.

2.0.4.4 Beta

fix: nfo files with non xml content caused an exception
fix: if subtitle and audio titles contained illegal
file system characters then these characters were replaced
with an underscore and thus being lost, now the characters
are escaped/unescaped and thus preserved
fix: update x265 switch --refine-mv
fix: in the nvenc dialog, Intel decoding options were present
even when no Intel GPU is present
new: a link to the web site has been added to the menu
new: option to check online for new stable version once per day
new: avs plugin HDRTools
new: avs, vs plugin DGHDRtoSDR
new: ffms2 parameter colorspace has menu support in the avs code editor


https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

[NikosD]

2.0.4.4 Beta

fix: in the nvenc dialog, Intel decoding options were present
even when no Intel GPU is present
I can't test right now the fix because I have no discrete GPU here, but I tried the opposite.

I have a PC with no discrete GPU - only Intel's iGPU - but I can choose nVidia H.264 & H.265 encoders or AMD H.264 & H.265 encoders from the first screen and I can see the decoders too in the drop-down of course.

Now that you have the ability to hide options depending on the presence or not of an iGPU, maybe it would be useful the opposite too.

To hide nVidia's and AMD's encoders and decoders for systems with no discrete cards.

[stax76]

I can't test right now the fix because I have no discrete GPU here, but I tried the opposite.

I have a PC with no discrete GPU - only Intel's iGPU - but I can choose nVidia H.264 & H.265 encoders or AMD H.264 & H.265 encoders from the first screen and I can see the decoders too in the drop-down of course.

Now that you have the ability to hide options depending on the presence or not of an iGPU, maybe it would be useful the opposite too.

To hide nVidia's and AMD's encoders and decoders for systems with no discrete cards.

In the main window, it's useful to see that staxrip supports these encoders and how the options look like, users can customize several types of profiles directly from the menus, choose 'Edit Profiles'.

[NikosD]

Hello everybody. Unfortunately the dxva2 function can not be used in the current version of staxrip.Right. Here is a link to my version.
https://github.com/staxrip/staxrip/issues/43#issuecomment-531877274Works like a charm.

2.0.4.4 Beta

fix: in the nvenc dialog, Intel decoding options were present
even when no Intel GPU is present

Fixed.In the main window, it's useful to see that staxrip supports these encoders and how the options look like, users can customize several types of profiles directly from the menus, choose 'Edit Profiles'. Fair enough!

[Patman]

Works like a charm.

Thank you for downloading and using my files.

In the main window, it's useful to see that staxrip supports these encoders and how the options look like, users can customize several types of profiles directly from the menus, choose 'Edit Profiles'.

What do you think about a button that detects GPU's and shows only the encoders which are supported by the GPU/GPU's? Without pressing button nothing happend. All encoders and options are shown. Only an idea :p

[chipxtreme]

NVEnc 4.48 is out

[Natty]

need GUI for --selective-sao options in x265. it enables --sao directly if not set to zero. eg- --selective-sao 0

[Patman]

NVEnc 4.48 is out

https://github.com/staxrip/staxrip/issues/58

need GUI for --selective-sao options in x265. it enables --sao directly if not set to zero. eg- --selective-sao 0

https://github.com/staxrip/staxrip/issues/60

[stax76]

NVEnc 4.48 is out

Will be included in the next build, thanks.

need GUI for --selective-sao options in x265. it enables --sao directly if not set to zero. eg- --selective-sao 0

GUI support will be available in the next build, I hope Wolfberry makes a new build.

[ZeroCool22]

Will be included in the next build, thanks.


I can update manually the NVEnc on the StaxRip-x64-2.0.4.4-beta or it will cause some problem?

[Z'Hadum]

One Short Question:
I recently upgraded to 2.0.4 from 2.0.2:
With the new Version I get the following error from eac3to:

Audio encoding 1 using eac3to 3.34 failed with exit code: -1073741515 (0xC0000135)

The exit code might be a system error code: The program can't start because hs is missing from your computer. Try reinstalling the program to fix this problem.

What is "hs"?
I think I have to reinstall something?

Thx in advance! :thanks:

[Patman]

I can update manually the NVEnc on the StaxRip-x64-2.0.4.4-beta or it will cause some problem?Yes you can do that. No problems are caused by this method.

Gesendet von meinem HMA-L09 mit Tapatalk

[Patman]

One Short Question:
I recently upgraded to 2.0.4 from 2.0.2:
With the new Version I get the following error from eac3to:

Audio encoding 1 using eac3to 3.34 failed with exit code: -1073741515 (0xC0000135)

The exit code might be a system error code: The program can't start because hs is missing from your computer. Try reinstalling the program to fix this problem.

What is "hs"?
I think I have to reinstall something?

Thx in advance! :thanks:

Hi Z'Hadum,

this could be due to Microsoft Visual C ++ and .Net Framework. Update both and give notice again. Since version 2.0.2.6 .Net-Framework 4.8 is used in Staxrip.

[stax76]

@Z'Hadum

Please post the command line used by eac3to and mediainfo of the input file, both can be found in the log file, maybe post the full log file on pastebin.

You can also try downloading an old staxrip version and then use the eac3to files from there, few weeks ago two eac3to libraries were updated, I think it was flac and dts.

[JKyle]

NVEnc 4.49 is released today.

[Patman]

Hi @ all,

I've updated my builds of MP4Box, x265 and ffmpeg (with dxva2 support). For these who are intresteted.

Builds (http://www.mediafire.com/folder/vkt2ckzjvt0qf/StaxRip_Tools)

[JKyle]

Hi @ all,

I've updated my builds of MP4Box, x265 and ffmpeg (with dxva2 support). For these who are intresteted.

Builds (http://www.mediafire.com/folder/n3i63ycbsm1avc9,k4q0tpatqrbesm1,7uburgmezbw5lkm,19e41n4fvfi7phi/shared)

Wow! Thanks for sharing your assets. :)
I decided to use your MP4Box instead of Wolfberry's 'cuz Wolfberry's seems to insert an unwanted build number into the video stream metadata of the output mp4 file.

https://i.imgur.com/twwAWUM.jpg

I pm'ed Wolfberry but I don't know when he will fix it.

BTW, your version of ffmpeg is very slim compared to the Wolfberry built ffmpeg, which is more than 90MiB in size.
Can you please explain what makes the big difference?

Thanks.

[ZeroCool22]

When it comes to reduce the size of the video using H265 i have a doubt, i already have my config done but sometimes the resulting video size is a little more bigger than what i would wish.

So the only way to get a more low size video is playing with the quality sliders, but Staxrip is not like other converters that have 1 quality slider, it have 3, so here is my question, i should increase the 3 sliders or only play with 1 of them?

https://i.ibb.co/m5RZZKc/Screenshot-20.jpg

Thx in advance!

[sneaker_ger]

You would increase all of them. (Usually you would keep the factors between them constant.)


P.S.: It seems you cannot select e.g. --vbrhq 0 --vbr-quality <float> in StaxRip. It always sets --vbrhq 7677.

[JKyle]

P.S.: It seems you cannot select e.g. --vbrhq 0 --vbr-quality <float> in StaxRip. It always sets --vbrhq 7677.

I already brought up that issue, and I guess Stax or Revan has a plan for that in the future.

See this (https://github.com/staxrip/staxrip/issues/17).

[Patman]

I pm'ed Wolfberry but I don't know when he will fix it.
I sent Wolfberry pm too. But no reaction till now.

BTW, your version of ffmpeg is very slim compared to the Wolfberry built ffmpeg, which is more than 90MiB in size.
Can you please explain what makes the big difference?


Wolfberry's build have a lot of external libraries included. My version based on zeranoe builds + openal, opencl, opengl, vapoursynth and cuda-nvcc. Final size of my build is about 65 MB. After compiling i compress my files with upx, so the filesizes are like now. You can also see it by the filesize of x264 and x265. Until now, i had no problems with the compressed files during my encodes/decodes.

[stax76]

I already brought up that issue, and I guess Stax or Revan has a plan for that in the future.

See this (https://github.com/staxrip/staxrip/issues/17).

I've bookmarked it, it looks like there is more than one issue and likely they are not easy to solve.

[ZeroCool22]

You would increase all of them. (Usually you would keep the factors between them constant.)


P.S.: It seems you cannot select e.g. --vbrhq 0 --vbr-quality <float> in StaxRip. It always sets --vbrhq 7677.

Thank you.

I tried VBR, it's good to get low size, but i notice pixelation in fast movement scenes.

So i just keep with CQP.

[JKyle]

Wolfberry's build have a lot of external libraries included. My version based on zeranoe builds + openal, opencl, opengl, vapoursynth and cuda-nvcc. Final size of my build is about 65 MB. After compiling i compress my files with upx, so the filesizes are like now. You can also see it by the filesize of x264 and x265. Until now, i had no problems with the compressed files during my encodes/decodes.

Awesome! I'll be using your builds instead of the default Wolfberry builds, and see if I can provide any feedback for you.

Thank you again. :)

[Atlantis]

I encoded an HDR mp4 and it seems the HDR flags are not passed.

This is the original file
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom)
File size : 724 MiB
Duration : 1 min 23 s
Overall bit rate mode : Variable
Overall bit rate : 73.1 Mb/s
Encoded date : UTC 2016-10-24 05:40:14
Tagged date : UTC 2016-10-24 05:40:14

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 1 min 23 s
Bit rate : 72.9 Mb/s
Maximum bit rate : 94.2 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.147
Stream size : 722 MiB (100%)
Encoded date : UTC 2016-10-24 06:37:11
Tagged date : UTC 2016-10-24 05:40:23
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : R: x=1.000000 y=1.000000, G: x=1.000000 y=1.000000, B: x=1.000000 y=1.000000, White point: x=1.000000 y=1.000000
Mastering display luminance : min: 0.1000 cd/m2, max: 1 cd/m2
Codec configuration box : hvcC

This is what Staxrip 2.0.4 gives
ormat : Matroska
Format version : Version 4
File size : 253 MiB
Duration : 1 min 23 s
Overall bit rate : 25.5 Mb/s
Encoded date : UTC 2019-09-21 09:45:52
Writing application : mkvmerge v37.0.0 ('Leave It') 64-bit
Writing library : libebml v1.3.9 + libmatroska v1.5.2
Writing frontend : StaxRip v2.0.4.0

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5.1@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 1 min 23 s
Bit rate : 25.3 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.051
Stream size : 251 MiB (99%)
Writing library : x265 3.1+11-de920e0a3183:[Windows][GCC 9.1.1][64 bit] 10bit
Encoding settings : rc=crf / crf=18.0000 / qcomp=0.60 / qpstep=4 / qpmax=69 / qpmin=0 / no-lossless / no-cu-lossless / ipratio=1.40 / pbratio=1.30 / aq-mode=2 / aq-strength=1.00 / psy-rd=2.00 / psy-rdoq=0.00 / rdoq-level=0 / cbqpoffs=0 / crqpoffs=0 / ctu=64 / min-cu-size=8 / ref=3 / limit-refs=1 / no-limit-modes / me=1 / subme=2 / merange=57 / no-hme / rd=3 / no-rd-refine / no-ssim-rd / rdpenalty=0 / deblock=0:0 / min-keyint=25 / keyint=250 / bframes=4 / bframe-bias=0 / b-adapt=2 / b-intra / b-pyramid / cutree / max-merge=3 / no-fades / weightp / no-weightb / no-rect / no-amp / sao / no-limit-sao / no-sao-non-deblock / early-skip / no-splitrd-skip / rskip / no-tskip / no-tskip-fast / no-fast-intra / scenecut=40 / scenecut-bias=0.05 / rc-lookahead=20 / gop-lookahead=0 / lookahead-slices=8 / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / qg-size=32 / radl=0 / open-gop / no-hevc-aq / no-aq-motion / no-dynamic-refine / dynamic-rd=0.00 / nr-intra=0 / nr-inter=0 / strong-intra-smoothing / no-constrained-intra / no-strict-cbr / no-const-vbv / no-rc-grain / wpp / no-pmode / no-pme / no-psnr / no-ssim / signhide / stats-write=0 / stats-read=0 / zone-count=0 / input-csp=1 / input-res=3840x2160 / interlace=0 / total-frames=4980 / frame-threads=3 / level-idc=0 / high-tier=1 / uhd-bd=0 / no-analyze-src-pics / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd / info / hash=0 / temporal-mvp / no-temporal-layers / no-splice / no-intra-refresh / sar=0 / overscan=0 / videoformat=5 / range=0 / colorprim=9 / transfer=16 / colormatrix=9 / chromaloc=0 / display-window=0cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / no-opt-cu-delta-qp / no-hdr / no-hdr-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=0 / refine-ctu-distortion=0 / refine-analysis-type=0 / ctu-info=0 / copy-pic=1 / max-ausize-factor=1.0 / no-single-sei / no-svt / no-field / no-lowpass-dct / cpuid=1111039 / numa-pools=8 / log-level=2 / qp-adaptation-range=1.00
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant

[Atlantis]

Here is the original file:
https://uhdsample.com/43-download-sony-bravia-make-glass-oled-4k-uhd-hdr10-60-fps-demo-video.html

[NikosD]

Here is a link to my version.

https://github.com/staxrip/staxrip/issues/43#issuecomment-531877274 I've updated my builds of MP4Box, x265 and ffmpeg (with dxva2 support). For these who are intresteted.

Builds (http://www.mediafire.com/folder/n3i63ycbsm1avc9,k4q0tpatqrbesm1,7uburgmezbw5lkm,19e41n4fvfi7phi/shared)

@stax76

Hello @Patman.

I replied earlier that ffmpeg DXVA2 worked like a charm and indeed, using my GTX 1660, the performance and CPU usage of ffmpeg DXVA2 was like NVEnc Hardware.

But using my older Haswell system with no discrete card, just the iGPU, both "ffmpeg Intel" and "ffmpeg DXVA2" options inside StaxRip give me very bad results using both versions of ffmpeg (65MB and 20MB)

The ffmpeg Intel option has 25% CPU usage for ffmpeg.exe + 10% CPU usage for QSVEncC = 35% CPU with highest CPU clock and 80% slower FPS than "QSVEnc Hardware" option.

The ffmpeg DXVA2 options has 25% CPU usage for ffmpeg.exe + 25% CPU usage for QSVEncC = 50% CPU with highest clock and 40% slower FPS than QSVEnc Hardware option

I think both ffmpeg Intel and DXVA2 use DXVA2 copy-back mode instead of DXVA2 native and that could be the reason of very high CPU usage and slow FPS performance.

QSVEnc Hardware has lowest CPU clock during encoding and very low total CPU usage ~8% which is normal for DXVA2 native mode, along with highest FPS performance of course.

@Patman

Could you check if there is an option during compilation of ffmpeg for Intel hardware decoding regarding DXVA2 mode ?

Thanks!

[JKyle]

I encoded an HDR mp4 and it seems the HDR flags are not passed.

AFAIK, the default x265 encoder included with 2.0.4 is Wolfberry's build and it's already reported to rearrange the order of 'Encoding Settings' metadata in the video stream.

See here (https://forum.doom9.org/showthread.php?p=1884691#post1884691).

My guess is that the HDR flags are missing in the course of tweaking the metadata.

Why don't you try Patman's x265 and see if the same problem occurs?

See here (https://forum.doom9.org/showthread.php?p=1885316#post1885316).

[JKyle]

Maybe rigaya is in full gear these days.
It's only three days since he released 4.49 but today he released 4.50 again. :)

[Atlantis]

I like the order of the new stuff
rc=crf / crf=17.0000 / qcomp=0.60 / qpstep=4 / vbv-maxrate=160000 / vbv-bufsize=160000 / vbv-init=0.9 / ...

CRF at the beginning is great because it's the most important parameter that you might want to check and now I can see it at the beginning. I remember it was like this once before too.
Maybe it was Staxrip 2.0.2 or some other previous version.

[JKyle]

Hi @ all,

I've updated my builds of MP4Box, x265 and ffmpeg (with dxva2 support). For these who are intresteted.

Builds (http://www.mediafire.com/folder/n3i63ycbsm1avc9,k4q0tpatqrbesm1,7uburgmezbw5lkm,19e41n4fvfi7phi/shared)

Unfortunately, your build of MP4Box seems to generate the same unnecessary 'Title' metadata for the final video stream.

https://i.imgur.com/JTn9W3C.jpg

Now I highly suspect that it is an issue inherent in the MP4Box source. :(

[JKyle]

I like the order of the new stuff
rc=crf / crf=17.0000 / qcomp=0.60 / qpstep=4 / vbv-maxrate=160000 / vbv-bufsize=160000 / vbv-init=0.9 / ...

CRF at the beginning is great because it's the most important parameter that you might want to check and now I can see it at the beginning. I remember it was like this once before too.
Maybe it was Staxrip 2.0.2 or some other previous version.

I agree. As long as it does not make any mess or omission in the metadata, of course.

[Patman]

Unfortunately, your build of MP4Box seems to generate the same unnecessary 'Title' metadata for the final video stream.

https://i.imgur.com/JTn9W3C.jpg

Now I highly suspect that it is an issue inherent in the MP4Box source. :(

Hi JKyle,
that issue is related to mp4box. It's standard if no Tracktitle is set. I've run the mux process in command line with the parameter 'name:00009' after videoinput file and these is written to the title info.

https://i.imgur.com/5NlnIk6.png

The container options for MP4Box must be adapted like those for mkv and webm.

[imhh11]

I encoded an HDR mp4 and it seems the HDR flags are not passed.

This is the original file


probably because your HDR10 source got incomplete/incorrect metadata.

never seen metadata like this on any of the HDR10 file I have.

Mastering display color primaries : R: x=1.000000 y=1.000000, G: x=1.000000 y=1.000000, B: x=1.000000 y=1.000000, White point: x=1.000000 y=1.000000
Mastering display luminance : min: 0.1000 cd/m2, max: 1 cd/m2

you file should still trigger HDR10 since PQ is still there (--transfer smpte2084)

[-QfG-]

Here is the original file:
https://uhdsample.com/43-download-sony-bravia-make-glass-oled-4k-uhd-hdr10-60-fps-demo-video.html

Enter this Line in your CUSTOM Section, for Display P3 D65 HDR10:

--hdr --output-depth 10 --hdr-opt --max-cll "1000,400" --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)"

EDIT:
--max-cll "1000,400"
L(10000000,1)

You can see this values with "MediaInfo" from your source file.

With my little HDR Parser tool u must use this settings:
https://s17.directupload.net/images/190922/9tfvf63y.png

--hdr --output-depth 10 --hdr-opt --master-display "G(50000,50000)B(50000,50000)R(50000,50000)WP(50000,50000)L(5000,1000)"

[sneaker_ger]

He can't see these exact values for his speficic source file because like imhh11 said this file's ("Sony Bravia OLED 4K Demo.mp4") mastering display color primaries and luminance metadata values are bogus. (Though this does not yet explain why StaxRip didn't transfer the metadata to the output.)

[-QfG-]

Problem with the filename (the tool is in beta). Renaming and working, correct values now in the post.

[Atlantis]

you file should still trigger HDR10 since PQ is still there (--transfer smpte2084)

Yes it does trigger the HDR in players. I just don't see it in MediaInfo.
I need it to be recognized as HDR in MediaInfo. For easy checking and organization of my files on PC.

[Atlantis]

Where can I get your HDR Parser tool?

[Atlantis]

I just found out that in StaxRip there is
Apps->Media Info->Ingest HDR.

When I use it, I see these added in MediaInfo

HDR format : SMPTE ST 2086, HDR10 compatible
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0100 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000
Maximum Frame-Average Light Level : 300

Is this enough and correct? It will always add the same value?

[-QfG-]

Where can I get your HDR Parser tool?

It's still for personality usage and in beta status. Too many bugs, for an official release. Also it works only with a graphics card from Nvidea, GeForce GTX 1050 or higher.

HDR format : SMPTE ST 2086, HDR10 compatible
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0100 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000
Maximum Frame-Average Light Level : 300

--hdr --output-depth 10 --hdr-opt --max-cll "1000,300" --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,100)"

This line for your HDR10 Metadata.

Maximum Content Light Level : 1000 Maximum Frame-Average Light Level : 300 = --max-cll "1000,300"
Mastering display color primaries : Display P3 = --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)
Mastering display luminance : min: 0.0100 cd/m2, max: 1000 cd/m2 = L(10000000,100)

Examples:

Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2 = L(10000000,1)
Mastering display luminance : min: 0.0010 cd/m2, max: 1000 cd/m2 = L(10000000,10)

[NikosD]

Hi NikosD,

thanks for doing a test. Then it can either be the file or a compatibility issue with the hardware. I reported the problem. It's been almost three weeks since you reported the issue to rigaya, but he needs a not working VC-1 sample in order to work on it.
Because generally speaking, VC-1 HW decoding is working for all his transcoders (Intel, AMD, nVidia)
He needs the specific file that doesn't work with QSVEnc HW decoder.

Cheers.

[Patman]

@stax76

Hello @Patman.

I replied earlier that ffmpeg DXVA2 worked like a charm and indeed, using my GTX 1660, the performance and CPU usage of ffmpeg DXVA2 was like NVEnc Hardware.

But using my older Haswell system with no discrete card, just the iGPU, both "ffmpeg Intel" and "ffmpeg DXVA2" options inside StaxRip give me very bad results using both versions of ffmpeg (65MB and 20MB)

The ffmpeg Intel option has 25% CPU usage for ffmpeg.exe + 10% CPU usage for QSVEncC = 35% CPU with highest CPU clock and 80% slower FPS than "QSVEnc Hardware" option.

The ffmpeg DXVA2 options has 25% CPU usage for ffmpeg.exe + 25% CPU usage for QSVEncC = 50% CPU with highest clock and 40% slower FPS than QSVEnc Hardware option

I think both ffmpeg Intel and DXVA2 use DXVA2 copy-back mode instead of DXVA2 native and that could be the reason of very high CPU usage and slow FPS performance.

QSVEnc Hardware has lowest CPU clock during encoding and very low total CPU usage ~8% which is normal for DXVA2 native mode, along with highest FPS performance of course.

@Patman

Could you check if there is an option during compilation of ffmpeg for Intel hardware decoding regarding DXVA2 mode ?

Thanks!

Hi NikosD,

I did some tests at the weekend with ffmpeg and the options Intel and dxva2. My results were similar to yours, whether I used mine, wolfberry's or the official build. Only dxva2 in conjunction with nvidia works with a decent load on the GPU. I found a statement that dxva2 native is used in ffmpeg. This is peculiar.

It's been almost three weeks since you reported the issue to rigaya, but he needs a not working VC-1 sample in order to work on it.
Because generally speaking, VC-1 HW decoding is working for all his transcoders (Intel, AMD, nVidia)
He needs the specific file that doesn't work with QSVEnc HW decoder.

Cheers.

I will post a link so that rigaya can perform appropriate tests.

[Z'Hadum]

Hello,
sorry for the late reply. I was a little busy.
Hi Z'Hadum,

this could be due to Microsoft Visual C ++ and .Net Framework. Update both and give notice again. Since version 2.0.2.6 .Net-Framework 4.8 is used in Staxrip.
.net 4.8 is installed and c++ runtimes also (all that staxrip lists in the app section.)

@Z'Hadum

Please post the command line used by eac3to and mediainfo of the input file, both can be found in the log file, maybe post the full log file on pastebin.

You can also try downloading an old staxrip version and then use the eac3to files from there, few weeks ago two eac3to libraries were updated, I think it was flac and dts.

Thank you for your help:
indeed, it seems to happen to dts sources

I will try to copy eac3to from the old version to the new one.

Here is the eac3to part from the Logfile:

--------------- Error Audio encoding 1 using eac3to 3.34 ---------------

Audio encoding 1 using eac3to 3.34 failed with exit code: -1073741515 (0xC0000135)

The exit code might be a system error code: The program can't start because hs is missing from your computer. Try reinstalling the program to fix this problem.


------------------ Audio encoding 1 using eac3to 3.34 ------------------

C:\StaxRip-x64-2.0.4.0-stable\Apps\Audio\eac3to\eac3to.exe "N:\ShareTest\Source\test_temp\test ID1 German.dtshd" "N:\ShareTest\Source\test_temp\test ID1 German_a1.m4a" -quality=0.8 -progressnumbers


------------------ Audio encoding 1 using eac3to 3.34 ------------------

C:\StaxRip-x64-2.0.4.0-stable\Apps\Audio\eac3to\eac3to.exe "N:\ShareTest\Source\test_temp\test ID1 German.dtshd" "N:\ShareTest\Source\test_temp\test ID1 German_a1.m4a" -quality=0.8 -progressnumbers

Start: 08:41:37
End: 08:41:37
Duration: 00:00:00


:thanks: Z'Hadum

[NikosD]

Hi NikosD,

I did some tests at the weekend with ffmpeg and the options Intel and dxva2. My results were similar to yours, whether I used mine, wolfberry's or the official build. Only dxva2 in conjunction with nvidia works with a decent load on the GPU. I found a statement that dxva2 native is used in ffmpeg. This is peculiar. Hmm... Interesting.
The results show that they are not using a direct, native mode of DXVA2 but some form of copy-back.
I don't know if you have access to other documentation or ffmpeg developers in order to find out what's happening.
I will post a link so that rigaya can perform appropriate tests. That's good, I hope rigaya to see the update in ticket.

[Z'Hadum]

indeed, it seems to happen to dts sources

I will try to copy eac3to from the old version to the new one.

Here is the eac3to part from the Logfile:

--------------- Error Audio encoding 1 using eac3to 3.34 ---------------

Audio encoding 1 using eac3to 3.34 failed with exit code: -1073741515 (0xC0000135)

The exit code might be a system error code: The program can't start because hs is missing from your computer. Try reinstalling the program to fix this problem.


------------------ Audio encoding 1 using eac3to 3.34 ------------------

C:\StaxRip-x64-2.0.4.0-stable\Apps\Audio\eac3to\eac3to.exe "N:\ShareTest\Source\test_temp\test ID1 German.dtshd" "N:\ShareTest\Source\test_temp\test ID1 German_a1.m4a" -quality=0.8 -progressnumbers


------------------ Audio encoding 1 using eac3to 3.34 ------------------

C:\StaxRip-x64-2.0.4.0-stable\Apps\Audio\eac3to\eac3to.exe "N:\ShareTest\Source\test_temp\test ID1 German.dtshd" "N:\ShareTest\Source\test_temp\test ID1 German_a1.m4a" -quality=0.8 -progressnumbers

Start: 08:41:37
End: 08:41:37
Duration: 00:00:00




In addition:
with the eac3to version from 2.0.2.0 it is working. May be the eac3to version in 2.0.4.0 is not ok. Can you check this?
:thanks:

[stax76]

@Z'Hadum

DTSMA and DTSX input works here on Win 10 1903, I don't have a DTSHR sample, please post MediaIinfo for the input file.

According to Dependency Walker libdcadec.dll depends on VCRUNTIME140.DLL, that is Visual C++ 2017.

[Z'Hadum]

@Z'Hadum

DTSMA and DTSX input works here on Win 10 1903, I don't have a DTSHR sample, please post MediaIinfo for the input file.

According to Dependency Walker libdcadec.dll depends on VCRUNTIME140.DLL, that is Visual C++ 2017.

Hmm, Staxrip says, that the status of Visual C++ Runtime 2017 is ok.

All Files where I tried to convert the Audio to AAC eac3to crashed with the new version. Most of the time I do this with DTS-HD Sources.

As a workaround, I copied the old eac3to from Staxrip 2.0.2.0 to 2.0.4.0. This works for me. I think I am missing some kind of dll.
If it is not VC++2017 is there any other that only eac3to uses?
Or should I try to reinstall VC++2017?



General
Format : Matroska
Format version : Version 2
File size : 11.2 GiB
Duration : 1 h 18 min
Overall bit rate mode : Variable
Overall bit rate : 20.4 Mb/s
Movie name : Test
Writing application : MakeMKV v1.14.5 win(x64-release)
Writing library : libmakemkv v1.14.5 (1.3.5/1.4.7) win(x64-release)

Video
ID : 1
ID in the original source medium : 4113 (0x1011)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.1
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Format settings, GOP : M=3, N=18
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 h 18 min
Bit rate mode : Variable
Bit rate : 18.0 Mb/s
Maximum bit rate : 28.0 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 24.000 FPS
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.362
Stream size : 9.85 GiB (88%)
Language : English
Default : No
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Original source medium : Blu-ray

Audio
ID : 2
ID in the original source medium : 4352 (0x1100)
Format : DTS XLL
Format/Info : Digital Theater Systems
Commercial name : DTS-HD Master Audio
Codec ID : A_DTS
Duration : 1 h 18 min
Bit rate mode : Variable
Bit rate : 2 407 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 93.750 FPS (512 SPF)
Bit depth : 16 bits
Compression mode : Lossless
Stream size : 1.32 GiB (12%)
Title : Surround 5.1
Language : German
Default : Yes
Forced : No
Original source medium : Blu-ray

Text #1
ID : 3
ID in the original source medium : 4608 (0x1200)
Format : PGS
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 10 s 813 ms
Bit rate : 50.4 kb/s
Count of elements : 4
Stream size : 66.5 KiB (0%)
Language : German
Default : No
Forced : No
Original source medium : Blu-ray

Text #2
ID : 5
ID in the original source medium : 4609 (0x1201)
Format : PGS
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 1 h 13 min
Bit rate : 38.8 kb/s
Count of elements : 1545
Stream size : 20.4 MiB (0%)
Language : German
Default : No
Forced : No
Original source medium : Blu-ray

Menu
00:00:00.000 : en:Chapter 01
00:05:26.708 : en:Chapter 02
00:11:05.291 : en:Chapter 03
00:15:13.083 : en:Chapter 04
00:19:27.916 : en:Chapter 05
00:25:51.875 : en:Chapter 06
00:29:00.958 : en:Chapter 07
00:36:10.291 : en:Chapter 08
00:45:43.875 : en:Chapter 09
00:51:26.250 : en:Chapter 10
00:59:47.166 : en:Chapter 11
01:08:55.375 : en:Chapter 12
01:13:27.083 : en:Chapter 13


:thanks:

[stax76]

@Z'Hadum

Thanks for the log. At least you should keep in mind there could be something broken on your system, or there is something wrong with the library. I have tried to google it but found nothing specific apart from that the problem occurred most often about 5 years ago, so I assume it's Win 7 specific. It would be helpful if other Win 7 users confirm that it's not a general issue. If more people report it I'll just revert the library, it was updated due to a user requests, I think I had compiled it myself.

[Natty]

try this
https://github.com/abbodi1406/vcredist/releases/

[Z'Hadum]

@Z'Hadum

Thanks for the log. At least you should keep in mind there could be something broken on your system, or there is something wrong with the library. I have tried to google it but found nothing specific apart from that the problem occurred most often about 5 years ago, so I assume it's Win 7 specific. It would be helpful if other Win 7 users confirm that it's not a general issue. If more people report it I'll just revert the library, it was updated due to a user requests, I think I had compiled it myself.

I'm not using win7, I'm on Win10 and had the same issue on a second testing environment with Win Server 2016.

I also think, that I'm missing some kind of dll. But the Question is which one :confused:;)

[Z'Hadum]

try this
https://github.com/abbodi1406/vcredist/releases/

Hi,
many thx. This helped. It seems this package installs all available VC++ Runtimes ?

:thanks:

[Natty]

Hi,
many thx. This helped. It seems this package installs all available VC++ Runtimes ?

:thanks:

yes it's a full fat pack

[Natty]

Hi @ all,

I've updated my builds of MP4Box, x265 and ffmpeg (with dxva2 support). For these who are intresteted.

Builds (http://www.mediafire.com/folder/n3i63ycbsm1avc9,k4q0tpatqrbesm1,7uburgmezbw5lkm,19e41n4fvfi7phi/shared)

great job, this ffmpeg is running atleast 2x faster :thanks:

[ZeroCool22]

H.265/HEVC isn't supported by the graphics card. (I have a 1080 TI)

PC Specs:

I7 77OOK | CORSAIR 32 GB | MSI GTX 1080TI 11GB GAMING X.

Nvidia Drivers: 436.15 STANDARD - Game Ready.

Version of the program: StaxRip-x64-**x64-2.0.4.4-beta

NVEnc Version: 4.50_x64

https://i.ibb.co/0nZZqx1/Screenshot-7.png

I only have this problem when use a version of NVEnc above of 4.48 x64, with 4.48 everything works fine:

https://i.ibb.co/P5JQwq5/Screenshot-8.png

Full Log: https://pastebin.com/0pip7jqi

[JKyle]

Hi JKyle,
that issue is related to mp4box. It's standard if no Tracktitle is set. I've run the mux process in command line with the parameter 'name:00009' after videoinput file and these is written to the title info.

The container options for MP4Box must be adapted like those for mkv and webm.

Hi.

Thanks for your advice.

After more study, I've come to the conclusion that this "bug" arises from MediaInfo, not from MP4Box.

Look at this mp4 file which was encoded in late June.

https://i.imgur.com/HHNNdxP.jpg

MediaInfo 19.09 shows this 'Title' metadata on the video stream, which didn't appear in previous versions.

OTOH, MediaInfoXP 2.35, another MediaInfo GUI based on MediaInfo 19.07, does not show this.

https://i.imgur.com/WHaH90A.jpg

Well, is this a "bug"?
Or have they decided that displaying 'Title' metadata on the video stream is more appropiate than not?
If the latter is the case, do I have to set the 'Title' metadata everytime I mux an mp4 file?

I have no idea. :(

[Patman]

Hi.
Well, is this a "bug"?
Or have they decided that displaying 'Title' metadata on the video stream is more appropiate than not?
If the latter is the case, do I have to set the 'Title' metadata everytime I mux an mp4 file?
I have no idea. :(

Thank you for the information. I looked at mediainfo's changelog but didn't find metadata information for the (video) title. The default for mp4 files in the next Staxrip build is that this title is tagged as "blank". This results in the title not being displayed. If you want to display the title you have to enter the titel in staxrip.

[Patman]

great job, this ffmpeg is running atleast 2x faster :thanks:

Thanks for your positive feedback. I want to update my builds weekly.

[Patman]

H.265/HEVC isn't supported by the graphics card. (I have a 1080 TI)

https://i.ibb.co/P5JQwq5/Screenshot-8.png

Full Log: https://pastebin.com/0pip7jqi

The codec option is wrong. --codec h265 must be changed to --codec hevc. This should work.

Update:

Not wrong option, my mistake! I've used your settings with NVEnc 4.50 and everything works fine. Option --codec h265 is ok, --codec hevc can be used as alternative.

[sneaker_ger]

--codec h265 works here. It's not mentioned in the readme but it is via nvencc.exe -h

[-QfG-]

Hi.

Thanks for your advice.

Well, is this a "bug"?
Or have they decided that displaying 'Title' metadata on the video stream is more appropiate than not?
If the latter is the case, do I have to set the 'Title' metadata everytime I mux an mp4 file?

I have no idea. :(

This is no Bug. The field "Title" means, what they say. This is not Metadata from HDR, this is just simply the title of this track. No idea why MediaInfoXP don't show this.
Btw. you can leave this field empty!

Example:

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format-Profil : Main 10@L5.1@High
HDR_Format/String : SMPTE ST 2086, HDR10 compatible
Codec-ID : V_MPEGH/ISO/HEVC
Dauer : 2 h 12 min
Bitrate : 28,3 Mb/s
Breite : 3 840 Pixel
Höhe : 2 160 Pixel
Bildseitenverhältnis : 16:9
Modus der Bildwiederholungsrate : konstant
Bildwiederholungsrate : 23,976 (24000/1001) FPS
ColorSpace : YUV
ChromaSubsampling/String : 4:2:0 (Type 2)
BitDepth/String : 10 bits
Bits/(Pixel*Frame) : 0.142
Stream-Größe : 26,1 GiB (87%)
Titel : John.Carter.Zwischen.zwei.Welten.2012.REGRADED.German.DTSHD.DL.2160p.HDR.UpsUHD.x265-QfG
Default : Ja
Forced : Nein
colour_range : Limited
colour_primaries : BT.2020
transfer_characteristics : PQ
matrix_coefficients : BT.2020 non-constant
MasteringDisplay_ColorPrimaries : Display P3
MasteringDisplay_Luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
MaxCLL : 1000 cd/m2
MaxFALL : 400 cd/m2

Green = HDR METADATA
Red = Only bitstream Infos

[JKyle]

Thank you for the information. I looked at mediainfo's changelog but didn't find metadata information for the (video) title. The default for mp4 files in the next Staxrip build is that this title is tagged as "blank". This results in the title not being displayed. If you want to display the title you have to enter the titel in staxrip.

The thing is, this 'Title' metadata appears only on an HEVC stream.

I'd appreciate it if StaxRip could leave the title blank instead of an MP4Box build number which looks really weird as it does now.

Thanks.

[JKyle]

This is no Bug. The field "Title" means, what they say. This is not Metadata from HDR, this is just simply the title of this track. No idea why MediaInfoXP don't show this.

Thank you for your advice. But I think I need to provide more explanation though:

1. My video is not an HDR stream. I just converted an SDR H.264 video to SDR HEVC. I didn't talk about HDR in my post.

2. MediaInfo does NOT show 'Title' on video streams encoded in other than HEVC. If it is not a bug, then why is MediaInfo's 'behavior' inconsistent?

3. I know I can set the title tag when muxing an mp4 file. I'm not talking about how to correct the title. I'm just describing the situation that this weird 'Title' tag with the MP4Box build number appears if I do nothing in the course of muxing an HEVC video stream. (I leave StaxRip to do the muxing job using MP4Box, and if the 'Title' metadata is not set, this weird 'MP4Box build info' appears as the title.)

[JKyle]

Thanks for your positive feedback. I want to update my builds weekly.

Thanks a million. I DO like your builds. I replaced all the default binaries in StaxRip with yours. :)

BTW, I'd greatly appreciate it if you could release your build of ffprobe along with ffmpeg.

Thanks in advance. :)

[Patman]

Thanks a million. I DO like your builds. I replaced all the default binaries in StaxRip with yours. :)

BTW, I'd greatly appreciate it if you could release your build of ffprobe along with ffmpeg.

Thanks in advance. :)

Done :D
Look at my sig

[Natty]

Done :D
Look at my sig

ffprobe is not there.
btw are your x265 builds optimized like ffmpeg? how are they different from builds by others?
can you add stylish progress bar like meteor rain?

https://down.7086.in/x265-Yuuki-Asuna/

https://github.com/msg7086/x265-Yuuki-Asuna/commit/daa22d26c2bd6a6a93e7f5107c00f62d964d4a4a

[Patman]

ffprobe is not there.
btw are your x265 builds optimized like ffmpeg? how are they different from builds by others?

Hi Natty,

sure that ffprobe isn't there? :) I included it into ffmpeg package.

I've started compiling three weeks ago and i'm now learning day by day. I've tested my x265 build and i noticed there is a little speed boost. I don't think there is a different to other builds. I use fewer libraries compared to others, but all those that are important and enable all supported processor instruction sets. I compile as described in the documentation, but I compress all my builds.

can you add stylish progress bar like meteor rain?

https://down.7086.in/x265-Yuuki-Asuna/

https://github.com/msg7086/x265-Yuuki-Asuna/commit/daa22d26c2bd6a6a93e7f5107c00f62d964d4a4a

I'll have a look at this and do my best.

[Natty]

Hi Natty,

sure that ffprobe isn't there? :) I included it into ffmpeg package.

I'll have a look at this and do my best.

got it

:thanks: :)

[JKyle]

Done :D
Look at my sig

Fantastic!

Thanks a lot.

----------------------------------

I tried to launch your ffmpeg/ffprobe but they failed to execute complaining that I'm missing the following dll's.

nppicc64_10.dll
nppidei64_10.dll
nppig64_10.dll

Maybe it's because you linked the CUDA SDK headers(--enable-libnpp) in compiling ffmpeg/ffprobe, so systems without npp dll's cannot launch your ffmpeg.

Can you fix this, please?

Thanks.

[Patman]

Fantastic!

Thanks a lot.

----------------------------------

I tried to launch your ffmpeg/ffprobe but they failed to execute complaining that I'm missing the following dll's.

nppicc64_10.dll
nppidei64_10.dll
nppig64_10.dll

Maybe it's because you linked the CUDA SDK headers(--enable-libnpp) in compiling ffmpeg/ffprobe, so systems without npp dll's cannot launch your ffmpeg.

Can you fix this, please?

Thanks.

Thank you for the information,

I forgot to disable the option. I have updated ffmpeg. Pls test...

[suarsg]

I just noticed in StaxRip 2.0.3 this changelog: colorspace="YV12" removed from ffms2 defaults because it converts to 8 bit

I never touched any of the default settings on StaxRip except for x265 settings. So I was checking the StaxRip-logs on some of my old encodes (x265), and sure enough, many of my HDR10 encodes I spent 15+ hours on have this in their log:

FFVideoSource("video.hevc", colorspace = "YV12" ...
and
YUV-420-planar-8bit progressive video
y4m [info]: 3840x2160 fps 24000/1001 i420p8 unknown frame count

So, does this mean my HDR10 input video was actually converted to 8bit before it was piped into x265 (which then encoded it in 10bit and HDR10 again)? Do I have to re-do all these wrong encodes or is that may be something not to worry about? I find it hard to believe this bug has been around for years with nobody noticing, so I'm hoping this is just a "cosmetic" issue in the logs or something.

It's hard to tell on my 8bit monitor if there's something wrong with the encodes. I don't think there was any banding introduced but it's hard to tell if the colors or something got screwed up? This is probably 250+ hours of encode time I really don't want to do again.

[JKyle]

Thank you for the information,

I forgot to disable the option. I have updated ffmpeg. Pls test...

Hi.

Thanks for the quick update.

Now your ffmpeg/ffprobe run without problems.

:thanks:

[Atlantis]

I just noticed in StaxRip 2.0.3 this changelog: colorspace="YV12" removed from ffms2 defaults because it converts to 8 bit

I never touched any of the default settings on StaxRip except for x265 settings. So I was checking the StaxRip-logs on some of my old encodes (x265), and sure enough, many of my HDR10 encodes I spent 15+ hours on have this in their log:

FFVideoSource("video.hevc", colorspace = "YV12" ...
and
YUV-420-planar-8bit progressive video
y4m [info]: 3840x2160 fps 24000/1001 i420p8 unknown frame count

So, does this mean my HDR10 input video was actually converted to 8bit before it was piped into x265 (which then encoded it in 10bit and HDR10 again)? Do I have to re-do all these wrong encodes or is that may be something not to worry about? I find it hard to believe this bug has been around for years with nobody noticing, so I'm hoping this is just a "cosmetic" issue in the logs or something.

It's hard to tell on my 8bit monitor if there's something wrong with the encodes. I don't think there was any banding introduced but it's hard to tell if the colors or something got screwed up? This is probably 250+ hours of encode time I really don't want to do again.

Yes, you have to redo them all. Any encoding of a 10bit source with Staxrip was done incorrectly before version 2.0.3.

It's not about large banding, it's like small compression artifacts more visible in red color places.

[suarsg]

Any encoding of a 10bit source with Staxrip was done incorrectly before version 2.0.3.

:(:(:(:(

The worst part is, I was already on 2.0.4 and was still getting these incorrect encodes. It turns out, the contents of the old AVS-script were saved in the settings file. So you actually have to either reset your settings or manually fix the script in AVS Filters -> Profiles.

[Atlantis]

Oh I always do a clean install of Staxrip with each new release. I delete all. Unpack the new Staxrip and recreate any template needed from new.

[ZeroCool22]

Done :D
Look at my sig


Hey Pat, what are the differences between your BUILDS and the ones that come in SatxRip by default, i mean what imrpoves it have? Thx!

PD: I mostly use the H265 when convert, so i can take advantage of my GPU, your BUILD could help me in my case, maybe more speed or something? Thx again.

[jlw_4049]

Yes, you have to redo them all. Any encoding of a 10bit source with Staxrip was done incorrectly before version 2.0.3.

It's not about large banding, it's like small compression artifacts more visible in red color places.Pretty sure @stax76 said the program was required to say 8 bit at some point and it really was encoding in 10 bit.

Sent from my SM-G965U1 using Tapatalk

[Patman]

Hey Pat, what are the differences between your BUILDS and the ones that come in SatxRip by default, i mean what imrpoves it have? Thx!

PD: I mostly use the H265 when convert, so i can take advantage of my GPU, your BUILD could help me in my case, maybe more speed or something? Thx again.

Look here (http://forum.doom9.org/showthread.php?p=1885841#post1885841)

Just try it out and see if they have an added value.

Natty has already given me some feedback. Feedback Natty (http://forum.doom9.org/showthread.php?p=1885770#post1885770)

[suarsg]

Pretty sure @stax76 said the program was required to say 8 bit at some point and it really was encoding in 10 bit.

Holy sh*t, is that true?
This is the exact kind of thing I was hoping for. @stax76 can you please please chime in regarding this (https://forum.doom9.org/showthread.php?p=1885868#post1885868), I really want to avoid redoing all my 2160p "Slow" encodes :scared:

[Atlantis]

Pretty sure @stax76 said the program was required to say 8 bit at some point and it really was encoding in 10 bit.

It was encoding in 10bit, that was not the problem. We got 10bit encoded files.

The problem was that it converted the 10bit source to 8bit.

So it did this 10bit->8bit->10bit. So it converted to 8bit and we lost a lot of information and quality.

This is clear like day. I said this before take the same test file. Encode it 2 times, once with the bad old version and the second time with the new version. You will see that the encoding time of the old bad version is a lot faster. So this also proves that the old version had less information to encode.

[Atlantis]

Also when you encode the same file 2 times, you will see that the encode with the new Staxrip gives a smaller size. So that also proves it had less artifacts and compressed better. With the old version and conversion to 8bit, it produced artifacts and the resulted encode is a little bigger.

[jlw_4049]

It was encoding in 10bit, that was not the problem. We got 10bit encoded files.



The problem was that it converted the 10bit source to 8bit.



So it did this 10bit->8bit->10bit. So it converted to 8bit and we lost a lot of information and quality.



This is clear like day. I said this before take the same test file. Encode it 2 times, once with the bad old version and the second time with the new version. You will see that the encoding time of the old bad version is a lot faster. So this also proves that the old version had less information to encode.Keep in mind he updates the ffmpeg, x264, x265 versions everytime. Which could be seeing your speed benefit.

I'm 99% sure Stax went over this once before already. It just said 8 bit to work correctly and it was actually 10 bit.

Sent from my SM-G965U1 using Tapatalk

[suarsg]

I have now done some test encodes with the exact same settings in 2.0.4.0 vs 2.0.2.1 vs source. What I previously thought were just "encoding artefacts" turned out to be the result of some weird conversion. The 2.0.4.0 encoded sample, when comparing frame for frame zoomed in, looks much much closer to the original source. For example I can see there's some slight red banding in the source. The banding in the newer encode looks pretty much the same. The banding in the "8bit"-version looks very different and is even shifted. So there was definitely something wonky going on.

[jlw_4049]

I have now done some test encodes with the exact same settings in 2.0.4.0 vs 2.0.2.1 vs source. What I previously thought were just "encoding artefacts" turned out to be the result of some weird conversion. The 2.0.4.0 encoded sample, when comparing frame for frame zoomed in, looks much much closer to the original source. For example I can see there's some slight red banding in the source. The banding in the newer encode looks pretty much the same. The banding in the "8bit"-version looks very different and is even shifted. So there was definitely something wonky going on.@stax76 will be around eventually and he can respond to you in more depth. Staxrip has been having a 10 bit pipeline since v 2xxx

Sent from my SM-G965U1 using Tapatalk

[Natty]

high bit depth pipelining support was always there, you just had to order your encoding script correctly. i had no problem ever pipelining 16bit correctly to encoder.

[suarsg]

high bit depth pipelining support was always there, you just had to order your encoding script correctly. i had no problem ever pipelining 16bit correctly to encoder.

The AVS script of FFMS2(?) had code in it to just assume YV12-colorspace for everything. So unless you actually edited the scripts, it didn't matter what you had configured inside your application if it used FFMS2 as a source provider (which is the auto/default setting).

[-QfG-]

YV12 Colorspace (YUV420) is correct. But you must tunneling with a 10-Bit Pipeline. I use DGindexNV for this.

[suarsg]

The thing is, specifying colorspace="YV12" resulted in the video being (silently) converted to 8bit. Not specifying any colorspace however, results in correctly auto-detecting the colorspace and not converted to 8bit before being piped.
In other words, specifying the correct colorspace lead to a 8bit pipeline, not specifying any colorspace lead to an actual 10bit pipeline. And StaxRip was, by default, specifying a colorspace in its AVS script.

[stax76]

Truth is I'm retired from encoding anything and as a result am by no means an expert in modern settings such as high bit depth and HDR, fortunately Revan made much improvements in this regard and I hope he will continue to do so.

StaxRip allows to use almost any setting that can be used in avs, vs, x265, nvenc etc. and it's easy to find out what settings it uses because there is everywhere a script or command line preview feature and the log file is very clean and readable.

I don't think there are or was many limitations, one limitation is the drawing code used in the preview and the crop dialog, it's imitated both in performance and color accuracy. How it works is staxrip modifies the avs/vs script, this modification can be seen in the file _preview.avs/_preview.vpy, with that it uses the avifile api and System.Drawing.Bitmap, this can't obviously compete with madvr, people can use mpv for previewing, this will only work with avs because mpv don't support vpy, using mpc with madvr for preview is possible I guess but not many people have the required time and knowledge required to do it, PowerShell is needed because the script needs to be written to disc first. If somebody has interest in doing this please create a ticket and I will take care of it, it could take me some time because at the moment I spend time improving my .NET knowledge because .NET Core 3.0 and C# 8.0 was released this week and I still have some enthusiasm about dotnet, did my first tiny app ShellNew (https://github.com/stax76/ShellNew) with .NET Core 3.0 and C# 8.0.

[-QfG-]

I don't know, i specified always INPUT and OUTPUT in the script. I never used "Standard Settings". Example for a DNxHR YUV422 HEVC Encode:

LoadPlugin("E:\VIDEOTOOLS\AVIS riPPen\StaxRip-x64-2.0.4.4-beta\Apps\Plugins\both\L-SMASH-Works\LSMASHSource.dll")
LSMASHVideoSource("D:\VIDEO\HDR\Untitled2.mov", format = "YUV422P10") <--- INPUT and activating 10-Bit Pipeline
ConvertToYV12() <--- Change Colorspace from YUV422 to YUV420.

I used this a long time and ConverttoYUV never changes the pipeline. If i use this:

LSMASHVideoSource("D:\VIDEO\HDR\Untitled2.mov")

I have activated the 8-Bit Pipeline all the same the input file has another bitdepth.

You must choose the pipeline with the source string.

If you encode from HEVC to HEVC you don't need the line "ConvertToYV12()", because your source is YUV420.

[stax76]

Info() can be added in the script editor to show the colorspace and bitdepth, Info() supports font size for High DPI:

Info(size=40)

I don't know what is the VapourSynth equivalent but vspipe info was added to the main menu some time ago:

Main Menu > Apps > Media Info > vspipe

It prints:

Width: 1920
Height: 1080
Frames: 6172
FPS: 30000/1001 (29.970 fps)
Format Name: YUV420P8
Color Family: YUV
Alpha: No
Sample Type: Integer
Bits: 8
SubSampling W: 1
SubSampling H: 1

[Natty]

The thing is, specifying colorspace="YV12" resulted in the video being (silently) converted to 8bit. Not specifying any colorspace however, results in correctly auto-detecting the colorspace and not converted to 8bit before being piped.
In other words, specifying the correct colorspace lead to a 8bit pipeline, not specifying any colorspace lead to an actual 10bit pipeline. And StaxRip was, by default, specifying a colorspace in its AVS script.

yeah ffvideosource is also a part of your encoding script. i think everyone just ignored it and left it as default, and never bothered to see what commands are being used during encoding, read documentations, etc.

you can not specify anything and just leave it blank to keep it same as source. works for normal sources which we use.

[jlw_4049]

So has the encoder been doing 10 bit hdr with ffvideosource this whole time or does something more need to be edited?



Sent from my SM-G965U1 using Tapatalk

[suarsg]

So has the encoder been doing 10 bit hdr with ffvideosource this whole time or does something more need to be edited?


It has been doing 10bit HDR encoding, but it was being fed an 8bit input instead of the correct 10bit. You need to update to the latest StaxRip and either completely reset your settings or reset to defaults under AVS Filters -> Profiles ... just make sure it doesn't have the colorspace parameter anymore.

[jlw_4049]

It has been doing 10bit HDR encoding, but it was being fed an 8bit input instead of the correct 10bit. You need to update to the latest StaxRip and either completely reset your settings or reset to defaults under AVS Filters -> Profiles ... just make sure it doesn't have the colorspace parameter anymore.Which version changed this?

Sent from my SM-G965U1 using Tapatalk

[suarsg]

Which version changed this?

2.0.3 ... but the issue will still persist if you upgraded from a previous version. Hence my comment on what you need to do.

[jlw_4049]

2.0.3 ... but the issue will still persist if you upgraded from a previous version. Hence my comment on what you need to do.Shit. Wonder how many I've encoded with older versions. I've been using 2.0.4.0 for a while now. I just do a fresh install each time but normally copy over my profile settings so I don't have to reset it all up. I never change the default script settings though.

Sent from my SM-G965U1 using Tapatalk

[-QfG-]

FFVideoSource("%source_file%", cachefile = "%source_temp_file%.ffindex", colorspace = "YUV420P10")

Use this Source Filter for force YUV 4.2.0 10-Bit (HEVC Input) and 10-Bit pipeline.

[jlw_4049]

Use this Source Filter for force YUV 4.2.0 10-Bit (HEVC Input) and 10-Bit pipeline.Is this nessecary to get the 10 bit pipeline for HDR?

Sent from my SM-G965U1 using Tapatalk

[-QfG-]

10-Bit Pipeline for 10-Bit Input. Every Retail movie with the HEVC Codec is encoded in 10-Bit (Also BT709 Content). With this string (colorspace = "YUV420P10") you Force Avisynth to the 10-Bit Input.
If you leave the string empty, FFVideoSource will Autodetect the Input. This works well, too.

Example:

If you convert a 1080p SDR 8-Bit movie with x265 to a 10-Bit HEVC SDR movie, you use the 8-Bit pipeline:
FFVideoSource("%source_file%", cachefile = "%source_temp_file%.ffindex", colorspace = "YUV420P8")

The output bitdepth will be set with the x265 Codec Settings (--output-depth 10 & the Main10 profile).

INPUT=Avisynth
OUTPUT=Encoder

[jlw_4049]

10-Bit Pipeline for 10-Bit Input. Every Retail movie with the HEVC Codec is encoded in 10-Bit (Also BT709 Content). With this string (colorspace = "YUV420P10") you Force Avisynth to the 10-Bit Input.
If you leave the string empty, FFVideoSource will Autodetect the Input. This works well, too.

Example:

If you convert a 1080p SDR 8-Bit movie with x265 to a 10-Bit HEVC SDR movie, you use the 8-Bit pipeline:


The output bitdepth will be set with the x265 Codec Settings (--output-depth 10 & the Main10 profile).

INPUT=Avisynth
OUTPUT=EncoderSo I can leave the custom settings alone for the pipeline as long as its empty?

Sent from my SM-G965U1 using Tapatalk

[-QfG-]

Yes, in most cases FFVS will recognize the input correctly and x265 will automatically work with the data it gets from y4m.

[jlw_4049]

Yes, in most cases FFVS will recognize the input correctly and x265 will automatically work with the data it gets from y4m.What way do you recommend then? The above instructions. Do you think it's good enough to leave it blank?

Sent from my SM-G965U1 using Tapatalk

[suarsg]

Shit. Wonder how many I've encoded with older versions.

You can go to your AppData/Roaming/StaxRip folder, the old logs might still be there. You can check for every encode you did if it was 8bit or 10bit.

[jlw_4049]

You can go to your AppData/Roaming/StaxRip folder, the old logs might still be there. You can check for every encode you did if it was 8bit or 10bit.What string of words am I looking for?

Sent from my SM-G965U1 using Tapatalk

[-QfG-]

What way do you recommend then? The above instructions. Do you think it's good enough to leave it blank?

Sent from my SM-G965U1 using Tapatalk

If you don't know what you do, leave it blank.

What string of words am I looking for?

Search for the Line with your encoding log.
-------------- Video encoding using x265 3.1+19 Wolfberry --------------

"E:\VIDEOTOOLS\AVIS riPPen\StaxRip-x64-2.0.4.3-beta\Apps\Support\avs2pipemod\avs2pipemod64.exe" -y4mp "E:\Video\PitchBlack\Timeline 1_temp\Timeline 1.avs" | "E:\VIDEOTOOLS\AVIS riPPen\StaxRip-x64-2.0.4.3-beta\Apps\Encoders\x265\x265.exe" --crf 16 --preset slow --qcomp 0.7 --no-open-gop --chromaloc 2 --no-info --aud --input-depth 10 --no-strong-intra-smoothing --level-idc 5.1 --sar 1 --aq-mode 1 --selective-sao 0 --no-sao --me umh --repeat-headers --deblock -3:-3 --no-open-gop --uhd-bd --min-keyint 1 --keyint 24 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --range limited --bframes 4 --hrd --vbv-bufsize 35000 --vbv-maxrate 40000 --hdr --output-depth 10 --hdr-opt --max-cll "1000,400" --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --frames 1357 --y4m --output "E:\Video\PitchBlack\Timeline 1_temp\Timeline 1_out.hevc" -

avs2pipemod[info]: writing 1357 frames of 24000/1001 fps, 3840x2160,
sar 0:0, YUV-420-planar-10bit progressive video.
y4m [info]: 3840x2160 fps 24000/1001 i420p10 sar 1:1 unknown frame count

[jlw_4049]

If you don't know what you do, leave it blank.



Search for the Line with your encoding log.Thank you!

Sent from my SM-G965U1 using Tapatalk

[Atlantis]

I have now done some test encodes with the exact same settings in 2.0.4.0 vs 2.0.2.1 vs source. What I previously thought were just "encoding artefacts" turned out to be the result of some weird conversion. The 2.0.4.0 encoded sample, when comparing frame for frame zoomed in, looks much much closer to the original source. For example I can see there's some slight red banding in the source. The banding in the newer encode looks pretty much the same. The banding in the "8bit"-version looks very different and is even shifted. So there was definitely something wonky going on.
I'm glad you reached the same conclusion. What tool do you use to do the frame by frame comparison? Do you know anything better than the tool that is already provided with Staxrip?

[Atlantis]

Question, does having more RAM result in faster encodes? (encoding with x265) I tested two almost identical PCs and one encodes faster.

encoded 1146 frames in 516.31s (2.22 fps), 20859.12 kb/s, Avg QP:27.55
encoded 1146 frames in 403.19s (2.84 fps), 20859.12 kb/s, Avg QP:27.55

The faster PC has everything the same except double the RAM and a little better Graphics Card which I suppose doesn't do anything in x265.

[jlw_4049]

Question, does having more RAM result in faster encodes? (encoding with x265) I tested two almost identical PCs and one encodes faster.

encoded 1146 frames in 516.31s (2.22 fps), 20859.12 kb/s, Avg QP:27.55
encoded 1146 frames in 403.19s (2.84 fps), 20859.12 kb/s, Avg QP:27.55

The faster PC has everything the same except double the RAM and a little better Graphics Card which I suppose doesn't do anything in x265.

Is the one with more ram faster ram perhaps? Is the one with less ram single channel memory vs the other dual channel memory?

Is CPU cooling in both computers the same or is the faster one possibly equipped with a better cooler?

[Atlantis]

The cooling is the same, all is the same except these 2.

one is
GSKILL RIPJAWS V DDR4-3000 PC4-24000 16GB x 4 = 64GB RAM

the other is
Corsair DDR4 8GB 2400MHZ Vengeance LPX CMK8GX4M1A2400C14 x 4 = 32 GB RAM

The Graphics Card doesn't matter, right?

[stax76]

### 2.0.4.5 Beta

Thanks to Patman for providing the download links of the tools !!!

- update: JPSDR 3.1.3
- update: nvenc 4.50
- update: AVSMeter 2.9.6
- update: DGHDRtoSDR 1.12
- update: mvtools2 2.7.41
- update: FFT3dFilter 2.6.7
- update: TIVTC 1.0.14
- update: RgTools 0.98
- update: havsfunc r32
- update: DFTTest r6
- update: TCanny r12
- update: BM3D r8
- update: L-Smash Works 2019-09-17 HolyWu
- update: x265 3.2+3-fdd69a76688 Patman
- update: ffmpeg 2019-09-27 Patman

- new: x265 switch --selective-sao added
- new: L-Smash Works parameters prefer_hw 3 HW auto added to menu
- new: the way --vbr-quality works in nvenc was changed,
if it's value is -1 the bitrate in the main dialog is used,
if it's higher then -1 the bitrate is set to 0
- new: add support of video track title/name using MP4Box
- new: simple QP mode added to nvenc to use one instead of three QP values
- new: the menu renderer has now Win 10 style arrows for sub menu indication
- new: icons added to filter list and script editor, shortcuts added to script editor
- new: the preview can be closed by clicking in the top right corner
- new: in the script editor there are now two players available,
mpv.net and whatever is registered for mkv, mpc-be supports vpy playback
- new: the way filters are added, replaced and inserted in the script editor
was changed in order to improve the menu performance
- new: in the main menu a sub menu was added: Apps > Script Info,
it contains avsmeter, vspipe and avs2pipemod for showing
info about the currently active AviSynth or VapourSynth script,
vspipe and avs2pipemod show parameters like bit depth, colorspace and framecount.
In the script editor there is a new 'Script Info' menu item (Ctrl+I) doing the same.
- new: the mediainfo dialog shows the formats in the tab captions
- new: the mediainfo dialog has a new feature to move
to the next and previous file via menu and shortcut

- fix: docs weren't built automatically
- fix: some bugs were fixed in the nvenc command line import feature

https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR

[jlw_4049]

The cooling is the same, all is the same except these 2.

one is
GSKILL RIPJAWS V DDR4-3000 PC4-24000 16GB x 4 = 64GB RAM

the other is
Corsair DDR4 8GB 2400MHZ Vengeance LPX CMK8GX4M1A2400C14 x 4 = 32 GB RAM

The Graphics Card doesn't matter, right?Yeah it's the RAM speed that's causing the difference. Honestly its such a small difference I I wouldnt worry about it.

If you're any good at it you could try overclocking that kit of RAM but in my opinion it's not worth it. Especially for an encoding machine as you want maximum stability.### 2.0.4.5 Beta

Thanks to Patman for providing the download links of the tools !!!

- update: JPSDR 3.1.3
- update: nvenc 4.50
- update: AVSMeter 2.9.6
- update: DGHDRtoSDR 1.12
- update: mvtools2 2.7.41
- update: FFT3dFilter 2.6.7
- update: TIVTC 1.0.14
- update: RgTools 0.98
- update: havsfunc r32
- update: DFTTest r6
- update: TCanny r12
- update: BM3D r8
- update: L-Smash Works 2019-09-17 HolyWu
- update: x265 3.2+3-fdd69a76688 Patman
- update: ffmpeg 2019-09-27 Patman

- new: x265 switch --selective-sao added
- new: L-Smash Works parameters prefer_hw 3 HW auto added to menu
- new: the way --vbr-quality works in nvenc was changed,
if it's value is -1 the bitrate in the main dialog is used,
if it's higher then -1 the bitrate is set to 0
- new: add support of video track title/name using MP4Box
- new: simple QP mode added to nvenc to use one instead of three QP values
- new: the menu renderer has now Win 10 style arrows for sub menu indication
- new: icons added to filter list and script editor, shortcuts added to script editor
- new: the preview can be closed by clicking in the top right corner
- new: in the script editor there are now two players available,
mpv.net and whatever is registered for mkv, mpc-be supports vpy playback
- new: the way filters are added, replaced and inserted in the script editor
was changed in order to improve the menu performance
- new: in the main menu a sub menu was added: Apps > Script Info,
it contains avsmeter, vspipe and avs2pipemod for showing
info about the currently active AviSynth or VapourSynth script,
vspipe and avs2pipemod show parameters like bit depth, colorspace and framecount.
In the script editor there is a new 'Script Info' menu item (Ctrl+I) doing the same.
- new: the mediainfo dialog shows the formats in the tab captions
- new: the mediainfo dialog has a new feature to move
to the next and previous file via menu and shortcut

- fix: docs weren't built automatically
- fix: some bugs were fixed in the nvenc command line import feature

https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/f/s!ArwKS_ZUR01gySQIE1QCL2i9F_uR
Wow! Massive update! I'm solid on 2.0.4.0 so I might wait for next stable release.
Sent from my SM-G965U1 using Tapatalk

[JKyle]

### 2.0.4.5 Beta

- new: the way --vbr-quality works in nvenc was changed,
if it's value is -1 the bitrate in the main dialog is used,
if it's higher then -1 the bitrate is set to 0
- new: add support of video track title/name using MP4Box
- new: simple QP mode added to nvenc to use one instead of three QP values

Good. Smart insertion of the --vbr-quality parameter.

BTW, I'd appreciate it if I can see the quality parameter value in the output file info pane on the main window when I set --vbr-quality to a positive number. It currently shows '0' instead of a really value.

:thanks:

[stax76]

It's a quality mode and I missed setting the main window to quality mode view, 2.0.4.6 Beta is available.

[Atlantis]

Yeah it's the RAM speed that's causing the difference. Honestly its such a small difference I I wouldnt worry about it.

Oh it's a huge difference. Encoding a 2 hours movie

with 2.22 fps takes 22 hours.
with 2.84 fps takes 17 hours.

The difference is 5 hours and it's worth it, every second counts.

If your source is 1080 8bit, it doesn't matter much but if you are encoding 4K HDR 10bit, everything counts and it takes a long time.

Question for suarsg. With your encoding test, did you also write down the speed? Did you notice that with the new correct method, it takes longer to encode?

Not only we have to redo all our previous work, we didn't even realize that the speed was not right and it was not the real speed. We have to redo all and with even slower speed! :D:D

[Patman]

can you add stylish progress bar like meteor rain?

https://down.7086.in/x265-Yuuki-Asuna/

https://github.com/msg7086/x265-Yuuki-Asuna/commit/daa22d26c2bd6a6a93e7f5107c00f62d964d4a4a

I've updated my builds and add two versions of x265. The one from git (x265-3.2...) and the modifided version (x265_custom_...) with custom progress bar like MeteorRain uses. THX for code @ MeteorRain

[suarsg]

Question for suarsg. With your encoding test, did you also write down the speed? Did you notice that with the new correct method, it takes longer to encode?

Not only we have to redo all our previous work, we didn't even realize that the speed was not right and it was not the real speed. We have to redo all and with even slower speed! :D:D

For me the speed hasn't changed much. Maybe yours are faster now because of a different x265-feature or some default changes? (like aq-mode defaults to 2 instead of 1 now)

As for your comparison question: I don't like the intergrated tool because you can't zoom in at 100%, which is really needed for comparing 4k. So what I'm doing: I use MPC-HC with madVR, open two videos, Ctrl+G to jump to a specific frame number, Alt+I to save a PNG of the frame in both players, and then open both PNGs in Photoshop, put them into one so I can quickly switch between the 2 layers and zoom around see the difference with just 1 click. You can also navigate 1 frame forward and 1 frame backward in MPC-HC which allows me to compare subsequent frames easily for both files. It's kinda tedious, but so far the most effective way I found.

It'd be amazing if the Video Comparison-Tool in StaxRip let me have pixel-perfect 100% zoom and drag around the frame (4k image on a non-4k-monitor). But I feel like the StaxRip-tool already has so many good features, I didn't wanna bother the dev with such a small quality-of-life issue :D