random weirdness with scene builder audio, and scene builder shuts down when page not directly focused

[lilmike]

Hiya,

I tried using scene builder on Saturday as part of running a Secrets of Cats campaign, and had some weird issues:

1. We had five people total, including myself, and audio worked very well, except for one strangeness: Every time we'd try to load the scene and have everyone join, audio would work but one person would not be able to hear another person, and usually the person they couldn't hear couldn't hear them either. So If player 1 joined, followed by players 2 3 4 and 5 in order, it might happen that player 1 could not hear player 3, and in most cases player 3 could not hear player 1 either. In a few cases this happened to more than one group of player pairs. I would love to know what could possibly be causing this, we did everything we could think of, refreshing the page with all combinations of exiting the game, exiting the game and stopping it, etc, and nothing worked. Three of us were using brave, one was usint firefox but also tried chromium, and one was using edge. Browser didn't seem to corolate to who couldn't or could hear anyone else in any meaningful way.
2. It seemed that while I, the gm, was not directly focused on the page with the scene in it, it would stop responding for everyone else, and disconnect them, hanging trying to reconnect until I rejoined the page. Once I left the page for quite a while, and after returning, I had a message that said lost connection to server. This was me, using brave, if that matters. It would be great if we could figure out a way around this, because not being able to reference documentation and other materials makes the scene builder pretty useless heh.

It's worth noting thatI did a successful test with only one other person several months ago, and had neither of these issues. Any thoughts?

-Michael.

[sheibeck]

Hi, Michael, I'm terribly sorry, but I did not see this message until just now. Really sorry you were having this issue and is the first I'm hearing of it. I did test this using 5 people when I was working on it way back.

What I do know is that right around the time frame you were trying there was a back-end changeover in the system that hosts our peerjs server. They upgraded their systems and I was on a legacy system that they were deprecating. Are you still experiencing this issue. Just wondering if the new peerjs server might have solved the problem?

Let me know if you have a chance to try it again.

update:
So, I was reading over your message again and saw that you already included browser information. Sorry about that.