Syrincape Controller with Foundry V13 in Firefox

Support
#1

Hi, thanks for working on tools for Foundry, I used the previous version in Foundry v12 all the time and it was great. I can’t seem to get the new module working with the latest version of Foundry in Firefox though.

I installed module and added my API key. It was stuck saying downloading cache data or something like that and when I hit the browse button it said there was no data. I tried hitting the “Syrinscape Player” button on the left side of the UI under “Ambient Sound Controls” and that pops up a window trying to go to app.syrinscape.com//gm/ with gives a 404.

I was wondering if this was a browser-specific issue so I loaded Foundry up in Safari and was able to get the Syrinscape cache to download there. Only the free soundsets showed up in the browser but none of the sounds (even the free ones) would actually play. The Syrinscape Player button load the control panel but in Safari you get a message that that browser isn’t supported.

I switched back to Firefox and looked in the console, the module is just constantly throwing JS errors :
000/modules/syrinscape-control/lib/homePlayer.js:172

[homePlayer.js:5:318](http://[server-name]/modules/syrinscape-control/lib/homePlayer.js)

Uncaught (in promise) Error: bad response: [object Response] [Detected 1 package: syrinscape-control(1.0.2)]

and

Uncaught (in promise) Error: localForage error: InvalidStateError: A mutation operation was attempted on a database that did not allow mutations.
[Detected 1 package: syrinscape-control(1.0.2)]

I’ve been avoiding using Chrome with Foundry for both performance and ideological reasons. I guess I could download it and try there for additional troubleshooting purposes but I was just wondering if this is a known issue? I didn’t see anything in the module docs about requiring Chrome.

I’m on a Mac M4 Pro running on Sequoia 15.5 if that makes a difference.

#2

If you are on v13, you should be using Syrinscape Controller - note the “er” at the end of the word “control”. They’re two different modules. Syrinscape Control was written by a volunteer and only supports version 12 and one or two versions below that.
Syrinscape Controller is a complete rewrite by a group of developers. It only works on version 13.

Oh - I fired up Firefox and tested with Syrinscape Controller - works like a charm.

1 Like
#3

I believe I am using Syrinscape Conroller - it’s the only one that’s v13 compatible, the v12 one was called SyrinConrol (all one word).

If you look at the package manifest (in the module.json file as well as in the pacakage.json) you’ll see the new one it calls itself syrinscape-conrol it’s not my fault the names are so similar. ( https://github.com/MetaMorphic-Digital/syrinscape-control )

I’m glad it’s working for you that gives me hope… still doesn’t explain why it is not working for me.

#4

I downloaded Chrome to test and I was able to get it working there. No errors in the console and my campaign soundsets were able to be controlled from another computer. It all worked as expected.

I logged out of Chrome and back in on Firefox and it doesn’t work at all. The console is just a constant stream of JS errors.
Uncaught (in promise) Error : bad response: [object Response]
/modules/syrinscape-control/lib/homePlayer.js:5

I tried disabling all browser plugins in Firefox as well but that didn’t help. Not sure what else to try, some of my player refuse to use Chrome, so it’s not enough just to get this working for me. They had trouble connecting to the shared stream directly so really appreciated being able to have it just come in through the VTT.

#5

I saw the log saying syrin-control and thought that you had the wrong module. They really should have used a their own name in the code or fully taken over the original syrin control module.

I think you should probably open an issue in the github repository. I don’t know if the developers monitor this forum.

#6

Yeah, I couldn’t tell which method was the best way to raise this issue. In some of the other tickets in the repo, I saw Ben pointing people back here so I thought I’d try here first.

I’ve put in a ticket in GitHub as well, we’ll see what happens. We just finished off a long term campaign a couple weeks ago and I was holding off on upgrading Foundry to v13 until we finished that up. So excited to start up the next big campaign on v13… just ran into a SNAFU with Syrinscape.