StaxRip

[44vince44]

Line > Sharpen provides you with some filters.

You can also check many other filters here: http://avisynth.nl/index.php/Main_Page
or google for VapourSynth filter.

[JKyle]

Since the AviSynth native Sharpen filter is missing from the default AVS Profiles, let me add it and make a PR.
(And same for the VapourSynth port muvsfunc.Sharpen.)

---

...And done.

The next release will have Sharpen in the default AVS/VS filter profiles.

In the meantime, add the following line in your AVS/VS Profiles under the [Line] section in order to use Sharpen from now on.

## AVS
Sharpen | Sharpen = Sharpen($enter_text:Enter the Amount of Sharpness in decimal (from -1.58 to 1.0)$)

## VS
Sharpen | Sharpen = clip = muvsfunc.Sharpen(clip, $enter_text:Enter the Amount of Sharpness in decimal (from -1.58 to 1.0)$)


BTW, you can always add native AVS filters in the Code Editor not worrying about dependencies.
Just because native filters are not listed in the default filter profiles does not mean they are not available.
Think of the filter profiles as just helpers.

[shodan5000]

BTW, you can always add native AVS filters in the Code Editor not worrying about dependencies.
Just because native filters are not listed in the default filter profiles does not mean they are not available.
Think of the filter profiles as just helpers.

That is something that I've always found confusing and annoying. Why can't ALL available filters be listed? Why some and not others? I believe many do not wish to have to add code just to see functions that the program has but just chooses not to show.

[JKyle]

That is something that I've always found confusing and annoying. Why can't ALL available filters be listed?

Aside from @stax76's original idea, I personally don't like the idea of carrying the list of all internal filters as a user. Packing all internal filters into default profiles just makes the list unnecessarily long and unwieldy.

Users can always refer to the list of internal filters (http://avisynth.nl/index.php/Internal_filters) on the AviSynth wiki, and make up their own scripts in the Code Editor. If they find some filters are important to them but missing, they can make their own filter profiles for those filters.

Why some and not others?

Because those filter profiles were composed and contributed by participants.

StaxRip is not some clandestine software program that is closed to general users. If you find something annoying and confusing, you can customize the app to your taste. If you want to share your work, you can participate and make a pull request on the GitHub repo.

To be frank, I don't understand why this can be a matter to complain about. :eek:

[JKyle]

I tried and compared this (checked with 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9 & 1.0 decimal value) with RipBot264 v1.26.0's Sharpen (at 100%) but none of them matched with RipBot264 v1.26.0's Sharpen (at 100%).

Where RipBot264 v1.26.0's Sharpen script is:
#Sharpen
Loadplugin("C:\RipBot264v1.26.0\Tools\AviSynth plugins\Plugins_JPSDR\Plugins_JPSDR.dll")
Loadplugin("C:\RipBot264v1.26.0\Tools\AviSynth plugins\CAS\CAS.dll")
Import("C:\RipBot264v1.26.0\Tools\AviSynth plugins\Scripts\MCAS.avs")
video=MCAS(video,1.0)

That's why I asked for a script code in the first place. :(

Basically, the sharpen filter you're talking about is MCAS(MCAS.avs), but I have no idea where it came from. It's not listed in the (official) external filter list of the AviSynth wiki (http://avisynth.nl/index.php/External_filters). I can't proceed without a proper pointer here. :confused:

And one of its dependencies, CAS is an external AVS plugin listed in the AviSynth wiki (http://avisynth.nl/index.php/CAS), but it's not registered in StaxRip.

So basically you need to get two things to begin with: MCAS.avs and CAS.dll (x64 build).

Then you can

1) either put them somewhere under %settings_dir%Plugins\AviSynth\ and use by yourself after composing a corresponding avs profile script for MCAS

or

2) request MCAS and CAS to be registered in StaxRip with a proper profile script code in Tool Update Request (https://github.com/staxrip/staxrip/wiki/Tool-Update-Requests).

Like I said above, I can't help any more without further info and resources.

[JKyle]

OK. I've figured out that MCAS is an in-house script composed by the RipBot264 author @Atak_Snajpera.

I slightly modified the script code for use in StaxRip and am asking for a redistribution permission from him: here (https://forum.doom9.org/showthread.php?p=1940875#post1940875).

If he says yes, we can go on.

[guest]

OK. I've figured out that MCAS is an in-house script composed by the RipBot264 author @Atak_Snajpera.

I slightly modified the script code for use in StaxRip and am asking for a redistribution permission from him: here (https://forum.doom9.org/showthread.php?p=1940875#post1940875).

If he says yes, we can go on.

I think if you have a look here, it's just a "tidy up" of a slightly different script.

http://forum.doom9.net/showthread.php?p=1927744#post1927744

And scroll down to the script being shown...

And if he says no...then what ??? call it something else.

[BobDig]

I saw this (complicated) Guide explaining:How to set up a simple multithreaded QTGMC template for AviSynth

Why not just using the QTGMC deinterlacer with VapourSynth, is the one for avisynth any better?

[JKyle]

If you find it complicated/difficult and are not willing to figure out the underlying workings, then don't bother.
As a matter of fact, I don't understand why users keep asking about this not even giving it a try.

[44vince44]

Thanks JKyle for your latest additions, and for helping users with their requests.

In return, I wish users were more willing to overcome the apparent difficulty they find, because it is only apparent, and this "complication" only reflects what video processing can sometimes be, by nature, complicated.
I wish to express my full support to what you do JKyle !

[JKyle]

I wish to express my full support to what you do JKyle !

:thanks:

And if he says no...then what ??? call it something else.

I believe @Atak_Snajpera will not disagree.
But in the meantime, users can still use MCAS on their own by taking the following steps.

1) Go to this post (https://forum.doom9.org/showthread.php?p=1940875#post1940875), copy what's inside the Code:, and save it as MCAS.avsi using a text editor.
Make sure the text encoding is UTF-8.

2) Download CAS-1.0.1.7z from here (https://github.com/Asd-g/AviSynth-CAS/releases), unzip it, and get the x64 CAS.dll file.
(CHANGELOG.md and README.md are optional.)

3) Put the files from 1) and 2) in one folder, like %settings_dir%Plugins\AviSynth\CAS as follows:

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

4) Compose an AVS filter profile item under the [Line] category as follows:

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

Sharpen | MCAS =
Loadplugin("%app:JPSDR%")
Loadplugin("%settings_dir%Plugins\AviSynth\CAS\CAS.dll")
Import("%settings_dir%Plugins\AviSynth\CAS\MCAS.avsi")
MCAS($enter_text:Enter the Amount of Sharpness in decimal (between 0.0 and 1.0)$)

(Blank lines above and below)

Then you'll be able to start using MCAS in Line > Sharpen.

[guest]

I believe @Atak_Snajpera will not disagree.

Well, so much for Atak giving you his permission.....I would have been VERY surprised if he had of said anything....it's not copyrighted , but I guess it's the "polite thing to do", so props to you, for at least trying to reach out.

I recall some time back, someone actually had the audacity to ask him for the Distributed Encoding code, as he was working on his own project. Needless to say.....(do you hear that ???..silence)

But you could have made some subtle changes (other than what you needed to do for Staxrip to use it), and simply named it something else. And you still could !!!

I also think it was a lot of trouble to go to, for a filter that in my experience, doesn't make much difference, anyway.

There must have been a slightly easier way to have done it, tho.

Anyway, the deed is done, I guess it will be made available in the next Staxrip build.

What REALLY needs to be worked on is a Distributed Encoding option...now THAT would be a massive game changer for Staxrip.

With the already almost limitless options that Staxrip offers (compared to RipBot264), if it had DE, then EVERYONE would be using it.

[guest]

Thanks. It worked and matched.

And I know you (ProBroSam) asked Atak a question about HDR to SDR, and his reply was basically useless...he posted a LONG line of code, and said "...manually tweak values..." ....der !!!

Let me remind you :-

https://forum.doom9.org/showthread.php?p=1938810#post1938810

Frustrating, to say the least :(

[JKyle]

But you could have made some subtle changes (other than what you needed to do for Staxrip to use it), and simply named it something else. And you still could !!!
I also think it was a lot of trouble to go to, for a filter that in my experience, doesn't make much difference, anyway.
There must have been a slightly easier way to have done it, tho.

I know and I agree. But I just don't want to steal someone else's idea and put it in StaxRip officially without prior acknowledgement.
Using a publicly available script personally as a user and putting it officially in a release are totally different things.

Anyway, the deed is done, I guess it will be made available in the next Staxrip build.

We could simply put CAS instead of the in-house script MCAS if we do not hear anything from him.
But users could still use MCAS on their own with some slightly modified AVS profile script.

What REALLY needs to be worked on is a Distributed Encoding option...now THAT would be a massive game changer for Staxrip.
With the already almost limitless options that Staxrip offers (compared to RipBot264), if it had DE, then EVERYONE would be using it.

Distributed Encoding in RipBot264 (without distribution to different servers) = Chunk Encoding in StaxRip.

They are already available for x265 and aomenc in StaxRip (although the chunks are uniformly divided total number of frames, which is kind of primitive in that the division is not scene-aware...)

Combined with Maximum number of parallel processes in Tools > Settings > General,

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

you can make full use of your CPU cores by utilizing chunk encoding options in x265 and aomenc:

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

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


Scene-aware chunk encoding was proposed by @tkozybski recently (https://github.com/staxrip/staxrip/issues/619), but we have a couple of BIG barriers that hinder its implementation in StaxRip, and so it's kind of on hold as of now.

[guest]

I know and I agree. But I just don't want to steal someone else's idea and put it in StaxRip officially without prior acknowledgement.
Using a publicly available script personally as a user and putting it officially in a release are totally different things.

We could simply put CAS instead of the in-house script MCAS if we do not hear anything from him.
But users could still use MCAS on their own with some slightly modified AVS profile script.

Scene-aware chunk encoding was proposed by @tkozybski recently (https://github.com/staxrip/staxrip/issues/619), but we have a couple of BIG barriers that hinder its implementation in StaxRip, and so it's kind of on hold as of now.

Nice little explanation & tutorial there, thanks :)

Excuse my ignorance, but what's "aomenc" ?

Yeah, well I will be paying attention to see if you get some response from him...but I kinda doubt it, somehow.

I'd just rename it, and be done.

If RipBot264 didn't have Distributed Encoding, I don't think too many people would be using it, (I wouldn't) and it hasn't really got that much going for it, compared to Staxrip & Hybrid....it's difficult to change that much, although you can add new & different filters & scripts (which I have been busy doing)

I think there is only one other app that has a limited type of DE, and I think it's call Media Coder..I tried it once, but :(

The thing with RB, IS the DE function, you get the "help" of as many other pc's that you've got, and it speeds up the process so much..and with x265 & 4K encoding all the go, speed & power is a must.

I must admit I haven't spent too much time using Staxrip, but even with the chunk encoding option, it's still only using one machine :(

I do have a Ryzen 3950X, so that would help I'm sure, but then why just use the one pc....you know where I'm going with this, don't you ??

It's just the raw encoding speed & power of DE, that just makes you want to use RipBot for basic, no frills encoding.

Once you've used DE, you can never go back !!

[JKyle]

aomenc is an AV1 encoder by AOM.

As a matter of fact, I'm not interested in distributing the encoding processes to different machines.

You could add it as a feature request on the GitHub Issue Tracker (https://github.com/staxrip/staxrip/issues) if you so eagerly wish for such a feature, but I'm not sure if it will be adopted.

My guess is that there are too many barriers and complications if this 'distributed encoding among multiple machines' feature is to be PROPERLY implemented along with the rich features currently available in StaxRip. But I don't have enough knowledge to talk about it beyond that point.

[guest]

aomenc is an AV1 encoder by AOM.

As a matter of fact, I'm not interested in distributing the encoding processes to different machines.

You could add it as a feature request on the GitHub Issue Tracker (https://github.com/staxrip/staxrip/issues) if you so eagerly wish for such a feature, but I'm not sure if it will be adopted.

My guess is that there are too many barriers and complications if this 'distributed encoding among multiple machines' feature is to be PROPERLY implemented along with the rich features currently available in StaxRip. But I don't have enough knowledge to talk about it beyond that point.

Well, maybe Atak has more know how (or help) to have been able to successfully implement it.

I did read somewhere that he stated it was quite easy to do.

Oh well....keep up the good work :)

[craigpro]

silly question regarding StaxRIP - in the bottom line while encoding it says GPU xx% and VE yy% where GPU usageis fairly obvious, but what does VE stand for please?

Google didn't help me find the answer.

Thank you.

[guest]

Now I have only three things left to know.

1. I need the SMDegrain MDegrain3 code for StaxRip. So that I can add it manually

2. Image Output Mod 4 vs Image Output Mod 8. Which is better? Do they really affect the quality?

3. What is the right order to use the filters serially for better output? I use only this filters. Is the serial okay?

I might be able to help you with #1 :-

Can you change this in the editor and some how save it...

super_search = Dither_Luma_Rebuild(S0=1.0, c=0.0625).MSuper(rfilter=4)
bv1 = super_search.MAnalyse(isb=true, delta=1, overlap=4)
bv2 = super_search.MAnalyse(isb=true, delta=2, overlap=4)
bv3 = super_search.MAnalyse(isb=true, delta=3, overlap=4)
fv1 = super_search.MAnalyse(isb=false, delta=1, overlap=4)
fv2 = super_search.MAnalyse(isb=false, delta=2, overlap=4)
fv3 = super_search.MAnalyse(isb=false, delta=3, overlap=4)
MDegrain3(MSuper(levels=1), bv1, fv1, bv2, fv2, bv3, fv3, thSAD=300, thSADC=150)

[JKyle]

super_search = Dither_Luma_Rebuild(S0=1.0, c=0.0625).MSuper(rfilter=4)
bv1 = super_search.MAnalyse(isb=true, delta=1, overlap=4)
bv2 = super_search.MAnalyse(isb=true, delta=2, overlap=4)
bv3 = super_search.MAnalyse(isb=true, delta=3, overlap=4)
fv1 = super_search.MAnalyse(isb=false, delta=1, overlap=4)
fv2 = super_search.MAnalyse(isb=false, delta=2, overlap=4)
fv3 = super_search.MAnalyse(isb=false, delta=3, overlap=4)
MDegrain3(MSuper(levels=1), bv1, fv1, bv2, fv2, bv3, fv3, thSAD=300, thSADC=150)

Thanks for the info.

MDegrain3 filter profile will be added to the default AVS profiles.

2. Image Output Mod 4 vs Image Output Mod 8. Which is better? Do they really affect the quality?

Mod 4 = divisible by 4 = multiples of 4
Mod 8 = divisible by 8 = multiples of 8

They have nothing to do with quality. Some codecs/encoders are picky about resolution like whether the height/width is divisible by a particular number, e.g. 2 (=even). For example, x264 and x265 require that source resolution should be even.

This is esp. important considering that chroma subsampling is mostly done by the unit of 4x2 pixel blocks. But when the chroma subsampling scheme is 4:2:0, (which is very popular in most video pixel formats), mod 2 (=even) is more than enough. That's why popular encoders require only mod 2.

3. What is the right order to use the filters serially for better output?

You better learn by doing. ;)

[JKyle]

what does VE stand for please?

VE = Video Encode

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

It shows how hard the NVENC chips are working.

[Andy]

:)

I believe @Atak_Snajpera will not disagree.
But in the meantime, users can still use MCAS on their own by taking the following steps.

1) Go to this post (https://forum.doom9.org/showthread.php?p=1940875#post1940875), copy what's inside the Code:, and save it as MCAS.avsi using a text editor.
Make sure the text encoding is UTF-8.

2) Download CAS-1.0.1.7z from here (https://github.com/Asd-g/AviSynth-CAS/releases), unzip it, and get the x64 CAS.dll file.
(CHANGELOG.md and README.md are optional.)

3) Put the files from 1) and 2) in one folder, like %settings_dir%Plugins\AviSynth\CAS as follows:

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

4) Compose an AVS filter profile item under the [Line] category as follows:

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

Sharpen | MCAS =
Loadplugin("%app:JPSDR%")
Loadplugin("%settings_dir%Plugins\AviSynth\CAS\CAS.dll")
Import("%settings_dir%Plugins\AviSynth\CAS\MCAS.avsi")
MCAS($enter_text:Enter the Amount of Sharpness in decimal (between 0.0 and 1.0)$)


Great! :) :thanks:

[guest]

Thanks for the info.

MDegrain3 filter profile will be added to the default AVS profiles.

Hey JKyle,

I actually didn't expect that script to be added to Staxrip, so that's a pleasant surprise.

And I'd say this would be MDegrain4 :-

super_search = Dither_Luma_Rebuild(S0=1.0, c=0.0625).MSuper(rfilter=4)
bv1 = super_search.MAnalyse(isb=true, delta=1, overlap=4)
bv2 = super_search.MAnalyse(isb=true, delta=2, overlap=4)
bv3 = super_search.MAnalyse(isb=true, delta=3, overlap=4)
bv4 = super_search.MAnalyse(isb=true, delta=4, overlap=4)
fv1 = super_search.MAnalyse(isb=false, delta=1, overlap=4)
fv2 = super_search.MAnalyse(isb=false, delta=2, overlap=4)
fv3 = super_search.MAnalyse(isb=false, delta=3, overlap=4)
fv4 = super_search.MAnalyse(isb=false, delta=4, overlap=4)
MDegrain4(MSuper(levels=1), bv1, fv1, bv2, fv2, bv3, fv3, bv4, fv4, thSAD=300, thSADC=150)

You might be able to add blksize=8 (which I think might be default, and for SD), or blksize=16 for HD.

I've been using this one (slightly differently scripted) a lot in RipBot, and had some great results.

But just in the last week or so I have been trying SMDegrain with a heavy grain filter, and to my eye's I think it's better, especially on older "dirty" footage.

I'm curious about the SMDegrain MDegrain2 filter in Staxrip, does that use both filters ???...to my untrained eye, it looks like it has MANY dependancies, but only the "script" for MDegrain....how does that work ??:confused:

[craigpro]

VE = Video Encode

It shows how hard the NVENC chips are working.

Ahh thank you JKyle - yeah VE is always 99%, so guess it's going flat out (CPU is usually under 10%).

[Atlantis]

For Image Output Mod definitely go with 8 and not lower. For long I said it should be mod 2 and I will go safe and go mod 4 and I learned it the hard way.

Some of the even recent hardware, especially amlogic for example can only handle mod 8 and higher. Most of my encodes are bad. Personally when I have to add black bars, I just go mod 16.

[JKyle]

I'm curious about the SMDegrain MDegrain2 filter in Staxrip, does that use both filters ???

The SMDegrain MDegrain2 filter profile in the default AVS profiles is kind of a misnomer.
It's just a call to MDegrain2 with proper options that has the same result with a simple call to SMDegrain().
You can see it here (http://avisynth.nl/index.php/SMDegrain#Introduction).
The profile name will be modified properly in the next release.

...to my untrained eye, it looks like it has MANY dependancies, but only the "script" for MDegrain....how does that work ??:confused:

Because StaxRip takes care of all the dependencies.

---

About MDegrain4 etc., I think we better leave it to users' choice. A custom filter profile item can be easily made, IMHO.

[JKyle]

For Image Output Mod definitely go with 8 and not lower. For long I said it should be mod 2 and I will go safe and go mod 4 and I learned it the hard way.

Some of the even recent hardware, especially amlogic for example can only handle mod 8 and higher. Most of my encodes are bad. Personally when I have to add black bars, I just go mod 16.

That's definitely a hardware issue. It's not related to the video quality or codec/encoder specs per se.

Users are required to look closely into the hardware specs before they do any encodes for the corresponding hardware.

[guest]

The SMDegrain MDegrain2 filter profile in the default AVS profiles is kind of a misnomer.
It's just a call to MDegrain2 with proper options that has the same result with a simple call to SMDegrain().
You can see it here (http://avisynth.nl/index.php/SMDegrain#Introduction).
The profile name will be modified properly in the next release.

Because StaxRip takes care of all the dependencies.
---
About MDegrain4 etc., I think we better leave it to users' choice. A custom filter profile item can be easily made, IMHO.

Thanks for the great explanation :)

So in your opinion, which filter does the better job, MDegrain(s), or SMDegrain(s) ??

As a RipBot user, "we" only have MDegrain filters (1 - 3) as default, and I was using 3 & 4 to clean up some nasty grainy stuff, and was pretty happy with the result's, albeit, it would take a long time, especially on 4K footage.

But very recently I have created / added several SMDegrain filters to RipBot, and the one I call SMDegrain_Grainy, does a much better job than MDegrain4. IMO.

This script here (I know, pretty basic), works very well..

SMDegrain(tr=6,thSAD=600,contrasharp=30,prefilter=1,str=1.2,refinemotion=true) from here (http://avisynth.nl/index.php/SMDegrain#Introduction), sort of.

[JKyle]

So in your opinion, which filter does the better job, MDegrain(s), or SMDegrain(s) ??

...very recently I have created / added several SMDegrain filters to RipBot, and the one I call SMDegrain_Grainy, does a much better job than MDegrain4. IMO.

This script here (I know, pretty basic), works very well..

SMDegrain(tr=6,thSAD=600,contrasharp=30,prefilter=1,str=1.2,refinemotion=true) from here (http://avisynth.nl/index.php/SMDegrain#Introduction), sort of.

Actually, @44vince44 added the following two SMDegrain filter profiles to the default AVS profiles a while ago:

SMDegrain Hard Grain:
SMDegrain(tr=6, thSAD=600, contrasharp=true, refinemotion=true)

SMDegrain Light Grain:
SMDegrain(tr=1, thSAD=300, contrasharp=true)

Yours seems pretty similar to his SMDegrain Hard Grain setting.

About which is better b/w MDegrain and SMDegrain, I can't tell because I don't use denoise filters a lot. But at least I can tell this: use whichever fits your goal better. :)

# BTW, I've found that MDegrain4 through MDegrain6 are not registered as available filters for MVTools in StaxRip. Will fix this for later releases.

[lordalibaski]

Gents I have just tried adding this command line in the latest version

-af dynaudnorm=p=0.94:m=80:s=22

to boost audio and it come up with this error it worked fine in version 2.1.8.


Error Audio Encoding 1 (v2.4.0)

Audio Encoding 1 returned exit code: 1 (0x1)

It's unclear what this exit code means, in case it's
a Windows system error then it possibly means:

# for hex 0x1 / decimal 1
STATUS_WAIT_1 ntstatus.h
ERROR_INVALID_FUNCTION winerror.h
# Incorrect function.
# as an HRESULT: Severity: SUCCESS (0), FACILITY_NULL (0x0), Code 0x1
# for hex 0x1 / decimal 1
ERROR_INVALID_FUNCTION winerror.h
# Incorrect function.



-------------------------- Audio Encoding 1 --------------------------

ffmpeg N-101743-gcad3a5d715-x64-gcc10.2.0 Patman

C:\Users\jimmy\Desktop\Stax\StaxRip-v2.4.0-x64\Apps\FrameServer\AviSynth\ffmpeg.exe -i "C:\Users\jimmy\Desktop\To Convert\1990 DMC World Finals_temp\1990 DMC World Finals T80 2_0ch 256Kbps DELAY -192ms.ac3" -c:a ac3 -b:a 256k -af volume=2.9dB af dynaudnorm=p=0.94:m=80:s=22 -y -hide_banner "C:\Users\jimmy\Desktop\To Convert\1990 DMC World Finals_temp\T80 2_0ch 256Kbps DELAY -192ms_2168800970.ac3"

[ac3 @ 000001c4fb37b140] Estimating duration from bitrate, this may be inaccurate
Input #0, ac3, from 'C:\Users\jimmy\Desktop\To Convert
\1990 DMC World Finals_temp\1990 DMC World Finals T80 2_0ch 256Kbps DELAY -192ms.ac3':
Duration: 01:05:32.69, start: 0.000000, bitrate: 255 kb/s
Stream #0:0: Audio: ac3, 48000 Hz, stereo, fltp, 256 kb/s
[NULL @ 000001c4fcae44c0] Unable to find a suitable output format for 'af'
af: Invalid argument

StaxRip.ErrorAbortException: Audio Encoding 1 returned exit code: 1 (0x1)

It's unclear what this exit code means, in case it's
a Windows system error then it possibly means:

# for hex 0x1 / decimal 1
STATUS_WAIT_1 ntstatus.h
ERROR_INVALID_FUNCTION winerror.h
# Incorrect function.
# as an HRESULT: Severity: SUCCESS (0), FACILITY_NULL (0x0), Code 0x1
# for hex 0x1 / decimal 1
ERROR_INVALID_FUNCTION winerror.h
# Incorrect function.



-------------------------- Audio Encoding 1 --------------------------

ffmpeg N-101743-gcad3a5d715-x64-gcc10.2.0 Patman

C:\Users\jimmy\Desktop\Stax\StaxRip-v2.4.0-x64\Apps\FrameServer\AviSynth\ffmpeg.exe -i "C:\Users\jimmy\Desktop\To Convert\1990 DMC World Finals_temp\1990 DMC World Finals T80 2_0ch 256Kbps DELAY -192ms.ac3" -c:a ac3 -b:a 256k -af volume=2.9dB af dynaudnorm=p=0.94:m=80:s=22 -y -hide_banner "C:\Users\jimmy\Desktop\To Convert\1990 DMC World Finals_temp\T80 2_0ch 256Kbps DELAY -192ms_2168800970.ac3"

[ac3 @ 000001c4fb37b140] Estimating duration from bitrate, this may be inaccurate
Input #0, ac3, from 'C:\Users\jimmy\Desktop\To Convert\1990 DMC World Finals_temp\1990 DMC World Finals T80 2_0ch 256Kbps DELAY -192ms.ac3':
Duration: 01:05:32.69, start: 0.000000, bitrate: 255 kb/s
Stream #0:0: Audio: ac3, 48000 Hz, stereo, fltp, 256 kb/s
[NULL @ 000001c4fcae44c0] Unable to find a suitable output format for 'af'
af: Invalid argument


at StaxRip.Proc.Start() in D:\Code\Github\staxrip\staxrip\Source\General\Proc.vb:line 361
at StaxRip.GUIAudioProfile.Encode() in D:\Code\Github\staxrip\staxrip\Source\General\AudioProfile.vb:line 826
at StaxRip.GlobalClass._Closure$__._Lambda$__115-4() in D:\Code\Github\staxrip\staxrip\Source\General\GlobalClass.vb:line 310
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:\Code\Github\staxrip\staxrip\Source\General\GlobalClass.vb:line 353



Hmmm put this command in and its working fine -af dynaudnorm=p=0.94:m=70:s=22.

[JKyle]

Yeah. Wrong syntax.

It should be -af, not af.

[NULL @ 000001c4fcae44c0] Unable to find a suitable output format for 'af'
af: Invalid argument

[manolito]

Not related to StaxRip, but to the ffmpeg command line syntax:

If you have two -af commands in the same command line, only one of them (the latest one) will be executed. To combine filters you need to put them into one -af command separating the filters with a comma. No spaces between the filters (unless you put the filter params between double quotes).

[JKyle]

Thanks for the reminder, @manolito.

So basically, -af volume=2.9dB is redundant(=overridden) in your command line, @lordalibaski.

Kill it by toggling off Normalize in Audio Settings.

Or else choose dynaudnorm instead of volumedetect in More... > ffmpeg > Normalize Method.

[lordalibaski]

Yeah. Wrong syntax.

It should be -af, not af.

[NULL @ 000001c4fcae44c0] Unable to find a suitable output format for 'af'
af: Invalid argument

This is what I couldn't understand mate cos all I changed was 70:s=22 in the command line and it worked, it might have been because I pasted it and it put a space giving it an extra character at the front.

Also having a weird issue converting using quality 14 - super high, usually when converting a file of this size it usually comes out the exact same size or slightly bigger but it's been coming out at 1.6gb in size like it's not converting at 14 super high.

This was my setting (1st time I have used SMDegrain end result on that was poor)

https://i.postimg.cc/26DLQJr0/Screenshot-2021-04-24-013143.png

Here's the log file
https://www.sendspace.com/file/7iy3y5

[JKyle]

As of today(Apr 26, 2021), DG announced that the DRM (licensing) of DGDecNV is removed.
Read this update notification (http://rationalqm.us/board/viewtopic.php?f=5&t=463&start=275).

So starting now, you can download and use it for free in StaxRip (and in other AVS related software as well).

Use the default x64 build and rename DGIndexNV.exe.manifest~ to DGIndexNV.exe.manifest before putting it to use in StaxRip. This makes the generated dgi file encoded in UTF-8.

You can refer to this wiki document (https://github.com/staxrip/staxrip/wiki/How-to-register-DGDecNV(DGSource-and-DGIndexNV)-in-StaxRip) for how to use it in StaxRip.

Personally, I welcome and appreciate their decision although I am a licensed user myself. :) However, this decision doesn't necessarily mean that DGDecNV can be included and shipped/redistributed with StaxRip. As usual, it requires further confirmation from the author's end.

[Atlantis]

What's the use for DGDecNV? Is it even good?

Is the decoded quality always the same? Hardware or software? If it's speed, does it make a difference? When encoding x265 it takes so much time that does it really make a difference?

[jlw_4049]

It's a source filter with included CUDA utility filters. The source filter has HW crop, resize, and deinterlacing. Yes, it is good.

Yes.

Any CPU saved during decoding/crop/resize/deinterlacing is available for encoding.

Beyond frame serving to Avisynth/Vapoursynth, DGIndexNV is a useful tool for analyzing streams.

You may also find DGDemux useful.Never tried it before myself, but seems interesting.

Sent from my SM-G986U1 using Tapatalk

[manolito]

VideoHelp has 3 reviews about DGDecNV, they are by everyone, gonca and veresov. I do not know everyone, I know gonca from Doom9 and I know that he is a longtime fan of DG Tools. And veresov is just another incarnation of Mr. DG himself.

The thing which makes me chuckle is that only veresov gives DGDecNV an overall rating of only 9/10, the other two rate it as 10/10. So only the author himself thinks that his software is below the highest possible rating. Just being humble?

Don't get me wrong, I am absolutely sure that the DGTools are top notch software, second to none. I cannot use them myself because my hardware does not support it (older Lenovo ThinkPad with NVidia Optimus hardware, but no way to use current NVidia drivers).

Cheers
manolito

[44vince44]

DGDecNV is known to be very good.

This is great news, especially if we could include it as possible source filter in StaxRip!

[Atlantis]

Who removed the author's post? Overall I don't believe there be any advantage when encoding x265. The encoding is already slow and I bet this doesn't improve anything.

[Atak_Snajpera]

Who removed the author's post? Overall I don't believe there be any advantage when encoding x265. The encoding is already slow and I bet this doesn't improve anything.

Most likely the author himself. He does that from time to time...

[Arkana]

Hello, is it possible to encode Dolby Vision (retaining the metadata) on Staxrip yet? Just like HDR10+ that yet possible

[44vince44]

The main advantage of DGDecNV is as a source/frameserver. Many users have found that using it allows opening some files better than other sources.

[OAKside]

Is there any way to preview at 1:1 (no resizing)? I've tried a few settings under "Preview size compared to screen size" but it seems I can't accomplish this. Or maybe someone can explain why it was removed (many months ago), or the superiority of the current preview options.

[JKyle]

Hello, is it possible to encode Dolby Vision (retaining the metadata) on Staxrip yet? Just like HDR10+ that yet possible

Simply put, you need to

1) extract the RPU file (containing the dynamic metadata of the video stream) using dovi_tool (https://github.com/quietvoid/dovi_tool) in the Command Prompt.

2) use x265 to inject the RPU file in the HEVC video stream while in encoding by sticking to some Dolby Vision encoding rules.

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

For further info, refer to this post (https://codecalamity.com/encoding-uhd-4k-hdr10-videos-with-ffmpeg/).

[Atlantis]

This is great that we can encode Dolby Vision in Staxrip. Is this information available in a Staxrip Wiki? It should be a guide if already not.

[44vince44]

StaxRip version 2.5.0 is out.

The main significant changes:
- updated VapourSynth to R53, which does not support Windows7 anymore.
- AviSynth JPSDR plugin included in StaxRip is now the AVX2 version, therefore users with older processors (generations older than 5 years or more) have to replace it with the AVX version
- Many filter definitions have been added, many others modified. They won't appear unless you "Restore Defaults" from the filter profiles window, or simply purge the old settings.

The full changelog and download here (https://github.com/staxrip/staxrip/releases/tag/v2.5.0) for all the bugfixes and tool updates.

[JKyle]

- AviSynth JPSDR plugin included in StaxRip is now the AVX2 version, therefore users with older processors (generations older than 5 years or more) have to replace it with the AVX version

I've updated this wiki document (https://github.com/staxrip/staxrip/wiki/If-QTGMC-raises-errors-right-after-the-fresh-install...) for users who may run into errors with QTGMC and other filters depending on JPSDR.

[44vince44]

Thanks @JKyle !!

[guest]

I've updated this wiki document (https://github.com/staxrip/staxrip/wiki/If-QTGMC-raises-errors-right-after-the-fresh-install...) for users who may run into errors with QTGMC and other filters depending on JPSDR.

I'm surprised you didn't add DGDecNV to the mix ?!?!?

I did manage to set it up myself, thanks to your instructions, now I just need to get the "NV" part to co-operate.

And you've changed the SMDegrain & MDegrain filters around a fair bit also (as mentioned)...it would have been nice to have been given a tiny bit of credit for the MDegrain3 script suggestion ;)

Yes, it's shame when you have a mix of old & newer PC's, referring to the AVX instruction thing :(

Cheers