Ibasso DX180 (Android 13)

Issue description:

I have noticed Synfonium (trial version at this time) does not play well on iBasso DX180 (Android 13). Especially noticeable in quieter parts of the music, the sound comes through pixelated (if this is the proper term to describe it), sort of broken and inconsistent. Are there known issues with it yet? Are there any settings that can be changed?
thx

Logs:

Upload description: sngreen

Additional information:

 
The described problem is audible at the beginning, when audience is clapping hands. It comes through unnatural and broken. Once music plays, it appears to be fine.
I do not experience this issue with the other music apps.
 

Reproduction steps:

 
Activated debug mode.
Started playback.
After a minute or so shared logs.
 

Media provider:

Any provider

Screenshots:

     

Please upload the file to https://upload.symfonium.app to see if it’s an ffmpeg issue.

You have enabled the EQ engine but are not actually using it, disable it as your device may embed bad libraries causing this too.

You can uncheck the option prefer internal decoder in settings/playback to use the device decoder and see if this changes something.

I did try it earlier, it did not help.

Try what there’s 4 combinations here proposed :wink:

And I’d still need the file to repro.

Activated all four (two are marked as experimental).
No change.
Uploaded logs.

I fast-forwarded it a bit, made the second upload.
In the quieter parts it is a complete mess. It is Ok when it gets louder.
-s

I’m only talking about 2 settings and none are experimental.

So not sure at all what you are changing here.

So disable the EQ, uncheck the prefer internal decoder, don’t touch the rest, press restore default just in case before unchecking internal decoder.

Then to be sure force kill the app and start a new playback so I have everything in the logs.

And for the third time : Can you upload that audio file to https://upload.symfonium.app so I can reproduce ?

I was under an impression you get the whole picture from the logs … sorry, I misunderstood. I don’t think I have an equipment to record the output - how do I do it?

I only see some stuff when playback starts and not all the combination, specially when you talk about experimental options that I did not asked you to touch at all.

And I do not need the output record I need the flac file that you play to see if the file have something special in it break the packet parser.

I see. Now I uploaded the file. First, the audience, it does not come through as smooth (and realistic) as it is recorded, obviously. And then after about 3/4 it goes to quieter parts; you should hear it is not reproduced well again. It appears to be fine when the music is, for a better word, full and forceful.
thx

So no issue reproducing here on all devices.

But it’s an hi res file, are you listening on a BT headphone?

It can be a BT codec issue but properly handling such hi res stuff when compressing it.

The issue is there, it is not going away, regardless of the headphones.
I tried with these;

Bluetooth;

  • Soundcore Space A40
  • Sony wh-1000xm4
  • Sennheiser Momentum 4

Wired headphones;

  • Bayerdynamic DT770 (32Ohm)
  • HifiMan Sundara

Makes no difference, it is all the same.

Fast-forward that tune I uploaded to after 10:49, in the complex parts (with many instruments) it is almost unlistenable. It only gets ‘normal’ (perceivably) once the music gets louder, as if it forces its way through.

Unless there is something wrong with my device, but then again, the other player apps play fine and without issues. Which devices did you try it on?

On pixels, but again what options have you tested ? Are you sure you disabled the EQ ?

EQ is disabled through Mongo, yes. It was never on.

The EQ engine inside Symfonium that was definitively enabled in the logs as said in a previous post.

So let’s start again :

  1. Disable EQ engine in Symfonium (Settings/Playback/Playback/Equalizer)

And try and report with new logs with a proper playback start (So clicking on that song in a list)

  1. On Settings/Playback/Decoding press restore defaults

And try and report with new logs with a proper playback start (So clicking on that song in a list)

  1. On Settings/Playback/Decoding uncheck prefer internal decoder

And try and report with new logs with a proper playback start (So clicking on that song in a list)

Some thing (no change).

I’ve written 3 times: “and report with new logs with a proper playback start (So clicking on that song in a list)”

and yet not a single log :frowning:

So at this point I think it’s safer to just assume that the app is broken on that device and since I do not own one there’s not much I’ll be able to do to fix it sorry.

It has been a busy day for me today, just uploaded the log again.
The device is brand new, all apps work as intended, except one. So the probability it is the device are almost null. Also you do not tell what devices you tested it on. You should be testing it on every device this app could be played on, or how else would you know!? There is sure a bug in Symfonium somewhere, but where - I am not a developer to tell. Except that I hear it when using this app.

Every device is different, and device manufacturers can modify stuff to their linking. It is not like that every device runs the exact same Android operating system. Manufacturers add their own software packages and libraries. If you are not a millionaire developer and can afford to buy every single device on the market (and have the time to test on all of them), it is virtually impossible to guarantee that every bit of the app works the same on every device.

For example I have a Samsung device, and sometimes on my device things look different from how they look on the Google devices, because Samsung uses a different front end to the operating system. So Tolriq has to fix stuff specifically for Samsung devices. Your device is not even a smartphone and uses custom audio hardware, for which for sure the manufacturer included specific drivers or libraries, which might be the problem here. That “all apps work as intended” is not necessarily an indicator for anything. They might not use the specific functions Symfonium uses. It is more likely that your device deviates from the standard that Symfonium currently relies on. But it is also possible that the program code can work around such an issue, if it is only known what the exact issue is.

This is just to help you understand why there can be an issue with your specific device, even if other Android 13 devices do not have that issue. The only way for Tolriq to find out what the issue is is that you help him by providing the neccessary data in form of logs, because only then he can (possibly) see the specific error occuring. So if you want Symfonium to work on your device, I would recommend you work with him and provide what he asks for, and do not assume that there is more magic in all of this than in fixing a strange noise that a car makes: you have to bring the car to the garage in that case - and providing logs, probably multiple times, is the only way to bring your device into the Symfonium garage :wink:

@splinter
I agree completely, you made it very clear for me. Now am able to see the light. :slight_smile: