Rolling back changes in load audio
I was unhappy with some of the changes that had been made to the load_audio method in this recent merge which I did not have the opportunity to review, so I have created this new branch where the changes are rolled back.
In particular, I was unhappy with the new interface of the load_audio method which requires the user to specify the representation class when the data is loaded. This is in my view not a great solution since it would allow the user to specify a class inconsistent with the data that is being loaded. For example, the data saved to the database may be a Waveform in which case it makes little sense to specify the class as MagSpectrogram.
The idea behind the design of the write and load functions in the database_interface module is that the presentation information (class as well as parameters) gets saved to the database along with the data, so that the objects can be recreated automatically with all the correct properties.
If you think this is a bad idea, I'd like to understand why. Thanks!