Page 1 of 7

CUDA Suggestions and Talk

Posted: Sat May 20, 2017 8:26 pm
by admin
All your feature requests, suggestions, acute analysis, performance reports, and random thoughts are welcome in this thread.

Re: CUDA Suggestions and Talk

Posted: Sat May 20, 2017 8:35 pm
by gonca
If I may break the ice
Feature request
Resizer and a cropper would be good.
I realize that it can be done (cropping) through the dgi file but sometimes it just works better(?) if it is done after all other processing
Resizing can be done through DGSource but again sometimes it is better after everything else

Re: CUDA Suggestions and Talk

Posted: Sun May 21, 2017 1:10 am
by hydra3333
OK, random thoughts. I know we are already rich :-
What is DGDecodeNV?
Filter Syntax
DGSource()
DGDenoise()
DGSharpen()
DGTelecide()
DGDecimate()
DGBob()
PVBob()
Usage Examples
LoadPlugin() Example
DGSource() Examples
But you know how it is, rich people like to amass wealth.

I deal with a mostly interlaced material, sometimes noisy and blocky. Would it be difficult to create a DGDeblock which handles 576i/p, 720p, 1080i/p ?

DGDenoise is good ... would there be any merit in considering an equivalent to DGDegrain1/2/3 (yes, mvtools) which handles handles both interlaced and progressive ?

Re: CUDA Suggestions and Talk

Posted: Sun May 21, 2017 2:18 am
by Sharc
Here my carpet for visual comparison of 4 bobbers.
(PVBob lags by 1 frame)

http://www.mediafire.com/file/dr11b0pm9 ... st_city.ts

Comments are welcome.

Re: CUDA Suggestions and Talk

Posted: Sun May 21, 2017 7:11 am
by gonca
PVBob looks good, but did I notice a little softness in the two bobbers?
Only really noticeable on a frame by frrame advance

Re: CUDA Suggestions and Talk

Posted: Sun May 21, 2017 8:01 am
by admin
gonca wrote:If I may break the ice
Feature request
Resizer and a cropper would be good.
I realize that it can be done (cropping) through the dgi file but sometimes it just works better(?) if it is done after all other processing
Resizing can be done through DGSource but again sometimes it is better after everything else
Cropping is trivial and doesn't need any CUDA support. You can crop anywhere in your script for essentially zero cost.

Resizing is different of course. Did you have some specific use case in mind, such as increasing vertical size by using an EDI-type algorithm? Do you not see the core resizers as adequate?

Re: CUDA Suggestions and Talk

Posted: Sun May 21, 2017 8:12 am
by admin
hydra3333 wrote: But you know how it is, rich people like to amass wealth.
Poor people too. ;)
I deal with a mostly interlaced material, sometimes noisy and blocky. Would it be difficult to create a DGDeblock which handles 576i/p, 720p, 1080i/p ?
Yes, I want to do a deblocker. You could help by providing typical samples and describing how you process them now. To be honest, I am not very familiar with real-world deblocking use cases and processing.
DGDenoise is good ... would there be any merit in considering an equivalent to DGDegrain1/2/3 (yes, mvtools) which handles handles both interlaced and progressive ?
Possibly. The mv-based stuff is tricky. You'll have to be patient for it. Denoising interlaced can be done with separatefields/denoise/weave, etc.

Re: CUDA Suggestions and Talk

Posted: Sun May 21, 2017 8:13 am
by admin
@Sharc, thanks for the comparison. I'll check it out after my breakfast. You can put a Trim(1,-0) on PVBob to get the frames matching up.

Re: CUDA Suggestions and Talk

Posted: Sun May 21, 2017 8:23 am
by gonca
Resizing is different of course. Did you have some specific use case in mind, such as increasing vertical size by using an EDI-type algorithm? Do you not see the core resizers as adequate?
Core resizers are good but if I have to use PVBob then the cropping and resizer should be used after deinterlacing, I believe

Re: CUDA Suggestions and Talk

Posted: Sun May 21, 2017 9:04 am
by admin
It's just a few simple lines for the VPP config to duplicate what DGSource() can do, so I'll put it on the list. I want to get this one-frame lag thing sorted out first, though.