When and Where is INI file read during processing

[psubsee2002]

I am working on a script to automate comskip and I have a question about the INI file and where and when it is read during processing so I can make sure my script does not break anything.

I see that as of Revision 0.79.10 (at least in the donator version), you can put the INI file with the recording, and as of 0.77.59, you can specify the ini file via a command line switch

So if I run comskip like this:

Code: Select all

comskip "C:\MyPath\input.wtv" --ini=mysettings.ini

Will comskip first look for "mysettings.ini" in C:\MyPath\ and if it doesn't find it, it will look in the directory of the exe?

And when are the ini file parameters read? Is everything read up front and stored in memory? Or does comskip go back to the file during processing? Reason I ask this is I am wondering what would happen if the ini were to be accidentally deleted or changed while processing a video. Would it break comskip? Or does it not need the ini after it has started?

[erik]

When a --ini switch is used comskip will look for the specified file.
If no --ini switch is used comskip will first look in the folder where the recording is found. If no ini file found in that folder comskip will look in the folder where comskip.exe is located

[psubsee2002]

Thanks Erik.

What about "when"? Is the *.ini read and stored in memory initially when executed? If the *.ini is changed during execution, will that affect the currently running comskip instance?

Not that I'm planning on doing this, but I have to think about protecting my app from the situation if it were to occur and would cause complications.

[erik]

The ini file is only read once before the start of processing.