You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PHP briefly connects to each server to gather each connection's username, instrument, and location.
I have considered re-implementing this by repurposing lounge.
However, I know lounge cannot connect to every server. (I wonder why?) I also have heard that the PHP code might just trigger initial connection steps, while the lounge code establishes a stream. Maybe lounge only fails in a later step. So maybe lounge's Go could replace the PHP for this essential data service.
The most valuable piece of new data I want is the "you're muted" state for every channel. I would like to identify servers where nobody can hear a new joiner. Levels are also informative, because I could probably identify silent servers.
Do you think the lounge Go could be repurposed to replace and extend jamulus-php?
The text was updated successfully, but these errors were encountered:
The actual Jamulus client implementation is in gojam project.
Most connection issues are due to the server’s firewall. The official Jamulus client uses a UDP hole-punching technique, with the help of a directory, to make these server open a port for the client. gojam does support UDP hole punching by supplying a -directory argument, however, it has not been implemented in jamulus-lounge, because it is intended for use with localhost.
Right now gojam does not provide information about muted state. However it is possible to retrieve it by implementing support for the relevant message.
Hi.
I rely on https://github.com/softins/jamulus-php to gather current details about every connection on every public server.
This PHP briefly connects to each server to gather each connection's username, instrument, and location.
I have considered re-implementing this by repurposing lounge.
However, I know lounge cannot connect to every server. (I wonder why?) I also have heard that the PHP code might just trigger initial connection steps, while the lounge code establishes a stream. Maybe lounge only fails in a later step. So maybe lounge's Go could replace the PHP for this essential data service.
The most valuable piece of new data I want is the "you're muted" state for every channel. I would like to identify servers where nobody can hear a new joiner. Levels are also informative, because I could probably identify silent servers.
Do you think the lounge Go could be repurposed to replace and extend jamulus-php?
The text was updated successfully, but these errors were encountered: