Thanks for your reply. I'm only really interested in making the encoding process simpler, not the dumping / pre-encoding (Subtitle config, etc). Nothing I am proposing is particularly hard, but it requires work from people who can make a good GUI, and considering I mainly do web backend engines, I don't think I am that guy. FerretFaucet seems to be interested in helping with that area, but I think he's a bit preoccupied right now. The main goals are:
- Make it easy to create / load config that stores the information used for encoding. This makes it easy to hold onto our encoding information for future use in case something goes wrong. It's pretty silly to save an .avs for every encode.
- Make it easy to create / load a queue of processes. For example, I should be able to tell it to create an HD, SD, and 512KB from a particular config file in that order. This way, I can set up fifty dumps for encoding, let it run over a vacation, and come back to see them all done.
- Encode based on that queue using a .avs template and a library of files bundled with the installer. Once we have the other steps done and make a prototype using the script in this topic, I suggest that the experts take a look at the template and give their feedback. I'm not writing this program because I'm good at encoding; I'm writing this program because everyone should be using the best script available, and I know we have talented people here to help create this script.
Let me know what you could help with.
Now, I'll encode the SD if absolutely necessary, but I'd prefer if NitroGenesis could have me diagnose the issue with his desync. Or, if he's not available to do that, perhaps laranja's first encode could be his own publication!
Will keep in contact with NitroGenesis regarding his encode. He and FerretFaucet are using my script, so this run will inevitably have awesome encodes. =P
Optimized. Will publish as soon as my encode finishes unless someone has a better shot. What do you think?