Thanks for your comments. It sounds like we need to clarify our position on 3rd party integrations.
We are and have been encouraging and supportive of 3rd party integrations, developed by our community or the communities of 3rd party apps like Foundry VTT.
That is why we implemented the 3rd party API in the genre players, and allow access to the REST and websocket APIs for the online player master interface, and allow the downloading of remote control links in a CSV file from the online player, ready for import into 3rd party systems. Much of this was implemented in direct response to requests by the developers of 3rd party integrations.
All of this was intended to support 3rd parties wanting to seamlessly control Syrinscape from directly within a 3rd party system. This has been done successfully in several Fantasy Grounds extensions, and from what I saw also at least two Foundry VTT community members who are working on integrations. This is something we are excited to see and would love to support.
What we have not built support for, and are not currently considering, and what was recently requested, is access to the online player app source code, so that the audio engine can be completely recreated directly within the Foundry VTT extension.
The player app contains the audio engine that is the heart of Syrinscape. It is what transforms a list of samples into a dynamic non-repeating soundscape.
As I’m sure you can appreciate, this type of deep integration could not happen without first addressing a number of significant issues, including but not limited to:
Protection of our intellectual property, both the audio engine itself and access to the massive library of original content that we have created.
Audio consistency. Our content would need to sound the same. We cannot simply provide a list of sample URLs and a playlist to any audio player. Samples are positioned dynamically and move in 3D space, effects are applied, and we do make changes to the data format from time to time.
Development capacity. We already support 4 player apps (3 genres plus online) on 5 platforms. Given the aforementioned issues, any new player app really would need to be the exact same codebase, and tied into our release process.
Business model. A LOT of effort (time and money spent) over many years has gone into creating our apps, making remote online play possible, allowing users to create their own soundsets, and creating a HUGE library of original content.
I’m sure you can appreciate this would be no small undertaking, and it is not something we are currently considering given that we have a number of other priorities which are always adjusting in order to best serve all our users.
That said, there ARE still things 3rd parties can do, and things we can do to support them, to make 3rd party integrations more functional and less clunky.
What is possible in the integration itself will depend on the plugin capabilities of the platform being integrated. In this case, Foundry VTT. Some features might need support to be built directly into the Foundry VTT app.
Here are a few ideas:
Linking online player devices to accounts could be streamlined and done within Foundry VTT.
Foundry VTT could itself download, install and manage the running of the online player app.
We could implement an API to allow remote control of the local online player volume. This is currently the ONLY interactive control in the app that cannot already be adjusted via the online control panel.
With these changes, a near-identical outcome for end users could likely be achieved, without having to re-implement and support a new player app.
The only limitation to the possibilities is that the audio output must come from the Syrinscape online player app.