StaxRip 2.0 Support Thread

[BobbyBoberton]

Got this as a reply from the github after putting an issue in since it happened in so many versions and as told that it is a bug with staxrip not ffmpeg (Weird to me) and that it will probably be easier to disable DXVA2 decoding that trying to figure out a -pix_fmt to be put in the command line but I am talking with the maintainer of the code, I think that it can be worked around rather easily if you just make a new box that appears if you choose FFMpeg (DVXA2) as the decoder then you also need to specify what you want -pix_fmt is supposed to be. I believe it should be set to whatever kind of output you are looking for like if you want 10-bit HDR the you want yuv420p10le and if you want 8-bit SDR you need to choose yuv420p or 10-bit SDR yuv420p10 (I think) so that could work right?

This is what I got from github:

When the x265 option Decoder FFmpeg (DXVA2) is used then avisynth/vapoursynth is not used at all but rather the source file is opened directly by ffmpeg and therefore the pipe option is not relevant because piping is done in order to pipe data from avisynth/vapoursynth to x265.

The problem is when the ffmpeg option -hwaccel dxva2 is used then as you pointed out it's also necessary to define the -pix_fmt option, this is a bug in staxrip, I don't understand why ffmpeg requires it in this case, without -hwaccel option -pix_fmt is not necessary.

In order to fix it staxrip would have to generate the -pix_fmt argument based on media info of the source file, it's more likely that we rather remove the Decoder FFmpeg (DXVA2) feature because it's too much work to generate the -pix_fmt argument.

The second problem is that the staxrip docs currently don't explain how hardware decoding can be used with avisynth/vapoursynth, here is a screenshot:

https://postimg.cc/HV8SCNDC

[hevron]

2.1.3.8 Beta, DTS-HD MA core not extracted, Сору/Mux only 🤔

[stax76]

Which source container?

[hevron]

Originally Posted by stax76

Which source container?

When adding a DTS-HD MA file from another folder to the MKV container.
P.S. The DTS-HD MA is packed in an MKA container.

[stax76]

In the Copy/Mux options there is an Extract DTS Core option.

[hevron]

There is of course, but in version 2.1.3.8 Beta, it does not work well with MKA.

[hevron]

I update the last 3-4 versions of the program manually from the Tools by Patman folder:
ffmpeg, NVEnc, rav1e, SVT-AV1, MP4Box, x264 ��

[Mason1171]

Im just having trouble setting it up to run the same template on multiple files sequentially. When I run the test clips individually with my template, the outcome is great. When I use the file batch feature on more than 1 clip, it uses the correct template but uses the BT. 2020 colorspace instead of BT709. This results in very red tinted video.

The Template

Solution: Options > Video > Import VUI Metadata (Needs to be unchecked)

[44vince44]

Originally Posted by hevron

There is of course, but in version 2.1.3.8 Beta, it does not work well with MKA.

I confirm this behaviour:

Copy/mux option Extract DTS Core does not work when the audio source is an external file mka file. It only copies the stream without extracting DTS core.


@hevron I will create a ticket to report the bug.
USE THIS WORKAROUND:
download MKVCleaver or use mkvmerge to extract the dtshd stream.
Rename it to stream.dtshd
Add it in staxrip instead of the mka, and you'll be able to extract the dts core.

[hevron]

ffmpeg N-98623-g315706c227-g9d2ba8980b-gcc10.2.0 by Patman (02.08.20) doesn’t work ��, I am using ffmpeg N-98276-g1d5d8a30b4-g842bc312ad-gcc10.1.0 (10.07.20).

[Patman]

Originally Posted by hevron

ffmpeg N-98623-g315706c227-g9d2ba8980b-gcc10.2.0 by Patman (02.08.20) doesn’t work ��, I am using ffmpeg N-98276-g1d5d8a30b4-g842bc312ad-gcc10.1.0 (10.07.20).

Thx, i'll fix it.

EDIT:
Fixed, new version online. Now as x86 and x64 release.

[wallander]

Hello,
how can I change back to my settings in the app folder.
After new windows installation, staxrip aked at first start and I klicked the false folder

[jlw_4049]

Originally Posted by wallander

Hello,

how can I change back to my settings in the app folder.

After new windows installation, staxrip aked at first start and I klicked the false folder

Redownloading and launching the first time will make it ask again.

Sent from my SM-G986U1 using Tapatalk

[wallander]

Thanks,

I found it in the Registry and could change it

[Atlantis]

Didn't staxrip for resizing use Spline16Resize before? Today I resized and it used bicubic. Any reason for the change? Spline16Resize is sharper.

[44vince44]

Yes indeed spline is sharper and lanczos is even sharper. All have advantages and disadvantages. There is no special reason. Bicubic is the most popular among the standard players because it's fastest and is handled by most older hardware. Advanced players use better resizing that bicubic. Video processing software give you the choice. Feel free to change it and to create your startup template as you wish.

Note: If using Avisynth, you need to take care of multithreading so the resizing doesn't slow down the whole process. If using vapoursynth, multithreading is already handled.

[Atlantis]

I use mod 8 and if the size is not mod 8 it gives me error message of course.

So I use AddBorders to make it mod 8 but staxrip doesn't understand that I have used AddBorders and that the output resolution is different. It still thinks it is not mod 8 and I can't continue and encode. How to do?

[44vince44]

I face the same problem with some videos, so either I resize or crop, or also addborders, and in that last case, I reduce Mod to 2, and make sure manually (with a calculator) that the final size with addborders is Mod 8. To check the final size, you can either open preview and display information, or use the "Info..." in the filters menu (the blue "AVS Filters" or "VS Filters"). Note that Mod is a setting that only checks that the size is respecting Mod. Let's say, if you set Mod = 2, but your video size is multiples of 8, then the video will be processed as Mod 8 by the filters and the encoder.

[Atlantis]

Thanks. Staxrip should change the behavior. The mod warning should be based on the output resolution and not the input resolution.

[BobbyBoberton]

Also would be nice if hwaccel would be figured out but can't figure out the best options for -pix_fmt, according to the manual setting -pix_fmt to

-pix_fmt +

should set pix_fmt to the input format of the video but this seems to not work with the generated command lines or even just with ffmpeg alone (both pre-compiled binaries and self-compiled ones) so anyone have any ideas about how to fix the -pix_fmt issue with staxrip when trying to use ffmpeg (dxva2) as the decoder with a pipe to x265.exe? My best option if the + thing did not work was to just add another menu that will need to be set if you choose to use ffmpeg (dxva2) as the decoding program then you need to set -pix_fmt yourself, as I have posted about before on here when I was trying to compile 10-bit HDR content this way the generated command line would work if I added -pix_fmt yuv420p10le after the input command, however the maintainer says that it is not that simple and that he would need to find a way to properly automatically pull this info from the file through mediainfo or something like that, I don't see why that is necessary here if it is just being used as a piping program, as long as it generates a y4m stream and the encoder can read it then isn't that really what matters?