Feature Requests

Support forum for DGDecNV
User avatar
admin
Site Admin
Posts: 3669
Joined: Thu Sep 09, 2010 3:08 pm

Re: Feature Requests

Post by admin » Fri Mar 23, 2018 8:21 am

If I wanted DGIndexNV to be some kind of frame accurate editor or something, then what I would do is require the project to be saved first and then use DGDecodeNV to render the video, etc. But it's intended to be an indexer, anything else is gravy. So, highly unlikely I'm going to do anything for your request. In any case, it would be so low in priority that it would likely never see the light of day.

Nancy Reagan: "Just say no."

User avatar
admin
Site Admin
Posts: 3669
Joined: Thu Sep 09, 2010 3:08 pm

Re: Feature Requests

Post by admin » Sat Mar 24, 2018 6:41 pm

I'm thinking of unbundling the utility CUDA filters and releasing them as open source dual VS/AVS filters. DGDecodeNV would remain closed and licensed but will be released as dual VS/AVS. Could spur on further CUDA porting. We do need to instantiate pipelines on the GPU to avoid a round trip to and from the GPU for each filter. That's what I mean by CUDASynth. It could be implemented as a VS/AVS filter. ;) :scratch:

gonca
Distinguished Member
Distinguished Member
Posts: 515
Joined: Sun Apr 08, 2012 6:12 pm

Re: Feature Requests

Post by gonca » Sat Mar 24, 2018 6:48 pm

Sounds interesting
Might even make maintenance of the modules easier if they are uncoupled

User avatar
admin
Site Admin
Posts: 3669
Joined: Thu Sep 09, 2010 3:08 pm

Re: Feature Requests

Post by admin » Sat Mar 24, 2018 7:27 pm

Maintenance is not really an issue. It's the pipeline on the GPU that is intriguing. Need a lot of memory up there.

Post Reply