StaxRip

[Atlantis]

AviSynth+ 3.7.0
https://github.com/AviSynth/AviSynthPlus/releases

[chipxtreme]

Originally Posted by Atlantis

AviSynth+ 3.7.0
https://github.com/AviSynth/AviSynthPlus/releases

Won't install for me.

[uNderdog_101]

Originally Posted by chipxtreme

Won't install for me.

You have Avast antivirus?
It's blocking the installation for me until they have scanned through the file for malware, seems to take a while since I tried an hour ago and I still can't install.

[chipxtreme]

Originally Posted by uNderdog_101

You have Avast antivirus?
It's blocking the installation for me until they have scanned through the file for malware, seems to take a while since I tried an hour ago and I still can't install.

No AVG

[JKyle]

Originally Posted by videoh

DGIndex fast version:

http://rationalqm.us/misc/DGIndex_fast.rar

Feedback will be appreciated.

I put it to test with two video files - test1.vob and test2.vob.
They are both MPEG-2/AC-3 files with minor differences.

Result: DGIndex_fast is significantly faster than the old one.

I put the detailed test result on my Google Drive: here.

In summary,

[test1.vob: running time 1h 18mn]
DGIndex: 38.40s
DGIndex_fast: 27.70s

[test2.vob: running time 2h 1mn]
DGIndex: 44.28s
DGIndex_fast: 29.24s

=> 40~50% speed improvement on my mediocre system (i5-7300HQ).

Of course, the output d2v files are identical for both.
For their mediainfo, log, d2v files, refer to the shared folder on Google Drive.

Anyway, you guys did a wonderful job!
I'm looking forward to its release.

[videoh]

Thank you for your results, JKyle. There are a couple things to be aware of when doing the performance testing.

1. Things can be complicated by Windows and HDD caching. So before doing a run, you should flush the windows cache by using flushmem.exe (google it) and power cycling the HDD.

2. The performance gain depends on if you have mechanical HDDs involved. For all SSD, I measure a 300% speed increase. For HDD much less but still quite significant. Seems to me that all serious work should be done on SSDs these days.

Will try to release it today. Just need to finish testing.

Anything else you'd like to see that we could possibly whip up quick for you?

Technical note: The gain was achieved mainly from two things: 1) Replaced _write()'s with fwrite()'s to leverage OS file caching, and 2) stop hammering the CPU with system calls to write to the Info dialog fields by updating only every 1000 frames (same as DGIndexNV).

[ChaosKing]

It would be nice if DGDecode could also set clip props like PictType (I, P, B Frame). I can't use DGDecNV since I switched to Amd Radeon T_T

EDIT:
SSD
DGIndex: 22s
DGIndex_fast: 10s

nvme
DGIndex:19s
DGIndex_fast: 7s

*note with audio demux

[videoh]

Thanks for your testing!

Originally Posted by ChaosKing

It would be nice if DGDecode could also set clip props like PictType (I, P, B Frame).

I'll look into it but not for this release.

http://rationalqm.us/dgmpgdec/dgmpgdec2002.zip

Sorry to hear about your video card downgrade.

[JKyle]

Originally Posted by videoh

There are a couple things to be aware of when doing the performance testing.

1. Things can be complicated by Windows and HDD caching. So before doing a run, you should flush the windows cache by using flushmem.exe (google it) and power cycling the HDD.

Thank you for the advice.

The reason I did the testing in a casual way is because I wanted to see how much performance improvement I could get from the new build on everyday use.

BTW, thank you for the new release today.

[JKyle]

Originally Posted by YaBoyShredderson

Does staxrip encode eac3 7.1 audio? ...... I ask because i updayed staxrip and it looks like the audio encoding is working again, and i have the option of eac3 in 7.1, but i also have 7.1 for ac3, which i know isnt a real thing. So can i do it? And at what bitrate should i chose if i can?

You're right. Both AC3 and EAC3 encode up to 5.1 channels in StaxRip as it is released.

Since StaxRip calls ffmpeg for AC3 and EAC3 encoding (ac3 and eac3 encoders respectively), you can check how many channels are supported by looking up the command line help of ffmpeg.exe called by StaxRip.


1. Click Apps > Manage... menu. Or shortcut F9.

2. Search for ffmpeg, click ffmpeg item and click Tools > Explore menu (or Ctrl + E).

3. On the Explorer window, go to the address bar by pressing Ctrl + L.

4. Type cmd and enter to open a Command Prompt window at the current location.

5. In the Command Prompt window, run the following command to see how many channels the ac3 encoder of ffmpeg supports.

.\ffmpeg.exe -hide_banner -h encoder=ac3 | findstr "channel"

This is the result for the default ffmpeg shipped with StaxRip 2.1.7.1 Beta.

Supported channel layouts: mono stereo 3.0(back) 3.0 quad(side) quad 4.0 5.0(side) 5.0 2 channels (FC+LFE) 2.1 4 channels (FL+FR+LFE+BC) 3.1 5 channels (FL+FR+LFE+SL+SR) 5 channels (FL+FR+LFE+BL+BR) 4.1 5.1(side) 5.1
-channel_coupling <int> E...A...... Channel Coupling (from -1 to 1) (default auto)

(The second line is an irrelevant option that passed the search keyword.)

You can see that ac3 supports up to 5.1 channels.


Likewise, if you run a similar command for eac3 in the same Command Prompt window, you'll get this result.

Supported channel layouts: mono stereo 3.0(back) 3.0 quad(side) quad 4.0 5.0(side) 5.0 2 channels (FC+LFE) 2.1 4 channels (FL+FR+LFE+BC) 3.1 5 channels (FL+FR+LFE+SL+SR) 5 channels (FL+FR+LFE+BL+BR) 4.1 5.1(side) 5.1
-channel_coupling <int> E...A...... Channel Coupling (from -1 to 1) (default auto)

You can see eac3 has the same feature.


The values for Channels option in the Audio Settings window of StaxRip are just there for all audio encoders. If you don't want to go through the manual search process like mentioned above or don't like to see unavailable channel numbers for a specific audio encoder, you can always post a feature request on the GitHub Issue Tracker.

Plus, bitrate choice is totally up to you. Only the source and your preference can be the criteria.

[videoh]

Originally Posted by JKyle

The reason I did the testing in a casual way is because I wanted to see how much performance improvement I could get from the new build on everyday use.

Indexing a job twice in a row with different versions is not everyday use! The first run may not benefit from the caches whereas the second always will. That is why I recommend to purge windows and disk caches before every run when doing performance testing. So if you would run the first time with the new version and the second with the old version, you won't see the same gains as you would if each ran without caches.

Alternatively, I suppose you could do it three times, using the first to just fill the caches and ignore its result. Then both following runs would benefit from the caches.

[JKyle]

You're right. I didn't treat them fairly.
I was just too lazy. :sweat:

Three step testing seems more reasonable than a naive two-step comparison.
Thanks for pointing it out.

[Andy]

To get the latest QTfiles64 libraries, download the latest iTunes64 installer https://secure-appldnld.apple.com/it...nes64Setup.exe and makeportable2.zip https://sites.google.com/site/qaacpage/cabinet for it.
You put them in the same folder. You run mekeportable2.cmd and a QTfiles64 folder is created that contains all the libraries for QAAC decoding.
There will be a lot of them, you only need these:
QTfiles \ ASL.dll
QTfiles \ CoreAudioToolbox.dll
QTfiles \ CoreFoundation.dll
QTfiles \ icudt55.dll
QTfiles \ libdispatch.dll
QTfiles \ libicuin.dll
QTfiles \ libicuuc.dll
QTfiles \ msvcp100.dll
QTfiles \ msvcr100.dll
QTfiles \ objc.dll
You can then paste the QTfiles64 folder into C: \ Program Files \ Common Files \ Apple and set the path in Staxrip 2.1.7.0.
There may not be a folder in the qaac directory.
Previously, it was enough to install Apple Application Support64.msi on Windows10 and the libraries were in this folder. Newer versions of iTunes no longer contain this file.

[AMED]

I think i have found a memory leak with x265 M-3.4+28 gcc10.2.0 Yuuki-Asuna/msg7086/DJATOM/Patman thats included with Staxrip.




Encoding started out at about 4GB memory usage. After encoding 20% of the Bluray it's now at 7.6GB and it will get to the point where it runs out of memory and crashes.

I don't seem to have the same problem when using VSpipe.

EDIT: now up to 10GB


EDIT2:
the VS script i'm using.

clip = core.ffms2.Source(r"Z:\Bluray\Queue\1080p\1080p.mkv", cachefile=r"C:\TMP\1080p_temp\temp.ffindex")
#clip = core.std.AssumeFPS(clip, None, 25, 1)
clip = core.std.Crop(clip, 0, 0, 22, 22)
clip = core.fmtc.bitdepth(clip, bits=16)
clip = havsfunc.SMDegrain(clip, tr=6, RefineMotion=True, thSAD=500)
clip.set_output()

The x265 commandline i'm using.

x265.exe --crf 18 --preset slow --output-depth 10 --dither

I'm waiting for it to crash so i can grab the logs.

[44vince44]

@AMED can you please replace it with Patman86's build and give us feedback!
Here is his repository. His builds have the same features.
https://www.mediafire.com/folder/vkt.../StaxRip_Tools
Use any x64 build called x265M-

Edit: as we're talking now DJATOM is working on a fix!

[AMED]

Do you still want me to test?

I have downloaded x265M-3.4+35-772bb4c84-x64-gcc10.2.0.

EDIT:
x265M-3.4+35-772bb4c84-x64-gcc10.2.0 does the same thing.

[44vince44]

@AMED thanks for testing. Your result has been confirmed by other users. This matter is being investigated. Check the thread here:https://github.com/staxrip/staxrip/issues/445

[YaBoyShredderson]

Originally Posted by JKyle

You're right. Both AC3 and EAC3 encode [B]up to 5.1 channels

Ill keep using flac then. Thanks.

[lifta19]

In 2-pass encoding, commands can only be checked for 1 pass
Please let me see the 2-pass command
Sometimes you can encode one pass first and two passes a few days later

[aegisofrime]

Hi, can I ask how do I go about getting VSGAN to work with StaxRip? Details of VSGAN can be found here:

https://github.com/rlaPHOENiX/VSGAN

VSGAN is typically installed via

pip install vsgan

, so I tried to navigate to the Python executable in my StaxRip folder, and run

python.exe -m pip install vsgan

, however this errors out with it saying that no module pip was found. What's the easiest way to go about getting it to work?

I have already installed VSGAN using my "installed" python installation, is there a way to just tell StaxRip to load it from the folder that's installed to site-packages?