Announcement

Collapse

Forum Rules

  • No flaming or derogatory remarks, directly or through insinuation.
  • No discussion, sharing or referencing illegal software such as hacks, keygen, cracks and pirated software.
  • No offensive contents, including but not limited to, racism, gore or pornography.
  • No excessive spam/meme, i.e. copious one liners in a short period of time, typing with all caps or posting meme responses (text/image).
  • No trolling, including but not limited to, flame incitation, user provocation or false information distribution.
  • No link spamming or signature advertisements for content not specific to Dota 2.
  • No Dota 2 key requests, sell, trade etc.
  • You may not create multiple accounts for any purpose, including ban evasion, unless expressly permitted by a moderator.

  • Please search before posting. One thread per issue. Do not create another thread if there is an existing one already.
  • Before posting anything, make sure you check out all sticky threads (e.g., this). Do not create new threads about closed ones.
  • It is extremely important that you post in correct forum section.

  • Balance discussion only in Misc.
  • All art related (such as hero model) feedbacks go to Art Feedback Forum.
  • All matchmaking feedback should go here: Matchmaking Feedback
  • All report/low priority issues should go here: Commend/Report/Ban Feedback
  • No specific workshop item feedback. These should go to workshop page of that item.
  • When posting in non-bugs section (such as this), use [Bugs], [Discussion] or [Suggestion] prefix in your thread name.



In case you object some action by a moderator, please contact him directly through PM and explain your concerns politely. If you are still unable to resolve the issue, contact an administrator. Do not drag these issues in public.



All rules are meant to augment common sense, please use them when not conflicted with aforementioned policies.
See more
See less

Commentators voice bug in replays

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Commentators voice bug in replays

    Hello,

    I noticed there is a bug with this new update, regarding the commentator audio in replays. This didn't happen last week, so it must be new.

    In any demo I replay (even old ones I downloaded that I was able to play without problems before), the commentators voice stutters a lot and has a very bad quality.

    In the console, the following lines keep showing all the time:


    387.43: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)
    387.43: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 256 LOST -256 bytes? (Offset 0, expected -256)
    387.49: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)
    387.49: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)
    387.49: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 256 LOST -256 bytes? (Offset 0, expected -256)
    387.56: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)
    387.56: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 256 LOST -256 bytes? (Offset 0, expected -256)
    387.63: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)
    387.69: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)
    387.69: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 256 LOST -256 bytes? (Offset 0, expected -256)
    387.70: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)
    387.70: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)
    387.76: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 256 LOST -256 bytes? (Offset 0, expected -256)
    387.83: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)
    387.83: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)
    387.90: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 256 LOST -256 bytes? (Offset 0, expected -256)
    387.90: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)
    387.90: Received voice channel= 0: section= 0 seq= 0 time= 0 bytes= 128 LOST -128 bytes? (Offset 0, expected -128)

    Any ideas?

  • #2
    same problem here, just great now i cant even watch the ti4 games i missed...
    why valve change working things??
    VALVE FIX FAST !!!!
    Last edited by Aod_Knight; 07-14-2014, 05:55 PM.

    Comment


    • #3
      Still have this problem even with latest patch just a COUPLE MINUTES AGO .. (same exact error line from console , happens after 9mb patch yesterday CMIIW ..)

      PLZ FIX THIS ASAP VALVE

      Comment


      • #4
        I have the same issue. Replays recorded after 11th July work fine, but all replays before then have the distorted commentary during replays. The issue only started after the latest patch.

        Comment


        • #5
          It was fixed yesterday but it's back again today
          Explanations on the normal, high and very high brackets in replays: here, here & here
          Why maphacks won't work in D2: here

          Comment


          • #6
            Okay , Fixed On this day patch (260mb+ patch) , no more error log on console too .. TY

            Comment

            Working...
            X