StaxRip

[stax76]

Have been working on some requests and the docs, it's maybe the first time I can say the docs don't suck, I hope it can help a few people that don't have interest in StaxRip so far.


2.1.1.4 Beta
============

- dark color theme for built-in help.
- improved built-in help for various dialogs.
- various docs pages improved.
- ffmpeg video encoder codec FFV1.
- x264 and x265 dialogs have a new Bitrate option, the default value is 0 which
means the bitrate of the project/template in the main dialog is used,
this behavior is documented in the F1 help of the x264 and x265 dialog.
- for file batch jobs only the file name is shown in the jobs dialog and not the full path.
- audio encoder supports extracting DTS core using ffmpeg, generated name is _Extract DTS Core_.
- the audio Copy/Mux profile has a _Extract DTS Core_ feature.
- the command line audio encoder has a Default and Forced option.


Download

https://staxrip.readthedocs.io/introduction.html#beta

[jlw_4049]

Have been working on some requests and the docs, it's maybe the first time I can say the docs don't suck, I hope it can help a few people that don't have interest in StaxRip so far.


2.1.1.4 Beta
============

- dark color theme for built-in help.
- improved built-in help for various dialogs.
- various docs pages improved.
- ffmpeg video encoder codec FFV1.
- x264 and x265 dialogs have a new Bitrate option, the default value is 0 which
means the bitrate of the project/template in the main dialog is used,
this behavior is documented in the F1 help of the x264 and x265 dialog.
- for file batch jobs only the file name is shown in the jobs dialog and not the full path.
- audio encoder supports extracting DTS core using ffmpeg, generated name is _Extract DTS Core_.
- the audio Copy/Mux profile has a _Extract DTS Core_ feature.
- the command line audio encoder has a Default and Forced option.


Download

https://staxrip.readthedocs.io/introduction.html#beta

Awesome update! I'm taking a look at it now :)

:thanks:

[colinhunt]

2.1.1.4 Beta
Brilliant, thank you!

[jlw_4049]

@stax76 I put a new request in the tracker. Let me know what you think about it! :)

https://github.com/staxrip/staxrip/issues/202

[minda76]

2.1.1.3 Beta
============

- DGDecNV removal, there are better open source tools,
L-Smash-Source supports hardware decoding for NVIDIA, Intel and AMD



https://staxrip.readthedocs.io/introduction.html#beta

Why? if people use dgdecnv, why to remove it?

[videoh]

You can still use it. It's just not a hard-coded part of the application, as stax76 has explained. For pedal to the metal, index separately with DGIndexNV, make your avisynth script, and open that with staxrip. It's a powerful and flexible combination.

[Groucho2004]

2.1.1.3 Beta
============

- DGDecNV removal, there are better open source tools,
L-Smash-Source supports hardware decoding for NVIDIA, Intel and AMD

You're not wrong about LSmash. I benchmarked DGDecodeNV and the latest lsmash with a 4K HEVC stream:

Video card: NVIDIA GeForce GTX 1660
GPU version: TU116
Video memory size: 6144 MiB
OpenCL version: OpenCL 1.2 CUDA
Graphics driver version: 26.21.14.3648 (NVIDIA 436.48) / Win7 64



DGDecodeNV result:
Frames processed: 4080 (0 - 4079)
FPS (min | max | average): 79.12 | 157.8 | 153.6
Process memory usage (max): 200 MiB
Thread count: 9
CPU usage (average): 27.8%

GPU usage (average): 33%
VPU usage (average): 54%
GPU memory usage: 589 MiB
GPU Power Consumption (average): 34.1 W


LSmash result:
Frames processed: 4080 (0 - 4079)
FPS (min | max | average): 34.94 | 196.2 | 177.6
Process memory usage (max): 213 MiB
Thread count: 8
CPU usage (average): 23.0%

GPU usage (average): 36%
VPU usage (average): 57%
GPU memory usage: 649 MiB
GPU Power Consumption (average): 39.2 W

[videoh]

It all depends on your GPU. With my 2080Ti I get 308 fps for 4K compared to your 177 fps with LSmash. CPU usage is 12%, which is half of LSmash.

I know you'll ask me to run LSmash on that card. Don't have it installed and I'm very busy so may take a while but I will do so and report back.

[jlw_4049]

Why? if people use dgdecnv, why to remove it?


You can re-add it in the program and it works perfectly. It was removed by default as a request by the author.

[videoh]

It was removed by default as a request by the author. That is false! I asked that the executables not be bundled and instead download links be provided. The total removal from the application was a decision by stax76.

[jlw_4049]

That is false! I asked that the executables not be bundled and instead download links be provided. The total removal from the application was a decision by stax76.My apologies. I just thought I read that somewhere.

Sent from my Pixel 3a using Tapatalk

[minda76]

How to re-add dgdecnv? Don't want to use lsmash..

[stax76]

How to re-add dgdecnv? Don't want to use lsmash..

It depends on what functionality you want, if you want to open mkv causing staxrip to run dgindexnv then the configuration is a bit advanced.

If you want to open dgi, then it's simple:

To customize the Automatic source filter you can first create a source filter profile (right-click Filters -> Profiles) and after that associate a file extension to this source filter profile at:

Main Menu > Tools > Setting > Source Filters

[mcjordan]

...and then create the appropriate point in Main Menu -> Tools -> Settings -> Preprocessing
(with hardcoded path to DGIndexNV executable).

[JKyle]

AviSynth+ is updated to 3.6.0 today.

https://github.com/AviSynth/AviSynthPlus/releases/tag/v3.6.0

[chipxtreme]

NVEnc 5.02 is out

[stax76]

2.1.1.5 Beta
============

- In the video encoder dialogs the feature *Execute Command Line* failed when
Windows Terminal is installed and paths contained spaces.
- The video encoder dialog feature *Show Command Line* is shown using a console.
- Maximum number of parallel processes increased from 4 to 16.
- On systems with restricted PowerShell execution policy several features
like the media info folder view feature failed.
- The Tools page in the docs lists all tools in a grid view
with columns: Name, Type, Filename, Version, Modified Date.
- Muxer dialog is resizable and remembers the size.
- Muxer dialog supports Drag & Drop for subtitles, audio and attachments.
- Video Comparison crash fixed and hardware render support added.
- aomenc.exe GUI re-enabled, executable not included
- AviSynth headers updated.
- AviSynth 3.6
- x265 M-3.3+31-g431a22e82-gcc11.0.0 Patman
- NVEnc 5.02
- ffmpeg N-97868-gaa6f38c298-g38490cbeb3-gcc10.1.0 Patman
- yadifmod2 avs 0.2.2
- AVSMeter 2.9.9.3
- KNLMeansCL avs/vs 1.1.1
- MPEG2DecPlus avs 0.1.2 (untested)
- QTGMC avs 3.364s
- masktools2 2.2.23
- DCTFilter 0.5.1
- MediaInfo.NET 6.4.0.0


Download

https://staxrip.readthedocs.io/introduction.html#beta

[Patman]

Download



THX for the new update. I've added the aomenc to my folder. At the moment, i'm playing a bit with the implemantation of direct input for .avs and .vpy files in x265.

[stax76]

THX for the new update. I've added the aomenc to my folder. At the moment, i'm playing a bit with the implemantation of direct input for .avs and .vpy files in x265.

Direct avs vpy input would be a good feature, in particular to use with powershell since powershell does not support this kind of piping it seems, unless cmd is used in powershell :-). There was a post lately about a mabs fork that mentioned x265 using libavformat, I think the vpy reader in libavformat was written by a mpv dev.

[jlw_4049]

2.1.1.5 Beta
============

- In the video encoder dialogs the feature *Execute Command Line* failed when
Windows Terminal is installed and paths contained spaces.
- The video encoder dialog feature *Show Command Line* is shown using a console.
- Maximum number of parallel processes increased from 4 to 16.
- On systems with restricted PowerShell execution policy several features
like the media info folder view feature failed.
- The Tools page in the docs lists all tools in a grid view
with columns: Name, Type, Filename, Version, Modified Date.
- Muxer dialog is resizable and remembers the size.
- Muxer dialog supports Drag & Drop for subtitles, audio and attachments.
- Video Comparison crash fixed and hardware render support added.
- aomenc.exe GUI re-enabled, executable not included
- AviSynth headers updated.
- AviSynth 3.6
- x265 M-3.3+31-g431a22e82-gcc11.0.0 Patman
- NVEnc 5.02
- ffmpeg N-97868-gaa6f38c298-g38490cbeb3-gcc10.1.0 Patman
- yadifmod2 avs 0.2.2
- AVSMeter 2.9.9.3
- KNLMeansCL avs/vs 1.1.1
- MPEG2DecPlus avs 0.1.2 (untested)
- QTGMC avs 3.364s
- masktools2 2.2.23
- DCTFilter 0.5.1
- MediaInfo.NET 6.4.0.0


Download

https://staxrip.readthedocs.io/introduction.html#beta


Amazing update! :)


Completely off topic, where do I learn to code programs like you? haha

[bananenmann]

It depends on what functionality you want, if you want to open mkv causing staxrip to run dgindexnv then the configuration is a bit advanced.


Hello,
I've bought DGIndexNV some days ago and started to work with Staxrip Beta 2.1.1.2 for the first time. I was surprised how great this program is and how huge the possibilities are that can be chosen. Today I updated to Version 2.1.1.5 (deleted old folder before) and suddenly I wasn't able to find this app again. Since I paid Money for it I surely want to use it. Please could you tell me, what do I have to do, to get it back in Staxrip? I've already added the old two demuxer command lines for it in the Settings-> Preprocessing Section, as suggested. (Copied all the Parameters from an old Staxrip Version, where it wasn't removed yet). Then I've copied the DGIndexNV Folder into the Staxrip directory. But what now?

How do I get back the Option to manage it in the Apps Section and to use it automatically in the Source: DGindex - Automatic Filter, when I open a file? Please explain it carefully, I'm a newbie :)

I'm very sad about the decision to remove it from Staxrip, because the removal was unessesary (in my Opinion). Those People who didn't want to use it, weren't forced to do so. Now those People who want to use it and are no Video-Pro's, like me, are lost :( ... Could't you ask the Author to please reintegrate it? That would be great and no great effort for him.

With best regards,
Bananenmann

[-QfG-]

Ok, i see it, DGDecNV support ends now. Ok, i use LSmash Indexing for my DNxHR Intermediates, but the problem is that the newest version gives me Errors while indexing. So my Question till which version of LSmash is the CUDA support?

[stax76]

Completely off topic, where do I learn to code programs like you? haha

In the beginning I've learned to code by reading books, in recent years I preferred free web resources, the tutorial I used most recently is learncpp.com, it's pretty good, I think I found it by searching for something like 'best C++ tutorial'.

It probably makes sense to learn which resources exist and how to find them, I typically spend quite some time searching for good resources as I don't enjoy learning and coding without good resources. I maintain a well organized bookmark collection with coding resources and quick access via bookmark bar.

VS Code, Python and PowerShell are probably a good start, for PowerShell I know a good resource:

https://adamtheautomator.com/tag/powershell/

For GUIs the easiest way to start is Visual Studio Community, Visual Basic.NET, .NET Framework and Windows Forms, that's exactly what StaxRip uses. This has however drawbacks, Windows Forms has major flaws in my opinion, the biggest problem is that all this isn't portable, that's why I rather recommend VS Code, Python, PowerShell and the console, unlike dgdecnv it's open source and runs on every popular OS and hardware.

Ok, i use LSmash Indexing for my DNxHR Intermediates, but the problem is that the newest version gives me Errors while indexing. So my Question till which version of LSmash is the CUDA support?

The LSmash version in staxrip has robust cuvid support in my experience, maybe it can be fixed if you upload a sample.

[JKyle]

I've added the aomenc to my folder.

Well, running the aomenc.exe file in aomenc-v2.0.0-masterbranch-gcc11.0.0.7z returns nothing.
Deja vu (https://forum.doom9.org/showthread.php?p=1912799#post1912799)!

I guess at this time we need another tester like before.
Can anyone test this?
The file is here (http://www.mediafire.com/file/6fdmmjaqxihqbbj/aomenc-v2.0.0-masterbranch-gcc11.0.0.7z/file).

[stax76]

I confirm it:


Desktop> .\aomenc.exe
Desktop> .\aomenc.exe --help
Desktop> .\aomenc.exe --aaa
Desktop>

[mcjordan]

Yadifmod2 is updated to v0.2.3
https://github.com/Asd-g/yadifmod2/releases

Changelog: Fixed crash for mode=2/3 when opt>0.

AVSMeter is updated to v3.00 (thanks to Groucho)
https://www.mediafire.com/folder/x6f7yqjufdg7c/Groucho's_Avisynth_Stuff

Changelog:
- Added check for duplicate functions
This checks for duplicate functions
1. within .avsi files
2. against functions in other .avsi files
3. against internal/plugin functions

MVTools2 is updated to v2.742 (thanks to master pinterf)
https://github.com/pinterf/mvtools/releases/tag/2.7.42
Changelog:
MDegrain family: limit and limitc to float, allowing more granurality for 10+ bit depth
Update Avisynth headers, use V8 interface frame property copy if available

https://github.com/Asd-g?tab=repositories
There are many of chikuzen's and some Vapoursynth plugins ported to V8 interface,
like a yadifmod2, SangNom2, MSharpen (renamed to vsMSharpen), MPEG2DecPlus,
DCTFilter, TMM2, TCannyMod etc.

Thanks to Asd-g for hard work.

Here is the place of real.finder stuff:
https://github.com/realfinder/AVS-Stuff/

Here are located many invaluable modified (with HDB support and AviSynthPlus 3.5/3.6 support) scripts, like a:
DebilinearM, MCTemporalDenoise, AdvancedDenoising, SMDegrain, SeeSaw, QTGMC, FineSharp, ResizeX,
edi_rpow2, eedi3_resize16, maa2, nnedi3_resize16, and much more.

Thanks to real.finder for great work.

Most of them are subject of update in the StaxRip distribution.

And at the end - there is compiled by me MP4Box 0.90 r170 (VS2019):
https://www.upload.ee/files/11758164/MP4Box_v0.90_r0170_VS2019_16.60.7z.html

[Patman]

Well, running the aomenc.exe file in aomenc-v2.0.0-masterbranch-gcc11.0.0.7z returns nothing.
Deja vu (https://forum.doom9.org/showthread.php?p=1912799#post1912799)!

I guess at this time we need another tester like before.
Can anyone test this?
The file is here (http://www.mediafire.com/file/6fdmmjaqxihqbbj/aomenc-v2.0.0-masterbranch-gcc11.0.0.7z/file).

Fixed it! Now with version and rev in filename.
:stupid: I forgot a command for the compiler.

[-QfG-]

The LSmash version in staxrip has robust cuvid support in my experience, maybe it can be fixed if you upload a sample.

The problem is somewhere in my Avisynth line with Lsmash. This is my line, i used for YUV422 10-Bit Input:

LSMASHVideoSource("%source_file%", format="YUV422P10")
ConvertToYUV420()

This works fine with my old version of LSmash (I don't know the revision number, the file have 13.598.208 bytes). The version which is included in your StaxRip says an error like this: "format="YUV422P10" unknown command". And without this line, the video will only pipelined with 8-Bits.

[stax76]

@-QfG-

I cannot reproduce what you describe, if I open a YUV422P10 hevc .mp4 with either LSMASHVideoSource("%source_file%", format="YUV422P10") or LSMASHVideoSource("%source_file%") I get both times working YUV422P10 avs output.

[-QfG-]

I will test it in few hours, an encode is working, with a DNxHR HQX 10-Bit source. If i have the error again, i will post some screenshots.

EDIT:
Lol it works, i don't know why, but it works :D.

[stax76]

Media info and ideally sample would be great.

[JKyle]

The version which is included in your StaxRip says an error like this: "format="YUV422P10" unknown command". And without this line, the video will only pipelined with 8-Bits.

Well, just in case, check if this downsampling option is turned on:

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

As you know, it's in Tools > Settings > Video.

[JKyle]

Fixed it! Now with version and rev in filename.

:thanks:

aomenc-2.0.0-267-ga5e3f02b1-gcc11.0.0.7z seems OK. :)


BTW, the help file in x_v_i_d_encraw-1.3.7.7z is empty.

I've found this weird behavior with xvid_encraw and SVT-AV1: the standard output redirection does now give the desired help file! Instead, I need to redirect the standard error to a text file in order to get a help text file.

I.e., for xvid_encraw, this command yields a help file:

.\xvid_encraw.exe -help 2> help.txt

not this:

.\xvid_encraw.exe -help > help.txt

If anyone knows why, please teach me.

[stax76]

I've found this weird behavior with xvid_encraw and SVT-AV1: the standard output redirection does now give the desired help file! Instead, I need to redirect the standard error to a text file in order to get a help text file.

It's not a surprise, these guys (SVT-AV1) managed to do everything wrong that can possibly go wrong in a console app, I had to jump through hoops to make this encoder work in staxrip, full day work replacing a complex dotnet component with a customized version supporting the weird progress it writes.

[-QfG-]

Well, just in case, check if this downsampling option is turned on:

This is a bad idea, if i do this, in the script will be forced this line:

ConverttoYV12()

With this option enabled, the input stream will be pipelined with 8-Bits, so i use ConverttoYUV420()

[JKyle]

This is a bad idea, if i do this, in the script will be forced this line:

ConverttoYV12()

With this option enabled, the input stream will be pipelined with 8-Bits, so i use ConverttoYUV420()

Oh, you got me wrong.

I was wondering if the 8-bit pipelining was caused by this option with it being turned on.
Good to know that your problem is not caused by this. :)

[stax76]

This is a bad idea, if i do this, in the script will be forced this line:

ConverttoYV12()

With this option enabled, the input stream will be pipelined with 8-Bits, so i use ConverttoYUV420()

In 2.1.0.5 there was:

- the global setting 'Add filter to convert chroma subsampling to 4:2:0' uses now ConvertToYUV420 instead of ConverttoYV12.

[-QfG-]

But i have a new problem, if i use LSMASH for AVC or HEVC indexing, StaxRip will hang "No Response"...
With DNxHR HQX Indexing, i have no problems...

https://s12.directupload.net/images/200524/f7v74bb8.png

After few minutes:

https://s12.directupload.net/images/200524/xqhb9qnu.png

In 2.1.0.5 there was:

- the global setting 'Add filter to convert chroma subsampling to 4:2:0' uses now ConvertToYUV420 instead of ConverttoYV12.

Nice to know :). I must read all changelogs, lol, i updadeted today from 2.0.8.0 stable to the newest beta, because i need to test the chunk encoding.

I found this an another Thread:
LSMASHVideoSource only supports .mp4 and it's an index free source filter because the container format allows that.

I think, this is my problem with the mkv container, but i think Quicktime (mov) will be supported, too. My DNxHR Streams are in this container and this works fine.

[stax76]

That error comes directly from avisynth, if you open this avs script with any other avisynth app you will almost certainly see exactly the same error.

Alternatively you can try FFVideoSource and LWLibavVideoSource.

[jlw_4049]

Avspmod is good to find errors in your script before you encode

Sent from my SM-G986U1 using Tapatalk

[bananenmann]

I have exactely the same error like -QFG- ... so if you can't use LSMASH for AVC or HEVC indexing, it's Cuda Hardware support is not usable. So please again: Put back the DGINdexNV Support. It is so Important - not only for me: A lot of People have NVidia Cards and could benefit from it...

[JKyle]

I have exactely the same error like -QFG- ... so if you can't use LSMASH for AVC or HEVC indexing, it's Cuda Hardware support is not usable. So please again: Put back the DGINdexNV Support. It is so Important - not only for me: A lot of People have NVidia Cards and could benefit from it...

I've put guide posts on the other StaxRip thread about setting up DG Tools in StaxRip (>2.1.0.7).

How to register DGDecNV in StaxRip (>2.1.0.7) with the macro %startup_dir%:
https://forum.doom9.org/showpost.php?p=1913597&postcount=1885

How to register DGTonemap & DGHDRtoSDR filters in StaxRip (>2.1.0.7) with macros:
https://forum.doom9.org/showpost.php?p=1913616&postcount=1893

I hope it helps.

[bananenmann]

Great!!!

You're my Hero. Thank you for your big effort!!!
So now I can further use future Staxrip Versions!!

:)

[stax76]

I have exactely the same error like -QFG- ... so if you can't use LSMASH for AVC or HEVC indexing, it's Cuda Hardware support is not usable. So please again: Put back the DGINdexNV Support. It is so Important - not only for me: A lot of People have NVidia Cards and could benefit from it...

L-Smash CUVID hardware decoding is very robust in my experience. Please upload a sample!


@JKyle

Thanks for making the Guide. :thanks:

[JKyle]

@JKyle

Thanks for making the Guide. :thanks:

You're welcome.

BTW, these apps are updated:

chapterEditor (https://www.videohelp.com/software/chapterEditor) is now 1.23.

AVSMeter (https://www.videohelp.com/software/AVSMeter) is updated to 3.0.0.3.

QSVEnc (https://github.com/rigaya/QSVEnc/releases/tag/4.02) is now 4.02.

[JKyle]

@stax76

In 2.1.1.5, the default (empty project) Container Configuration window is too big. For both mp4 and mkv.
(Windows 10 x64 2004)

Is there any option for enabling StaxRip to remember window sizes along with positions?
The Container Configuration window reverts to its default big size after I close it.

[stax76]

@JKyle

It does remember the size, this code is new and probably has a bug with your setup. I try to upload a fix shortly.

https://github.com/staxrip/staxrip/blob/master/Forms/MuxerForm.vb#L580

[stax76]

2.1.1.6 Beta
============

- muxer dialog size issue fixed
- low DPI menu font render issue
- the Jobs, Log and Video Comparison dialogs do remember the size

[jlw_4049]

2.1.1.6 Beta
============

- muxer dialog size issue fixed
- low DPI menu font render issue
- the Jobs, Log and Video Comparison dialogs do remember the size
Thanks for the new update [emoji3]

Sent from my SM-G986U1 using Tapatalk

[JKyle]

2.1.1.6 Beta
============

- muxer dialog size issue fixed
- low DPI menu font render issue
- the Jobs, Log and Video Comparison dialogs do remember the size


Thanks for the update. I verified that the weirdly big muxer window size is fixed. :)

BTW, StaxRip-x64-2.1.1.6-beta.7z does not include DGIndex in Apps => Support folder while it's registered in the apps manage section and the version info is put in Versions.txt. Plz check it out.

And submenus in the Apps Manage window are cropped at the end, blocking part of the contents and shortcuts.

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

It's been around for quite a long time, but I've been forgetting to report.

:thanks: