Brian McFee

> I get a series of errors for some files (eg, the famous SALAMI_114) and it doesn't really include any multisegment annotations for the ones that fail. That's correct. The...

O_o really? do you have the most recent version of the notebook?

> So, how come the files you uploaded and fail contain multi_segment annotations Derp, sorry, I was unclear before. Failure is determined on an annotator-basis, not track basis. I still...

> Yeah, I get that. But the notebook doesn't do that, right? How did you > compute that in your last commit? Doesn't it? My last commit was done just...

... if you're already in the process of automating this step, how about taking a crack at the salami annotations as well? I tried running the notebook over them, and...

This is a little subtle, but I think the behavior here is intended at least for time-like axes. From the code excerpt you cite, we do add physical units when...

> You guessed it: this came out while looking into #1746, in the context of visualizing long-duration bioacoustic signals. > I'd expect `4:33` to be labeled as `Time (m)`. >...

The documentation does explicitly say in the first line: https://github.com/librosa/librosa/blob/8ba6d8d93276c2ee1439fb006d8869ef525b8c54/librosa/core/notation.py#L607-L609 Is there some way this could be made more clear? The general idea in the API here is, as you've...

I've been mulling this one over a bit, and considering the option of adding a shortcut to implement the degree slicing logic to return only the in-key notes. Having thought...

Taking the :+1: as endorsement to not expand functionality, but instead add documentation. Putting it on the 0.11 docket.