Lestaticon

Oh, now that doesn't sound good (pun not intended). I feel these headphones have a wider sound stage than the DAS set. I wonder if that's part of the trouble. They are less heavy bass, but a larger sound stage and very precise sounds. I also notice you need to get them right over your ears and siting flat against them. They sound very high end to me, but less bass than DAS.

I don't think there is anything else you can do with software to address that. Since you have gone through this thread, you may have guessed that the bass/volume may be an egineering flaw. The pressure of the earcups on your ears may not be sufficient. What I and others have done is get some addon clamp/springs installed, designed by . You can download the 3d printable design. See here. If you need someone to print it, go to 3dhubs.com and submit the design there. I got mine printed there for less than $13, shipped. It solved the issue for me, confirming that this is a hardware design flaw. Hope it helps.

Wow, you've become the unwilling poster boy of bad service. So sorry you are dealing with this level of bad service. Frankly, this is on the edge of consumer protection services stepping in. Really, you had a faulty product, sent it in, and it was returned damaged. That alone should warrant a special case response. After all this back and forth, if I was in charge, I'd see if you would be interested in a brand new Vive Pro as a gesture. Rest assured, there are customers, current and future, reading about your experiences on social media and places like Reddit.

I recommend wearing a sweat band like this one. http://a.co/d/9UQxT6x I try to remember to put it on, especially if I'm going to play Beatsaber or something else active like that. And if you are a particularily heavy sweater, or just in general, remember to not let the headset hang down (pointing downward) in between sessions or even temporarily as that would allow any moisture collected to enter the internals more easily. Tilt it where the lenses are facing down or angled downward instead.

I saw your thread on Reddit about this. You should get a totally new headset, because if yours was botched so badly, who knows what else is wrong with it now. I get how frustrating it is to have sent your Vive in, wrapped to protect it, and then get it back ravaged by a really exceptionally bad repair (including scratches to the lenses!, stripped screws, cracked HDMI port - and who knows if anything else was damaged). When you said it was the same serial number, I was shocked. HTC's repair center simply did you wrong. I hope you get this resolved 100%.

In continuation of the distorted audio issue for the displayport, onboard Vive audio device, I recently came across a tip on reddit that actually solved this issue in a satisfactory way. I no longer need to rely on the Nvidia audio device, nor have to deal with its shortcomings (the fact the Nvidia device is constantly disappearing, for example). Now I am able to use the DP "Vive Pro Mutimedia" device without any corruption or distortion. Here is a link to the reddit thread. Please also see my comment on that thread for further tips. Maybe it will help you.

The 3rd system? It would be the same as the 1st and 2nd system. It would all depend on what you are trying to do and the space. All the rules have been outlined above. Maybe you could start by posting a drawing with details as that would help.

, just wondering - Does it say Vive Pro "Multimedia" or actually Vive Pro "Mutimedia", with the missing L? Just curious as that has been like that a while for me. I assumed it was the same for everyone, but I would be curious to find it was correct in your setup. I don't think this issue has been automatically fixed for others as you mentioned in your original post. I think people have just been working around it and dealing with the issue. Some just consider it fixed even though all they have done is stop using their displayport "Mutimedia" device and are instead using the audio supplied by their graphics card. I have no idea whether or not HTC is actually working on a solution or are letting it go, but I have found that some people sadly just overlook it now. You too will probably arrive at some workaround for this, which is a shame.

I tried the windows update 1803 again, after cleanly uninstalling all Vive software and drivers, doing the update, then reinstalling all, and I still get distorted audio through the USB pro driver output. If I select the hdmi output supplied by the nvidia driver, the audio clears up. If, however, I then reselect the usb outpout for the HMD, SteamVR may suddenly lose all tracking, lighthouses report as offline (even though on) and controllers power off. The audio through my creative external DAC works fine. Is this a Vive driver issue with 1803 or a Windows 1803 audio issue? it seems like the audio driver for the Vive Pro's USB audio are generic Windows usb ones. They are supplied by Microsoft and they are dated 4/11/2018. Version #10.0.17134.1 (found in device manager). I wonder if anyone still on Windows 1709 could check device manager and look at the "VIVE Pro Mutimedia Audio" (yes it is misspelled in device manager....) under "Sound, video and game controllers" and tell me what version they have?

However, when I updated Windows 10 to 1803, I get the distorted audio issue. (crackling) I noticed that switching the audio device to the Vive Nvidia audio device, it clears up. However, as soon as I switch back to the Vive Pro audio (the usb one), audio crackles and SteamVR may lose the status of the HMD and base stations. (tracking lost and base stations show as off even though they are on). I had to revert Windows back to 1709 to correct that issue. https://pureinfotech.com/uninstall-windows-10-1803-april-2018-update/ However, as part of the troubleshooting process, I uninstalled all Vive drivers and software. There is a new Vive Pro software installer on the website and durring part of the process you must "sign in" to your HTC account. Pressing sign-in does nothing so I cannot continue the install process. This leaves me with a broken install and software entries in add/remove programs I cannot remove. I've read posts here from others with similar issues with the "sign in" button (but using different installers or the regular Vive instead of pro) and have tried switching my default browser from Firefox to Chrome and even IE to see if that made a difference. It has not. EDIT: I realized that the bigger Windows 10 updates tend to mess with drivers often, especially third party ones like, I assume, the Vive's, Nvidia's, and Createive (my external usb DAC). I cleanly installed my DAC and GPU drivers. I also removed any other instances of them from device manager (show hidden devices). After cleaning all of those and removing the Viveport service which was still there even though the exe was not, I redownloaded the HMD install exe from https://www.vive.com/us/setup/vive-pro-hmd/ Once it downloaded, I right clicked it, opened properties, and checked off the "unblock" box at the bottom, just to make sure there were no issues there. Previously, I had also made sure my default browser was chrome. As an additional step, I also went to "set defaults by app", selected chrome, and made sure all the set protocols there were also chrome and not firefox. Of course, there were numerous reboots throughout this process and I am still on windows 1709 and not 1803, which was even more problematic. Now the "sign in" step worked. I plan to continue the installation later when I'm home and retest the audio again. EDIT2 5/31: After all the effort above, I managed to get the vive software installed. I received an error that viveport could not be installed during the process. I had to run the viveport installer exe manually from program files and choose "repair" to get it working. Audio is no longer distorted. All other issues with audio aside, and with the new silence from HTC about it, we are perhaps on our own at this point. 's awesome 3d printable springs for the headphones has helped a lot too and gives more ways to improve the experience. If I am courageous enough, I may try updating to windows 10 1803 again. However, before doing so, I plan to uninstall all the vive software and drivers again, cleanly, uninstall my creative external usb DAC, and then do the update. After the update is installed, I will then reinstall everything (including the GPU drivers). My guess is that the update process messes with the drivers and I'm curious if there might be a solution.

I was away a couple weeks and, upon my return, found a firmware update notification for the HMD in SteamVR. (An actual firmware update, updated the firmware present on the HMD). It appears to have updated a couple firmwares, specificaly the Watchman. The audio firmware appears to be the same, but I'm no expert. Does anyone know what this firmware changed? I also has crackling audio after this firmware update. I powercycled the HMD (removed power from the linkbox, and disconnected the HMD cord from the linkbox, letting it sit like that several minutes before plugging it all back in and turning it on). I also changed BACK the audio sample rate from 16 bit 44100 hz TO 16 bit 48000 hz. I believe I also rebooted after that. Eventually, one of these steps resulting in the audio clearing up again. edit: and here is my current firmware information from the SteamVR System Report Device 1 - Headset VIVE_Pro MV HTC LHR-977A625FFirmware: 1526689969 watchman@runner-watchman 2018-05-18 FPGA 531(2.19/7/2) BL 1513896911Hardware Revision: product 133 rev 2.0.6 lot 2000/0/0 0Hardware Id: 0x85020006Watchman Firmware: 1526689969 / 1526689969 (2018-05-18) Watchman FPGA: 531 / 531 (2.19) Dongle Version: E1818A69FE Version: 1461100729 / 1461100729 (2016-04-19) Dongle Version: 51C8F36B0E Version: 1461100729 / 1461100729 (2016-04-19) Camera Firmware: 12884967859 / 12884967859 (Version: 03.01.1B3 Date: 2018.Jan.11) Display Firmware: 2105635 / 2105635 Display FPGA: 6 / 6 Display Bootloader: 1056771 "0x0000000000102003"Display HW Revision: 2 "0x2"Audio Firmware: 6 / 6 Audio Bridge Firmware: 288 / 288 Image Bridge Firmware: 9 / 9 VSync to Photons: 0.0004Display Frequency: 90User IPD (m): 0.0636Current Universe ID: 1472096683Previous Universe ID: 0

, yes that's right. You would need to install Vive Port to explore that. I installed it, after having read the manual, while troubleshooting this audio fault. PS. Thanks again for sharing your spring design. I'm having it printed now and will keep an eye out for your refinements if you do that :)

Also, if you look at the Vive Pro manual, it says you can go to the Vive app (IN SteamVR - the rows of icons on the SteamVR dashboard) and click the gear icon in the Vive app to select a sound profile. I haven't really heard anyone mention that. I checked and it has 3 settings. The settings seem to allow you to control how much outside sound gets to you. I was set on "normal" by default. The other options appear to be there to let more outside sound in. I guess that would only work if the headphones were actually isolating well.

Which is a little odd because the deluxe audio strap for the non-pro Vive doesn't give me this issue. Though, the springs were more sensitive on my head (meaning, sometimes would not click down just right). The pro springs seem more ridgid and clamp down easier. I'm sure we can come up with mods like did with the 3d printed springs, but I prefer HTC stand behind their product and come up with something. They were working on something, then the SteamVR patch came and I'm worried they have stopped.

I came across this detailed review of the Vive Pro audio and found it interesting. https://www.lesnumeriques.com/casque-realite-virtuelle/htc-vive-pro-p42559/labo-htc-vive-pro-que-valent-ecouteurs-hi-res-n73909.html It is in french, but it essentially says that the technical aspects of the headphones are excellent (which I also agree with), but the issue is in the engineered design of the headset and the pressure applied to the ears. They found that, in their office, about 50% experienced the attenuated frequencies, depending upon head shape and size. This falls in line with what others have said here, reddit, and other places. If it IS actually a physical design flaw, is it unreasonable to think that HTC could come up with a solution and be able to ship that to those affected?

Thank you, . I appreciate the time. This just confirms that my unit has not received any HMD resident firmware updates since release and that all updates connected to this audio fix have been SteamVR files only.

thanks for clarifying. I do not have any way to manually install an update to the HMD firmware (or other devices - like the controllers or lighthouses) because all of them show as "up to date" when I go to Devices, update firmware, in SteamVR. If you saw your HMD out of date there, then maybe it was the scenario I mentioned before. Perhaps your HMD came with a version or two older than the unit I received. did at least confirm that we both are on the latest version. So I guess my point from all of this is that there has been no update to the HMD resident firmware since release of the Pro. So nothing has been installed to it directly to correct the audio issue. All the updates have been to the SteamVR files (and their own firmwares, which do not get pushed to the device). Which just makes me wonder if the fix they had been working on is just the SteamVR update or is there an actual HMD firmware update in the works? It would great to know what is currently being worked on and if we can expect more to come.

Hey , thanks for sharing your solution and design! What material did you use? I would like to give this a try if it comes to it.

Thanks for posting back. The only fact I can provide is that I had the vive pro since a few days after release and have yet to get a firmware notification. It came with the version I posted. It could also be that my HMD was a batch that came with the Feb version and yours had one or to versions before? Though, hard to speculate but I've read of people getting update notifications without an actual update being delivered. I just want to rule out mine being out of date, which, so far, mine seems to be the same version as everyone else's.

I too would really like a response to this. I've read so many say they have updated their HMD firmware, but no one has shown any evidence of that actually being the case. You can check by opening SteamVR, and from the menu choose to generate a System Report. Go to devices in that report and you will find a section listing information for your HMD. There is firmware version and dates show. Mine still shows firmware from Feb (so release version). I have yet to get an update notification and all my devices show as up to date to (Vive Pro, controllers, lighthouses). At this point, I am doubting people have actually updated the firmware ON their HMD. But I too would love to confirm that and see if we are missing one. Would anyone who says they did an update, copy paste their HMD information from their System Report so we can compare?

When you guys are saying you installed an updated firmware regarding this issue, are you saying you received an alert notification in the SteamVR status UI and then right clicked the HMD icon (see screenshot) and selected update firmware? Or are you talking about a SteamVR update? I'm asking because I've been following this issue and the only updates I've received have been SteamVR updates. I have yet to see a firmware notification show on the HMD icon in the SteamVR status interface. I too have the same tinny audio with my Vive Pro. EDIT: Also, when I check for updated firmware through SteamVR, it shows the list of all devices (lighthouses, controllers, HMD) and each one shows as up to date. However, when I review the System Report, my HMD firmware is dated from Feb, so I am assuming it is not the update/fix firmware others are talking about. So, just want to clarify the 'firmware' people are pointing out. EDIT2: And this is the firmware information showing for my HMD via the System Report generated in SteamVR. I would be curious the version of the firmware of those who say they have the update? Device 1 - Headset VIVE_Pro MV HTC LHR-977A625F Firmware: 1518508151 watchman@runner-watchman 2018-02-13 FPGA 531(2.19/0/2) BL 1513896911 Watchman Firmware: 1518508151 / 1518508151 (2018-02-13) Camera Firmware: 12884967859 / 12884967859 (Version: 03.01.1B3 Date: 2018.Jan.11) Display Firmware: 2105635 / 2105635 Audio Firmware: 6 / 6 Audio Bridge Firmware: 288 / 288 Image Bridge Firmware: 9 / 9