![](/s/cache/10/e0/10e03067734d7b4d3a4cf8c7a1233123.png)
0
Fixed
Some AAC+ files plays in mono
Hello,
using this amazin app I realized that AAC+ streams weren't playing correctly (SBR wasn't applied) so I googled the problem and I read here that using the internal decoding (in beta I KNOW!) will solve it. It did fix it, quality is much better. But then I realized that some streams were decoded in mono (infact it shows 1ch) so I thought I would report this issue. It must be some different encoder those streams use.
By the way why using the phone decoder won't decode the correct way? I tried aac+ files (NOT STREAMS) in Music (standard android app) and the playback is correct.
Thank you
using this amazin app I realized that AAC+ streams weren't playing correctly (SBR wasn't applied) so I googled the problem and I read here that using the internal decoding (in beta I KNOW!) will solve it. It did fix it, quality is much better. But then I realized that some streams were decoded in mono (infact it shows 1ch) so I thought I would report this issue. It must be some different encoder those streams use.
By the way why using the phone decoder won't decode the correct way? I tried aac+ files (NOT STREAMS) in Music (standard android app) and the playback is correct.
Thank you
Answer
![](/s/cache/dc/f7/dcf79ef987a3dff7f95fa884f39afb67.png)
0
Answer
Fixed
Jona (Lead Developer) fa 11 anys
Currently resolved on latest versions of XiiaLive v3.
![](/s/cache/dc/f7/dcf79ef987a3dff7f95fa884f39afb67.png)
Under review
Thanks for your feedback and sorry very delayed response!
What you are seeing is what exactly is being reported by the decoders however there are a couple patches to make sense of this data that we haven't added and need to be added to show 2ch stream.
In regards to your question about decoding. Well it's a bit complex. The way in which AAC is played from a file is different than how is played live from the internet. This is a bug on Android OS decoding properly AAC. Some phones have hardware decoders for AAC and do a great job decoding while others use the Android OS decoders which had bugs on it. Latest versions of the Android OS I believe have this issue resolved.
![](/s/cache/dc/f7/dcf79ef987a3dff7f95fa884f39afb67.png)
Started
This has been resolved will be part of the next beta update.
![](/s/cache/dc/f7/dcf79ef987a3dff7f95fa884f39afb67.png)
If you have sample URLs we can use to verify the issue has been resolved please let me know.
Customer support service by UserEcho