LoudnessCorrection Version 227
------------------------------
- I wrote a 'torture test' script that continuously copies files to loudness correction and deletes them while LoudnessCorrection is processing them. This allowed me to find more situations where LoudnessCorrection could be crashed (cases below) by deleting files that are already being processed upon.
- Bugfix: When debug mode is on then LoudnessCorrection changes 'debug-variables_lists_and_dictionaries' filename every 24 hours. The new filename was incorrect.
- Bugfix: When debug mode was on then LoudnessCorrection should have printed all variables read from configfile to logfile 'debug-variables_lists_and_dictionaries' but didn't.
- Bugfix: Some stdout and stderr files used by 'subprocess.Popen' on several subroutines of LoudnessCorrection.py were not defined in the beginning of the subroutine. This sometimes caused these files to be 'undefined' if a audio file was deleted just the right moment in the middle of processing it.
- Bugfix: If email sending failed, then the error message printed in error_log did not have timestamp and other vital information on it.
- Bugfix: If user repeatedly copies the same file to the HotFolder and deletes it, then the file went multiple times in the processing queue.
- Bugfix: If a file was just entering ffmpeg extraction and the user copied the same file to the HotForlder again, then the default dummy file info that is used before we really know file properties overwrote info for the file entering ffmpeg extraction causing a crash. This only happened if timing was just