andrewwardell
100+ Head-Fier
…wait, there’s a shelf filter now?
[FiiO BTR7] Portable Bluetooth Amplifier, Color IPS display,High-performance DAC ES9219C*2,THX AAA-28*2 amps,3.5+4.4mm outputs,One-click “dongle” mode
- Thread starter FiiO
- Start date
Thank you fiio for having solved the filter problem with the latest app uploaded to your website. 
Today I have noticed that the Q factor set to 0.53 in the EQ is not preserved after exiting and re-entering to EQ configurationThank you fiio for having solved the filter problem with the latest app uploaded to your website.
Last edited:
Dear friend,Today I have noticed that the Q factor set to 0.53 in the EQ is not preserved after exiting and re-entering to EQ configuration
Hi, we have reported this problem to the engineer when you mentioned in the BTR15 thread. Maybe it still takes the engineer some time to fix the problem.
Best regards
Great UPGRADE for BTR7.The new firmware V2.02 for FiiO BTR7 is now available!
BTR7 firmware download: Click here
How to upgrade the BTR7: Click here
Can rename all 3 EQ settings. Much easy to resetting EQ with “Advanced setting”.
Thank you for taking care of your customers.
Hi, Today I discovered another bug in the fiio control application. It is the Bost bal out mode function that if you activate it does not stay ON when you exit and re-enter the application. Sincerely.
Aevum
Headphoneus Supremus
- Joined
- May 15, 2007
- Posts
- 2,769
- Likes
- 320
today i discovered that its recommeded to factory reset it once in a while,
Had issues with it sounding weird, always connecting in aptx even whem my phone supports ldac, and things like that, factory reset from the device fixed it.
Had issues with it sounding weird, always connecting in aptx even whem my phone supports ldac, and things like that, factory reset from the device fixed it.
blorg
100+ Head-Fier
@FiiO shelf filter on the new firmware is not working for me. It at first seems like it has worked, and appears in the graph OK. But when I swap to another EQ or tab and go back (so it reloads them from the device) the shelf filters turn into peak filters. Any tips would be appreciated.
As a note, this is one of the problems with this device, and the app control on all your other devices as well- that there is a certain decoupling between the app and the device. So the app will present a setting as having worked, when they haven't actually been set that way on the device. This makes using them extremely frustrating as you can have no trust as to whether what you did is what is actually on the device. It would be better, if the app fails to set whatever it is trying to set, that the user gets feedback in the app that it didn't work. I know you aren't the only company with this issue, Moondrop has the exact same problem with their DSP cables for example. Qudelix does NOT have this problem, and would be a good example to learn from. I have quite a few of your devices, and they all seem to have this problem that the app doesn't wait for feedback that a setting actually worked on the device, it just sets it in the UI when often it hasn't actually set. Some more than others, the FW5 is much less reliable. But it's a a general app/UI issue, that you need to verify that it actually worked before presenting to the user that it did.
As a note, this is one of the problems with this device, and the app control on all your other devices as well- that there is a certain decoupling between the app and the device. So the app will present a setting as having worked, when they haven't actually been set that way on the device. This makes using them extremely frustrating as you can have no trust as to whether what you did is what is actually on the device. It would be better, if the app fails to set whatever it is trying to set, that the user gets feedback in the app that it didn't work. I know you aren't the only company with this issue, Moondrop has the exact same problem with their DSP cables for example. Qudelix does NOT have this problem, and would be a good example to learn from. I have quite a few of your devices, and they all seem to have this problem that the app doesn't wait for feedback that a setting actually worked on the device, it just sets it in the UI when often it hasn't actually set. Some more than others, the FW5 is much less reliable. But it's a a general app/UI issue, that you need to verify that it actually worked before presenting to the user that it did.
blorg
100+ Head-Fier
For me, not even if you switch tab and come back to it, even without exiting and re-entering entirely. From testing with a low shelf filter very high up (at 8kHz), while it shows the shelf on the graph, it's not actually setting it at all. It's only ever a peak filter. This is again, part of the whole problem with the Fiio Control app, it misrepresents to the user what has actually happened. Better if it didn't work just tell the user that. It would make it easier for Fiio to debug too.
I also don't see how it is possible to rename the EQs, they are still USER1, USER2, USER3.
Hi, You need to download the latest version (3.22) of Fiio control app from the official page to fix the filter issue. But they still have to fix some bugs that have already been reported.
Dear friend,@FiiO shelf filter on the new firmware is not working for me. It at first seems like it has worked, and appears in the graph OK. But when I swap to another EQ or tab and go back (so it reloads them from the device) the shelf filters turn into peak filters. Any tips would be appreciated.
As a note, this is one of the problems with this device, and the app control on all your other devices as well- that there is a certain decoupling between the app and the device. So the app will present a setting as having worked, when they haven't actually been set that way on the device. This makes using them extremely frustrating as you can have no trust as to whether what you did is what is actually on the device. It would be better, if the app fails to set whatever it is trying to set, that the user gets feedback in the app that it didn't work. I know you aren't the only company with this issue, Moondrop has the exact same problem with their DSP cables for example. Qudelix does NOT have this problem, and would be a good example to learn from. I have quite a few of your devices, and they all seem to have this problem that the app doesn't wait for feedback that a setting actually worked on the device, it just sets it in the UI when often it hasn't actually set. Some more than others, the FW5 is much less reliable. But it's a a general app/UI issue, that you need to verify that it actually worked before presenting to the user that it did.
Hi, please check whether the APP version is the latest version as well? As the working feedback, we will report to the engineer for assessing adding. Thanks.
Best regards
rlw6534
Headphoneus Supremus
One post up. Version 3.22 seems to work properly.
