Feature Requests
Re: Feature Requests
You can read as well as me, and vice versa. What do you see that there that intrigues you?
Re: Feature Requests
KNLMeansCL (Nvidia OpenCL) + DGDecIM = Works on both Win10 and Win8.1
KNLMeansCL (Nvidia OpenCL) + DGDecNV = Freezes on Win10 but works on Win8.1
So I had hoped that there was something new in the SDK that could help on my problem.
KNLMeansCL (Nvidia OpenCL) + DGDecNV = Freezes on Win10 but works on Win8.1
So I had hoped that there was something new in the SDK that could help on my problem.
Re: Feature Requests
I don't see any mention of OpenCL or interoperation of OpenCL with NVCUVID.
Re: Feature Requests
What about an email notification/subscription for any updates to the binaries?
Be it silent or new stable.
Be it silent or new stable.
Re: Feature Requests
Would this work: I have a single thread that I post to when I upload something. You subscribe to the thread and the forum automatically notifies you.
Re: Feature Requests
That would work!
Re: Feature Requests
Subbed. Thanks a lot!
Re: Feature Requests
You're welcome, and thank you for the suggestion.
- Aleron Ives
- Posts: 126
- Joined: Fri May 31, 2013 8:36 pm
Re: Feature Requests
You might want to just lock the thread to prevent people from posting in it and triggering e-mail notifications for all of the subscribers. Administrators and moderators can usually post in locked threads on phpBB forums, while regular users cannot (so you could post updates without anyone else causing interference). That is assuming, though, that users can subscribe to locked threads on this version of phpBB.
Re: Feature Requests
That's an interesting idea. I'll lock it now. Then perhaps you can help by unsubscribing and then trying to resubscribe, and let me know the result. Thanks.
- Aleron Ives
- Posts: 126
- Joined: Fri May 31, 2013 8:36 pm
Re: Feature Requests
The subscription link still works for me, and the binaries update notification thread now appears in my UCP in my list of subscriptions. As for you, you should find that the "LOCKED" image is actually a hyperlink that allows you to post in the thread, whereas for us peons, the link directs us to a page saying that we're not allowed to post in that thread.
Re: Feature Requests
OK, sounds good, Aleron. Let's see what happens on the next upload. Thanks again for the suggestion.
- Aleron Ives
- Posts: 126
- Joined: Fri May 31, 2013 8:36 pm
Re: Feature Requests
FYI, I just got an e-mail that you posted in the binaries update thread, so all seems well on the notification-of-posts-in-locked-threads front.
Re: Feature Requests
Great. Thanks, Aleron.
Re: Feature Requests
Sure, I can do that. Give me a few days to get some time for it.
DGinfo()
Is there any chance to call "debug=true".. um. 'outside' of "dgsource()" call?
Cropping with DGsource must be mod4, in rare circumstances, conversion to yv24 to use odd crops must be taken.
Once those measures are taken, using 'debug=true' is cropped out as well.
Maybe a DGinfo() for such occurances?
Cropping with DGsource must be mod4, in rare circumstances, conversion to yv24 to use odd crops must be taken.
Once those measures are taken, using 'debug=true' is cropped out as well.
Maybe a DGinfo() for such occurances?
Re: Feature Requests
Hi sparktank.
Oy, I wasn't aware that cropping cut off the debug output. Let me look into solutions for that. If the debug info was located within the cropped area, would that be enough for you?
Oy, I wasn't aware that cropping cut off the debug output. Let me look into solutions for that. If the debug info was located within the cropped area, would that be enough for you?
Re: Feature Requests
I'll trust your decision.
Anything that wouldn't critically increase your taskload.
Anything that wouldn't critically increase your taskload.
Re: Feature Requests
My kind of user.sparktank wrote:Anything that wouldn't critically increase your taskload.
Re: Feature Requests
OK, I tried to duplicate this but failed. I tried both cropping in DGI and cropping using the DGDecodeNV parameters. So it seems I do not understand what you are doing. Please provide a step-by-step process to see your issue. Thank you.
Re: Feature Requests
Code: Select all
DGsource ("movie.mkv", debug=true, crop_b=148, crop_t=140) #crop is mod4
Code: Select all
DGsource ("movie.mkv", debug=true) #do not crop here since we're not doing mod4
ConvertToYV24 (matrix="Rec709") #to make crops that are mod1
## crop examples
# for wallpapers and image_processing, not critical video_processing but where all picture data can be used
#Crop (0, 139, 0, -138) # top crop is mod1 # resulting height=mod1
#for movies that are 1.85:1
#Crop (0, 21, 0, -21) # top+bottom crop is mod1 # resulting height=mod2
Just for exapmle, clip with black bars to keep debug on clean area:
DGSource("F:\Clips\Inception\Inception CH1.dgi", debug=true)
now same screenshot with mod1 crops to achieve 1.85:1 resolution (for sake of test):
DGSource("F:\Clips\Inception\Inception CH1.dgi", debug=true)
ConvertToYV24 (matrix="Rec709")
Crop(0, 21, -0, -21)
The bigger the Crop() values, the more the debug info gets cropped.
Re: Feature Requests
You're cropping after DGSource() in your script and then expecting the debug info to be repositioned or something? Tell me I have missed something, because there is no way for DGSource() to know you have a crop later in the script.
Best thing I can think of is to comment out your crop line when you need to see the debug ouput. Do you have another idea?
Best thing I can think of is to comment out your crop line when you need to see the debug ouput. Do you have another idea?
Re: Feature Requests
Here's what I'm thinking of: Add an INI file option called Force_Zoom. It can have values 0 (default), 1, 2, or 4. If it is zero the current behavior is used, i.e., after a file is loaded a reasonable zoom factor is automatically chosen. Otherwise the specified value is forced, i.e., Force_Zoom = 2 forces zoom to be 1/2. This allows me to have my favorite auto zoom mode but allows you to force a zoom if you want to. In no case would the GUI selected Zoom be saved in the INI file; it would always be controlled by Force_Zoom. My reasoning for the auto mode is that if I load a UHD video on a 1920x1080 display I don't want to have to go into Video/Zoom to make it all visible.Groucho2004 wrote:Don, any chance you could make DGIndexNV remember the last zoom factor, i.e. add an INI option?
Unless you refute that idea I'll go with it.
Re: Feature Requests
I was hoping maybe for something like a separate call for the info at any time later.admin wrote:Do you have another idea?
Similar to Info() and FFInfo() for the frame information.