USB Audio Player PRO (UAPP): 24- and 32-bit playback, ubiquitous USB audio support for Android

[LightBlue77]

will this do the trick to connected LG V20 to mojo and be detected by uapp? it's Romanian, but you'll get the point. The title says it all.
https://altex.ro/cablu-adaptor-usb-2-0-type-c-plug-usb-micro-b-plug-hama-135713-0-75m/cpd/AIS135713/

 

[ThanosD]

Guys, is there a way to exclude the m3u files from the database? For some reason, deleting them does not do the trick

 

[Davy Wentzler]

Deducing from the above: if UAPP were to ignore all erroneous, negative "Duration" metadata values it reads (and/or setting them as "00:00:00"), the issue could be circumvented? I'm no coder but the thought came up.

Edit: Uh, I see now all the missing metadata is loaded into UAPP at playback start, not before it when just library browsing. So the only mystery left is the "Duration" metadata of the transcoded files, which shows ok in the BubbleUPnP app but shows weird values in UAPP.

I downloaded Minimserver on my Windows 10 PC, set it to serve a folder with many different audio tracks. (did not install the Minimstreamer)
Played tracks in UAPP using UPnP/DLNA, as you found out, all ok.
Then started the UPnP renderer and started Bubble on another Android device. Select UAPP as UPnP render target. Played several tracks from the Minimserver. All play ok, including display of duration in the current song display and meta data dialog. I didn't use a DAC, but the Direct driver of my S7, in case that matters (although I don't think so).

I assume you are running 5.0.3 as well?

 

[anttipi]

I downloaded Minimserver on my Windows 10 PC, set it to serve a folder with many different audio tracks. (did not install the Minimstreamer)
Played tracks in UAPP using UPnP/DLNA, as you found out, all ok.
Then started the UPnP renderer and started Bubble on another Android device. Select UAPP as UPnP render target. Played several tracks from the Minimserver. All play ok, including display of duration in the current song display and meta data dialog. I didn't use a DAC, but the Direct driver of my S7, in case that matters (although I don't think so).

I assume you are running 5.0.3 as well?

Yeah, it's 5.0.3

I exchanged some e-mails with bubbleguuum when doing testing.

According to him, the FLACs transcoded by BubbleUPnP are "not seekable and it is probable that UAPP
decoders rely on that to compute a duration and produce this bogus value" (meaning the negative Duration metadata as seen in my previous screenshot).
Bubbleguuum also wrote:
"BubbleUPnP transmits the proper duration via XML metadata that UAPP
could use as a fallback, but that's not going to make the FLAC seekable."

Personally, what I saw in the log was a TagLib metadata reading error. Possibly related to what the bubbleguuum quotes above refer to?

 

[anttipi]

Edit: double post

 

[Davy Wentzler]

Yeah, it's 5.0.3

I exchanged some e-mails with bubbleguuum when doing testing.

According to him, the FLACs transcoded by BubbleUPnP are "not seekable and it is probable that UAPP
decoders rely on that to compute a duration and produce this bogus value" (meaning the negative Duration metadata as seen in my previous screenshot).
Bubbleguuum also wrote:
"BubbleUPnP transmits the proper duration via XML metadata that UAPP
could use as a fallback, but that's not going to make the FLAC seekable."

Personally, what I saw in the log was a TagLib metadata reading error. Possibly related to what the bubbleguuum quotes above refer to?

Ok, so the issue is in the transcoding (which it didn't do here in my test). Could you please tell me how I get it to transcode? I only saw an option in Bubble to limit to 48kHz, not 96kHz (although that would probably suffice for the test)

 

[anttipi]

Ok, so the issue is in the transcoding (which it didn't do here in my test). Could you please tell me how I get it to transcode? I only saw an option in Bubble to limit to 48kHz, not 96kHz (although that would probably suffice for the test)

A new BubbleUPnP Server version was released on Dec. 22nd, which added the option to transcode files >96kHz. For some reason, I had to re-install the update manually to get the new transcoding options visible, even though the version number was updated correctly after the automatic update. Not sure if that's what happened to you too. https://bubblesoftapps.com/bubbleupnpserver/

Anyway, it's good to have the transcoding option now for us with the Dragonflies (among others). Needless to stream as 192kHz when the cap is at 96kHz. Maybe doesn't matter in wifi but mobile bandwidth might be more scarce

 

[Davy Wentzler]

A new BubbleUPnP Server version was released on Dec. 22nd, which added the option to transcode files >96kHz. For some reason, I had to re-install the update manually to get the new transcoding options visible, even though the version number was updated correctly after the automatic update. Not sure if that's what happened to you too. https://bubblesoftapps.com/bubbleupnpserver/

Anyway, it's good to have the transcoding option now for us with the Dragonfly Red. Needless to stream as 192kHz when the cap is at 96kHz. Maybe doesn't matter in wifi but mobile bandwidth might be more scarce

Ok, I only have the BubbleUPnP app itself.

 

[Davy Wentzler]

A new BubbleUPnP Server version was released on Dec. 22nd, which added the option to transcode files >96kHz. For some reason, I had to re-install the update manually to get the new transcoding options visible, even though the version number was updated correctly after the automatic update. Not sure if that's what happened to you too. https://bubblesoftapps.com/bubbleupnpserver/

Anyway, it's good to have the transcoding option now for us with the Dragonflies (among others). Needless to stream as 192kHz when the cap is at 96kHz. Maybe doesn't matter in wifi but mobile bandwidth might be more scarce

Edit: never mind, found it. So the current song display shows the duration as --:--, only the meta data dialog shows a weird number.

So, the duration in the stream is set to 9223372036854775808 (that's microseconds but still a bit big), so I assume the duration field in the meta data is not filled in correctly, although the UPnP meta data might be (but is unused by UAPP atm).

 

[anttipi]

So, the duration in the stream is set to 9223372036854775808 (that's microseconds but still a bit big), so I assume the duration field in the meta data is not filled in correctly, although the UPnP meta data might be (but is unused by UAPP atm).

I'm not 100% sure I understand what you mean by "the duration field in the meta data is not filled in correctly", but be that as it may, Android BubbleUPnP shows the duration metadata correctly when browsing and, although the transcoded files are not seekable, the ongoing progress and the total duration at least are shown in BubbleUPnP's Now playing view.

What I found weird was that the bogus metadata value is always the same identical negative value for every to-be-transcoded track, regardless of their actual length.

I don't mind the metadata but would be nice to see the progress display also in UAPP. I have no idea how hard or easy that is to implement, I just had a vague wish for a "fallback solution", which according to bubbleguuum (and also according to you, if I read you right) could be doable.

 

[DBaldock9]

On my rooted DP-X1 - if the V4A FX v2.5.0.4 driver is installed/enabled, then UAPP v5.0.3 will not operate in HiRes or Bit Perfect mode, apparently due to driver conflicts.

If the V4A driver is enabled, and UAPP "Internal Audio Driver" is set to "HiRes Direct Driver", it won't play music, and displays "Failed to find or setup HiRes DAC!".
If the V4A driver is enabled, and UAPP "Internal Audio Driver" is set to "Original Android Driver", and "Internal HiRes Audio > Bit Perfect Mode" is not set to "Off", then the audio that does play is very distorted.

UAPP does play music, with V4A effects enabled, when UAPP "Internal Audio Driver" is set to "Original Android Driver", and "Internal HiRes Audio > Bit Perfect Mode" is set to "Off".
But the V4A driver has to be Uninstalled, and the DP-X1 rebooted, before UAPP can use its HiRes driver / Bit Perfect mode.

Is there some log data that I could provide, which could be used for a workaround, that might allow both drivers to be loaded and switched between (without having to reboot)? Thanks!

 

[Davy Wentzler]

On my rooted DP-X1 - if the V4A FX v2.5.0.4 driver is installed/enabled, then UAPP v5.0.3 will not operate in HiRes or Bit Perfect mode, apparently due to driver conflicts.

If the V4A driver is enabled, and UAPP "Internal Audio Driver" is set to "HiRes Direct Driver", it won't play music, and displays "Failed to find or setup HiRes DAC!".
If the V4A driver is enabled, and UAPP "Internal Audio Driver" is set to "Original Android Driver", and "Internal HiRes Audio > Bit Perfect Mode" is not set to "Off", then the audio that does play is very distorted.

UAPP does play music, with V4A effects enabled, when UAPP "Internal Audio Driver" is set to "Original Android Driver", and "Internal HiRes Audio > Bit Perfect Mode" is set to "Off".
But the V4A driver has to be Uninstalled, and the DP-X1 rebooted, before UAPP can use its HiRes driver / Bit Perfect mode.

Is there some log data that I could provide, which could be used for a workaround, that might allow both drivers to be loaded and switched between (without having to reboot)? Thanks!

I'm very sorry, but I really cannot help with this.

 

[buonassi]

I'm very sorry, but I really cannot help with this.

Hey, at least you're replying to everyone! I've said it before, but man are you guys good at customer engagement/support. Wow.

I'm happy with my setup using UAPP - fully loaded, with peq/mqa etc. I just keep subscribed to see the awesome support and trust that if I have an issue, you'll be there for help!

 

[Primus_111]

Hi Davy - thank you for the MQA updates! Now I'm trying to choose between Tidal and Qobuz. Using LG G7, Android 8.0, and assorted headphones driven directly by the G7 Quad DAC. My questions:

1. Does the UAPP MQA decoder provide any benefit over the built-in LG G7 decoder? Unlike Hippocamp, I don't use any external DACs.
2. How should I set the HiRes driver flags, and Bit-perfect settings?
3. (Unrelated) What sort of benefits could I expect from the Morph-it headphone profiles? Do they operate in floating 32-bit domain like equalizers?

Hi Davy

Excellent addition. Just wondering if the new integrated MQA decoder provides any benefit over the MQA capabilities already in my combo of LG G7 + Dragonfly Red (currently have the HiRes driver flags set to "MQA").

Thanks!

 

[Davy Wentzler]

Hi Davy - thank you for the MQA updates! Now I'm trying to choose between Tidal and Qobuz. Using LG G7, Android 8.0, and assorted headphones driven directly by the G7 Quad DAC. My questions:

1. Does the UAPP MQA decoder provide any benefit over the built-in LG G7 decoder? Unlike Hippocamp, I don't use any external DACs.
2. How should I set the HiRes driver flags, and Bit-perfect settings?
3. (Unrelated) What sort of benefits could I expect from the Morph-it headphone profiles? Do they operate in floating 32-bit domain like equalizers?

1) No
2) The app will inform you automatically if the settings are not correct for MQA decoding. If you don't see anything, you can be reasonably sure they are correct
3) Everything that processes sound is done in 32-bit floating point (except MQA decoding, which cannot be used together with any processing, it needs bit-perfect). With MorphIt you can simulate how other headphones would sound, without actually buying them. Of course there is a limit to that. And there are profiles that 'optimize' frequency response for use in public transportation (subway) for example, boosting frequencies that would otherwise compete with surrounding sounds.