HaiRon97
commented
1 month ago Issue still persists. Only used on legacy mode (haven't tested with legacy mode off).
I physically got over it by making it a habit to turn off/on the player whenever I use my headphones/TWS/Bluetooth.
Should be easy for the app to detect when a device is connected to turn off/on the EQ interface.
Example: Headphone 1 (H1) with EQ1 in AutoEQ Headphone 2 (H2) with EQ2 in AutoEQ
Listen to H1 -> Wavelet Recognizes H1 and uses EQ1 in AutoEQ -> EQ1 sounds good. Switch to H2 -> Wavelet Recognizes H2 and uses EQ2 in AutoEQ -> EQ2 sounds messed up -> Turn Wavelet off/on (the green power button at the bottom) -> EQ2 sounds good.
Listen to H1 -> Wavelet Recognizes H1 and uses EQ1 in AutoEQ -> EQ1 sounds good. Switch to H1 (unplug/turn off H1 and plug/turn on H1) -> Wavelet Recognizes H1 and uses EQ1 in AutoEQ -> EQ1 sounds good.
In the second case, it still doesn't hurt to turn wavelet off/on just as a precaution. Should probably avoid/stop playback before restarting the EQ to avoid sudden noises.
I noticed that when I use different headphones that have different codecs (e.g. AAC vs. LDAC), that they mess up the EQs. The only way I could fix it was to use the power off/on button within the app.
It'd be nice that if the app detects a different headphone is being sent audio, it would power off/on automatically. . . or have a way where the EQ doesn't mess up when a different codec is being used.