Translation channels are blocked

If the translators select a channel, e.g. English, and are muted at the same time, the floor is not switched through. This can be solved if the interpreters always go to "None" when they are not speaking. However, this takes too long. In addition, the participants do not receive a complete translation if the language on the floor is the same as in the translation channel.

added Bug label

changed the description

assigned to @martin.klampfer

You have set the server settings to:

translation:
  floorVolume: 0.0
  translator:
    speakDetection:
      enabled: true
      timeout: 60000
      delay: 3000
      threshold: -70

Indeed, switching trough the floor should happen after 3 seconds of muting. We'll have a look.

Meanwhile I suggest you set

  floorVolume: 0.2

Then you have the floor as a background in all translated channels.

quick workaround you can try: set the timeout to 3s as well I guess. We actually detect if the interpreter is still speaking, so those long timeouts should be unnecessary.

The app checks periodically if an interpreter is still speaking by listening to a 'stopped_speaking' event and will then update the state in the DB accordingly. When an interpreter switches between different channels in quick succession, it is possible that the 'stopped_speaking' event fires after the channel has been switched, leaving the old channel in a 'speaking' state, with a muted floor. This is only recovered when the timeout is reached. This is why the suggestion from @Beier should provide a workaround.

I have added a fix to bbb80 that, upon changing a channel, will always set the speaking state of the old channel to false. This will, however, mute any interpreter in the same channel for three seconds whenever another leaves for a different interpreter channel.

For better usability, we could adapt the state that is kept in the DB to include which interpreter is speaking, thus allowing for a smoother switching between interpreters.

A fast and smooth transition from one channel to the next is needed. Additionally, I think that the 3 second break of the other channel will disturb a seamless translation. Usability is key.

added inactive label

closed