Feature Requests
Re: Feature Requests
Pretty sure it was me the first time.
Grateful for the efforts put into it.
Grateful for the efforts put into it.
Re: Feature Requests
He he, if at first you don't succeed...
Re: Feature Requests
Good things come to those who wait
P.S.
Good memory Don
P.S.
Good memory Don
Re: Feature Requests
Every bit counts!
Thanks for the update. Can't wait to try it out.
Thanks for the update. Can't wait to try it out.
Re: Feature Requests
The new feature for default save path is fantastic! Thanks a lot.
Re: Feature Requests
Glad you like it and thanks for pushing me a bit on it.
Resize in crop panel
Can I ask you the feasibility to add a small slider, radio or whatever to pass rw and rh parameters from crop (& resize at this point) panel to AviSynth?
I find useful when you want to resize from 4k to 1080p or 720p for the vertical resolution height, the most commonly cropped.
Something like 1, 1/2 and 1/4 would me more than enought.
The masterpiece would be a slider aware of mod of resized resolution
I find useful when you want to resize from 4k to 1080p or 720p for the vertical resolution height, the most commonly cropped.
Something like 1, 1/2 and 1/4 would me more than enought.
The masterpiece would be a slider aware of mod of resized resolution
Re: Feature Requests
Request noted. Thank you.
Re: Feature Requests
Seeing as how the option fulldepth= is now gone, would it be possible to have an option to deliver P016 all the time.
Use case
8 bit video is encoded at higher bit rates (10) to avoid banding in final result.
It actually saves only one line in script "ConvertBits(16)" but it would be nice to have, specially since your filters need either 16 or 8 bit inputs.
For 10 bit encode
8 bit input
ConvertBits(16)
Use your filters to preprocess
ConvertBits(10)
Encode
Use case
8 bit video is encoded at higher bit rates (10) to avoid banding in final result.
It actually saves only one line in script "ConvertBits(16)" but it would be nice to have, specially since your filters need either 16 or 8 bit inputs.
For 10 bit encode
8 bit input
ConvertBits(16)
Use your filters to preprocess
ConvertBits(10)
Encode
Re: Feature Requests
Very good points and very good questions. Thank you. All is possible and everything is on the table.
- Bullwinkle
- Posts: 338
- Joined: Thu Sep 05, 2019 6:37 pm
Re: Feature Requests
Hello lovers of all that is rational and correct. Stuck in the handcuffs of Zoom. Randomness is beautiful and arbitrary window size is The Beauty. Throw off the handcuffs! And so confused specifying crop into script via dgindexnv but not resize who pointed that out? Guest 2. A fine collection of pixels he is for one to contemplate. But who are we to speculate?
Re: Feature Requests
Whee!
- Bullwinkle
- Posts: 338
- Joined: Thu Sep 05, 2019 6:37 pm
Re: Feature Requests
Is synthesis the antithesis of Randomness? You could think about it. Here we have the definitive analysis. cudasynth must be absorbed into the mainline. We all die but try to postpone it. Now watch me.
Re: Feature Requests
Not to mention that mainline is avs+ nowadays, as 2.6 being dead for many years.
PC: RTX 2070 | Ryzen R9 5950X (no OC) | 64 GB RAM
Notebook: RTX 4060 | Ryzen R9 7945HX | 32 GB RAM
Notebook: RTX 4060 | Ryzen R9 7945HX | 32 GB RAM
Re: Feature Requests
I think by "mainline" Bullwinkle didn't mean Avisynth but meant the official DGDecodeNV (i.e., not have a separate CUDASynth package). Your point is well taken and further integration into Avisynth+ itself remains under study.
Re: Feature Requests
Absorbing Cudasynth into the DGTools mainline would be awesome.
With the template feature creating the scripts, using multiple filters would be quicker.
Might just need an updated avscompat (for vpy) to get closer to perfection, hint, hint
With the template feature creating the scripts, using multiple filters would be quicker.
Might just need an updated avscompat (for vpy) to get closer to perfection, hint, hint
- Bullwinkle
- Posts: 338
- Joined: Thu Sep 05, 2019 6:37 pm
Re: Feature Requests
avscompat is it possible to be more brain dead (vs not you gonca)? when pride bursts its britches. Be nice.
Re: Feature Requests
I might be a little brain dead/damaged myself
A few good drinks do that
A few good drinks do that
Re: Feature Requests
Plusgonca wrote: ↑Tue Aug 27, 2019 5:02 pmSeeing as how the option fulldepth= is now gone, would it be possible to have an option to deliver P016 all the time.
Use case
8 bit video is encoded at higher bit rates (10) to avoid banding in final result.
It actually saves only one line in script "ConvertBits(16)" but it would be nice to have, specially since your filters need either 16 or 8 bit inputs.
For 10 bit encode
8 bit input
ConvertBits(16)
Use your filters to preprocess
ConvertBits(10)
Encode
DGTelecide and DGDecimate working with 16 bit depth would help with the 10 bit encode chain
Just asking, I know that you are busy on DGDemux
Re: Feature Requests
By the way, you'll want to ditch the last ConvertBits. Both x264 and x265 will happily accept 16-bit input and convert down to the final bitdepth (x265 has the parameter --dither to enable HQ dithering). If I'm not mistaken, they both work internally in 16 bits anyway.
Re: Feature Requests
Yeah, I know
The ConvertBits or vpy equivalent is a simple truncation of the padding zeroes since final output is 10 bit
The ConvertBits or vpy equivalent is a simple truncation of the padding zeroes since final output is 10 bit
Re: Feature Requests
No, but if I want an 8 bit file preprocessed and encoded in 10 bit (DVD and some BD, imported) right now the preprocessing must be done in 8 bit and then converted to 10 bit for encoding