[feature requests] Send variable for latest user to chat in a voice channel about companion-module-discord-api HOT 4 OPEN

I like the idea! One potential issue I can see is what if User A starts talking, User B then starts talking while A also is, and then User B stops talking so it's only user A talking again. In that situation the variable would be indicating User B, despite the fact that User A is the one talking at the end it's just they didn't stop/start again.

from companion-module-discord-api.

I like the idea! One potential issue I can see is what if User A starts talking, User B then starts talking while A also is, and then User B stops talking so it's only user A talking again. In that situation the variable would be indicating User B, despite the fact that User A is the one talking at the end it's just they didn't stop/start again.

That is a good point though.

I wonder if it's possible to detect when they START talking rather than to detect when they ARE talking. That could make triggering stuff a little more linear and not as conflicting.

I could see in my use case, id need some filtering done to keep things from being crazy.

I think regardless of it's use case, being able to fetch the variable "user/Dave/istalking=true or false would be SUPER useful in creating triggers within companion.

I noticed that the there is a voice indicator within the feedbacks when a user talks. I was trying so hard to somehow figure out how to grab that value and use it as a trigger.

Dude also thanks so much for getting back so quick!

from companion-module-discord-api.

I've been trying a few different ideas, and have pushed an update that will be in the next Companion beta build, that you may want to try out and see if it meets your needs.

There's now the variables voice_current_speaker_id, voice_current_speaker_nick, voice_current_speaker_number, as well as the user specific variables voice_user_X_volume, voice_user_X_mute, voice_user_X_self_mute, voice_user_X_self_deaf, voice_user_X_speaking (where X is the index, nick, or ID).

There's also a Speaker Delay option in the settings, which will be the delay before a new speaker is updated on the speaking variables. For example, if Speaker Delay is 0, the moment a user presses their mic the voice_curent_speaker_... will update to them. If they release their mic it'll return to the last recent speaker who's still speaking, and empty when no one is speaking. If I was to set the delay to 500 that would stop someone who just tapped their mic on/off (frequent if using sound activated rather than PTT). If you want to also prevent people who speak just for a 1 word answer like 'yes', 'no', 'uh huh', etc... then you may need a slightly longer delay.

from companion-module-discord-api.

I've been trying a few different ideas, and have pushed an update that will be in the next Companion beta build, that you may want to try out and see if it meets your needs.

There's now the variables voice_current_speaker_id, voice_current_speaker_nick, voice_current_speaker_number, as well as the user specific variables voice_user_X_volume, voice_user_X_mute, voice_user_X_self_mute, voice_user_X_self_deaf, voice_user_X_speaking (where X is the index, nick, or ID).

There's also a Speaker Delay option in the settings, which will be the delay before a new speaker is updated on the speaking variables. For example, if Speaker Delay is 0, the moment a user presses their mic the voice_curent_speaker_... will update to them. If they release their mic it'll return to the last recent speaker who's still speaking, and empty when no one is speaking. If I was to set the delay to 500 that would stop someone who just tapped their mic on/off (frequent if using sound activated rather than PTT). If you want to also prevent people who speak just for a 1 word answer like 'yes', 'no', 'uh huh', etc... then you may need a slightly longer delay.

Dude! Awesome!! I'm gonna try it out now!! Thank you so much for implementing this!!

from companion-module-discord-api.