UltraTV
30th October 2008, 01:13
We've been in the process of integrating DGIndex into our automated transcoding system. Here are some suggestions to improve the software for automated use:
- Command line parsing causes issues when, for example, an automatically generated output filename contains characters with -SD. I think this is the only flag that's read between brackets, but this cost us a few hours diagnosing and correcting. It would be ideal if flags were not recognized in between the brackets. The Delimiter could instead be read outside of the brackets.
- When -HIDE mode is invoked, GUI error messages shouldn't pop up. Instead, it would be more helpful if the error messages were hidden and an error level was returned, similar to x264 or one of the other tools we're using.
I'll keep updating this as we continue to integrate DGIndex into our toolset. Making DGIndex into a more command-line centric utility would be a huge boon to our integration efforts. Having said that, it's a brilliant utility and we owe a great deal of gratitude to the authors.
- Command line parsing causes issues when, for example, an automatically generated output filename contains characters with -SD. I think this is the only flag that's read between brackets, but this cost us a few hours diagnosing and correcting. It would be ideal if flags were not recognized in between the brackets. The Delimiter could instead be read outside of the brackets.
- When -HIDE mode is invoked, GUI error messages shouldn't pop up. Instead, it would be more helpful if the error messages were hidden and an error level was returned, similar to x264 or one of the other tools we're using.
I'll keep updating this as we continue to integrate DGIndex into our toolset. Making DGIndex into a more command-line centric utility would be a huge boon to our integration efforts. Having said that, it's a brilliant utility and we owe a great deal of gratitude to the authors.