amoeba1126
100+ Head-Fier
- Joined
- Mar 25, 2012
- Posts
- 395
- Likes
- 333
You did what I should have done and read here before ordering/shipping
Spent some time playing Fortnite last night, quite nice although my ears started to protest after a couple of hours..
Back to this then:
Any idea on when these fixes will be available/implemented?
Honestly I've never seen an equalizer that drastically lowers the overall volume when adjusting a single slider upwards. How can they even release a product with such obvious bugs? Is the reasoning that it's a weird bug but one can still make adjustments and correct for volume changes using the volume wheel on the left ear cup, so better to have these shipped out so people can start beta testing? Also, I've tested perhaps 6-7 different headsets over the past few months, trying to find the ultimate product. None of them failed to respond to the general Windows volume adjustment.
The good news, I suppose, is that all of this can and hopefully will be addressed with future firmware upgrades. I'm just curious what kind of time perspective we are looking at here? I'm not interested in using the dual audio wireless/BT, so any of the issues related to this feature are irrelevant. Sole reason I bought these is to get rid of the cable that's required with the Mobius, and PC Gaming.
How does one achieve the best performance in terms of localization of sounds, i.e. where footsteps and such come from? Use the Windows surround settings or disable it and use the headset in Stereo and leave it to the game?
Regarding the equalizer behavior and volume control via Windows, these are NOT bugs with the product. The former is a design choice by Audeze. They explained why this design choice was made. I don't remember their reason offhand, but I am sure you can dig it up via the search function. That said, they did mention they plan on looking into it and seeing how they can address it. As for the volume control, that also isn't a bug but rather a limitation of their current wireless SDK. They have already requested the feature from the devs for their wireless SDK and no timeline has been provided yet.