Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 5 of 5
  1. #1
    Join Date
    February 2010
    Location
    Seattle
    Posts
    69

    3.0.0-pre9 Cut-Out bug persists

    After extensive, large player testing (~25-45 players) we have noticed the cut-out bug still persists, but is now much more obvious (I say obvious as in, the actual cause and visibility of the bug happening is easily detectable)

    Mainly, at random times, in random scenarios, the onTalkStatusEvent fires for players and is basically a STOP_SPEAKING event. It is like the person let go of their PTT key (from a code perspective), however they have not.

    Additionally - this seems to be more prevalent on some players more than others.

    I can confirm, however, that this *is* related directly to the (other clients) receiving a stopTalking event for that client - when they have not in fact stopped talking.

    Lastly - this stopTalking event fires for plugins, and obviously for the sound engine. HOWEVER - it does not seem to fire somewhere within Ts3 - The users icon stays lit, even though you cannot hear them, and the plugin has registered them as "stopped talking".

    I believe the above may help you trace the bug.

  2. #2
    Join Date
    July 2002
    Location
    Germany
    Posts
    2,191
    Is the stop talking event followed by a start talking event shortly after or before? In this case the client only had a very short hickup and is still transmitting. As the light in the clientui stays lit you as the client plugin sdk should also be able to detect the client is still sending.

  3. #3
    Join Date
    February 2010
    Location
    Seattle
    Posts
    69
    No, it does not appear to be followed by another START_TALKING event. Let me get exact logs for you on the function calls though, so I can be 100% exact on the order of operations happening here.

  4. #4
    Join Date
    February 2010
    Location
    Seattle
    Posts
    69
    Okay tested now.

    It seems the cut-out portion of this I *think* was my code. However, one oddity that did come up:

    It seems that TS3 (and it seems much more frequent with VAD), sends non-linear START/STOP talking events. e.g. you might get:

    START_TALKING
    START_TALKING
    START_TALKING
    STOP_TALKING

    is this intended?

  5. #5
    Join Date
    July 2002
    Location
    Germany
    Posts
    2,191
    It can happen that a client is talking multiple times at once (overlapping talking), so you might get:

    start1
    start2
    stop1
    stop2

    You should always have the same number of starts and stops (provided the client is currently talking ). A single stop even might not mean the client stopped sending, provided there were two (or more) "open" start events before.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Internet disconnects with pre9-pre10
    By DJ_Casper in forum Bug Reports [EN/DE]
    Replies: 3
    Last Post: March 2nd, 2011, 11:38 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •