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
The driver does work correctly with USB 3 ports. Granted I have found one exception with an earlier version of the driver but then I haven't yet seen a windows machine that doesn't have at least one USB 2 port.
If ever you see that the device only works at a singe sample rate take a look at your audio player. Is it set to use the Direct Sound driver? Instead you will need to use either WASAPI or ASIO. If using Direct Sound, the OS will convert everything to the sample rate that is selected in the Control Panel Sound settings.
For bit-perfect playback with foobar, you will need to use the ASIO or WASAPI component with the m9xx. VLC uses the directsound driver as far as I know, so it will sample rate convert to whatever is set in the sound control panel for the m9xx. Are you using ASIO or WASAPI with foobar?