Uh, nope. Haven't tried that. I will, but I have to go out for dinner and watching my grand daughter tonight. ASAP.admin wrote:You're staying in DGIndexNV throughout, not exiting and reopening, right?
[RESOLVED] Problems using AVS Templates with 2052 DGIndex GUI.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
You exit DGIndexNV every time? I haven't tried that yet. Will do.
EDIT: Can't make it fail, no matter what I do.
EDIT: Can't make it fail, no matter what I do.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
In the directory with the templates, do you have any other files, such as .avsi files?
Re: Problems using AVS Templates with 2052 DGIndex GUI.
No. But I think I see the underlying problem. The file *does* change but it is changed to the *previous* selection. Not the current selection.admin wrote:In the directory with the templates, do you have any other files, such as .avsi files?
Meaning, if I select template 1 but have the script from template 3 already in the directory. When I run the index the file time stamp changes but not the content of the file. If I then start DGIndex again and leave the script in the directory, but this time select template 7 and run the index, the file from template 3 will show up with a new time stamp. If I run index again with yet another template the script will be the one from template 7. Always one behind.
I select the template from the DGIndex GUI window before I open the Explorer window to select the video file to index. Should I have been selecting the video file first and *then* the avs template?
Re: Problems using AVS Templates with 2052 DGIndex GUI.
It doesn't matter when you open the file.
Exactly how do you select the template?
I cannot duplicate your report. I select the template by checking the template from the menu drop down, not by going into settings. If you do the same you could select from the drop down and then go into settings and see if the right file is shown before doing save project.
There is nothing in the code that could remember your previous setting.
Exactly how do you select the template?
I cannot duplicate your report. I select the template by checking the template from the menu drop down, not by going into settings. If you do the same you could select from the drop down and then go into settings and see if the right file is shown before doing save project.
There is nothing in the code that could remember your previous setting.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Then there's only one answer, it's my system. This is not the first time my machine and yours have differed in how the GUI performs. When I was using Windows 8 the GUI would crash and you couldn't replicate the problem. I remember you told me it was Microsoft's compiler of the time and MS wouldn't release a fix. With Win 10 everything changed and the GUI worked, until this. Thank goodness it's not a show stopper. All I have to do is delete the script first, then index. For the heck-of-it I'm going to install the software on my wife's pristine new Win 10 home-office system and see what happens. Thank you for your efforts, at least one bug was real.admin wrote:There is nothing in the code that could remember your previous setting.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
If you have the time I'd like you to try what I suggested in my last post. Choose the template and then go into settings and verify that the file and directory are correct in there before doing save project. If so, then that is what is used when the save project ends and the AVS file is created. There is no memory of past settings. Also, check that your methodology to identify the used template is correct. I have this in each of my templates:
# template7.avs
etc.
Meanwhile I will perform an exhaustive code review today with your symptoms in mind.
Thanks for your patience and for bringing this to light.
# template7.avs
etc.
Meanwhile I will perform an exhaustive code review today with your symptoms in mind.
Thanks for your patience and for bringing this to light.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Thank you for the time spent.admin wrote:If you have the time I'd like you to try what I suggested in my last post. Choose the template and then go into settings and verify that the file and directory are correct in there before doing save project. If so, then that is what is used when the save project ends and the AVS file is created. There is no memory of past settings. Also, check that your methodology to identify the used template is correct. I have this in each of my templates:
# template7.avs
etc.
Meanwhile I will perform an exhaustive code review today with your symptoms in mind.
Thanks for your patience and for bringing this to light.
Yes, I have done the above and verified I was selecting the correct template. But one more thing. I looked at the DGIndexNV.ini file. What I saw was the "AVS_Template_File=720p AVS Script.avs" parameter didn't change to the template I currently chose *until* I closed and reopened DGIndexNV.exe. That is, when I chose template "1080p AVS Script.avs" I still got "720p AVS Script.avs". The ini file didn't change until I closed and reopened DGIndexNV. Then the parameter changed to "1080p AVS Script.avs". And when I indexed the video file the AVS script changed to
"1080p AVS Script.avs". Could this be the "memory" you were looking for? This behavior matches the "one-behind" problem of not changing the file until the next try at indexing.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Nice try but no cigar. Sure the last one is stored in the INI file when you exit. But that setting is read back into the template settings only when DGIndexNV starts and is not used again thereafter. So if you start DGIndexNV and then select a new template, the memory of it is overwritten in DGIndexNV memory (i.e., the file field of the settings dialog) and the newly selected template is used for the following save project. Bottom line: if you select a template in DGIndexNV and then do save project, that template setting is used, being read from the field in the settings dialog.
You use only the GUI and not the CLI, right?
Meanwhile let me cook up a way to give you a debug load that will help us. I can pop up a dialog giving the path and file that is being opened as the template at the end of save project, for example.
You use only the GUI and not the CLI, right?
Meanwhile let me cook up a way to give you a debug load that will help us. I can pop up a dialog giving the path and file that is being opened as the template at the end of save project, for example.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
OK.admin wrote:Hmm, I found something strange that might affect this. Standby...
Re: Problems using AVS Templates with 2052 DGIndex GUI.
False alarm, it is OK and works as I described.
I will make a debug build for you. Meanwhile, can you post your full INI file?
I will make a debug build for you. Meanwhile, can you post your full INI file?
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Really need to see that INI file and for you to tell me you don't use CLI.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
People always go away just when I need them.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Sorry, went out to dinner again. No, I'm not using the CLI in this case.admin wrote:People always go away just when I need them.
Here's the ini file:
Code: Select all
Version=DGIndexNV 2052
Window_Position=246,168
Info_Window_Position=892,168
Process_Priority=2
Playback_Speed=3
AVS_Template_Folder=C:\HQ Encoder NV\AVS Script Templates
AVS_Template_File=720p AVS Script.avs
AVS_Enable_Template=1
AVS_Overwrite=1
Full_Path_In_Files=1
MRUList[0]=C:\Input Files\Input_File.h264
MRUList[1]=C:\Input Files\Input_File.dgi
MRUList[2]=C:\Input Files\Input_File.avs
MRUList[3]=C:\MKVideo Files\Input_Video_File.h264
Enable_Info_Log=0
Loop_Playback=0
AVC_Extension=264
MPG_Extension=m2v
VC1_Extension=vc1
HEVC_Extension=265
Deinterlace=0
UsePF=0
AlwaysCrop=1
UseD3D=0
Snapped=1
ResponseOnAudioMismatch=0
Enable_Audio_Demux=1
CUDA_Device=255
Decode_Modes=0,0,0,0
Full_Info=1
Bare_Demux=0
Disable_Encrypted_Audio_Warning=0
Fine_Cropping=0
Force_Zoom=0
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Thanks, gaak. Checking some things and then will make a debug build for you. I want to get to the bottom of this!
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Aha, I just duplicated the problem! Should be easy to debug now.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Jolly good. Please re-download 2052 DGIndexNV.exe and re-test. It should be fixed.
I had a bad code leg for the case where you don't use the default template folder but instead define your own.
I had a bad code leg for the case where you don't use the default template folder but instead define your own.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Wonderful! I was beginning to doubt my sanity.admin wrote:Aha, I just duplicated the problem! Should be easy to debug now.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Check my post just above yours.
I often doubt my sanity. It keeps me sane.
I often doubt my sanity. It keeps me sane.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Thank you! Will try it now.admin wrote:Check my post just above yours.
I often doubt my sanity. It keeps me sane.
Re: Problems using AVS Templates with 2052 DGIndex GUI.
Yes! It's alive and bug-free! Thanks so much!
Re: Problems using AVS Templates with 2052 DGIndex GUI.
My pleasure, Sir. Thanks once again for your assistance. I have credited you in the Binaries Notification post that I made.