Page 14 of 29
Re: Feature Requests
Posted: Wed Jul 17, 2019 5:03 pm
by sparktank
Pretty sure it was me the first time.
Grateful for the efforts put into it.
Re: Feature Requests
Posted: Wed Jul 17, 2019 9:50 pm
by admin
He he, if at first you don't succeed...
Re: Feature Requests
Posted: Fri Jul 26, 2019 11:56 am
by admin
I found the other guy.
viewtopic.php?f=8&t=294
Re: Feature Requests
Posted: Fri Jul 26, 2019 2:55 pm
by Guest
Good things come to those who wait
P.S.
Good memory Don
Re: Feature Requests
Posted: Fri Jul 26, 2019 3:42 pm
by sparktank
Every bit counts!
Thanks for the update. Can't wait to try it out.
Re: Feature Requests
Posted: Sat Jul 27, 2019 10:44 am
by sparktank
The new feature for default save path is fantastic! Thanks a lot.
Re: Feature Requests
Posted: Sat Jul 27, 2019 2:17 pm
by admin
Glad you like it and thanks for pushing me a bit on it.
Resize in crop panel
Posted: Tue Jul 30, 2019 5:54 am
by Guest 2
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
Re: Feature Requests
Posted: Tue Jul 30, 2019 8:36 am
by admin
Request noted. Thank you.
Re: Feature Requests
Posted: Tue Aug 27, 2019 5:02 pm
by Guest
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
Re: Feature Requests
Posted: Tue Aug 27, 2019 9:26 pm
by admin
Very good points and very good questions. Thank you. All is possible and everything is on the table.
Re: Feature Requests
Posted: Tue Sep 10, 2019 9:53 pm
by Bullwinkle
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
Posted: Tue Sep 10, 2019 9:54 pm
by Rocky
Whee!
Re: Feature Requests
Posted: Wed Sep 11, 2019 10:31 pm
by Bullwinkle
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
Posted: Thu Sep 12, 2019 5:00 am
by DJATOM
Not to mention that mainline is avs+ nowadays, as 2.6 being dead for many years.
Re: Feature Requests
Posted: Thu Sep 12, 2019 9:32 am
by Rocky
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
Posted: Thu Sep 12, 2019 3:50 pm
by Guest
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
Re: Feature Requests
Posted: Tue Oct 08, 2019 1:32 pm
by Bullwinkle
avscompat is it possible to be more brain dead (vs not you gonca)? when pride bursts its britches. Be nice.
Re: Feature Requests
Posted: Tue Oct 08, 2019 3:59 pm
by Guest
I might be a little brain dead/damaged myself
A few good drinks do that
Re: Feature Requests
Posted: Sat Nov 02, 2019 11:06 am
by Guest
gonca wrote: ↑Tue Aug 27, 2019 5:02 pm
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
Plus
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
Posted: Sat Nov 02, 2019 11:23 am
by Boulder
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
Posted: Sat Nov 02, 2019 11:39 am
by Guest
Yeah, I know
The ConvertBits or vpy equivalent is a simple truncation of the padding zeroes since final output is 10 bit
Re: Feature Requests
Posted: Sat Nov 02, 2019 11:40 am
by Rocky
gonca wrote: ↑Sat Nov 02, 2019 11:06 am
DGTelecide and DGDecimate working with 16 bit depth would help with the 10 bit encode chain
Have you ever seen a high-bit-depth video that is 3:2 telecined?
Re: Feature Requests
Posted: Sat Nov 02, 2019 11:45 am
by Guest
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
Re: Feature Requests
Posted: Sat Nov 02, 2019 12:12 pm
by Rocky
gonca wrote: ↑Sat Nov 02, 2019 11:45 am
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
And that's a problem because...?