Fabian Brinkmann

Seems to be a good idea for me. Color coding would make it easier to comprehend, inheriting would make it less prone to errors. What we should consider is that...

Thanks for the quick feedback. I discussed the EmitterDescription with @david-ackermann and we would suggest the following - Have `GLOBAL:EmitterDescription` as an optional attribute (not string variable) - Have `EmitterDescriptions`...

ps. How about using the new release to switch to sharing the same SOFA conventions from https://github.com/pyfar/sofar_conventions by including it as a git submodule? I would also be fine with...

> I agree for 'MS' and 'ES'. However, 'IS' would be just a copy of the attribute EmitterDescription, thus, it does not make much sense. As for 'MS' and 'ES',...

> So, you use "master" for releases, i.e., master is only updated when releasing a new version? This makes releases obsolete, doesn't? And what about tagging - we tag the...

> OK. So, development only in a "development" branch, master branch updated only when releasing. Development branch tagged on the release. A release is a zipped but otherwise the exact...

No, lets wait until the next release and move to develop after that. Would that be fine?

@petibub MultispeakerBRIR uses the FIRE data type and SingleRoomSRIR uses FIR. I don't see how the upgrade can work and would suggest to upgrade to SingleRoomMIMOSRIR instead.

Hi! someone asked me, if I could quickly compute loudness curves for classic performances that's why I was looking into it. I did a very quick hack to return the...

@Rodsis, @AndyP103, @ffont pull request #17 does this , but it seems to do more than changing setup.py. Maybe a simple pull doing only this could be merged quickly to...