StaxRip

[jlw_4049]

Thanks for the update! I'll put it to the test [emoji14]

Sent from my SM-G986U1 using Tapatalk

[jinkazuya]

Thanks for stax76 for showing me to make a proper request. I would prefer to ask to include detailsharpen filter in the future release of staxrip, which is much more convenient for noobs or newbies.

Below is the code snippet modified by Jenyok, originally created by Bloax


#
# http://forum.doom9.org/showthread.php?t=163598
#
# Function name DetailSharpen() is replaced by SharpenDetail() name function ...
#
function SharpenDetail(clip orig, int "str", int "thr")
{
#
# Another filter by, oh you guessed it, Bloax.
# Requirements: RedAverage, RemoveGrain and ASharp.
#
# A sharpening filter, that unlike usually, doesn't sharpen edges.
# Instead it sharpens the details, and thus it avoids the classic haloing.
# Not my idea of course, but anyways, enjoy.
#
# "str" Is the sharpening strength.
# "thr" Is the threshold for detecting edges. The higher, the more "edges" are caught, and less details are sharpened.
# Value 5 Is the best value, because 4 starts sharpening edges, and 6 sharpens way too little.
#

str = Default(str, 5)
thr = Default(thr, 5)
Threshold = Pow(2, thr)
sse0 = 0 # change this constant for limits the processor capabilities.
# -1 = use all (bitwise... 16, 8, 4 = SSE4.1, SSSE3, SSE2),
# 0 = no asm, which is veeeeryyyy sloooow.

clp = orig.IsYV12() ? orig.ConvertToYV12() : orig
msk = RAverageW(clp, Threshold, clp.RemoveGrain(19, -1), (-1) * Threshold, u=0, v=0, sse=sse0, bias=128). \
RemoveGrain(2, -1).Mt_Inpand(mode="both").Mt_Deflate()

return (RMerge(clp, clp.ASharp(str, -1), msk, sse=sse0))

#
# for debugging only
#
# return (msk)
# return (clp)
}

[JKyle]

I would prefer to ask to include detailsharpen filter in the future release of staxrip, which is much more convenient for noobs or newbies.

If you're serious about including this new filter, at least provide a working script sample, please.

Looking at the code, I see that the following plugins are required.


RedAverage
RemoveGrain
ASharp


Among them, only RemoveGrain is natively available in StaxRip (as of 2.1.9.0).

The RedAverage binary available on Avisynth wiki (http://avisynth.nl/index.php/RedAverage) seems 10 years old and built for x86. Are you sure this works without issues on x64?

(BTW, ASharp is available on @Asd-g's GitHub repo (https://github.com/Asd-g/AviSynth-ASharp/releases).)

[jinkazuya]

If you're serious about including this new filter, at least provide a working script sample, please.

Looking at the code, I see that the following plugins are required.


RedAverage
RemoveGrain
ASharp


Among them, only RemoveGrain is natively available in StaxRip (as of 2.1.9.0).

The RedAverage binary available on Avisynth wiki (http://avisynth.nl/index.php/RedAverage) seems 10 years old and built for x86. Are you sure this works without issues on x64?

(BTW, ASharp is available on @Asd-g's GitHub repo (https://github.com/Asd-g/AviSynth-ASharp/releases).)

I am not sure which one is right. I think probably this is the one.

https://github.com/Selur/VapoursynthScriptsInHybrid/blob/master/G41Fun.py#L2885

[JKyle]

https://github.com/Selur/VapoursynthScriptsInHybrid/blob/master/G41Fun.py#L2885

This is the filter function definition for VapourSynth, not a working sample of a script in use (for AviSynth+ or VapourSynth).

Besides, the function name is different for VapourSynth. It's DetailSharpen, not SharpenDetail as presented in the code in your above post.

Aside from the name issue, it's true that G41Fun.DetailSharpen is natively available in StaxRip as part of the G41Fun VapourSynth plugin, but I'm asking you to present a working script that utilizes the filter in practice.

As the Tool Update Requests (https://github.com/staxrip/staxrip/wiki/Tool-Update-Requests) Wiki document describes,
"only requests with script code will be accepted."

---

Update:

OK. I've included the G41Fun.DetailSharpen filter profile for VapourSynth with default options. But since AviSynth+ version SharpenDetail seems to have some issues, we need some more info and correct binaries in order to put it as SharpenDetail in AVS Profiles.

I've submitted a PR, and I guess it will be available in the next release.

[jinkazuya]

This is the filter function definition for VapourSynth, not a working sample of a script in use (for AviSynth+ or VapourSynth).

Besides, the function name is different for VapourSynth. It's DetailSharpen, not SharpenDetail as presented in the code in your above post.

Aside from the name issue, it's true that G41Fun.DetailSharpen is natively available in StaxRip as part of the G41Fun VapourSynth plugin, but I'm asking you to present a working script that utilizes the filter in practice.

As the Tool Update Requests (https://github.com/staxrip/staxrip/wiki/Tool-Update-Requests) Wiki document describes,
"only requests with script code will be accepted."

---

Update:

OK. I've included the G41Fun.DetailSharpen filter profile for VapourSynth with default options. But since AviSynth+ version SharpenDetail seems to have some issues, we need some more info and correct binaries in order to put it as SharpenDetail in AVS Profiles.

I've submitted a PR, and I guess it will be available in the next release.

Billion thanks u are the best. I have been wanting this for a long time cuz I used to use it for my video encoding in 32bits but now due to avisynth incompatibility issue, I have to give up on using it and switch to vapoursynth and now with staxrip, which is a very nice gui encoding app for newbies but as for importing scripts and using them, I am still not really that familiar, hopefully there would be an editor for scripting in the app like MEGUI or a really nooks guide. I have been using staxrip for three encoding, all worked pretty well. There are a lot of features in staxrip as well.

[Atlantis]

Is the Batch Job editing working properly? How do you edit a single job inside a batch job?

I use Load on the Jobs windows and things go completely wrong, nothing loads. It asks do you want to save the project.

[stax76]

@Atlantis

Batch job load is not supported I think.

[craigpro]

sigh.. so much has changed. I'm using beta 2.1.9.0 and manually edited my old settings I used to use - now the files are coming out larger than the source, in about half the stuff I've tried encoding.

Any advice on what to change would be most appreciated please.

--cqp 18:20:22 --codec h265 --preset P7 --output-depth 10 --level 5.1 --qp-init 20 --qp-max 22 --qp-min 18 --max-bitrate 5000 --aq --aq-temporal --gop-len 240 --lookahead 16 --multiref-l0 4 --multiref-l1 4 --strict-gop --nonrefp --weightp --cuda-schedule auto --output-buf 16

[Atlantis]

They clearly say to start with a clean install. I did so.

[JKyle]

...now the files are coming out larger than the source, in about half the stuff I've tried encoding.

Any advice on what to change would be most appreciated please.

--cqp 18:20:22 --codec h265 --preset P7 --output-depth 10 --level 5.1 --qp-init 20 --qp-max 22 --qp-min 18 --max-bitrate 5000 --aq --aq-temporal --gop-len 240 --lookahead 16 --multiref-l0 4 --multiref-l1 4 --strict-gop --nonrefp --weightp --cuda-schedule auto --output-buf 16

You know this is a matter of settings or usage, not something inherent in StaxRip, right?

That said, I'd like to recommend you use `Constant Quality Mode(vbr or vbrhq)` instead of `Constant QP(cqp)` for `NVEnc` to get a more desirable result.

There is a Discussions thread (https://github.com/staxrip/staxrip/discussions/417) regarding this matter on GitHub, and you may find it helpful (for what it's worth).

As for me, I adopt the `vpp-deband` filter instead of going with 10-bit encoding for an 8-bit source when it comes to NVEnc HEVC. And I usually don't attach other gratuitous strings.

--vbr 0 --codec h265 --preset P7 --multipass 2pass-full --vbr-quality 33 --aq --lookahead 32 --ref 5 --vpp-deband range=24,thre=6,thre_y=6,thre_cb=6,thre_cr=6,dither=24,dither_y=24,dither_c=24

You need to finetune the `--vbr-quality`value in order to adjust the quality and final output file size.

This usually yields a bitrate about 2500k (roughly) for a 1080p 29.97fps 8-bit AVC source. But of course the real result depends totally on the source properties.

My graphics card is Pascal. Since it looks like yours is Turing or Ampere, you may add additional architecture-specific options like

--bframes 4 --bref-mode middle --aq-temporal --multiref-l0 5 --multiref-l1 4

And as a side note, you also need to be aware that the encoding speed with Turing or Ampere may be slower than Pascal since they encode B-frames as well by default.

For more info, refer to the NVEnc online manual (https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md).

[JKyle]

They clearly say to start with a clean install. I did so.

You're doing good in that regard.

The reason that a clean install is always recommended is because you don't know what kind of issues you're carrying along if you continue to copy & use your old settings file without its update.

AFAIK, the only way to keep old settings is when this extra step is taken: you should update your settings by looking into/updating any changes in your settings every time you update StaxRip. This includes basically everything: menus (main menus and all other menus), templates, AVS/VS profiles, video encoder/audio encoder profiles, etc.

This is a very tedious/cumbersome/time-consuming job even if you know all the changes that have happened in between those two versions. This is more so esp. with a fast developing software program like StaxRip that has a LOT of changes b/w releases.

If you have so many customized settings that it takes too much time to set up the same in the new version and if you are sure you can do the above mentioned extra step successfully with every program update, then you can go on. Otherwise, you better go with a fresh start.

That's why a clean install is recommended in general.

[stax76]

@JKyle

I used to write a lot of migration code in the past but gave it up because it took too much time. It's a topic we should have an eye on, it can probably be improved without losing too much time.

[Atlantis]

new bug in v2.1.9.0-Beta

StaxRip\Apps\Plugins\AVS\SangNom2\SangNom2.dll

Not working. It says it is 32bit DLL and not working with 64bit staxrip.

I copied the old from 2.1.8.5-Beta and that works.

[stax76]

@Atlantis

Users can report tool update requests and issues in the following wiki page:

https://github.com/staxrip/staxrip/wiki/Tool-Update-Requests

This page can be found in the Tools section of the wiki:

https://github.com/staxrip/staxrip/wiki#tools

[craigpro]

Thank you very much for your info and forum suggestions JKyle - I'll check them out.

I did start with a totally new, clean install of 2.1.9.0 and was surprised when 5 of the 10 files I batch encoded came out larger than the source files.

So then I tried my old settings (by creating a new setting in my new, fresh install and matching the command line options to my old settings) and that was slightly better but still had some files larger than source.

Yes, I have an RTX 3070 which I use for encoding.

[JKyle]

I did start with a totally new, clean install of 2.1.9.0 and was surprised when 5 of the 10 files I batch encoded came out larger than the source files.

So then I tried my old settings (by creating a new setting in my new, fresh install and matching the command line options to my old settings) and that was slightly better but still had some files larger than source.

The default parameters setting for Nvidia H265 in StaxRip is

--cqp 18 --codec h265

You should always modify the default settings based on your hardware.

And the second issue comes from the fact that `NVEnc` itself has updated/changed in the meantime. It's not something inherent in StaxRip.
That's why you should always refer to the console help file or online help pages for the corresponding tools.

[JKyle]

new bug in v2.1.9.0-Beta

StaxRip\Apps\Plugins\AVS\SangNom2\SangNom2.dll

Not working. It says it is 32bit DLL and not working with 64bit staxrip.

You're right. The x86 dll was mistakenly included instead in the release. Good find, and thanks. :)

You can download SangNom2 0.6.0 from here (https://github.com/Asd-g/AviSynth-SangNom2/releases) and get the new x64 dll file. Don't forget to update the version number in Apps Manager (F9).

[JKyle]

2.2.0 is released just now. Here (https://github.com/staxrip/staxrip/releases/tag/v2.2.0).

There's a BIG must-know change in this release: full semantic versioning is applied.

Semantic versioning is easy to understand: versions of StaxRip now have the form of

v<major>.<minor>.<dev(patch)>

where


major: a version number where there are breaking modifications
minor: a version number that is compatible with previous versions
dev(patch): an increment for a bug fix or a patch fix. Intended for advanced users and testers.


There are NO MORE BETA versions, and all release versions have the form of v<major>.<minor>.0.

If you're interested in DEV versions, you are welcome to join in the DEV related threads on GitHub.

---

Among the many changes in Changelog (https://github.com/staxrip/staxrip/blob/master/Changelog.md), two default-value changes will surely affect your OLD templates/projects if you decided to carry them along despite the official recommendation.


New projects use Copy/Mux as audio profile

⇒ Your existent templates/projects will be force-reset to `Copy/Mux` for audio encoding setting.


Add option to demux subtitles without including them

⇒ Your existent templates/projects will be force-reset to `Demux and include preferred languages` in `Options` > `Subtitles` > `Subtitles`.

Therefore, you'd better back up your old settings, templates, and projects before carrying them along.

[Atlantis]

Another new bug. In the demux window you can't deselect correctly the attachments. No check boxes.

God knows how many times, how many years ago I asked please like for Audio and Subtitles, add buttons ALL and NONE for attachments. If we had those, at least we could deselect all with buttons.

https://i.postimg.cc/3x6wgwy6/Untitled.jpg

[jlw_4049]

Another new bug. In the demux window you can't deselect correctly the attachments. No check boxes.

God knows how many times, how many years ago I asked please like for Audio and Subtitles, add buttons ALL and NONE for attachments. If we had those, at least we could deselect all with buttons.

https://i.postimg.cc/3x6wgwy6/Untitled.jpgIs this with latest version?

Sent from my SM-G986U1 using Tapatalk

[Atlantis]

I already had this problem with a previous version. For sure I had it also with v2.1.9.0. Before that I don't think so.

[44vince44]

@Atlantis, @jlw please create an issue on github. this could be related to the new theme design in staxrip.

[stax76]

I'll fix it and add the buttons, this is not completely easy btw...

[stax76]

Here is hotfix build:

https://www.dropbox.com/sh/4ctl2y928xkak4f/AAADEZj_hFpGQaNOdd3yqcAHa?dl=0

https://1drv.ms/u/s!ArwKS_ZUR01g0kH4d4eT_6a3GaKe?e=qbOfGS

[jinkazuya]

Thanks Jkyle and stax76 for providing such a good GUI encoding program or application. BTW, a little suggestion, I know there is already a guide or wiki that documents the functions and features of staxrip. However, the documents are not detailed enough esp for noobs or newbies. I am just wondering if there will be a detailed documentation that features or explains everything associated with staxrip.

BTW, is there a way to encode a video faster? Or how to use it with hardware encoding? I really love staxrip now ever since this 2.2.0 version and after having used it for a while. However, a single episode of 45 mins of a series requires an hour of encoding and not sure if it has to do with vapoursynth or something (the speed). I think my computer is a little dated.

Here is the spec of my PC
Threadripper 1950X
32 rams
nvidia GTX 1080ti
Window 10
SSD intel card

So I am just wondering if there is a way to optimize it or improve the speed a little. Without deinterlacing the video by using QTGMC, the time spent on encoding reduces.

[44vince44]

@jinkazuya
I can help, and I probably know a way it can go 3 times faster... but need some information:

1) what is the resolution of the video
2) can you copy the command line of x265 here (in the encoder's options, the line appears at the bottom, with all the switches)
3) when you do an encode, how much is your cpu usage

Probably, after reading your answer, I'll suggest parallel processing or chunk encoding.

[JKyle]

I am just wondering if there will be a detailed documentation that features or explains everything associated with staxrip.

There's a (somewhat old) Tutorial written in German (https://encodingwissen.de/praxis/staxrip/) by @BrotherJohn. It needs update, but at least you can refer to it for learning the basics of StaxRip.
Any volunteer is welcome to update and translate the tutorial.

BTW, is there a way to encode a video faster? Or how to use it with hardware encoding? I really love staxrip now ever since this 2.2.0 version and after having used it for a while. However, a single episode of 45 mins of a series requires an hour of encoding and not sure if it has to do with vapoursynth or something (the speed). I think my computer is a little dated.

Here is the spec of my PC
Threadripper 1950X
32 rams
nvidia GTX 1080ti
Window 10
SSD intel card

So I am just wondering if there is a way to optimize it or improve the speed a little. Without deinterlacing the video by using QTGMC, the time spent on encoding reduces.

Your system is better than mine. My graphics card is GTX 1060 6G, and it takes me about 20 mins to encode a 2 hour FHD 29.97fps 8-bit AVC source to HEVC using NVEnc.

To give you a small tip, you can speed up the deinterlacing process by adopting the hardware deinterlacing filter `--vpp-yadif` embedded in NVEnc, instead of the CPU filter `QTGMC`.

--vpp-yadif mode=tff --interlace tff

If you need to bob the frame rate, use bob_tff instead of tff, and of course you need to choose b/w tff and bff depending on the source field parity.

Basically it's a matter of usage and settings for NVEnc command line, and you need to study how to optimize the settings for your hardware and the source file referring to various resources.

I already gave an answer to @craigpro's question in the above reply (https://forum.doom9.org/showthread.php?p=1939029#post1939029), and you can refer to it too.

Maybe I can write a short guide on the Wiki sometime (if I have time :D), but optimizing the options based on your hardware and the source is of course totally up to you.

In the meantime, refer to the NVEnc options document (https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md).

[stax76]

Thanks Jkyle and stax76 for providing such a good GUI encoding program or application. BTW, a little suggestion, I know there is already a guide or wiki that documents the functions and features of staxrip. However, the documents are not detailed enough esp for noobs or newbies. I am just wondering if there will be a detailed documentation that features or explains everything associated with staxrip.

It will be improved, but it's not a high priority task for any of the active contributors, at least not at the moment.

[jinkazuya]

@jinkazuya
I can help, and I probably know a way it can go 3 times faster... but need some information:

1) what is the resolution of the video
2) can you copy the command line of x265 here (in the encoder's options, the line appears at the bottom, with all the switches)
3) when you do an encode, how much is your cpu usage

Probably, after reading your answer, I'll suggest parallel processing or chunk encoding.

I basically use the default, but for better quality, I choose x264 with 18 quality and that is it. I have never altered anything. The resolution is
1280 x 720 and basically the CPU is 88% to 100% most of the time.

I think the default will be listed below
cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16
chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=22 lookahead_threads=3
sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0
rc_lookahead=40 rc=crf mbtree=1 crf=18.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00


There's a (somewhat old) Tutorial written in German (https://encodingwissen.de/praxis/staxrip/) by @BrotherJohn. It needs update, but at least you can refer to it for learning the basics of StaxRip.
Any volunteer is welcome to update and translate the tutorial.

Your system is better than mine. My graphics card is GTX 1060 6G, and it takes me about 20 mins to encode a 2 hour FHD 29.97fps 8-bit AVC source to HEVC using NVEnc.

To give you a small tip, you can speed up the deinterlacing process by adopting the hardware deinterlacing filter `--vpp-yadif` embedded in NVEnc, instead of the CPU filter `QTGMC`.

--vpp-yadif mode=tff --interlace tff

If you need to bob the frame rate, use bob_tff instead of tff, and of course you need to choose b/w tff and bff depending on the source field parity.

Basically it's a matter of usage and settings for NVEnc command line, and you need to study how to optimize the settings for your hardware and the source file referring to various resources.

I already gave an answer to @craigpro's question in the above reply (https://forum.doom9.org/showthread.php?p=1939029#post1939029), and you can refer to it too.

Maybe I can write a short guide on the Wiki sometime (if I have time :D), but optimizing the options based on your hardware and the source is of course totally up to you.

In the meantime, refer to the NVEnc options document (https://github.com/rigaya/NVEnc/blob/master/NVEncC_Options.en.md).

I do not use NVEncC, I am using vapoursynth for encoding. Anyway, I used the default setting of QTGMC, which is set to medium. The source that I encoded is TS of TV recording and for the latest staxrip, it gives me about 31 to 41 FPS, and without QTGMC, depending on the source, it gives me about 100 FPS.

BTW, how to I set --vpp-yadif mode=tff --interlace tff

[JKyle]

I basically use the default, but for better quality, I choose x264 with 18 quality and that is it. I have never altered anything.

IMHO, crf 18 is too much for x264. Maybe you can come down a little bit to 20-22. But of course you need to look at the source first and make a discreet decision.

BTW, how to I set --vpp-yadif mode=tff --interlace tff

It's part of NVEnc command line options.
It's not available with x264 or x265, so if you're not using NVEnc, you can forget about them.

BTW, did you multi-thread QTGMC (http://avisynth.nl/index.php/QTGMC#Multi-Threaded_Usage) to improve its efficiency?

[jinkazuya]

IMHO, crf 18 is too much for x264. Maybe you can come down a little bit to 20-22. But of course you need to look at the source first and make a discreet decision.



It's part of NVEnc command line options.
It's not available with x264 or x265, so if you're not using NVEnc, you can forget about them.

BTW, did you multi-thread QTGMC (http://avisynth.nl/index.php/QTGMC#Multi-Threaded_Usage) to improve its efficiency?

Well...The CPU is 100% already encoded with vapoursynth with staxrip. Everything is default. So I am not sure if the QTGMC is already tasked with multithreads.

[JKyle]

Well...The CPU is 100% already encoded with vapoursynth with staxrip. Everything is default. So I am not sure if the QTGMC is already tasked with multithreads.

Then you're already getting the most out of your CPU with QTGMC.

QTGMC is a heavily CPU intensive filter. I recommend you upgrade your CPU or try using another alternative deinterlacing filter.

Going to NVEnc encoding along with its hardware deinterlacing filter can be another option if you can bear with a (slightly) lower-quality-bigger-size output.

[Atlantis]

Thank you so much. I just checked the hotfix and the attachments demux is working correctly as before.
The addition of the All and None buttons are just perfection. It makes the life so much easier.

[NanoBot]

If you are willing to spend 15$, you may give DGDecNV a try. It's a decoder/frameserver package which uses your Nvidia GPU not only to decode the source material. In addition it offers, among other things, the possibility to deinterlace or telecide the content during the decoding process, all done in the GPU. This frees up more CPU ressources for the encoding process.

More information is avaliable here: http://rationalqm.us/dgdecnv/dgdecnv.html

Nevertheless I can't tell how good the deinterlacing quality of DGIndexNV compared to the deinterlacers provided by avisynth or vapoursynth is. I very rarely have to deal with interlaced content.

[stax76]

I'd rather donate that 15$ to charity and use L-Smash-Source instead.

[DavidRyan]

Trying out the new version (2.2.0) and when trying to demux an mkv originally from a DVD (converted to mkv with MakeMKV) staxrip crashes on the "extract forced subtitles" step. I don't actually need that step, is there anyway to stop it trying to do that? Had a look but couldn't see an option. Anyway I then tried staxrip 2.1.7.0 and it had no problems with the same file.

This is what was reported:
StaxRip.ErrorAbortException: Extract forced subtitles if existing returned error exit code: 1 (0x1)

It's unclear what the 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
ICERR_DONTDRAW vfw.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.

BDSup2Sub++ 1.0.3
OPTION: Exporting only forced subtitles.
Converting SUB/IDX
Loading D:/Video/Movies/xxx)/xxx/ID1 English_default.idx
WARNING: Invalid end sequence offset -> no end time
...
WARNING: Invalid end sequence offset -> no end time
Detected 0 forced captions.

at StaxRip.Proc.Start() in D:\Code\Github\staxrip\staxrip\Source\General\Proc.vb:line 357
at StaxRip.MainForm.ExtractForcedVobSubSubtitles() in D:\Code\Github\staxrip\staxrip\Source\Forms\MainForm.vb:line 2650
at StaxRip.MainForm.OpenVideoSourceFiles(IEnumerable`1 files, Boolean isEncoding) in D:\Code\Github\staxrip\staxrip\Source\Forms\MainForm.vb:line 2328


(The warning about invalid end sequence was repeated multiple times)

[videoh]

I'd rather donate that 15$ to charity and use L-Smash-Source instead. 20,000+ users beg to differ. Must suck to have to derive personal validation from virtue signaling. We will pray for you.

[stax76]

20,000+ users beg to differ. Must suck to have to derive personal validation from virtue signaling. We will pray for you.

Wasn't it 10000+ last year? I don't remember it. It handles TS well, that's it. I can't really recommend it regardless of who is selling it.

[DJATOM]

I'm pretty satisfied with DGDecNV, it's just sad that there's no Linux binary for plugin part (we can live with indexer over Wine).

[Jerethi]

I'm also receiving the same error with forced subtitles as reported by @DavidRyan.

[thomy22]

I'm also receiving the same error with forced subtitles as reported by @DavidRyan.

here also on every Movie

[thomy22]

In the case of one film, nothing works at all. After reading the window looks like everything is empty and there is this File:

recovery.srip

https://www.swisstransfer.com/d/38f4aa3a-e4e7-4253-946b-2de305d19a58

What can I do here?

[44vince44]

thomy we need a copy of the error, or find the log file in the temp folder, and the send us the log file, please...

[44vince44]

Jerethi, DavidRyan, Atlantis: thanks to @Mister-XY who made a PROPER bug report on github, and of course to the work of Dendraspis and Stax76, this bug of the forced subtitles, sadly introduced by a minor code optimization in v2.2, will be fixed in v2.3.
Please when a bug is confirmed, someone has to report it PROPERLY as Mister-XY did.
This is only a discussion forum! Github is the serious bug reporting place.

[thomy22]

thomy we need a copy of the error, or find the log file in the temp folder, and the send us the log file, please...

After all, there is no error message. Only this file that I have uploaded. The Staxrip window looks like I didn't upload anything. The folder is created but the audio tracks etc. are made but you can't set it to encode.

[DavidRyan]

As I don't have a github account (yes, I should probably register one) I thought mentioning it here was better than nothing, whether "PROPER" or not.

Lesson learned, won't mention bugs again. I assume cosmetic issues (like the digits at the bottom of each box rather than centered when editing audio profiles) should also go there so have just deleted the post I was in the process of making.

[videoh]

I'm pretty satisfied with DGDecNV, it's just sad that there's no Linux binary for plugin part (we can live with indexer over Wine). That's very interesting. A linux port was always blocked by the heavy win32 api usage in DGIndexNV. But if a DGDecodeNV port by itself is useful, then that is a real possibility. What linux distribution do you recommend for me to begin such a project? And are you favoring Vapoursynth or Avisynth+ for linux? You can reply in a PM or post at my forum if you like to keep off-topic stuff to a minimum in this thread.

[JKyle]

As I don't have a github account (yes, I should probably register one) I thought mentioning it here was better than nothing, whether "PROPER" or not.

I would also like to strongly recommend to post bug reports on GitHub (https://github.com/staxrip/staxrip/issues), not here.

One of the main reasons is that on GitHub, we can focus on the specific topic brought up in the bug report. This forum is not suitable at all for that purpose.

Another reason is that all developers/collaborators of StaxRip are watching/being notified of new issues on GitHub every time they are posted. We can't for posts on this forum unless we visit this forum on purpose.

That said, remember that when posting an issue/bug report on GitHub, sticking to the templates is very important. Insufficient information leads only to confusion and misunderstanding.

[JKyle]

...I used the default setting of QTGMC, which is set to medium. The source that I encoded is TS of TV recording and for the latest staxrip, it gives me about 31 to 41 FPS, and without QTGMC, depending on the source, it gives me about 100 FPS.

Maybe there's room for performance improvement of QTGMC.

Check if your CPU supports AVX2 (using CPU-Z and the like). If so, replace the shipped plugins_JPSDR.dll(in <StaxRip-Folder>\Apps\Plugins\AVS\JPSDR\) file with the AVX2 version in plugins_JPSDR_v3_2_5.7z (https://github.com/jpsdr/plugins_JPSDR/releases/tag/3.2.5). (The one in x64\Release_clang_W7_AVX2 is recommended.) See if it makes any change.

StaxRip ships with AVX version in consideration of backwards compatibility for more users.