StaxRip

[burfadel]

Originally Posted by stax76

Thanks for the links, I made all changes including description for qaac in the applications dialog:

There is however a problem with qaac 64-Bit, the command shell window pops up and StaxRip don't receive any output, I don't think I can do anything here other then report it to the author which I already did, waiting for a reply now.

Hope it isn't too much of an issue to resolve!

Originally Posted by stax76

Using the same filenames is IMO the best approach, 32-Bit StaxRip using 64-Bit ffmpeg is a bad, look at one of the current defaults:

"%app:ffmpeg%" -i "%avs_file%" -f yuv4mpegpipe -pix_fmt yuv420p - | "%app:NVEncC%" --sar %target_sar% --codec h265 --y4m --cqp 36 --input - --output "%encoder_out_file%"

Most people will use the NVEncC GUI, the nice thing about this profile is it teaches people that piping is possible and simple, ffmpeg interfaces with AviSynth here (loading the AviSynth library via COM+), 64-Bit applications can only load 64-Bit libraries (at least without black magic).

Ah okay! I didn't think of that, I don't use NVEnc, I mainly used ffmpeg for forced audio decoding. I found decoding to .wav first was more reliable for some sources than encoding the audio directly from the source file. For practicality, I just had it enabled by default .

[stax76]

Hope it isn't too much of an issue to resolve!

I hope it's not but this one could be difficult.

Ah okay! I didn't think of that, I don't use NVEnc, I mainly used ffmpeg for forced audio decoding. I found decoding to .wav first was more reliable for some sources than encoding the audio directly from the source file. For practicality, I just had it enabled by default

Another location where ffmpeg interfaces with AviSynth is the cut feature because for cutting mkvmerge needs a video file so StaxRip creates a 16x16 pixel AVI file with AviSynth and ffmpeg, decoding with ffmpeg isn't necessary in my experience but should be fine doing and has the advantage of most accurate cut points. I have to test if the new FLAC automatic gets in the way here.

[Patman]

I've tested xvid_encraw a bit with quality mode and 2-pass mode. The app worked as it should. In my opinion it's very easy to customize the settings. I made some changes for better quality.

[luigizaninoni]

I spoke too soon about the benefits of multithreaded Avisynth+

The speed benefits are there, but it is hardly stable. With Prefetch=3 or above, it invariably crashes in a few minutes. With prefetch=2 it is usually stable, however last night I launched a long encode and found that after a couple of hours it had crashed.

Maybe I am doing something wrong, or avisynth+ MT is not mature yet, or am using the wrong MT_MODE for some filter.

Anyhow, I am back to Staxrip with avisynth+ single-threaded, doing two encodes at the same time to fill CPU. Rock solid.

[burfadel]

Originally Posted by stax76

I hope it's not but this one could be difficult.

I am trying out the beta you posted for this, it works well so far! The issue with QAAC64 is of minor annoyance only (having that command window pop up). On the other hand, it starts encoding the video while the audio is still encoding, so you have accidental mutlithreading there!

So there's no way of just outputting just the title bar information, and hiding the window?

[thomy22]

I test the new Version thanks for that.

But why the Files are so big? I have the same options and the File on the Old version are 300-350 MB (for 23min DVD File on X264) now i have 750 MB.

on the Old Version i have this Filters here centrodiperditadipeso.info

FieldDeinterlace
Crop Boarders
DeGrainMedian

now i have the standart Filters:

TDeint
Crop
Remove Grain

Are the Filters not work the same like the Old one or why the Files are so big now?

All other Settings are the Same CRF 19 and B-Frames and R-Frames 16 on Present Slower Tune Film

[burfadel]

I notice that even though tfm is listed in the filter menu, the plugin isn't included. I believe tdecimate is also in the same package as tfm, so there should be an option in the filter menu for inverse telecining and decimation (which can be done with these two filters). Without inverse telecining and decimation, people will be doing a lot of bad encodes of telecined material!

[burfadel]

@Stax
I found out something 'important' regarding the QAAC issue, I'll send a PM

[burfadel]

@Stax
(from the private PM, glad the qaac issue was super simple to fix!)

I came across the flash3kyuu deband filter, and am extremely impressed with the results on a poor quality video I had. The compression is good too, I used dither_algo=2 as suggested (it's better for standard bitrates, algo 3 is better for high bitrate outputs).

Anyways, the doom9 page is here:
http://forum.doom9.org/showthread.php?t=161411

Both x64 and x86 versions are available. Help file is inside.

Now, I've come across a more updated version of it, still from the same sources as in the linked doom9 post, just that post hasn't been updated!

Topic here:
https://www.nmm-hd.org/newbbs/viewtopic.php?f=7&t=239

The version I used was the 2.0pre+b98d6bc x86/x64, inside which has the x64 and x86 dll's. It's up to date too! 2015-05-02, so only 2 days old.

If anyone is wondering, I see the removing the banding and other issues present in poor quality videos as important. Some say it's pointless because you may introduce banding with encoding anyway, but that is rather an old thought on the manner. If there is banding present in the source, when you encode you are going to encode the banding as well! If you have a debanded source, with a very mild light dither, modern encoders (especially 10-bit versions of x265 etc) will produce markedly better file outputs.

EDIT: Done a few more encodes, not only do I get a better quality output, but the output file size is actually smaller! I guess it makes sense since it's not using bits encoding the banding artifacts. I think it's well worth it going from 8-bit sources to 10-bit x265. It's also fast , especially the 02 Msy 2015 build. This is using dither_algo=2.

[luigizaninoni]

I made further findings on Avisynth+ MT issues.

I found that problems arise (encode crashes) ONLY when Qtgmc AND SelectEven() are both enabled.

So:
Script with only Qtgmc --> MT works fine, even with Prefetch(4)
Script with only SelectEven() --> MT works fine
Script with Qtgmc AND SelectEven() --> encode crashes

What's going on ? I have no clue. Is this a problem with Avisynth+ or with Staxrip ?

[Reel.Deel]

Originally Posted by luigizaninoni

I made further findings on Avisynth+ MT issues.

I found that problems arise (encode crashes) ONLY when Qtgmc AND SelectEven() are both enabled.

So:
Script with only Qtgmc --> MT works fine, even with Prefetch(4)
Script with only SelectEven() --> MT works fine
Script with Qtgmc AND SelectEven() --> encode crashes

What's going on ? I have no clue. Is this a problem with Avisynth+ or with Staxrip ?

This sounds like an AviSynth+ problem. Have you tried SelectOdd instead? Also you can try SelectEvery as an alternative? If that fails how about QTGMC(FPSDivisor=2)?

QTGMC()
SelectEvery(2, 0)  # identical to SelectEven()
#SelectEvery(2, 1) # identical to SelectOdd()

[luigizaninoni]

Thanks for the suggestion.

However, SelectOdd, SelectEvery and FpsDivisor all crash after a few hundred frames, just like SelectEven

[stax76]

@luigizaninoni

There is a similar report in the AviSynth+ thread, please post a full script, I want to test it too.

@burfadel

Thanks for the plugin suggestion and the help with qaac, I can add many more plugins, no problem. Regarding TDecimate, there is a crash in Win8/Win10 it seems so I removed the plugin and forgot to remove the filter. Some plugins have some CPU related parameters I need to try, overall there were many issues on Win8/Win10 not happening on Win7 so I decided to migrate to Win10 preview as main OS to investigate all problems.

@thomy22

if the quality looks good then filters cannot make such a big difference in file size, it's most likely related to source complexity and crf.

@Patman

Thanks for the tip about the new DLL.

[burfadel]

I just tried the StaxRip_2015.05.04_20-32 beta, and it errors as a result of AssumeFPS(%fps%) on existing projects. Even completed projects it says invalid argument because of this.

Just noticed that I reclicked the source filter I was using, saved the template, and recreated the projects that were in the queue, and they are encoding fine now. I guess assumefps(%fps) was a change between the last beta and this one .

[stax76]

I've removed all those macros because they are not needed any longer, instead of always using the frame rate from MediaInfo with macros I add AssumeFPS dynamically now only if correction is needed, the correction logic is following:

if frame rate from AviSynth is approximately 2 times more then frame rate from MediaInfo then StaxRip adds SelectEven().AssumeFPS(fpsFromMediaInfo)

this corrects a bug where ffms2/ffmpeg duplicates interlaced frames

the second correction fixes wrong PAL frame rates, NTSC I leave now which might improve or worsen things, I don't know too much about NTSC.

[luigizaninoni]

Here is the script:
Import("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\QTGMC\QTGMC.avsi")
LoadPlugin("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\masktools2\masktools2.dll")
LoadPlugin("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\mvtools2\mvtools2.dll")
LoadPlugin("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\nnedi3\nnedi3.dll")
LoadPlugin("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\RgTools\RgTools.dll")
LoadPlugin("C:\Users\admin\Desktop\Video\Stax beta\Tools\Plugins\ffms2\ffms2.dll")
SetFilterMTMode("DEFAULT_MT_MODE",2)
SetFilterMTMode("FFVideoSource",3)


FFVideoSource("C:\Users\admin\Desktop\Interceptor (1979) temp files\Interceptor (1979).m2v", cachefile = "C:\Users\admin\Desktop\Interceptor (1979) temp files\Interceptor (1979).ffindex", fpsnum = 25, fpsden = 1)
QTGMC(Preset="Slow")
SelectEven()
Crop(2, 70, -2, -70)
Prefetch(4)

[stax76]

@luigizaninoni

I might have found something, putting SelectEven and Crop after Prefetch!

edit:

too bad, it's also freezing.

[NikosD]

Originally Posted by stax76

this corrects a bug where ffms2/ffmpeg duplicates interlaced frames

The new method of 1.3.1.1 works fine with interlaced H.264 files and ffms2, just like the previous 1.3.1.0, but the new method is a lot faster I think.

[luigizaninoni]

Where is the new beta? I can't find it

[stax76]

there is a dropbox folder where I often upload bug fixes, it's here:

https://www.dropbox.com/sh/xiyz10pgh...srbITYDBa?dl=0