pixelcowboy
100+ Head-Fier
Yeah the biggest flaw is the poor multi device handling. They would be mostly perfect otherwise.
They might need to clarify how it changed but people have been asking for that feature for a while, and since it was even present in Audeze's previous gaming headphones, Penrose. Why remove something users want just to match an internal Audeze specification? I understand that something like that could introduce noise and although I have had the penrose and appreciated the feature myself but didn't use it much, I'd rather have it than not. Having a single pair of headphones on your head to create a private audio environment instead of speakers is a wonderful prospect.
Yeah I think the issue is Bluetooth. You'd essentially need two different radios to switch between inputs, I think. The limitations we're seeing are related to Bluetooth multipoint if I had to guess. I've never seen any Bluetooth devices that let you pick between two Bluetooth inputs. So the connection stability we're getting from Bluetooth is the reason you can't do that switch. Tradeoffs I guess. It makes so much more sense knowing that the dongle uses Bluetooth.I don't think the lack of simultaneous playback for certain inputs is a result of some internal Audeze specification, I think it's a technical limitation beyond Audeze's control given the components they used. That's why they were able to enable it for certain input combinations and not others. The Penrose was probably different because the dongle didn't use Bluetooth and the headphones likely used a different chipset all together, but Penrose also had worse stability and range than the Maxwell and lacked some other features.
I'll forward your issues to the fw engineers. IIRC, It should be behaving as before: BT audio should interrupt PC audio. But BT audio should not interrupt PS5 audio unless it's a phone call or anything using HFP.Another note. Before this update, simultaneous Aux+Dongle worked for me. Not only that, but bluetooth (as long as it wasn't LDAC as it stuttered) played simultaneously to Aux, and interrupted the dongle when playing. Since it was working, it seems like Aux+Dongle simultaneously should be possible, which would allow setups like using a PC and a console at the same time. I don't understand the logic of disabling that 'feature/bug'. To be fair, what didn't work is that while bluetooth audio was playing with the three connections, it would 'stutter' if bluetooth audio was high quality (LDAC). However, now you no longer get audio at all from the dongle if aux is connected, but bluetooth audio still 'stutters'.
Again, don't understand why we can't get the following behavior, since it was (mostly) working before.
Aux+Dongle=Simultaneous play
Aux+bluetooth=Simulataneous play
Bluetooth interrupts the Dongle when playing and still plays simultaneously to aux.
Got it and I understand, but besides the PC issue, will Bluetooth stutter be fixed if the above setup happens? (Dongle connected (but no output) + simultaneous Aux and bluetooth). Currently the only way to make this work is unplugging the dongle, or disabling LDAC audio. Otherwise Bluetooth stutters.I'll forward your issues to the fw engineers. IIRC, It should be behaving as before: BT audio should interrupt PC audio. But BT audio should not interrupt PS5 audio unless it's a phone call or anything using HFP.
And Aux interrupting all but BT is by design. We built it as a priority system, so it is as intended. Leaving it as before causes issues elsewhere. So, we may not make you happy, but the priority system is what was best for us in terms of development of Maxwell, and what will remain.
Did you update? V38 should have LDAC working. LDAC stutter was only an issue with initial release. That's why we mentioned LDAC working in our very first update patch.Got it and I understand, but besides the PC issue, will Bluetooth stutter be fixed if the above setup happens? (Dongle connected (but no output) + simultaneous Aux and bluetooth). Currently the only way to make this work is unplugging the dongle, or disabling LDAC audio. Otherwise Bluetooth stutters.
Yes, I'm on the latest. Like I said, this doesn't happen if you have Aux+bluetooth or USB-C plus bluetooth. It only happens if you also have the dongle powered on while having this setup.Did you update? V38 should have LDAC working. LDAC stutter was only an issue with initial release. That's why we mentioned LDAC working in our very first update patch.
I agree that the Maxwell headphones are pretty impressive, but as someone who takes their tech seriously, I always think there's room for improvement. While the single and double-click features are handy, I'm surprised that there isn't a button to switch between inputs. It would be great if the developers took note of user feedback on forums, as many people want to be able to use both their dongle and Bluetooth devices at the same time or switch between them more easily.
I'm sorry I'm just being as honest as I can and haven't had my coffee yet. These are the best bluetooth/gaming connected headphones I've ever owned so far, but I need to spend more time with them on my head to maintain that praise as these issues do exist and I'm sure there are more.
Thanks, your suggestion worked, I was on v38 but reinstalling the firmware fixed both issues, even though Audeze HQ reported I was on v38. Also, this time, the dongle didn't report the 'fail' error message that everyone else was reporting. So this is awesome and provides a way for me to have all of my 3 devices connected at the same time.Please try and update again (double press the device firmware version to display the update button. Do it on both.
The fact you're on V38 and are getting BT not taking over PC, and still having the LDAC issue shows me your update isn't going through properly, or have lingering old drivers.
please contact support@audeze.com, I'll have you try something. Contact us AFTER re-trying the firmware install.
I didn't mention as the dongle reported the update failed, but reconnected and showed v38. I think you or an Audeze rep here or on reddit had mentioned that that was a bug with the software notification and if the v38 firmware showed for the dongle in the software then it was considered successful? I just assumed that was an issue everyone had seen when they upgraded to v38. My headset upgrade went through fine though the first time.I'm glad to hear it fixed your issues.
Kinda weird, as those issues are like from v35. And thanks for letting me know about the update not fully going through last time.