Thanks for all your work on this @Portisch I’ll refresh my build with today’s nightlies - is this correct?
For my education, could you indicate what code changes were made to achieve this, please?
Joe
I’m not sure exactly what the differences are between Best Match and Optimised the Kodi docs says:
Best Match - Output properties are set to always be as close a match to the source properties as possible.
Optimised - Output properties are set at the start of playback and will not change if the properties of the source change
I’m not sure what counts as a source change.
@Joe_90 looks like these changes Commits · CoreELEC/xbmc · GitHub
Thanks @nissel - I did look on github, but in the wrong place 
@Portisch - the nightly build seems to have incorporated yesterday’s changes ok, thanks!
With the setting “best” selected, the various input formats (2.0/3.0/4.0/5.0) all seem to map correctly when I set Kodi speakers to 5.1 or 7.1.
My only concern is that the re-mapping may be a little too rigid for users who have systems who genuinely have 5.0 speaker systems (fullrange speakers with no subwoofer) and have configured Kodi for 5.0 or 7.0 and try to play back these input format files. I still wonder if the most flexible option would be to ensure that the ALSA mapping table selects the correct channel layout as per my previous post - Amlogic-NO discussion - #2898 by Joe_90
Tell me one…
Point me to the error of the Alsa mapping - I have no idea.
@Portisch - I have gone back earlier in this long thread. Another user @boxr4k and myself were exchanging a lot of posts on this 5.0 issue from here - Amlogic-NO discussion - #2212 by boxr4k to the most relevant one here - Amlogic-NO discussion - #2223 by boxr4k
Other posts by me - Amlogic-NO discussion - #1824 by Joe_90
and recently - Amlogic-NO discussion - #2518 by Joe_90
I maybe just did spot some difference in the driver source.
What device you are using? N2?
Yes - N2+ this is my daily use machine. The NG build works perfect but the ALSA mapping in in the older kernel is much simpler. I think that is what @boxr4k spotted.
4.9 only used 2.0, 3.1, 5.1 or 7.1. This is why it does work now same.
I did check NG again and it choose default setting 2.0 for the mapping on boot, also when 7.1 is adjusted in audio settings.
Now I start a 2.0 → 3.1 flac and it choose 3.1.
Then I start a 4.0 → 5.1 and it choose 5.1.
Then 6.0 → 7.1 it uses 7.1.
Then back to 5.0 and it still uses 7.1.
Only a reboot reset it.
Over HDMI it shows 2.0, 3.1, 5.1 and finally 7.1.
So I think it’s already correct in NO now?
Or I go to remove all other channel setups again and leave only thoose left with LFE channel.
Is it better to use user value he did adjust in audio settings or use dynamic the next matching x.1 mapping?
Yes - much simpler in 4.9. But I think that what @boxr4k and I were getting at was the the new mapping is actually selecting the wrong option from the list when there is an unusual number of channels in the input audio like 3 or 5 (or even 4). We thought that maybe the correct AE_CH_LAYOUT was not being selected when the number of channels was 3 or 4 or 5 and that by changing the sequence it would better. For example a 5 channel input should result in AE-CH_LAYOUT_5_0 (option 0x0a) being used. We thought that maybe the 4.1 (option 0x07) was being selected in error.
No, it did pick always the correct layout. But it looks like be limited by the sound card for mappings only with LFE.
No idea what is now the “correct” fix.
Sorry - @Portisch , I was interrupted typing my previous reply and your new one has just arrived.
I’m not 100% sure either! Perhaps leave your fix to pick the next highest x.1 option for now and see if there is a feedback from users. I think most “audiophile” users are probably not using CE but are spending big euros/dollars on dedicated hardware with magic DACs etc!
I will make a new test image a bit later.
I will remove this best match fix and limit kernel channel mappings.
1 Like
@Joe_90 Please try with this image:
Start with 2.0 up to 7.1.
1 Like
hello, i’m getting this error when i try single to set up single boot mode with ugoos sk1 on CE-NO (latest)
the latest android 14 v2.0.4 was installed before with burning tool.
maybe this brought up the error?
should i flash back to android 11 before trying a single boot emmc installation?
thx in advance
wiki not updated for CE-NO?
Did you really read the link?
1 Like