StaxRip

[JKyle]

Meanwhile, D2VSource is updated (again) to 1.2.2 (https://github.com/Asd-g/MPEG2DecPlus/releases/tag/1.2.2).

[44vince44]

@Atlantis, you need to grab beta 2.1.7.3, it has full unicode for x265 and other fixes.
https://staxrip.readthedocs.io/introduction.html#download

[Atlantis]

Thanks.

[uNderdog_101]

Any way to create the softlinks for avisynth manually? I cannot get staxrip to not fail to create them automatically, forcing me to use the installed version, and thought that it might work if I create them myself?

[stax76]

They can be created with mklink which is a cmd built-in.

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

But they are needed for all tools that don't support a custom avisynth path:

ffmpeg, x264, x265, VCEEnc

edit:

but this will not work due to how the feature is implemented in staxrip

[uNderdog_101]

They can be created with mklink which is a cmd built-in.

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

But they are needed for all tools that don't support a custom avisynth path:

ffmpeg, x264, x265, VCEEnc

Sorry, I should have been more specific, I know how to create symlinks, it's something I do a lot of, but I don't know what links need to be created where.

[44vince44]

Any way to create the softlinks for avisynth manually? I cannot get staxrip to not fail to create them automatically, forcing me to use the installed version, and thought that it might work if I create them myself?


DId you try running staxrip as administrator, only on time, so the links are created

[Atlantis]

Installed the beta. What is the new High Tier option in x265 encoding?

[JKyle]

@Atlantis
Right click on it.
And on Apps Manager(F9), go to x265 > Help > Online, and search.

It's not new. It's been around in some other category.
However, you don't have to touch it in reality in almost all cases.

[Atlantis]

I love those options. The best options are the options that you don't have to touch! :D
Maybe it was better to be in another category if it is not that important. Better to keep the main, first page options simple and clean.

[JKyle]

Maybe it was better to be in another category if it is not that important.

It's placed there because it's very closely related to Level.
Activating high tier becomes meaningful only when a specific level(--level-idc) is set.

[uNderdog_101]

DId you try running staxrip as administrator, only on time, so the links are created

Of course, first thing I tried.

[44vince44]

@uNderdog_101 there could be another reason why symlinks caan not be created: something is already there.
Go to the following folders inside Staxrip's tree:
APPS/Encoders/ffmpeg
APPS/Encoders/QSVEnc
APPS/Encoders/x264
APPS/Encoders/x265

If there is any avisynth.dll in those folders (with size zero or other than zero), delete those avisynth.dll.

Then retry.

[fredlkrue]

@fredlkrue
You're welcome. The behaviour you're describing is normal behaviour of a newly "installed" staxrip, since maybe forever. There was no bug indeed.
I think your other issue is also something "normal" that you'll figure out, since it has not been reproduced elsewhere...

Any way to create the softlinks for avisynth manually? I cannot get staxrip to not fail to create them automatically, forcing me to use the installed version, and thought that it might work if I create them myself?

I have figured it out why it fails to create the softlink. in my case AviSynth+ was installed, so I uninstalled it and remove/delete the avisynth.dll file that was left on the system32 folder. Then run StaxRip and all works fine.

[stax76]

I have figured it out why it fails to create the softlink. in my case AviSynth+ was installed, so I uninstalled it and remove/delete the avisynth.dll file that was left on the system32 folder. Then run StaxRip and all works fine.

I don't see how it would cause a problem, and it also cannot be reproduced. But DJATOM wants to add an option to define the avisynth location, then soft links are only needed when x264 or ffmpeg load avs.

For ffmpeg, soft links are needed even if avisynth is not installed, because ffmpeg does not use default DLL loading which would search in PATH, it uses a limited DLL search for increased security.

A possible solution that would remove the need for soft links altogether is described here:

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


2.1.7.4Beta


Changelog

https://github.com/staxrip/staxrip/blob/master/Changelog.md


Download

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

[44vince44]

Thanks @stax76, thanks for the new beta also:

2.1.7.5 Beta

Changelog

https://github.com/staxrip/staxrip/blob/master/Changelog.md


Download

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

[Atlantis]

Are there avisynth smoothing filters included in the staxrip menus? I don't find any.

[lordalibaski]

Just a simple question regarding audio issue.

I do a lot of VHS recording and all of these recordings come out like this

Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Muxing mode : DVD-Video
Duration : 1 h 8 min
Bit rate mode : Constant
Bit rate : 256 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Delay relative to video : -288 ms
Stream size : 126 MiB (3%)
Service kind : Complete Main


Now all I want to do is keep them at AC3 but boost the sound slightly using this custom command -af
dynaudnorm=p=0.94:m=70:s=22 though it won't let me keep the 256k bitrate at the same time as using the command.

Is there a way of getting Staxrip to let me keep the same audio bitrate of 256kbps and use the custom command.

Ps...sorry forgot to mention it will only let me set the bitrate at 224 if I got to 256 it says it's an invalid bitrate.

[abahram]

I have figured it out why it fails to create the softlink. in my case AviSynth+ was installed, so I uninstalled it and remove/delete the avisynth.dll file that was left on the system32 folder. Then run StaxRip and all works fine.

you solve my same problem on win10 LTSB . i uninstall it a while ago but never manage to use it in staxRip. delete 2 avisynth.dll C:\Windows\System32 & C:\Windows\SysWOW64 and no nag for creating soft link anymore.
thanks

[fredlkrue]

you solve my same problem on win10 LTSB . i uninstall it a while ago but never manage to use it in staxRip. delete 2 avisynth.dll C:\Windows\System32 & C:\Windows\SysWOW64 and no nag for creating soft link anymore.
thanks

You're welcome.

[AYColumbia]

I just updated staxrip and every time I launch it I get a pop-up dialog with the error
Load VapourSynth first
Filters > Filter Setup > VapourSynth
even though I have it installed. I've tried deleting the settings files and reset the load template I continue to get this error. I also tried to reset my filters so it's set to AVISynth instead and then save as template that loads on startup and it continues to load AVS Filters for vapoursynth instead. Appreciate any thoughts on how to fix this. Thank you.

[tormento]

I am trying to use StaxRip.

As a StaxRip noob I have two simple question.

1) How to use it as a simple encoder gui, with no audio/sub muxing?
2) Are the x264/x265 predefined settings the default ones of the encoder or some optimized ones? In the latter case, how do you configure both? My needs are 1080p 8bit SDR source (for now), encoding as 8 bit in x264 and 10 bit in x265.
3) Why it keeps on using --range limited even if I put "full" in x265 options?

Thanks :)

[d3rd3vil]

Can I use StaxRip or another program to add an HDR10 flag to a videofile (mov for example)?
Right now I am using ffmpeg via the command-line like this: "ffmpeg -i "Input.mov" -pix_fmt yuv420p10le -c:v libx265 -preset slow -b:v 100M -x265-params keyint=60:bframes=3:vbv-bufsize=75000:vbv-maxrate=125000:colorprim=bt2020:transfer=smpte2084:colormatrix=bt2020nc:master-display="G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)":max-cll="1000,400":hdr-opt=1 "Output.mp4"
And also this is brutal for the CPU as the GPU isnt used one bit. How can I change that? It might not be the right thread here though :( No idea where else to put it.

[Magik Mark]

When encoding x265 using nvidia gpu, is there a setting there that would make better black level? CPU encoding has very good black level. I'm trying to make it close as possible

[JKyle]

Can I use StaxRip or another program to add an HDR10 flag to a videofile (mov for example)?

In your template or project, turn on Import VUI metadata before loading a source.

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

And then finetune the encoder options for x265 or NVEnc H265 after loading the source.

[JKyle]

1) How to use it as a simple encoder gui, with no audio/sub muxing?

Video: respective encoders or Copy/Mux for stream copy
Audio: No Audio
Container Configuration > Subtitles > remove all subtitle tracks

Isn't it straightforward? :confused:

2) Are the x264/x265 predefined settings the default ones of the encoder or some optimized ones?

StaxRip is just a GUI for many media tools. No optimization or other tweaking is employed except for some modded tools (x265, x264, ffmpeg, etc.) fitted for portability, removal of file name length limit, and direct avs/vs input.

3) Why it keeps on using --range limited even if I put "full" in x265 options?

Not reproducible on my side. :confused:

[JKyle]

When encoding x265 using nvidia gpu...

:confused::confused::confused::confused::confused::confused:


BTW, have you tried --range full(x265) or --colorrange full(NVEnc)?

[tormento]

StaxRip is a video encoding GUI for Windows
I have to admit that StaxRip is a wonderful piece of software. I fed it with a messy mkv anime with ass subs and ttf fonts and it rendered output as the input was.

I have a small request. If you followed the Unicode thread about DGIndexNV, I'd like to ask you to have an external manifest, as I am working with non standard characters and I have some issues dealing with it. Do you think it is feasible?

[videoh]

If staxrip can't or won't do that you can try this:

https://www.unixgr.com/enable-external-manifest-control-on-windows-10/

You set these and put your own manifest file with the staxrip.exe. You can create a generic manfest file (that does not specify a codepage) and name it appropriately. Windows will use the external manifest in preference to the embedded manifest, and the system locale will be used as normal.

[tormento]

You set these and put your own manifest file with the staxrip.exe.
Good idea but I don't have any clue about how to create a proper manifest structure and content. :D

[videoh]

Put this in a text file called staxrip64.exe.manifest (check the exe name, I'm just guessing):

<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
<security>
<requestedPrivileges>
<requestedExecutionLevel level='asInvoker' uiAccess='false' />
</requestedPrivileges>
</security>
</trustInfo>
<assemblyIdentity type="win32" name="..." version="6.0.0.0"/>
<dependency>
<dependentAssembly>
<assemblyIdentity type='Win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*' />
</dependentAssembly>
</dependency>
</assembly>


You can use ResourceHacker to 'steal' manifests from existing EXE files. Choose an EXE that has an embedded manifest that doesn't specify UTF-8 of course.

[JKyle]

CropResize is updated today (https://forum.videohelp.com/threads/393752-CropResize-Cropping-resizing-script).

NVEnc is updated to 5.26 (https://github.com/rigaya/NVEnc/releases/tag/5.26).
A new edge-sharpening CUDA filter, --vpp-warpsharp, is introduced in this version.

[44vince44]

tormento, staxrip already uses windows 10 manifest for long file names and unicode. Maybe you should try latest beta.
Get it here https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

[tormento]

tormento, staxrip already uses windows 10 manifest for long file names and unicode. Maybe you should try latest beta.
Thanks but my problem is the opposite. AFAIK to use unicode you need to set beta support of Windows 10 and it gives me lot of problems with non unicode aware programs, as I don't use english regional settings but italian ones. I open recently a discussion on DGIndexNV forum, I invite you to take a look there. Having an external manifest file gives the opportunity to delete or rename it and have a standard ANSI only application.

[JKyle]

This is not an issue with StaxRip.exe alone. @DJATOM's modded x265 and other tools that have UTF-8 manifests are also related.

You need to read this issue thread (https://github.com/staxrip/staxrip/issues/456) about this ANSI vs UTF-8 codepage file name problem.

So if you're using a system older than Windows 10 1903 that ignores manifest's directives, you better try piping the files via avs2pipemod or ffmpeg instead of using direct input.

[videoh]

I had a look at your linked thread. In there you say:

Having said that, I'm seeing a weird behavior with VapourSynth encoding.
I guess I need to make a separate issue thread on this finding. ��

EDIT:
After some testing, I've found that the said problem has nothing to do with @DJATOM's new x265 build. It was related to the source filter itself: ffms2 is OK with my source video but DGSource warps the video - 1920x1080 becomes 1080x1080 mp4.
I'll be doing more testing to confirm the matter before I report this issue in the DGDecNV community.

For those interested, here's the source video I tested. (It's a short Japanese anime clip and the file name means 'test' in Korean.) I'm interested to follow-up on this. The video link is no longer valid and you did not report any issue to the DG forum and you did not follow-up in the cited thread. Can you please clarify the status of this issue? I'm sure you wouldn't want me to go around slagging off staxrip without anything to back it up. Right? You know I always jump immediately onto reported bugs, so please give me that opportunity.

[JKyle]

I had a look at your linked thread. In there you say:

I'm interested to follow-up on this. The video link is no longer valid and you did not report any issue to the DG forum and you did not follow-up in the cited thread. Can you please clarify the status of this issue?

It's been kind of put off for a while since there's no problem with AVS.

Per your ask, I did the postponed further testing and have found out that the issue is surely related with @DJATOM's x265 build, not with DGSource.

DGSource vpy -> vspipe -> x265 does not have this issue, while DGSource -> x265 suffers from this warped AR issue.

OTOH, ffms2 vpy -> x265 also does not have this issue.
This is why I was confused about the cause. Don't blame me. Like I said, more testing was due at that time, and I was forgetting about it for a while. That's why there was no report on the DGDecNV forum.

- DGSource: latest DGDecNV
- ffms2: StvG's latest build (https://forum.doom9.org/showthread.php?p=1928993#post1928993)
- x265: @DJATOM's latest aMod build (https://github.com/DJATOM/x265-aMod/releases/tag/3.4%2B65)
- StaxRip: 2.1.7.5 Beta


I've uploaded the same test video again here (https://drive.google.com/drive/folders/1R1jBzfCAn6d61kO5vDSDCQtk-pNJA7mU?usp=sharing).

I think I better report an issue on @DJATOM's x265 repo.

[videoh]

Thank you for your clarification. I'll check out the video and see if there is anything out of the ordinary.

[JKyle]

I've found that the only difference b/w DGSource and ffms2 is that x265 takes different SAR values from the vpy file.


[DGSource]
x265 3.4+65-aMod(GCC10.2.1) DJATOM

D:\Utilities\StaxRip\Apps\Encoders\x265\x265.exe --crf 27 --output-depth 10 --output D:\Downloads\test_1audio_temp\test_1audio_DGSource_x265-direct-input_out.hevc D:\Downloads\test_1audio_temp\test_1audio_DGSource_x265-direct-input.vpy

vpy [info]: 1920x1080 fps 24000/1001 i420p8 sar 9:16 frames 0 - 2478 of 2479
...


[ffms2]
x265 3.4+65-aMod(GCC10.2.1) DJATOM

D:\Utilities\StaxRip\Apps\Encoders\x265\x265.exe --crf 27 --output-depth 10 --output D:\Downloads\test_1audio_temp\test_1audio_ffms_x265-direct-input_out.hevc D:\Downloads\test_1audio_temp\test_1audio_ffms_x265-direct-input.vpy

vpy [info]: 1920x1080 fps 24000/1001 i420p8 sar 1:1 frames 0 - 2478 of 2479
...


I reported an issue (https://github.com/DJATOM/x265-aMod/issues/8) on @DJATOM's x265 repo.
Now the ball is tossed to him.

[videoh]

I believe sar 9:16 is correct. Let's see what our friend DJATOM thinks about it.

This thread may be helpful:

http://rationalqm.us/board/viewtopic.php?f=8&t=895

[JKyle]

I believe sar 9:16 is correct.

Well, that's quite opposite to what I know of.

The source video has a pixel aspect ratio(PAR) of 1:1, a display aspect ratio(DAR) of 16:9.
Isn't SAR(sample aspect ratio) in x265 pixel aspect ratio? So shouldn't it be 1:1 in this case?

ADDED:

FYI, DGIndexNV gets SAR at 1:1 for the same source video.

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

I have no idea how the wrong SAR value is passed on to x265.

[Atlantis]

So this is the only time I have seen this. I was watching a video I encoded using staxrip and I have pixelation for 2-3 seconds. At first I thought the file must be corrupt, so I spent a lot of time testing with ScanMedia (https://gist.github.com/Desani/129be27da7d735d7c75192ec1aa96c65) and
ffmpeg.exe -v error -i file.mkv -f null - >error.log 2>&1
that the encoded file itself is not corrupt.

The source file is also not corrupt. What can cause the corruption during the encode? Can pausing cause this? I suppose Avisynth had a problem and passed few bad frames. Anyone heard anything about this?
I used
StaxRip : 2.1.7.0
x265 M-3.4+28 gcc10.2.0 Yuuki-Asuna/msg7086/DJATOM/Patman

[JKyle]

So this is the only time I have seen this. I was watching a video I encoded using staxrip and I have pixelation for 2-3 seconds. At first I thought the file must be corrupt, so I spent a lot of time testing with ScanMedia (https://gist.github.com/Desani/129be27da7d735d7c75192ec1aa96c65) and
ffmpeg.exe -v error -i file.mkv -f null - >error.log 2>&1
that the encoded file itself is not corrupt.

The source file is also not corrupt. What can cause the corruption during the encode?

Sometimes simply changing the source filter to another solves this kind of anomalies.
What source filter did you use? Try something else.

[Atlantis]

Thankfully I keep all the log files for my encodes. What do you mean, do you mean this?

--------------------------- AviSynth Script ---------------------------

AddAutoloadDir("-------\StaxRip\Apps\FrameServer\AviSynth\plugins")
LoadPlugin("---------\StaxRip\Apps\Plugins\Dual\ffms2\ffms2.dll")
FFVideoSource("--------\video.mkv", cachefile="--------\video_temp\temp.ffindex")
#AssumeFPS(25)

The problem is that you can't catch this error unless you watch the whole video. The encoded file is not corrupt and there is no error in the staxrip log file. Everything went well according to staxrip and x265.

[JKyle]

Thankfully I keep all the log files for my encodes. What do you mean, do you mean this?

--------------------------- AviSynth Script ---------------------------

AddAutoloadDir("-------\StaxRip\Apps\FrameServer\AviSynth\plugins")
LoadPlugin("---------\StaxRip\Apps\Plugins\Dual\ffms2\ffms2.dll")
FFVideoSource("--------\video.mkv", cachefile="--------\video_temp\temp.ffindex")
#AssumeFPS(25)

There are many alternatives.

1) Try the most recent ffms2 plugin by StvG from here (https://forum.doom9.org/showthread.php?p=1928993#post1928993).

2) Try LSMASHVideoSource or LWLibavVideoSource.

3) If your encoder is x265 or x264, try ffmpeg as the decoder.

4) If your encoder is NVEnc, try NVEnc Hardware/NVEnc Software/ffmpeg as the decoder.

[Atlantis]

Do you mean you have seen this before that I have described?

The encoder is x265 as I noted. I hope more of my files are not like this. Would be very frustrating.
I go with the default source filters that staxrip is giving me supposing that they are the best and the latest. Should I switch to LSMASHVideoSource for mkv? Is it better, more safe than ffms2?

[JKyle]

Do you mean you have seen this before that I have described?

Of course. AFAIK, the issue arises when the PPS, SPS parameter values of frames are not interpreted appropriately by the decoder/source filter. That's why I recommend using another source filter.

I go with the default source filters that staxrip is giving me supposing that they are the best and the latest. Should I switch to LSMASHVideoSource for mkv? Is it better, more safe than ffms2?

What do you mean 'safe'?

StaxRip just offers a very good menu of various alternatives. It is up to you to choose from them depending on the situation.
Whether a specific source filter is better or not depends totally on the source video and other factors. There's no universally superior method.
Try out yourself. StaxRip lets you switch b/w alternatives very easily as you can see. If a problem occurs, StaxRip notifies you at the bottom of the main window so that you can roll back or choose another alternative.

[videoh]

Well, that's quite opposite to what I know of.
Sure looks that way. : thinking :

[JKyle]

Follow-up: a new SAR related option will be introduced in vpy direct reading for x265. See this (https://github.com/DJATOM/x265-aMod/issues/8#issuecomment-771299757).

[Atlantis]

The situation is always AVC inside MKV. By safe I mean I can always read the AVC inside MKV with no pixelation like that.

You say StaxRip notifies you but it doesn't. When I look inside the log file, there is no error, no warning. How am I supposed to check if a problem occurred?

You say you have seen this issue, how do you deal with this? Do you watch your entire video from start to end after encode?