Ducking happening in hi rez files in usb Allow symphonium

Support
, ,
1

App version

15.0.0B1

Issue description

High resolution audio files are being fucked and causing the sound to be off. It only happening for the high resolution files that is 24bit 88.1khz. It is happening in normal playback as well as the other two modes usb exclusive and android ones. Was not happening in the past builds for the same scenario

Device type

Phone

Media provider

Jellyfin

Steps to reproduce

Plug headphones and play any high resolution audio above 24bit 88.2khz

Additional information

Was not happening in old versions

I searched existing issues first

on

I understand that logs are mandatory

on

Log upload name / description

Current output summary Captured from USB. Android lane: Status: Reported by Android audio profiles PCM: 32-bit @ 48, 88.2, 96, 176.4, 192, 352.8, 384 kHz; 32-bit float @ 48, 88.2, 96, 176.4, 192,

2

I had something similar happen when playing hi-res files in the car. The sound was totally messed up, sounded like the speakers had been placed under water. After I set “Prefer hardware-accelerated codecs” to on, the sound went back to normal. :man_shrugging:

3

Tried it not working for me also my crinear protocol max was running on uac2 by default so I thought if I change it to uac 1 it will solve the problem but that also don’t seem to work.

4

I need the actual debug logs reproducing the issue… And details about “off” meaning.

@TheKingPin and you opened sn issue about that right ? :wink:

5

Not yet, as it happened in the car (while driving), so it was not possible to activate debug in the app and so on.

6

Yeah the debug button is completely different toggle than the prefer hardware one :wink:

7

haha Well I would need to press it twice… Unless you want 45 minutes of logs :wink:

8

This is a beta with a major changes, yes I would have taken the 45 minutes logs specially with … Google that takes 8 days to validate a build.

So far 4 reports of possible issues and 0 actual logs, so can’t fix so can’t push and so the delays grow fast.

With current Google behavior I need reactive users :slight_smile:

9

Understood, I’m not trying to frustrate you even more. I will try and get the logs for you later today and make a proper issue. :slight_smile:

10

Thanks, and yes I’m quite frustrated by Google right now, it completely breaks my normal build workflow that’s a fucking pain.

11

I have just uploaded the logs with the name overhaul4dabi. I have used the usb dac in both uac1 and uac2 mode with turning on a and off many things which doesn’t seem to solve anything.