StaxRip

[stax76]

Any versions of Staxrip built around ~3.5.1 seem to work fine. Any suggestions? I'm not sure whether the problems lies with Staxrip or AVS+, though it's possibly a combination of both. Unfortunately there's no way of testing the latest Stax release with an older AVS+ version.

I guess TMM2 is not compatible with AviSynth 3.6, normally StaxRip allows using old version tools but for AviSynth and VC Redist 2019 StaxRip does not allow using old versions because it has caused issued reported by users. It's still possible by editing the file Versions.txt located in the Apps folder, if you remove the AviSynth line then you can use any AviSynth version, do this on your own risk.

Maybe somebody is willing to update TMM2 if you request it in the AviSynth thread.

x264 is updated to 160 r3009.

Thanks, I've updated it to M-0.160.3007-235ce61-gcc11 Patman, it was built 5 days ago.


I noticed the same thing. I created an AVS file outside of staxrip and just called AnimeIVTC with not loading any of the plugins except for the one for the video and it loaded and worked. However if I just loaded TMM2.dll I would get the same error. So not sure what is going on but creating an AVS file and importing that should work fine I would think.


StaxRip uses a smart dependency detection, it reads the content of the script and used avsi files and then loads all dependencies it finds, it works like magic, except when it fails, for instance there are avsi files that depend on another avsi file which again depend on other avsi file, it's hardly possible to handle something like this automatically, in such case I modify the avsi file (# AvsPlusVersionNumber() added to end of MCTemporalDenoise.avsi)

If a user opens an external avs or vpy file in staxrip then this file is used as is without any modification so no automatic dependency handling happens.

[apophis906]

I guess TMM2 is not compatible with AviSynth 3.6, normally StaxRip allows using old version tools but for AviSynth and VC Redist 2019 StaxRip does not allow using old versions because it has caused issued reported by users. It's still possible by editing the file Versions.txt located in the Apps folder, if you remove the AviSynth line then you can use any AviSynth version, do this on your own risk.

Maybe somebody is willing to update TMM2 if you request it in the AviSynth thread.


I just looked and it seems that is was just updated last month. I downloaded it and tested a script loading that version and it showed no errors.
TMM2 (https://github.com/Asd-g/TMM2/releases)

[stax76]

I just looked and it seems that is was just updated last month. I downloaded it and tested a script loading that version and it showed no errors.
TMM2

Nice, I'll update it.

[Patman]

Thanks, I've updated it to M-0.160.3007-235ce61-gcc11 Patman, it was built 5 days ago.


Updated to *-0.160.3009-*

[stax76]

Thanks, I've updated it (and the download URL).

[chipxtreme]

NVEnc 5.06 has been released

Also with the latest beta it's saying my installed version of AviSynth is too old but it is current release 3.6

[jlw_4049]

NVEnc 5.06 has been released

Also with the latest beta it's saying my installed version of AviSynth is too old but it is current release 3.6I have also had this error.

Sent from my SM-G986U1 using Tapatalk

[stax76]

Using a tool with old version is allowed for any tool except avisynth and vc++ 2019, this restriction can be disabled by deleting the avisynth line in apps\versions.txt.

For this case it's better to copy the included 3.6.1 Test 8 to system32, it's a new test build but probably more stable than 3.6.0, it's used because it fixes an issue with VSFilterMod.

[Baconce]

Using a tool with old version is allowed for any tool except avisynth and vc++ 2019, this restriction can be disabled by deleting the avisynth line in apps\versions.txt.

For this case it's better to copy the included 3.6.1 Test 8 to system32, it's a new test build but probably more stable than 3.6.0, it's used because it fixes an issue with VSFilterMod.

Yeah .....Working ! plugins+ and plugins64+ added too. Don't know if it's necessary but in doubt.

[ACKR]

Hey guys just want to thank you for the new version. the file batch problem using vs is gone now everything works great now.

I wanted to ask is there a difference between these two hevc versions
3.3+2-gbe2d82093
M-3.4+6-g73f96ff39-gcc11.0.0

wanted to ask because i hadn't seen that m before in x265 builds is this a different branch?
Thanks for your time.

[stax76]

M stands for mod, it shows the estimated file size in the status line.

[ACKR]

M stands for mod, it shows the estimated file size in the status line.

ah thanks

[JKyle]

AviSynth+ 3.6.1 (https://www.videohelp.com/software/AviSynth-Plus) is released.

[Arkana]

Hi, I'm always getting this error when converting audio to AAC on latest version

----------------------- Error Audio encoding 2 -----------------------

Audio encoding 2 returned error exit code: -1073741701 (0xC000007B)


-------------------------- Audio encoding 2 --------------------------

eac3to 3.34

D:\Apps\StaxRip-x64-2.1.1.7-beta\Apps\Audio\eac3to\eac3to.exe "D:\JD DL\Crawl.2019_temp\Crawl.2019 ID1 English.ac3" "D:\JD DL\Crawl.2019_temp\Crawl.2019 ID1 English_a2.m4a" -quality=0.4 -normalize -progressnumbers


-------------------------- Audio encoding 2 --------------------------

eac3to 3.34

D:\Apps\StaxRip-x64-2.1.1.7-beta\Apps\Audio\eac3to\eac3to.exe "D:\JD DL\Crawl.2019_temp\Crawl.2019. ID1 English.ac3" "D:\JD DL\Crawl.2019_temp\Crawl.2019 ID1 English_a2.m4a" -quality=0.4 -normalize -progressnumbers

Start: 6:35:51 PM
End: 6:35:51 PM
Duration: 00:00:00

https://i.postimg.cc/WDJ2LYNk/screenshot-821.png (http://postimg.cc/WDJ2LYNk)

any idea why and how to solve it?

[jlw_4049]

Hi, I'm always getting this error when converting audio to AAC on latest version


https://i.postimg.cc/WDJ2LYNk/screenshot-821.png (http://postimg.cc/WDJ2LYNk)

any idea why and how to solve it?Try to use ffmpeg decode/encode

Sent from my SM-G986U1 using Tapatalk

[Patman]

Hi, I'm always getting this error when converting audio to AAC on latest version


https://i.postimg.cc/WDJ2LYNk/screenshot-821.png (http://postimg.cc/WDJ2LYNk)

any idea why and how to solve it?

neroAacEnc.exe is in eac3to folder?

EDIT:

I've updated some tools:

aomenc, ffmpeg (normal) and ffmpeg (libnpp_enabled), MP4Box, npp64_11 (from new cuda sdk), QTfiles64, rav1e and SVT-AV1EncApp

[JKyle]

I've updated some tools:

aomenc, ffmpeg (normal) and ffmpeg (libnpp_enabled), MP4Box, npp64_11 (from new cuda sdk), QTfiles64, rav1e and SVT-AV1EncApp

Many thanks.

It seems like ffmpeg (libnpp_enabled) has a dependency problem with libnpp library files.
I have no return from the executables.

Other binary files seem to be OK although I tested ffmpeg (normal), MP4Box, npp64_11, QTfiles64 only. :)

[JKyle]

qaac is updated to 2.69 (https://www.videohelp.com/software/qaac).

It seems OK except that the new version still fails to encode a flac file demuxed by mkvextract from an mkv file, which is an issue that needs to be addressed by mkvextract. :)

[stax76]

It seems OK except that the new version still fails to encode a flac file demuxed by mkvextract from an mkv file, which is an issue that needs to be addressed by mkvextract.

Maybe this here relates:

https://gitlab.com/mbunkus/mkvtoolnix/-/wikis/Appending-&-splitting-FLAC-audio-tracks-not-supported

[Patman]

Many thanks.



It seems like ffmpeg (libnpp_enabled) has a dependency problem with libnpp library files.

I have no return from the executables.

You need the npp files from npp64_11_v*.zip to use these version or use the npp64_11_v*.exe (extract the files to right folder). Pls test and give me a feedback.

[stax76]

@Patman

There is an issue with your SVT-AV1EncApp build not sending the same output as the official build, it causes staxrip not showing correct progress with your build, it works with the official build. Please note that my system don't use the western code page 1252 but rather UTF8.

[Patman]

@Patman

There is an issue with your SVT-AV1EncApp build not sending the same output as the official build, it causes staxrip not showing correct progress with your build, it works with the official build. Please note that my system don't use the western code page 1252 but rather UTF8.

I've found the reason, building with gcc is the problem. I've uploaded a static version (without shared lib) compiled with msvc1926 (vs).

[stax76]

I created an issue on their tracker, I think it's not because of text encoding but rather flush timing, somehow different console implementation of the compiler.

[JKyle]

You need the npp files from npp64_11_v*.zip to use these version or use the npp64_11_v*.exe (extract the files to right folder). Pls test and give me a feedback.

I verified that ffmpeg.exe/ffprobe.exe work OK if npp*.dll files in npp64_11_v2.7z are placed in the same folder as the executables.

That said, I'm wondering if this npp enabled ffmpeg will be able to provide any marginal benefit over NVEnc considering how handy and versatile it is to use NVEnc instead. NVEnc comes with more encoding options and hardware filters than ffmpeg, and in my experience, the result is almost always more satisfactory than ffmpeg. But of course npp enabled ffmpeg can become handy in a situation where ffmpeg should be run on its own. :)

BTW, is including fdk-aac in a distributed ffmpeg static build still against license? Well, since the native aac encoder in ffmpeg is still kind of mediocre, I think fdk-aac has a competitive edge in creating HE-AAC and HE-AACv2 so it's worth giving a try. But of course ignore it if it violates the license. :)

[JKyle]

Maybe this here relates:

https://gitlab.com/mbunkus/mkvtoolnix/-/wikis/Appending-&-splitting-FLAC-audio-tracks-not-supported

It's sad news. :(

Anyway, thanks for the pointer.

[JKyle]

This is a very trivial typo but since it's still there even in the latest beta (2.1.3.2), I'm putting it down here.

The Default VapourSynth Profiles line 68:

Dither | Gamma / Linear = clip = $select:Gamma To Linear|Dither.gamma_to_linear|Linear To Gamma|Dither.linear_to_gamma$(clip, curve='$select:msg:Select the Color Curve;601;709;2020$')

There, Dither.gamma_to_linear and Linear To Gamma should be separated by a semi-colon(;) not by a pipe(|).

[Patman]

BTW, is including fdk-aac in a distributed ffmpeg static build still against license?

Yeah, that's the reason why you can't find a ffmpeg with fdk-aac enabled.

EDIT:

I successfully build a x264 version with direct avs and vpy input (will upload later). My test build of x265 (not available yet) works with direct avs input and now I want to implement support for direct vpy input. I hope it works ;-)

EDIT2:

@stax76 pls update QSVEnc (4.04) and VCEEnc (6.02)

[JKyle]

I successfully build a x264 version with direct avs and vpy input.

I downloaded your new vpy-enabled x264(x264M-0.160.3009-4c9b076-gcc11.0.0.7z) and tested it with the following vpy input (resize and HDR to SDR).

import os, sys
import vapoursynth as vs
core = vs.get_core()
sys.path.append(r"D:\Utilities\StaxRip\Apps\Plugins\VS\Scripts")
core.std.LoadPlugin(r"D:\Utilities\StaxRip\Apps\Plugins\VS\fmtconv\fmtconv.dll", altsearchpath=True)
core.std.LoadPlugin(r"D:\Utilities\StaxRip\Apps\Support\DGDecNV\DGDecodeNV.dll")
clip = core.dgdecodenv.DGSource(r"D:\Work\tmp\tst\LG_New_York_HDR_UHD_4K_Demo.OriginalHDR10_temp\LG_New_York_HDR_UHD_4K_Demo.OriginalHDR10.dgi")
clip = core.resize.Spline64(clip, 1280, 720)
clip = core.fmtc.bitdepth(clip, bits=16)
core.std.LoadPlugin(r"D:\Utilities\StaxRip\Apps\Plugins\Dual\DGHDRtoSDR\DGHDRtoSDR.dll")
clip = core.dghdrtosdr.DGHDRtoSDR(clip, mode="pq", white=2600)
clip.set_output()

(I bypassed vspipe.exe by manually putting the x264 encoding command line in the Command Prompt.)

It works perfectly with direct vpy input and furthermore, gives a little gain in encoding speed over vspipe.exe in this test.

<Pipelining via vspipe.exe>
encoded 1806 frames, 37.77 fps, 4718.12 kb/s

<Direct x264 encoding>
encoded 1806 frames, 38.19 fps, 4717.61 kb/s

I guess StaxRip can now get rid of vspipe.exe when it comes to x264 encoding with your new x264 build.

:thanks:

#BTW, it would be helpful if the zipped filename is differentiated from your previous x264 builds. :)

[stax76]

Direct script input is a great feature not only for staxrip.

I changed the x264/x265 description in the apps dialog adding:

Patman mod shows the estimated size in the status line.

Remind me if I later forget to also add the avs/vpy support to the description.

If x265 supports avs input then it's necessary to generate an avisynth.dll soft link next to x265 in order to use the portable avisynth.dll instead of the installed one. Next build will do this.

I'll probably leave avs2pipemod the default however for increased compatibility, otherwise people not knowing the piping tool selection option would get an error if they replace the build with one that does not support script input.

[Patman]

#BTW, it would be helpful if the zipped filename is differentiated from your previous x264 builds. :)

THX for testing ;) all further version have vpy-input enabled, so the filename is the same. I hope it's okay :cool:

[RainyDog]

I successfully build a x264 version with direct avs and vpy input (will upload later). x265 works with direct avs input and now I want to implement support for direct vpy input. I hope it works ;-)

Thanks, look forward to giving it a whirl :)

One thing I have noticed with x264 using direct AVS input, though, is that the CPU priority in windows of x264.exe then defaults to high which makes everything else really sluggish.

But when fed via. piping it always defaults to normal, at least in the builds I've tried it with.

Do you know if there's anyway to control this because in windows you can change the priority of a running process but it just defaults back upon reboot :rolleyes:

[stax76]

2.1.3.5 Beta

- x264 encoder by default uses avs input.
- x264 encoder has pipe options for raw format.
- Flicker in Video Comparison fixed.
- New command AddBatchJob.
- AviSynth ImageSource support.
- x264 M-0.160.3009-4c9b076-gcc11 Patman
- QSVEnc 4.04
- VCEEnc 6.02
- AVSMeter 3.0.2.0

[JKyle]

TIVTC and TDeint are updated to 1.0.20 and 1.6 respectively.
Here (https://github.com/pinterf/TIVTC/releases/tag/v1.0.20).

[lordalibaski]

Just tried to do a fresh install of the latest beta and got this error

Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\Apps\Encoders\ffmpeg\AviSynth.dll

but then go to add it via apps and it says it's ok!

[JKyle]

@Patman:

On 2.1.3.6 beta, I tried to bypass avs2pipemod and input an avs file directly to your x265 build by selecting Pipe: None in x265 Options.

(Of course, 1) Decoder is set to AviSynth/VapourSynth and 2) I have AviSynth+ 3.6.1 installed on my system.)

But it fails with the following error message:

--------------------------- Video encoding ---------------------------

x265 3.4+6M(GCC11.0.0) Patman

D:\Utilities\StaxRip\Apps\Encoders\x265\x265.exe --crf 27 --output D:\Work\tmp\tst\..._temp\..._out.hevc D:\Work\tmp\tst\..._temp\....avs

x265 [error]: yuv: width, height, and FPS must be specified
x265 [error]: unable to open input file <D:\Work\tmp\tst\..._temp\....avs>

On the other hand, the same Pipe: None option with the same avs input works OK on your x264 build.

I'm curious. Doesn't your x265 support direct avs input like you said before?
If so, why does x265 require width, height, and FPS info when the input is an avs script while x264 does not?
Or, is direct avs input support not enabled in x265 yet? (This seems to be the case according to the x265 console help.)

Please enlighten me.

[Patman]

@Patman:

I'm curious. Doesn't your x265 support direct avs input like you said before?
If so, why does x265 require width, height, and FPS info when the input is an avs script while x264 does not?
Or, is direct avs input support not enabled in x265 yet? (This seems to be the case according to the x265 console help.)

Please enlighten me.

I have adjusted my previous post, which was worded unfavorably. I will upload the x265 version as soon as I have successfully implemented direct vpy input support. So far this version is not yet available for download. The demand for the height and width results from the source code see:

https://bitbucket.org/multicoreware/x265_git/src/5111e99709c830c15caf036196ba14f3a052f287/source/input/input.cpp#lines-37

https://bitbucket.org/multicoreware/x265_git/src/5111e99709c830c15caf036196ba14f3a052f287/source/input/yuv.h#lines-62

[RainyDog]

Just tried to do a fresh install of the latest beta and got this error

Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\Apps\Encoders\ffmpeg\AviSynth.dll

but then go to add it via apps and it says it's ok!

Same here. But I get the same message for a bunch of apps not just ffmpeg.

StaxRip then functions fine once I've acknowledged the errors but clearly something's a miss with this beta and AviSynth during program start up...

[lordalibaski]

Yes me too mate I couldn't be bothered to do them all last night was just putting a file in to convert before going to bed when I tried the beta these are all the errors.



Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\Apps\Encoders\ffmpeg\AviSynth.dll


Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\AviSynth.dll


Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\Apps\Encoders\NVEnc\AviSynth.dll


Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\Apps\Encoders\QSVEnc\AviSynth.dll


Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\Apps\Encoders\VCEEnc\AviSynth.dll


Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\Apps\Support\avs2pipemod\AviSynth.dll


Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\Apps\Encoders\x264\AviSynth.dll


Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\Apps\Encoders\x265\AviSynth.dll


Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\Apps\Support\mpv.net\AviSynth.dll

[stax76]

Just tried to do a fresh installation of the latest beta and got this error

Failed to create soft link.

C:\Users\jimmy\Desktop\StaxRip-x64\Apps\Encoders\ffmpeg\AviSynth.dll

but then go to add it via apps and it says it's ok!

With normal Win 10 setup creating a soft link does not need elevated privileges, there should not be any problem creating a soft link on a normal Win 10 setup! You can try creating a soft link manually to find out if it fails too.

mklink <link> <target>

Target is the full path to the real avisynth dll, link is the soft link next to ffmpeg.

https://docs.microsoft.com/de-de/windows-server/administration/windows-commands/mklink#:~:text=Erstellt%20einen%20symbolischen%20oder%20festen,file%20symbolic%20or%20hard%20link.

Alternatively you can use vapoursynth instead, it does not need any special soft link workarounds to make portable mode work. The problem is avisynth and avisynth tools and there is not much I can do except making feature requests for various avisynth tools.

A started pausing any development however, only critical issues will be fixed.

To enable VapourSynth:

Filters > Filter Setup > VapourSynth

Or you can use installed AviSynth, just install AviSynth 3.6.1 x64, go in the staxrip settings dialog and disable avisynth portable mode, restart staxrip, after that staxrip should not try creating soft links, you need the latest beta.

[JKyle]

With normal Win 10 setup creating a soft link does not need elevated privileges, there should not be any problem creating a soft link on a normal Win 10 setup!

True but only if you've enabled Developer Mode.

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

See this post (https://www.wintellect.com/non-admin-users-can-now-create-symlinks-windows-10/).

If Developer Mode is off, you need elevation.

[JKyle]

I will upload the x265 version as soon as I have successfully implemented direct vpy input support. So far this version is not yet available for download.

Got it. :thanks: for letting me know. :)

[lordalibaski]

Disabling portable worked a treat thanks stax.

Sorry to sound a bit daft here guys but I am wanting to put 5 minute chapters in a x265/mkv conversion how do I do this using chaptereditor, can it be done during conversion or does it need to be done after conversion? I have never used chaptereditor before I usually use mkv chapterizer but thought I would give chaptereditor a go.

[stax76]

@JKyle

Thanks for pointing out the soft link privilege issue, there is a new beta build which fixed it hopefully.

It creates soft links only when needed and gives clear instruction in case it cannot create the links:


Failed to create soft link

D:\Projekte\VB\staxrip\bin\Apps\Encoders\ffmpeg\AviSynth.dll

Soft link creation is required to use AviSynth+ in portable mode due to design limitations of AviSynth+ and ffmpeg.

Option one is installing a compatible AviSynth+ version and disabling AviSynth+ portable mode in the StaxRip settings (Tools > Settings > General).

Option two is running StaxRip with administrative privileges until soft link creation completes, this has to be done only once, after the links were created, regular privileges are sufficient.

Option three is enabling Developer Mode in the Windows 10 settings, this allows soft link creation without administrative privileges.

[JKyle]

...there is a new beta build which fixed it hopefully.

It creates soft links only when needed and gives clear instruction in case it cannot create the links:

Great! It's well guided. I'm sure it will remove users' confusion. :)

[JKyle]

MKVToolNix is updated to 48.0.0 (https://www.videohelp.com/software/MKVToolNix) today.

[JKyle]

NVEnc is updated to 5.07 (https://github.com/rigaya/NVEnc/releases/tag/5.07) today.

However, NVEncC64.exe in NVEncC_5.07_x64.7z returns nothing on my system.
Is anyone experiencing the same issue?
(I put an issue on rigaya's NVEnc GitHub repo (https://github.com/rigaya/NVEnc/issues/246).)

[chipxtreme]

NVEnc is updated to 5.07 (https://github.com/rigaya/NVEnc/releases/tag/5.07) today.

However, NVEncC64.exe in NVEncC_5.07_x64.7z returns nothing on my system.
Is anyone experiencing the same issue?
(I put an issue on rigaya's NVEnc GitHub repo (https://github.com/rigaya/NVEnc/issues/246).)

Once you download nppc64_10.dll it works. Oversight or bug

[JKyle]

Once you download nppc64_10.dll it works. Oversight or bug

:thanks: for the info.

You're right. Unlike 5.06, 5.07 needs this dll - nppc64_10.dll - and rigaya forgot to include it in the distributed zip file.

But I'd like to ask why 5.07 suddenly became dependent on this old dll while 5.06 was NOT.

We already have more recent dlls built by @Patman - nppc64_11.dll, nppif64_11.dll, nppig64_11.dll, etc. - and they are working good with 5.06.
I tried putting nppc64_11.dll instead of nppc64_10.dll, but unfortunately, it's not working with 5.07.

:(

[JKyle]

NVEnc is updated to 5.08 (https://github.com/rigaya/NVEnc/releases/tag/5.08) with the nppc64_10.dll dependency issue fixed.

[AntiqueRefrigerator]

I am attempting to convert some OBS footage that I recorded.

Input: AVC. Chroma subsampling: 4:4:4. Bit Depth: 8 bits Color range: Full. Matrix Co: BT.709

Source: FFVideoSource

Preview in StaxRip appears excessively dark.

Example (Left: MPC-BE) (Right: Staxrip Preview)

https://imgur.com/ShLb0Q9

Desired Output: NVENC HEVC. Chroma: 4:2:0 Bit Depth: 10 bits. Color range: Limited. Matrix Co: BT.709

All of my shadowplay footage appears correct, but for some reason, the footage I'm inputting from OBS appears really dark. Could this have something to do with my input chroma and color range?

Here's a 4 second sample (may take a while for me to upload): https://www.dropbox.com/s/o9ae9id536namzs/2020-07-02_12-10-09_sample_MKV.zip?dl=0