Add exeption handling to create_database function
The current implementation of the create_database function breaks if an exception is raised when it tries to load an audio segment or if it can't write it to the database.
This means that, if you have 10,000 segments and somewhere in the middle there's one single segment that raises an exception (because the audio file was corrupted, for example), the function exits there and the rest of the segments won't be computed or written to the database, even if they are perfectly fine.
It would be nice to add some exception handling to the for loop that loads and writes audio segments to the database. There could be an argument to control the desired behavior: halt when there's a problem or skip the problematic segment and continue to the next. The latter could even return a log of the segments (filename, start, end) that were skipped.