StaxRip

[tormento]

Next DGDecNV slipstream will demux chapters from MKV when the CLI -a is given. I've linked a test build at my forum.
How I wish to have full batch support for DGDecNV instead of being bond to non frame accurate indexers. For one movie I can manually feed DGI and manually remux the streams. I am currently converting some dozens of episode clips and I am tied up to default ffmsindex to keep on having the batch feature available.

[ChaosKing]

You can create a small bat file for that. I indexed/demuxed 26 episodes with my bat in one go, easy peasy.

[stax76]

The batch mode of staxrip would also work.

[tormento]

The batch mode of staxrip would also work.
Look what happens if I use DGIndexNV as preprocessor:
------------------------- System Environment -------------------------

StaxRip : 2.1.8.0
Windows : Windows 10 Enterprise 2004
Language : Italian (Italy)
CPU : Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz
GPU : NVIDIA GeForce GTX 1060 3GB
Resolution : 1920 x 1080
DPI : 96
Code Page : 1252

----------------------- Media Info Source File -----------------------

F:\In\test\06 Hitagi end 6.mkv

General
Complete name : F:\In\test\06 Hitagi end 6.mkv
Format : Matroska
Format version : Version 4
File size : 1.55 GiB
Duration : 26 min 26 s
Overall bit rate : 8 382 kb/s
Encoded date : UTC 2020-09-15 16:33:07
Writing application : mkvmerge v50.0.0.18 ('Awakenings') 64-bit
Writing library : libebml v1.4.0 + libmatroska v1.6.2
Attachments : IwaMinPro-Lt-Madoka.ttf / IwaOMinPro-Bd-Fate.ttf / LHF_Scriptana.ttf / Montara-Gothic_0.otf / Reswysokr.otf / arial.ttf / CenturyOldStyle-Light Bold.ttf

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : V_MPEGH/ISO/HEVC
Duration : 26 min 26 s
Bit rate : 8 142 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.164
Stream size : 1.50 GiB (97%)
Writing library : x265 3.1.1:[Linux][GCC 9.1.0][64 bit] 10bit
Language : Japanese
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Commercial name : Dolby Digital
Codec ID : A_AC3
Duration : 26 min 26 s
Bit rate mode : Constant
Bit rate : 224 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 31.250 FPS (1536 SPF)
Compression mode : Lossy
Stream size : 42.4 MiB (3%)
Language : Japanese
Service kind : Complete Main
Default : Yes
Forced : No

Text
ID : 3
Format : ASS
Codec ID : S_TEXT/ASS
Codec ID/Info : Advanced Sub Station Alpha
Duration : 26 min 23 s
Bit rate : 398 b/s
Count of elements : 951
Compression mode : Lossless
Stream size : 76.9 KiB (0%)
Language : Italian
Default : Yes
Forced : No

Menu
00 : 00:00.000 : it:Prologo
00 : 01:20.998 : it:Opening
00 : 02:51.046 : it:Episodio
00 : 25:40.039 : it:Anteprima

----------------------- DGIndexNV: Index, Demux -----------------------

D:\Eseguibili\Media\DGDecNV\DGIndexNV.exe -i "F:\In\test\06 Hitagi end 6.mkv" -o "F:\In\test\06 Hitagi end 6_temp\06 Hitagi end 6.dgi" -a -h

Project
20
33
42
75
80
100

Start: 13:35:23
End: 13:35:28
Duration: 00:00:04
And the file structure is:
Summary of path: F:\In\test
Created: 11/02/2021 13:41:08

F:\In\test\06 Hitagi end 6_temp
F:\In\test\06 Hitagi end 6_temp\06 Hitagi end 6.dgi
F:\In\test\06 Hitagi end 6_temp\06 Hitagi end 6.log
F:\In\test\06 Hitagi end 6_temp\06 Hitagi end 6.dgi_chapters.xml
F:\In\test\06 Hitagi end 6_temp\06 Hitagi end 6_new.avs
F:\In\test\06 Hitagi end 6_temp\06 Hitagi end 6_new_source.avs
F:\In\test\06 Hitagi end 6_temp\06 Hitagi end 6_new_staxrip.log
F:\In\test\06 Hitagi end 6_temp\06 Hitagi end 6_track2_jpn_DELAY 0ms.ac3
F:\In\test\06 Hitagi end 6_temp\06 Hitagi end 6_track3_ita.ass
F:\In\test\06 Hitagi end 6.mkv
F:\In\test\arial.ttf
F:\In\test\CenturyOldStyle-Light Bold.ttf
F:\In\test\IwaMinPro-Lt-Madoka.ttf
F:\In\test\IwaOMinPro-Bd-Fate.ttf
F:\In\test\LHF_Scriptana.ttf
F:\In\test\Montara-Gothic_0.otf
F:\In\test\Reswysokr.otf

[JKyle]

Seems like DGIndexNV.exe does not extract attachments to the temp subfolder - where the dgi file is - in CLI.
(All the jobs are done in the subfolder.)
Look. All the others except the attachments are in the subfolder.
It's something you have to ask the DGDecNV developer, not here.
It's not StaxRip but DGIndexNV.exe that does the extraction.
It's clear in the log.
Seems like you didn't try it on CMD like I recommended...

[tormento]

Seems like DGIndexNV.exe does not extract attachments to the temp subfolder - where the dgi file is - in CLI.
Tested and you are right. I'll write the author.

[videoh]

@tormento

Please create a new thread at my forum for this with full details on how to duplicate it. Thank you.

[tormento]

Please create a new thread at my forum for this with full details on how to duplicate it. Thank you.
Done.

[stax76]

2.1.8.0 users can take StaxRip.exe from the Beta cloud folders and auto update nvenc.

Main Menu > Apps > Manage > NVEnc > Tools > Auto Update

2.1.8.1 Beta

- aomenc options rearranged (Dendraspis)
- aomenc supports chunk encoding (Dendraspis, [#368])
- aomenc gets decoder and pipe settings (Dendraspis, [#497])
- aomenc default value for --kf-max-dist changed to 120 (Dendraspis, 44vince44, [#506])
- aomenc default value for --kf-min-dist changed to 120 (Dendraspis, 44vince44, [#506])
- aomenc sets --verbose by default (Dendraspis, 44vince44, [#506])
- Fix frame rates for AviSynth functions (44vince44)
- Replace Rapair16 with Dither_Repair16 for AVS (44vince44)
- Fix AvsResize website address and VS ConvertFormat command (JJKylee)
- aomenc 2-pass stats file extension change to '.fpf' (Dendraspis)
- Fix aomenc --webm parameter (Dendraspis)
- Force mkvmerge to write fps in case of aomenc not using IVF container (Dendraspis)
- Fix shortcut editor key default causing an issue when m is typed (stax76, [#505])
- x265 UI option for '--progress-readframes' on DJATOM builds (Dendraspis)
- nvenc 5.28 (Windows 10 long path and AviSynth Unicode support)

[Atlantis]

Nothing jumps at me that I use, only this
- Fix frame rates for AviSynth functions (44vince44)

Is this a major thing? What happens? I use AviSynth and many filters. If it's nothing, I want to avoid beta.

[JKyle]

Side note:

If you just overwrote StaxRip.exe(2.1.8.1 Beta) and still see the Menu Editor pop up whenever you type 'm' in Code Editor, don't forget to delete the shortcut 'M' assigned to Edit Menu... in the Code Editor right-click menu.

https://i.imgur.com/MdDcUo4.jpg

[stax76]

Nothing jumps at me that I use, only this
- Fix frame rates for AviSynth functions (44vince44)

Is this a major thing? What happens? I use AviSynth and many filters. If it's nothing, I want to avoid beta.

It was changed avs filter profiles. I think the old captions were OK,
what you see is what you get, now you see a float and get num,den.
But what can I do if 44vince44 prefers it. :)


[Frame Rate]
AssumeFPS = AssumeFPS($select:msg:Select a frame rate;23.976|24000, 1001;24;25;29.970|30000, 1001;30;50;59.940|60000, 1001;60;120;144;240$)
AssumeFPS Source File = AssumeFPS(%media_info_video:FrameRate%)
ChangeFPS = ChangeFPS($select:msg:Select a frame rate;23.976|24000, 1001;24;25;29.970|30000, 1001;30;50;59.940|60000, 1001;60;120;144;240$)
ConvertFPS = ConvertFPS($select:msg:Select a frame rate;23.976|24000, 1001;24;25;29.970|30000, 1001;30;50;59.940|60000, 1001;60;120;144;240$)
InterFrame = InterFrame(preset="Medium", tuning="$select:msg:Select the Tuning Preset;Animation;Film;Smooth;Weak$", newNum=$enter_text:Enter the NewNum Value.$, newDen=$enter_text:Enter the NewDen Value$, cores=$enter_text:Enter the Number of Cores You want to use$, overrideAlgo=$select:msg:Which Algorithm Do you want to Use?;Strong Predictions|2;Intelligent|13;Smoothest|23$, GPU=$select:msg:Enable GPU Feature?;True;False$)

[44vince44]

@Atlantis, it's only about proposing the correct standard values for fps ONLY WHEN USING FILTERS AssumeFPS, ChangeFPS and ConvertFPS. If you use those filters, you'll see how it is set now.
E.g:
If you select AssumeFPS -> choose 23.976 then this will create the filter AssumeFPS(24000,1001).
Also some frequencies have been added.
And finally, ChangeFPS was added (it wasn't there before).

@Stax76:
But what can I do if 44vince44 prefers it.

Not really:
Old captions were 24000/1001, value (24000,1001)
Then Dendraspis changed the captions AND THE VALUES to 23.976.
So I kept 23.976 caption because Dendraspis likes it, but we changed the VALUES back to 24000,1001 in order to respect the standards.
Initially, I only wanted to add filter ChangeFPS.
According to Dendraspis, the caption 23.976 is better for newbies. I tend to agree, as long as the real value used is 24000/1001.

[jlw_4049]

Thanks for the work everyone!

Sent from my SM-G986U1 using Tapatalk

[videoh]

Done. Fixed in DGDecNV build 228.

[stax76]

@44vince44

Ah OK, showing both would also be possible:

23.976 (24000/1001)

But it's fine either way.

[Magik Mark]

Guys,

When converting audio to AAC how do you increase the dialogue (midrage). I plan to use qaac and fdkaac.
I find it annoying ac3 dts atmos and other sound technologies have very subtle dialogue. Increasing the volume would also increase the other channels

Thanks

[tormento]

I find it annoying ac3 dts atmos and other sound technologies have very subtle dialogue. Increasing the volume would also increase the other channelsThanks
Usually dialogue is on C channel. Try to use FFMpeg with FDKAAC support and play with channel volume or gain or mixing. My suggestion, however, is not to touch it and adjust player mixer to enhance C channel.

[JKyle]

rigaya released QSVEnc 4.13 (https://github.com/rigaya/QSVEnc/releases/tag/4.13) today with the following important updates:


Add Avisynth Unicode support: QSVEncC will accept avs file in UTF-8. (For legacy avs scripts, new option is added to rerun QSVEncC in ANSI mode. (--process-codepage os))
Add support for Windows 10 long path support.


In order to avoid the exit code: 1 error like this (https://github.com/staxrip/staxrip/issues/519), maybe we need to update StaxRip to write the AVS script in UTF-8 for QSVEnc encoding. (Or... is it already there? :rolleyes:)

[stax76]

@JKyle

Will be fixed in the next build.

Wiki page (https://github.com/staxrip/staxrip/wiki/AviSynth-Unicode-support-on-Windows-10-1903) is updated.

[imhh11]

Hi, thanks for the update stax76.

I'm having an issue with the cutting options. After using the preview window, I can no longer manually edit the frames I want to trim... I can change the number but once I click on ''ok'' it reverts back to the original cutting values.
I don't know when this bug started but I'm upgrading from x64-2.1.3.7-beta and there wasn't this issue.

https://i2.extraimage.info/pix/2021/02/18/568f8a8e9af9397f094e3e783e5b5ef3.jpg

[JKyle]

AFAIK, this is not a bug. It's how StaxRip is designed.
See this issue thread (https://github.com/staxrip/staxrip/issues/511).

[imhh11]

but why is it working with x64-2.1.3.7-beta?
:( it was really useful.

[JKyle]

AFAIK, the internal rendering engine for Preview was replaced with something much, much faster, and in the course of the overhaul, linking the script to Preview was sort of inevitable.
But I don't know about it in detail. Ask @stax76.

BTW, the new approach isn't that complicated compared to direct script input.
You can use shortcuts to shorten the process:
F5(Preview) -> G -> (start frame number) -> Home, G -> (end frame number) -> End.
Repeat these steps for multiple cuts.
Unless your script is so complicated that rendering takes a lot of time, this may come in handy.

[JKyle]

BTW, Subtitle Edit is updated to 3.6.0 (https://github.com/SubtitleEdit/subtitleedit/releases/tag/3.6.0) today with a new program icon and support for a dark theme.

https://i.imgur.com/Eg34Gtc.jpg

[Yups]

In QSVEnc 4.13 rigaya corrected the CQP range in 10 bit mode, for reference: https://github.com/rigaya/QSVEnc/issues/45

8 bit range max: 51
10 bit range max: 63

Currently Staxrip allows CQP up to 51, with QSVEnc 4.13 it should allow CQP values up to 63.

[stax76]

but why is it working with x64-2.1.3.7-beta?

I don't remember anything related and there is nothing found in the changelog.

In case you want to request it on the tracker please describe the use case.


In QSVEnc 4.13 rigaya corrected the CQP range in 10 bit mode

It allows now 63 for both modes, changing it for only one mode would be too much work.


Subtitle Edit is updated to 3.6.0 today with a new program icon and support for a dark theme.

I've updated it. (apparently it's still not High DPI aware)

2.1.8.2 Beta

- New Preview dialog feature 'Create job for each selection' (stax76)
- Fix crash in Preview dialog using 2 instances and shortcut keys (stax76)
- NVEnc options have a bitrate option (Dendraspis)
- Blocking assistant warnings are shown in red with Next button disabled (stax76)
- On systems prior Windows 10 1903 using ANSI characters, avs2pipemod is now used automatically
because DJATOM/Asuna/Patman x265 builds have no working ANSI fallback (stax76)
- All important tools support AviSynth Unicode and Long Path on Windows 10 1903
- vspipe patched with Windows 10 Long Path manifest
- NVEnc 5.29, QSVEnc 4.13, VCEEnc 6.09 (Windows 10 AviSynth Unicode and Long Path)
- ffmpeg N-101189 gcc10.2.0 Patman (Windows 10 AviSynth Unicode and Long Path)
- MP4Box 1.1.0 rev506 gcc10.2 Patman
- Subtitle Edit 3.6.0

[44vince44]

Hi, thanks for the update stax76.

I'm having an issue with the cutting options. After using the preview window, I can no longer manually edit the frames I want to trim... I can change the number but once I click on ''ok'' it reverts back to the original cutting values.
I don't know when this bug started but I'm upgrading from x64-2.1.3.7-beta and there wasn't this issue.

https://i2.extraimage.info/pix/2021/02/18/568f8a8e9af9397f094e3e783e5b5ef3.jpg

This is not a bug, this is a new design. In Staxrip 2.1.3.7 you didn't have the possibility to TRANSPARENTLY work across MANY preview windows at the same time. You could open several preview windows, but some operations would cause inconsistencies.
Now Staxrip allows you to work on many preview windows, with NO inconsistencies at all, and allows to open preview and mpv.net/mpc previews directly from the code editor.
In order not to allow inconsistencies, The preview windows takes priority for the trim function, and not the code editor window.

Now if you tell me why you want to type your trim values, maybe there is a new feature that can help you with that.

[imhh11]

it's all good...
I was manually editing the cutting because I'm encoding using two PC. @JKyle method works fine.
thank you

[stax76]

Enjoy the new look and feel implemented by Dendraspis.

2.1.8.3 Beta

- Introduction of Themes (Dendraspis, testing and appreciated feedback by 44vince44 and JJKylee)
- NVEnc UI options move into new Input/Output section (stax76)
- AVS SMDegrain filter profiles refurbished (44vince44)
- x265 supports --reader-options library for Patman builds (Dendraspis)
- If the startup folder contained Turkish i character, QTGMC and any other avsi file failed to load (stax76)
- x264 10bit, --synth-lib, VapourSynth reader for DJATOM and Patman Mod
- Docs moved to GitHub Wiki, contributions are welcome! (stax76)
- x264 0.161.3048+17 gcc10.2 Patman Mod (improved progress display)
- x265 3.5 RC1+2+23 gcc10.2 Patman Mod (improved progress display)
- xy-VSFilter 3.2.0.802 (10bit support)
- Get-MediaInfo 3.6

[44vince44]

Thanks @Stax76 for the new Beta, especially thanks to @Dendraspis for the outstanding themes implementation, and for @JKyle for the thorough testing !

A note to all users: if you experience problems, please, before reporting, delete or reset your settings so Staxrip can create new fresh settings.

Thank you!

[DavidRyan]

Thanks to all involved for the continued development. I noticed in the changes to the SMDegrain profiles a comment that "Also, Contrasharp=true call does not work anymore due to recent update in RGTools.", does anyone have any background/links to more information on this? Couldn't find it mentioned anywhere else, such as in the RGTools thread.

[thomy21]

Always get the error about 7.1 sound. What do I have to change so that this works again?

Version 2.1.7.7 it worked. now no longer. It is especially not AC3 or EAC3 sound tracks but AAC, something goes wrong with the latest beta probably.

Am happy for any tip

Screenshot:

https://ibb.co/BzxqSzB

[JKyle]

@thomy21,

It's related to this issue thread (https://github.com/staxrip/staxrip/issues/521).
Seems like the first fix was not properly implemented.
I'm asking @stax76 to correct it.

[Atlantis]

Tried the new one. Nice new looks and colors. However the thing that doesn't work with the dark colors is cropping.
For cropping it should be an exception and the crop window should be bright white. For the moment I have switched back to default color.

[JKyle]

@thomy21,

Can you try the hotfix StaxRip.exe in @stax76's Beta archive and see if it resolves your issue?
It seems to be working alright for me.

[jlw_4049]

Thanks for the update <3

Sent from my SM-G986U1 using Tapatalk

[44vince44]

Thanks to all involved for the continued development. I noticed in the changes to the SMDegrain profiles a comment that "Also, Contrasharp=true call does not work anymore due to recent update in RGTools.", does anyone have any background/links to more information on this? Couldn't find it mentioned anywhere else, such as in the RGTools thread.

Can you please provide any experience/knowledge with that.
If you use the SMDegrain Light grain or SMDegrain hard grain, and add inside it the parameter "Contrasharp=true" it will fail, but NOT if you add "Contrasharp = 30" or any number. The difference is that with "Contrasharp=true", RGTools is called, whereas with "Contrasharp=number" LSFMod is called.

Then, browsing in the forums, I don't think I saw a single recent example with Contrasharp=True. Although the official docs give many examples with Constrasharp=True, the discussions in the forums display Contrasharp=false.

This is why, Contrasharp=True was removed.
This is a tool issue. If anyone has reliable information about it, please share it with us.

[stax76]

Tried the new one. Nice new looks and colors. However the thing that doesn't work with the dark colors is cropping.
For cropping it should be an exception and the crop window should be bright white. For the moment I have switched back to default color.

I don't know if white is the best cropping color, maybe create an issue on the tracker, for instance it might be a good idea to force a particular cropping color via option, the tracker is more suitable to discuss such things, Dendraspis does not post here.

[JKyle]

BTW, TIVTC is updated to 1.0.26 (https://github.com/pinterf/TIVTC/releases/tag/v1.0.26).

[thomy21]

@thomy21,

Can you try the hotfix StaxRip.exe in @stax76's Beta archive and see if it resolves your issue?
It seems to be working alright for me.

Thanks, it works now.

[44vince44]

I don't understand what you think is wrong in the crop window @Atlantis. The "active" border is highlighted in a very visible way...

[stax76]

BTW, TIVTC is updated to 1.0.26 (https://github.com/pinterf/TIVTC/releases/tag/v1.0.26).

Will be updated.

[ukmark]

Not specifically StaxRip related, but I do use StaxRip for encoding using Intel's QuickSync.

I have been using an Ice Lake laptop (i7-1065G7) for about a year now and wanted to provide an update. I've re-encoded quite a few of my blu rays (ripping with MakeMKV), and here are my observations.

1. "Fixed-function" CQP encode using HEVC 10-bit is superb. The quality I get with this method is very close to the original. There may be the odd frame here and there where there may be very slight differences in the really fine facial details, but these are few and far between and to my eyes, the differences are difficult to spot and are completely unnoticeable during normal viewing.

2.This method is also very fast - I normally get from 240fps to 340fps (source material dependent) when re-encoding to 1080p from blu ray source. If downscaling to 720p, the speeds can get up to 600fps!!

3. CQP fixed-function file sizes are very reasonable. I generally compare file sizes with the CQP fixed-function method to x265 10-bit CRF 24 encodes. The CQP encodes are usually 5-15% bigger. To me, this is very acceptable - for example a CQP 2.2gb file vs 2gb file with x265 etc. Differences are non-existent during normal viewing.

4. I use the following settings (using QSV hardware as decoder gives a big speed boost and also keeps CPU usage low):-
--avhw --codec hevc --quality best --profile main10 --open-gop --async-depth 4 --fixed-func --cqp 36:36:36 --qp-offset 2:6:8 --output-res 1920x1080

Sometimes I might lower the cqp i,p,b settings to 35 or 34 if I want a little more quality, but I have found these settings give excellent quality with very reasonable file sizes.

Apparently, with Tiger Lake CPU, you can also use b-frames and b-pyramid with CQP fixed-function mode to get even better quality at the same file size (or same quality at lower file sizes). With Ice Lake, b-frames and b-pyramid are disabled for fixed-function, but are available when encoding using GPU execution units - i.e. turn fixed-function off in the settings. I find that I can get approx. the same file size as fixed-function CQP 36 by using CQP 33 or 34 with 16 b-frames and b-pyramid on. However, the encode speed is about 6 times slower.

5. ICQ (Intelligent Constant Quality) mode is kind of broken for 10-bit HEVC. Fixed-function ICQ does work, but the file sizes tend to be 30-50% higher than CQP with no noticeable improvement in quality. Also, changing the ICQ "quality" has no effect (with CQP, changing quality does affect quality and size).

6. CPU usage is very low compared to x265 (always at 100% usage). Actually when using the GPU EU to encode (6x slower than fixed-function, but still getting 45-60fps for 1080p encodes), my CPU drops to 3 or 4% usage!! Crazy but true. When using fixed-function, it can range from 15-40%, but the encode is about 6x faster than using GPU EU and about 12x faster than x265.
You can get a faster speed using GPU EU by setting the quality to "balanced" (the default), from "best". This will raise the CPU usage to around 15%, increase the speed by around 3x to approx 150fps and also increase the file size by around 5-10%. Changing quality to balanced from best also works with fixed-function encoding and increases speed by approx a further 50% (say from around 300fps to 450fps), with the same 5-10% increase in file size. Video quality is identical between best and balanced, but balanced has the 5-10% higher bitrate to compensate for increased encoding speed.

I'm really impressed with QuickSync HEVC 10-bit encoding and no longer use x265. My one caveat is this. I have found that if your source is "low" quality, like a low bit-rate file, then x265 yields significantly better results, but with blu rays, I can't see any purpose in using x265.

[DavidRyan]

Can you please provide any experience/knowledge with that.
If you use the SMDegrain Light grain or SMDegrain hard grain, and add inside it the parameter "Contrasharp=true" it will fail, but NOT if you add "Contrasharp = 30" or any number. The difference is that with "Contrasharp=true", RGTools is called, whereas with "Contrasharp=number" LSFMod is called.

Then, browsing in the forums, I don't think I saw a single recent example with Contrasharp=True. Although the official docs give many examples with Constrasharp=True, the discussions in the forums display Contrasharp=false.

This is why, Contrasharp=True was removed.
This is a tool issue. If anyone has reliable information about it, please share it with us.

Thanks for the response. The only thing I had seen was a reference to contrasharp=true failing with higher bit depth sources due to medianblur2 not being updated to handle them (eg: https://forum.doom9.org/showthread.php?p=1845417#post1845417 ) , but medianblur2 was updated in mid-2020 to handle HBD ( http://avisynth.nl/index.php/MedianBlur2 ) so I guess that would no longer be an issue if staxrip includes the newer version?

So will also be interested if anyone has anything further on this.

[JKyle]

...medianblur2 was updated in mid-2020 to handle HBD ( http://avisynth.nl/index.php/MedianBlur2 )...

As a matter of fact, MedianBlur2 is updated to 1.1 (https://github.com/pinterf/MedianBlur2/releases/tag/1.1) about a month ago.

Thank you for the info.
Let's see if this update changes the game. :)

[JKyle]

@DavidRyan is right.

1. I updated MedianBlur2 to the most recent version.

2. Converted an 8-bit source to 10 bits.

3. Added Contrasharp=true option and force loaded MedianBlur2.dll right before SMDegrain as follows:

https://i.imgur.com/VqMqiMV.jpg

So the script code is as follows:

LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\AVS\DFTTest\dfttest.dll")
Import("D:\Utilities\StaxRip\Apps\Plugins\AVS\Dither\dither.avsi")
LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\AVS\Dither\dither.dll")
Import("D:\Utilities\StaxRip\Apps\Plugins\AVS\NNEDI3\edi_rpow2.avsi")
Import("D:\Utilities\StaxRip\Apps\Plugins\AVS\LSFmod\LSFmod.avsi")
LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\AVS\masktools2\masktools2.dll")
LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\AVS\mvtools2\mvtools2.dll")
LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\AVS\RgTools\RgTools.dll")
Import("D:\Utilities\StaxRip\Apps\Plugins\AVS\Zs_RF_Shared\Zs_RF_Shared.avsi")
Import("D:\Utilities\StaxRip\Apps\Plugins\AVS\SMDegrain\SMDegrain.avsi")
LoadPlugin("D:\Utilities\StaxRip\Settings\Plugins\Dual\DGDecNV\DGDecodeNV.dll")
DGSource("D:\Work\tmp\tst\test_1-audio-track_temp\test_1-audio-track.dgi", deinterlace=0, fieldop=0)
ConvertBits(10)
LoadPlugin("D:\Utilities\StaxRip\Apps\Plugins\AVS\MedianBlur2\MedianBlur2.dll")
SMDegrain(tr=2, thSAD=250, Contrasharp=true)


4. And I see no errors. Here's the Preview window:

https://i.imgur.com/eJbkl3K.jpg

---

So @stax76, updating MedianBlur2 and loading MedianBlur2.dll when SMDegrain is used seems to help solve the incompatibility issue with the Contrasharp=true option.

[44vince44]

Thanks @DavidRyan and @JKyle. Great find !! So do you prefer the presets to include Contrasharp = True ?

[JKyle]

I guess it's more desirable to leave contrasharp as an option so that users can make a choice themselves.
It doesn't matter whether it's false or true as long as MedianBlur2 is loaded.
Let's think of it as a reminder or a placeholder. :)

[44vince44]

Ok so as soon as I see the Medianblur2 update commit, I'll add it to the profiles!