Said it on GitHub, I'll say it again here: Didn't get around to test it yet, but this looks
really good. Keep it up! I'm sure this will come in handy for a lot of users.
importjingles wrote:
Things I'm unsure about are:
* Sensible way to report exceptions back to Duality. Currently I'm just letting them fly (I haven't read the Duality importer code much yet).
In general, if your code crashes in an
unexpected way, Duality will try to catch it and report back to the users, which will then come complaining to you, so you can fix the underlying problem.

If your code fails in an
expected way, you should generally try to fail gracefully,
but importers are a special case: Duality actually watches each of them closely and
handles their exceptions as an expected failure case, which is logged and later
reported to the user. So you can actually throw an Exception there and it will be fine. If you expect something bad to happen at some point out of your control, it's still a good thing to detect it first and do something about it yourself though. Prefer failing explicitly.
importjingles wrote:
Whether it can be released under MIT license (considering libsox is LGPL).
I
think, as long as you're only using its binaries, but do not include any of its source code, this should be fine - but this legal stuff really isn't my specialty either. RockyTV's link looks quite good and seems to have a similar gist.
Moving this to "Projects".