Great work so far! I have a couple changes I'd like to see:

1. Contrast - Given that the spectrogram is blue, it'll be hard to see colors like blue and cyan (green to an extent) overlaid on it. Can we limit the range of colors to those that are easier to see (e.g warm colors)?
2. Limited classes - If we want to display more than 6 classes, what happens? It would be nice to have set colors (for consistency), then further colors are autogenerated in case someone is working with large amounts of classes.
3. Customization - Along with consistency, can we have the option to specify colors? I'm thinking of a use case where you want to generate multiple spectrograms, but the color ends up different for the same class across multiple (e.g. Screaming Piha is red on one spectrogram, orange on another). There are multiple ways to go about this, but think from a user's perspective how you would want this to be standardized.

Currently, the colors can still change between each function call/different data sets. Is this the desired behavior, or should I make label colors persistent consistent throughout the entire program?

It'd be great if they were consistent throughout the whole program.

Commit 468cb4b is misnamed, that one is a large refactoring that changes spectrogram visualization to take a dataframe as input.

Once these changes are approved, I'll modify the tutorial notebook to properly call the new functions

Here are some examples of test outputs from this code:
The automated labels are always one color because they only have one label, but they are drawn with the same function as the manual labels, so once the models support multiple labels, the graphs will be able to show it.