StaxRip

[Z'Hadum]

Here is some info:

https://staxrip.readthedocs.io/faq.html#why-does-avisynth-portable-mode-require-soft-links

You can try:

x264/x265 Options > Input/Output > Pipe > avs2pipemod

avs2pipemod and nvenc support a custom AviSynth DLL path.

Or if you have AviSynth installed you can enable it in the settings:

Tools > Settings > Frameserver > AviSynth > Use Installed Directly

If your installed AviSynth version is too old you can copy the files from staxrip to system32.

I cannot tell you why soft link creation does not work on your system.
I'm using a network share, because I run the same Queue on different Computers
Softlink creation on networkshares is difficult, as far as I know. Because you need UAC, and in that environment the mapped Network path does not exist...

I will try your suggestions.. Thank you! :thanks:

[AMED]

Unfortunate bug for a stable release... It's the same reason and fixed in the next build.

It's not the best possible location, that's why it's not permitted by default:

Custom paths within the startup folder are not permitted
because it would prevent a simple update process.
Please put the file somewhere else outside the startup folder

Looks like there is still something funky with the apple application support files and QAAC using 2.1.7.0. I have set the location to the support files outside of the Staxrip folder and it will fail to encode with the following error.

ERROR: 193: CoreAudioToolbox.dll

Once i copy the QTfiles folder in to ..\StaxRip\Apps\Audio\qaac\ it works.

So I need to keep folder with the QTfiles in them outside of the staxrip folder to keep staxrip happy and another copy of the QTFiles folder in ..\StaxRip\Apps\Audio\qaac\ for QAAC to work.

[Atlantis]

Thank you, I have copied the entire eac3to folder in staxrip 2.1.7.0 to an outside place and point to that.

Question, what is this autoupdate procedure that people talk about? Staxrip auto updates? With every new version we have to download the whole package and overwrite.

[stax76]

@Z'Hadum

Soft links if needed are located within the startup folder where staxrip is located. It should not be a problem if staxrip is located on a local drive.

@AMED

Not reproducible for me, I've only one CoreAudioToolbox.dll on my system, it's outside and found by qaac because staxrip adds the folder to PATH per process, default DLL search includes PATH.

Question, what is this autoupdate procedure that people talk about? Staxrip auto updates?

It's mostly useful for the maintainer (me) and power users to easily update tools, it works for most GitHub hosted tools and for certain other tools, mkvtoolnix for instance is downloaded from videohelp.com, mediafire isn't supported. Updating tools was a burden for me before, now it's easy. Normal users should be careful, it has harm potential on certain tools, some of them are already locked.

[AMED]

Ahh ok, the path doesn't get added on my machine.

Apps > Manage > apple application support | I set the path to CoreAudioToolbox.dll outside of StaxRip install Directory. set version number to 7.10.9.0 and then click Tools > Path ENV Var... and then choose add and StaxRip crashes.


------------------------- System Environment -------------------------

StaxRip : 2.1.7.0
Windows : Windows Server 2012 R2 Standard
Language : English (New Zealand)
CPU : Intel(R) Xeon(R) CPU E5530 @ 2.40GHz
GPU : Matrox G200eW (WDDM 1.2)
Resolution : 2078 x 1332
DPI : 96

------------------------------ Exception ------------------------------

System.NullReferenceException: Object reference not set to an instance of an object.
at StaxRip.AppsForm.miPATHEnvVar_Click(Object sender, EventArgs e) in D:\Projekte\VB\staxrip\Forms\AppsForm.vb:line 1041
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at StaxRip.UI.MenuItemEx.OnClick(EventArgs e) in D:\Projekte\VB\staxrip\UI\Menu Types.vb:line 472
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[stax76]

This apps dialog feature adds a tool permanently to the user path. The code looks OK, powershell equivalent is this:

[Environment]::GetEnvironmentVariable('Path', 'User')

You can run it in a terminal, it should return on any system various paths.

It's only somehow related because when staxrip is processing it modifies PATH per process automatically, you don't have to do it manually in the apps dialog unless you want to run command lines without staxrip, changing PATH per process means it's not persistent, per process powershell code:

[Environment]::GetEnvironmentVariable('Path')

It should return the same or similar what $env:path returns.

PowerShell and VB.NET are using the very same .NET code here.

[JKyle]

@stax76

Thanks for 2.1.7.1 Beta.

BTW, I've found two redundant files in Apps\Conf:

DFTTest Neo vs.conf => not needed anymore
DGDecode avs.conf => not necessary

:)

[videoh]

DGIndex fast version:

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

Feedback will be appreciated.

[-QfG-]

@44vince44
2.1.3.7 w new apps and FFVideo = Duration: 08:19
2.1.3.7 w new apps and LWLibavVideoSource = Duration: 08:23
2.1.7.0 with LWLibavVideoSource = Duration: 13:10
2.1.7.0 with Automatic (FFVideo) = Duration: 13:01

Can't confirm this, make any test Encodes with 2.1.3.0 Stable and 2.1.7.0 Stable. x265 Encoder v 3.4+13 from Yuuki-Asuna. Test Template without pipelining and with LWLibav indexing. System Ryzen Zen2 3950x.

LOGFILE 2.1.3.0 and 2.1.7.0 included.

Testfile = 2 Minute Sample 4K HDR

Durations:

2.1.3.0 = 00:08:32 (encoded 2870 frames in 511.40s (5.61 fps), 7772.15 kb/s, Avg QP:22.01)
2.1.7.0 = 00:08:36 (encoded 2870 frames in 515.08s (5.57 fps), 7772.15 kb/s, Avg QP:22.01)

My only problem with 2.1.7.0 is, that the indexing window is invisible during indexing, this works fine with 2.1.3.0.

[YaBoyShredderson]

Does staxrip encode eac3 7.1 audio? Im encoding my 4k rips in staxrip but for some reason the audio encoding was broken, so just encoded the audio using handbrake and muxed them together. For my 1080p i use ac3 5.1 640kbs, but for the 4k ive had to settle for flac in handbrake as handbrake can only encode eac3 at 5.1 channels. 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?

[Atlantis]

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

[chipxtreme]

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

Won't install for me.

[uNderdog_101]

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]

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]

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 (https://drive.google.com/drive/folders/1IVQQmi1a-QJHhdX-2sn5PcJ6h2AyJn5o?usp=sharing).

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!

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]

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]

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 (https://github.com/staxrip/staxrip/issues).

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

[videoh]

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/itunes12/001-50023-20201019-A1CA6082-1239-11EB-990E-FA5946985FC9/iTunes64Setup.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.


https://i.ibb.co/ScfYdH2/Staxrip-x265.png (https://ibb.co/ScfYdH2)

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
https://i.ibb.co/DkmMTJF/Staxrip-x265-2.png (https://ibb.co/DkmMTJF)

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/vkt2ckzjvt0qf/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.

https://i.ibb.co/tLcFcNK/Staxrip-x265-3.png (https://ibb.co/tLcFcNK)

[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]

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

Ill keep using flac then. Thanks.

[lifta19]

https://funkyimg.com/i/3a4JA.jpg

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?

[stax76]

@lifta19

Please request it here:

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

[stax76]

2.1.7.2 Beta

- Using neo functions caused non neo plugins being loaded without reason (stax76)
- Fix weird behaviour on Audio Settings for qaac (Dendraspis)
- x265 fixed default value for --hist-threshold (Dendraspis, #441)
- x265 muxing won't mux chunks from recent encodes (Dendraspis, #438)
- x265 don't use a pipline for chunks if no pipeline is set (Dendraspis, #430)
- x265 --seek and --frames also work with chunks (Dendraspis, #430)
- x265 Pipe option is invisible if decoder is not set to AVS/VPY (Dendraspis)
- In the portable AviSynth folder there are two PowerShell scripts to install and uninstall AviSynth (stax76)
- Using ffmpeg as pipe tool with VapourSynth and x264/x265 (Patman86)
- QT libraries will be found if located at Apps\Audio\qaac, Apps\Audio\qaac\QTfiles64, download button points to wiki page with install instructions (stax76)
- Add 'ShowCodePreview' to commands list (Dendraspis, #444)
- x265 options set chromaloc automatically to 2 if HDR is set to "Yes", to 0 if HDR is disabled or keep it untouched if "Undefined" (Dendraspis, #319)
- "Import VUI metadata" also imports Chromaloc (Dendraspis, #319)
- "Import VUI metadata" sets "--hdr10" (Dendraspis)
- Moved '--high-tier' to 'Basic' page for x265 (Dendraspis)
- Introduce custom quality definitions for x264 and x265 via Settings > Video (Dendraspis)
- The x265 command line preview shows both passes for two pass (stax76, #454)
- MP4Box can import EAC3 (stax76, #455)
- Processing form remembers its size (stax76)
- Speed control in rav1e dialog has hint text: 0 = Slowest, 10 = Fastest (stax76)
- nvenc option --timecode (stax76)
- x265 UI bug in preset VerySlow showing unnecessarily default values in command line (Dendraspis, stax76)
- AviSynth 3.7
- x265 3.4+56 aMod gcc10.2.1 msg7086/DJATOM (VapourSynth reader fixed)
- MP4Box 1.1.0-rev447-g8c190b551-gcc10.2.0 Patman (Windows 10 long path support added)
- nvenc 5.25
- rav1e 0.4.0
- DgMpgDec 2.0.0.2

[apophis906]

Direct input chunk encoding is broken with the new beta. All chunks will be encoded with the first chunk part. When changing to avs2pipemod everything works like it should and each chunk is correct.

[44vince44]

Can you please report the issue directly here: https://github.com/staxrip/staxrip/issues

[stax76]

2.1.7.3 Beta

- Full AviSynth unicode and full long path support for users of Windows 10 1903, Windows 7 users need to enable avs2pipemod for x265 in order to use foreign (ANSI) characters
- Show also Source HDR Format on main window (Dendraspis)
- 3.4+62-aMod-gcc10.2.1+opt msg7086/DJATOM (avs unicode/long path/chunk encoding)

[jlw_4049]

2.1.7.3 Beta

- Full AviSynth unicode and full long path support for users of Windows 10 1903, Windows 7 users need to enable avs2pipemod for x265 in order to use foreign (ANSI) characters
- Show also Source HDR Format on main window (Dendraspis)
- 3.4+62-aMod-gcc10.2.1+opt msg7086/DJATOM (avs unicode/long path/chunk encoding)Thank you!

Sent from my SM-G986U1 using Tapatalk

[JKyle]

@stax76:

I think it's time we updated AvsResize to the most recent version r5 by StvG. The current one(r1d) is kind of outdated.

See this Wiki page about AvsResize (http://avisynth.nl/index.php/Avsresize).
(I think it's more appropriate for the Website link on Apps Manager.)

The most noticeable changes are as follows:


Many pixel types are added.
z_BlackmanResize(), z_GaussResize(), and z_SincResize() compatibility aliases have been removed.
zimg(z.lib) is updated.


But since we only have z_ConvertFormat filter in AVS/VS Profiles, we just need to add additional option values as follows:

[AviSynth]

Convert | Format = z_ConvertFormat(pixel_type="$enter_text:Enter the Format You Wish to Convert to$", colorspace_op="$select:msg:Select Input Color Matrix;rgb;709;unspec;fcc;470bg;170m;240;ycgco;2020ncl;2020cl;chromancl;chromacl;ictcp$:$select:msg:Select Input Color Transfer;709;unspec;470m;470bg;601;240m;linear;log100;log316;xvycc;srgb;2020_10;2020_12;st2084;std-b67$:$select:msg:Select Input Color Primaries;709;unspec;470m;470bg;170m;240m;film;2020;st428;st431-2;st432-1;jedec-p22$:$select:msg:Select Pixel Range;limited;l;full;f$=>$select:msg:Select Output Color Matrix;rgb;709;unspec;fcc;470bg;170m;240;ycgco;2020ncl;2020cl;chromancl;chromacl;ictcp$:$select:msg:Select Output Color Transfer;709;unspec;470m;470bg;601;240m;linear;log100;log316;xvycc;srgb;2020_10;2020_12;st2084;std-b67$:$select:msg:Select Output Color Primaries;709;unspec;470m;470bg;170m;240m;film;2020;st428;st431-2;st432-1;jedec-p22$:$select:msg:Select Pixel Range;limited;l;full;f$", dither_type="$select:msg:Select Dither Type;none;ordered;random;error_diffusion$")

[VapourSynth]

Convert | Format = clip = core.avs.z_ConvertFormat(clip, pixel_type='$enter_text:Enter the Format You Wish to Convert to$', colorspace_op='$select:msg:Select Input Color Matrix;rgb;709;unspec;fcc;470bg;170m;240;ycgco;2020ncl;2020cl;chromancl;chromacl;ictcp$:$select:msg:Select Input Color Transfer;709;unspec;470m;470bg;601;240m;linear;log100;log316;xvycc;srgb;2020_10;2020_12;st2084;std-b67$:$select:msg:Select Input Color Primaries;709;unspec;470m;470bg;170m;240m;film;2020;st428;st431-2;st432-1;jedec-p22$:$select:msg:Select Pixel Range;limited;l;full;f$=>$select:msg:Select Output Color Matrix;rgb;709;unspec;fcc;470bg;170m;240;ycgco;2020ncl;2020cl;chromancl;chromacl;ictcp$:$select:msg:Select Output Color Transfer;709;unspec;470m;470bg;601;240m;linear;log100;log316;xvycc;srgb;2020_10;2020_12;st2084;std-b67$:$select:msg:Select Output Color Primaries;709;unspec;470m;470bg;170m;240m;film;2020;st428;st431-2;st432-1;jedec-p22$:$select:msg:Select Pixel Range;limited;l;full;f$', dither_type='$select:msg:Select Dither Type;none;ordered;random;error_diffusion$')

Since I incorporated all available values here, we can omit some values depending on use case.

z_ConvertFormat is indispensable in tonemapping, so this needs to be taken care of appropriately.

And don't forget to delete the three filters(z_BlackmanResize, z_GaussResize, z_SincResize) from Apps Manager.

---

In addition, D2VSource is updated to 1.2.1 (https://github.com/Asd-g/MPEG2DecPlus/releases/tag/1.2.1).

[44vince44]

That seems interesting, thanks for doing the filter profile !

[fredlkrue]

Using the latest beta (2.1.7.3) under Windows 7, I have the following issues:
1. The zoom out option under preview doesn't work.
2. Fails to create links for the portable frameservers, I have to switch to the installed version instead.

Thanks for all the hard work and the continuation of this project.

[44vince44]

@fredlkrue, please check the following

1) Did you extract the new 2.1.7.3 archive at the same place as the older one ? you must always delete the content of the old root folder (APPS folder) before putting there the new files.
2) maybe you need to delete your old settings. This is sometimes required, when major changes are made in the software.

I have just checked the creation of symlinks: it works
I have just checked the zoom out, it works: key "-" of the main keyboard (not keypad) zooms out, key "=" zooms in. You can change the keys as you please.

No bug found here. Please give us feedback after you check 1) and 2)

[stax76]

@JKyle

I've created an issue for it.

@fredlkrue

Enabling avs2pipemod would also work as it supports defining a custom avisynth path, this feature can be requested from x265 modders, it's the last important missing feature. I just don't want to ask for a new feature every day.

[fredlkrue]

@fredlkrue, please check the following

1) Did you extract the new 2.1.7.3 archive at the same place as the older one ? you must always delete the content of the old root folder (APPS folder) before putting there the new files.
2) maybe you need to delete your old settings. This is sometimes required, when major changes are made in the software.

I have just checked the creation of symlinks: it works
I have just checked the zoom out, it works: key "-" of the main keyboard (not keypad) zooms out, key "=" zooms in. You can change the keys as you please.

No bug found here. Please give us feedback after you check 1) and 2)

1) I always do that with new StaxRip version.
2) I always start fresh with new settings.

I always get that error message while creating the symlinks and that -/= I always use from main keyboard it used to work a while ago (forgot what version).

[44vince44]

@fredlkrue

Let's see one thing at a time. The zoom out:
Please open Preview, press "m", this opens the Menu Editor.
Scroll down to View>Zoom In/Zoom out, check the command is "Zoom" and the factors are 1.1 and 0.9
There you can also set the shortcuts.

[fredlkrue]

@fredlkrue

Let's see one thing at a time. The zoom out:
Please open Preview, press "m", this opens the Menu Editor.
Scroll down to View>Zoom In/Zoom out, check the command is "Zoom" and the factors are 1.1 and 0.9
There you can also set the shortcuts.

I have the same settings, but I have just notice that for some reason the preview starts in fullscreen and by hitting "enter" it exits from fullscreen and the commands zoom in and zoom out works again. Thanks for your help.

[44vince44]

@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...

[Atlantis]

Is staxrip pipeline Unicode compatible? I had a file with ü in the file name and x265 couldn't open it. I renamed it to u and staxrip encoded it without fatal error.

[stax76]

@Atlantis

staxrip, mpv.net, x265 DJATOM and x264 official are the firsts avisynth apps that use a UTF-8 manifest, that means on Windows 10 1903 or higher avisynth uses UTF-8 as code page, on earlier Windows versions the manifest is ignored and the code page of the OS is used, this might not yet work in the modded x265 build. What staxrip does is saving the avs script with different text encoding depending on what application is going to open the script. So on Windows 10 1903 or higher there is full avisynth Unicode support in staxrip even if the system code page is not UTF-8. Windows 10 allows changing the system code page globally to UTF-8, this setting can be found in the administrative language setting and is often used by power users, in that case many avisynth apps will support Unicode. If you have problems with foreign characters I suggest using the latest staxrip beta.

[Atlantis]

I have Windows 10 Version 20H2. The Staxrip I have 2.1.7.0 the version you added output resolution on the top right. Do I need an even newer staxrip for Unicode to work?

[Atlantis]

This was also what I was talking about
All or None button for attachments

https://i.postimg.cc/G2dYN4Jt/Untitled.jpg

[DJATOM]

Yes, you have to use beta version to benefit from latest changes.