This EULA grants you the right to use FMOD Engine [...] subject to the following:
i. FMOD Engine is integrated and redistributed in a software application (Product) only;
ii. FMOD Engine is not distributed as part of a game engine or tool set;
[...]
This EULA grants you the right to use the FMOD SDK [...] subject to the following:
i. FMOD SDK is used in conjunction with development of a software application using the FMOD Engine.
It is my belief that fmod-rs is not redistributing FMOD Engine. fmod-rs is built from (and bundles) the FMOD SDK, but leaves acquisition of the FMOD Engine to the downstream user.
However, before publishing, I would like to clear this interpretation with Firelight Technologies. I am not a lawyer, etc., and I don't want to get myself or downstream into legal trouble.
The main point of potential contention is that fmod-rs is, technically, developed as a library with just the FMOD SDK and not in conjunction with an application using the FMOD Engine. Thankfully, that only impacts (distribution of) fmod-rs; an application utilizing fmod-rs clearly meets this requirement. (And I am developing fmod-rs in conjunction with an application, so it's just the separate distribution which is potentially questionable.)
This EULA grants you the right to use FMOD example code [...] subject to the following:
i. Media files included in FMOD examples, including wav, ogg, mp3, fsb and bank files, are not to be redistributed.
The ported examples do not contain the media files, leaving acquisition of the media files to the end user.
Relevant excerpts from the FMOD EULA:
It is my belief that fmod-rs is not redistributing FMOD Engine. fmod-rs is built from (and bundles) the FMOD SDK, but leaves acquisition of the FMOD Engine to the downstream user.
However, before publishing, I would like to clear this interpretation with Firelight Technologies. I am not a lawyer, etc., and I don't want to get myself or downstream into legal trouble.
The main point of potential contention is that fmod-rs is, technically, developed as a library with just the FMOD SDK and not in conjunction with an application using the FMOD Engine. Thankfully, that only impacts (distribution of) fmod-rs; an application utilizing fmod-rs clearly meets this requirement. (And I am developing fmod-rs in conjunction with an application, so it's just the separate distribution which is potentially questionable.)
The ported examples do not contain the media files, leaving acquisition of the media files to the end user.