Sennheiser PC37X randomly goes bad after disconnecting the cable ?
Greetings, Yesterday I was using my headset like normal with my macbook, just listening to music and on a call with people like usual, and the headset was perfectly fine. The stock wire that came with the headset is extremely long and yesterday it annoyed me very much that it kept getting tangled with itself, so I decided to see if the cable is replaceable. I pulled out the cable from the headset and saw the adapter, and looked online for a replacement. Upon plugging it back in, the audio sounded extremely muffled and washed out. Im not sure what I did wrong to make it mess up like that as I've always taken good care of it, ive had it for about 2 years and its always just been chilling on my desk, but anywho I thought the cable just went bad and ordered a replacement. The replacement came, and the issue is still persistant, so I am not sure what the issue is I've tried multiple different headsets and the issue is not with the port, and I also tried it with my windows laptop and...
Apr 23, 2024
I can't explain what you think you saw, but you're in a very small minority.
But yeah, with less than 10 people out of thousands reporting differing discrepancies, I would chalk that up possibly to some not reading, but another possible explanation that is equally, if not more plausible that I haven't seen brought up is the possibility of a minor database/server caching error occurring for a brief period of time, not unlike the one that notoriously plagued Steam only at a substantially reduced scale. When running a large scale website such as the Steam store or Massdrop, the best approach to handle that kind of traffic is to have hundreds, if not thousands of (small) server nodes with a cache of relevant store content, and only pushing users out to other servers, higher up in the chain when making actual database changes such as making a purchase or adding a comment, or updating a drop page for the administrative end. That being said, due to any number of scenarios involving some kind of software bug, it is reasonable to expect caching errors to happen from time to time, hence why we expect companies that do their job to have proper technical and relations fail over plans to quickly address the issue. *glares at Valve's PR* That said, this is nothing but speculation and I'm not setting out to make accusations as that only covers the server side of things. The client side is a whole other can of the worms, in which some users' web browsers may have retained outdated content, or more dangerously, scripts which interface with the server side to pull various content such as item descriptions, comments, or in this case, possibly drop dates. If these people actually saw different dates, some kind of caching error(s) would explain that, and if there was more than one out of sync (or more than one grabbing ship dates from several different drop pages as a bug), then that would also explain why they can't agree on a unified varying date that they allegedly saw as well. In the end, I don't claim to know what happened but I've heard whispers of such disagreement for a while, and having just thought of an alternate explanation, I figured I'd share/explain it as best I could.
I'm not the one imagining things.