BTR7 + UAPP (Android) + Tidal
Jul 11, 2023 at 7:44 PM Thread Starter Post #1 of 8

vafler86

100+ Head-Fier
Joined
Aug 25, 2021
Posts
160
Likes
405
Location
Oslo
Hey,

I prefer to use the BTR7 as a DAC but it keep lagging in DAC mode, but not in bluetooth mode. Is it my phone that cant handle it? anybody experienced any thing like that?

Also I thought i would ask what settings to use in UAPP, BTR APP and Tidal app to optimize the sound to my iem. I use Moondrop Variations, OH10 and Performers 5.
 
Jul 17, 2023 at 6:16 PM Post #2 of 8
Hello I'm brand new here so you may not see my post right away. Nothing wrong at all with using your Fiio as your main DAC.
In fact, it has 2 Sabre 9219 chips integrated into it which is the same chips LG popularized for the phone market initially with the LG V60(I'm on one as we speak). Very good sounding DAC chips for such a small form factor and that's coming from someone who likes Burr Brown or multibit/r2r type DACs generally.
If you have choosable filters I'd recommend the "short" filter.

Now as far as UAPP is concerned, it may very well be an MQA issue. I had countless issues with MQA back when I tried doing the whole Tidal thing. I don't want to offend you, but I would highly recommend dropping Tidal and integrating Qobuz instead since UAPP features it as well. It's factually much better quality and virtually bug free within the UAPP platform. I can send you some research if you'd like on why MQA might not be what you want to be supporting, but that's besides the point.

Try this in the meantime- go to your system & network settings in UAPP and uncheck the box that says "pause on audio focus loss" and check the box labeled " "release USB driver.. home"..... Then in network settings increase your buffer size slightly to either 15 or 18 seconds. Then decrease the network chunk size to 32 or 64 TOPS but 32 should definitely help in your case.

Let me know if that doesn't work.
 
Jul 17, 2023 at 11:25 PM Post #3 of 8
Android and USB audio is a bit of a mess lately, it's not just the BTR7. The Hidizs DH80S does the crackling thing with my Pixel 7 Pro... Sometimes. Not always. Topping G5? Never any issues. Couldn't tell you why.
 
Jul 20, 2023 at 6:48 AM Post #4 of 8
Hello I'm brand new here so you may not see my post right away. Nothing wrong at all with using your Fiio as your main DAC.
In fact, it has 2 Sabre 9219 chips integrated into it which is the same chips LG popularized for the phone market initially with the LG V60(I'm on one as we speak). Very good sounding DAC chips for such a small form factor and that's coming from someone who likes Burr Brown or multibit/r2r type DACs generally.
If you have choosable filters I'd recommend the "short" filter.

Now as far as UAPP is concerned, it may very well be an MQA issue. I had countless issues with MQA back when I tried doing the whole Tidal thing. I don't want to offend you, but I would highly recommend dropping Tidal and integrating Qobuz instead since UAPP features it as well. It's factually much better quality and virtually bug free within the UAPP platform. I can send you some research if you'd like on why MQA might not be what you want to be supporting, but that's besides the point.

Try this in the meantime- go to your system & network settings in UAPP and uncheck the box that says "pause on audio focus loss" and check the box labeled " "release USB driver.. home"..... Then in network settings increase your buffer size slightly to either 15 or 18 seconds. Then decrease the network chunk size to 32 or 64 TOPS but 32 should definitely help in your case.

Let me know if that doesn't work.
Hey,

Thanks alot. That settings did help alot. I still have some issues but they aren't as bad as they used too.

I really tried to lile quboz but it didnt have alot of deep trance music. Im just waiting for Spotify to get hi rea music and i will go back to it. Thank you so much for help
 
Jul 20, 2023 at 3:09 PM Post #6 of 8
Good. MQA needs to be a thing of the past and I can't wait until DAC manufacturers stop pandering to implementation of it. Instead they can shift to bettering their circuitry for pcm and even dsd files. Should be a very positive move to get back on track especially since affordable products won't have to feel obligated to try to spend unnecessary expenses on MQA hardware/software.
 
Jul 20, 2023 at 3:15 PM Post #7 of 8
Hey,

Thanks alot. That settings did help alot. I still have some issues but they aren't as bad as they used too.

I really tried to lile quboz but it didnt have alot of deep trance music. Im just waiting for Spotify to get hi rea music and i will go back to it. Thank you so much for help
Try these settings in addition. Works very well with my 9219 chip.
 

Attachments

  • Screenshot_20230720-141104.png
    Screenshot_20230720-141104.png
    177.7 KB · Views: 0
  • Screenshot_20230720-141131.png
    Screenshot_20230720-141131.png
    306.5 KB · Views: 0
  • Screenshot_20230720-141152.png
    Screenshot_20230720-141152.png
    209.1 KB · Views: 0
  • Screenshot_20230720-141214.png
    Screenshot_20230720-141214.png
    226.8 KB · Views: 0
  • Screenshot_20230720-141230.png
    Screenshot_20230720-141230.png
    204.8 KB · Views: 0
  • Screenshot_20230720-141259.png
    Screenshot_20230720-141259.png
    167.2 KB · Views: 0
  • Screenshot_20230720-141326.png
    Screenshot_20230720-141326.png
    235.5 KB · Views: 0
  • Screenshot_20230720-141353.png
    Screenshot_20230720-141353.png
    303.4 KB · Views: 0
  • Screenshot_20230720-141401.png
    Screenshot_20230720-141401.png
    264.1 KB · Views: 0
Jul 20, 2023 at 3:19 PM Post #8 of 8
Try these settings in addition. Works very well with my 9219 chip.
And on the setting where I have "device native sample rate" selected you can play around with using the variable rate selection if you still have glitching. However I must add that sometimes I indeed had to select "fixed 44100Hz" in order for MQA to not sound bad or glitchy.
 

Users who are viewing this thread

Back
Top