Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
31st August 2016, 04:42 | #63 | Link |
Registered User
Join Date: Feb 2004
Location: NYC
Posts: 124
|
With latest avs+ mt r2172 & your nnedi3 r26, using this yields a 1.5fps increase using this script on a (for now) stock 4770K. Sometimes the encode appears to halt entirely but I'm not sure if this is an avs+ issue or a ResampleMT/nnedi3 issue.
|
2nd September 2016, 17:22 | #64 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,317
|
New version, see first post.
I've added several parameter to allow to tune the created threadpool. I've made several testbench, and set the default settings correspond to the best result i have on my PC. But, it doesn't mean it will be also what produce the best result on others PC, so, the parameters added will allow to eventualy each one tune according his hardware configuration. Check the ReadMe file for precise information. Last edited by jpsdr; 2nd September 2016 at 17:25. |
10th October 2016, 17:38 | #65 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
I did edit to ResizeX to make it work with this plugin
edit : add edi_rpow2_v1.0.zip and maa2 new edit ResizeX and edi_rpow2 will work in new avs+ colour format edit: another ResizeX edit here https://forum.doom9.org/showpost.php...45&postcount=5 and use it with this https://pastebin.com/8kcg2MtJ edi_rpow2
__________________
See My Avisynth Stuff Last edited by real.finder; 3rd November 2017 at 19:22. |
7th December 2016, 20:10 | #68 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
I wonder how this filter work, it's depends on avs Resizers or have an edit of them?
I ask because I didn't see any mention on what colour format that this filter supports
__________________
See My Avisynth Stuff |
8th December 2016, 11:28 | #69 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,317
|
It uses the code of the internal avs+ resamplers. About supported format, it supports all the formats supported by avs+ at the time the filter has been build.
I'm working on the new version to support the new formats, but for now it crashes in both avisynth and avs+ and i don't had time to investigate futher. But i'll probably be able to resume work on it soon. |
8th December 2016, 15:50 | #70 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
why not try using avstp? and can z.lib make it faster?
__________________
See My Avisynth Stuff |
|
9th December 2016, 10:45 | #71 | Link | ||
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,317
|
Quote:
As there is only one threadpool shared instead of several (before, one was created for each instance filter) => result in slowdown when shared resources required. For optimal, i suggest if you're also prefetching to reduce the number of threads and make tests. The values i suggest for testing are first threads=1, and second threads=CPU/2. And if you're using ResampleMT within NNEDI3, don't forget also to put the value on the threads_rs parameter. Not interested, and using an external dll for the threadpool make it even slower (i've tested with my threadpool). Quote:
|
||
18th January 2017, 01:46 | #75 | Link |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Code:
range - This parameter specify the range the output video data has to comply with. Limited range is 16-235 for Y, 16-240 for U/V. Full range is 0-255 for all planes. Alpha channel is not affected by this paramter, it's always full range. Values are adjusted according bit depth of course. This parameter has no effect for float datas. 0 : Automatic mode. If video is YUV mode is limited range, if video is RGB mode is full range, if video is greyscale (Y/Y8) mode is Y limited range. 1 : Force full range whatever the video is. 2 : Force limited Y range for greyscale video (Y/Y8), limited range for YUV video, no effect for RGB video. 3 : Force limited U/V range for greyscale video (Y/Y8), limited range for YUV video, no effect for RGB video. Default: 0
__________________
See My Avisynth Stuff |
18th January 2017, 09:52 | #76 | Link |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,317
|
I don't agree, standard YUV is not full range, so it results that nnedi and resize can produce incorrect value output. On the oposite, someone who want to work with standard value has to put a limiter...?
No, that's not a proper behavior for me, it's the contrary, you have to specify "something" when you want to work outside standard values. |
18th January 2017, 18:09 | #77 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
edit: and scripts that did TV to PC range internally for some specific purpose like SMDegrain will fall too, so default should be 1 everywhere, that reminds me of keep_tv_range bool in flash3kyuu_deband, it's false by default
__________________
See My Avisynth Stuff Last edited by real.finder; 18th January 2017 at 18:26. |
|
18th January 2017, 19:25 | #78 | Link | |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,317
|
Quote:
A script/plugin can do whatever it wants internaly, it have to put back correct levels on its output, otherwise, it screws you things without telling you. Yes, it should be the oposite, when i use it on YUV data, i always have to put it to true. |
|
18th January 2017, 19:33 | #79 | Link | |
Registered User
Join Date: Jan 2012
Location: Mesopotamia
Posts: 2,587
|
Quote:
anyway, I will stick with the older versions, thank you for the old change efforts it was cool
__________________
See My Avisynth Stuff |
|
18th January 2017, 19:51 | #80 | Link | |
Registered User
Join Date: Oct 2002
Location: France
Posts: 2,317
|
Quote:
Of course, if a metadata tag existed, it would have been perfect... |
|
|
|