On my S905X box (Mecool KM8) CE 9.2.6 on new kernel (.ng) AAC 2.0 and 5.1 works correctly.
If you have set “Enable AC3 Transcoding” to ON, and AAC is not working, it’s maybe a Matrix thing.
If I remember correctly in Matrix you have to choose 7.1 output instead of 2.0 in Leia, so try that also…
I have configured the Settings/System/Audio the same as with Leia. 7.1 output using HDMI as the sound driver and Allow Passthrough. My receiver supports AC3, DTS, Dolby EX and DTS-HD.
In Matrix, I was able to only get audio from a file with AAC 7.1 when I switch over the Audio output device to PCM. However, in Leia, my Audio output device is kept setting at HDMI but AAC audio is still audible. It could be an internal programming that does the switch automatically,
The other thing I did notice with Matrix using HDMI and AAC encoded file, it would start to drop frames and stutter making viewing impossible after a few seconds. However, when PCM is selected video and audio plays correctly without frames dropping.
You need HDMI Multi PCM as audio device.
As @Ray says, I use “AML-Augesound, HDMI Multi Ch PCM” for my Audio output device and “AML-Augesound HDMI” for my Passthrough output device.
I can send you a SS of my settings that work for me on new kernel (.ng) version, if you need it
Hi, you are correct AML PCM is the correct Audio output device. It behaves the same way as Leia with HDMI. It is kind of odd, the drivers are behaving differently but I guess as long as it works.
old kernel worked differently. If you are at ng you need this if you need multi channel pcm like multi aac sound.
@bossanova808, try tomorrow nightly as it will be ready. TK confirmed your bug, so check if their solution solves your issue.
1 Like
I have the same errors, but not everytime. I can reboot or do systemctl restart kodi most of the time, but sometimes it throws the exact same errors and then addons won’t run properly anymore, not just the coreelec settings addon. Even did a clean install today. At first I thought it fixed my problem, but it’s still there.
Upload full log and ce-debug output…
I tried, but it won’t enter the coreelec config addon if the error occurs. It seems to crash python?
I’ve restarted Kodi untill it seemingly successfully loads, but when I try to upload a log it says ‘failed to paste log, please try again’. Don’t even know if that would include the previous run. The log is too big for pastebin (875KB), any other suggestions?
You can collect them via ssh after error occurance:
dmesg | paste
cat /storage/.kodi/temp/kodi.log | paste
ce-debugAnyone managed to ceemmc on s905x, say, gxl_p212_2g?
I get:
Warning: Could not find ‘dtbo’ partition!
Warning: Could not find ‘dto’ partition!
Error dtb magic: "!
Could not remove node ‘/partitions’ from dtb0!
Failed to write the new partition table to eMMC!
on spit-i7-pro
Spot-I7-Pro:~ # ceemmc -vx
Starting CoreELEC eMMC installation tool...
System is not supported: gxl_p212_2g!
There is NO official support by Team CoreELEC
if you continue to run this tool!
Continue? [y]: y
eMMC size: 0x0003a3e00000 [16GB]
Original partition table:
[mmcblk0p01] bootloader offset 0x000000000000, size 0x000000400000 [4 MB], unkn
[mmcblk0p02] reserved offset 0x000002400000, size 0x000004000000 [64 MB], unkn
[mmcblk0p03] cache offset 0x000006c00000, size 0x000020000000 [512 MB], cache
[mmcblk0p04] env offset 0x000027400000, size 0x000000800000 [8 MB], unkn
[mmcblk0p05] logo offset 0x000028400000, size 0x000002000000 [32 MB], code
[mmcblk0p06] recovery offset 0x00002ac00000, size 0x000002000000 [32 MB], code
[mmcblk0p07] rsv offset 0x00002d400000, size 0x000000800000 [8 MB], code
[mmcblk0p08] tee offset 0x00002e400000, size 0x000000800000 [8 MB], code
[mmcblk0p09] crypt offset 0x00002f400000, size 0x000002000000 [32 MB], code
[mmcblk0p10] misc offset 0x000031c00000, size 0x000002000000 [32 MB], code
[mmcblk0p11] instaboot offset 0x000034400000, size 0x000020000000 [512 MB], code
[mmcblk0p12] boot offset 0x000054c00000, size 0x000002000000 [32 MB], code
[mmcblk0p13] system offset 0x000057400000, size 0x000058000000 [1408 MB], code
[mmcblk0p14] data offset 0x0000afc00000, size 0x0002f4200000 [12098 MB], data
No CoreELEC installation found on eMMC
Install in dual boot mode, CoreELEC and Android on eMMC
Use CoreELEC data from
[1] current used SD or USB device
[2] existing backup on current used SD or USB device
Install in single boot mode, only CoreELEC on eMMC
Use CoreELEC data from
[3] current used SD or USB device
[4] existing backup on current used SD or USB device
Please choose one option? [1/2/3/4]: 3
Free space of 'partition CE_FLASH': 512MB
Warning: Could not find 'dtbo' partition!
Warning: Could not find 'dto' partition!
Free space of 'partition CE_STORAGE': 14234MB
New partition table:
[mmcblk0p01] bootloader offset 0x000000000000, size 0x000000400000 [4 MB], unkn
[mmcblk0p02] env offset 0x000000400000, size 0x000000800000 [8 MB], unkn
[mmcblk0p03] reserved offset 0x000002400000, size 0x000004000000 [64 MB], unkn
[mmcblk0p04] misc offset 0x000006400000, size 0x000002000000 [32 MB], code
[mmcblk0p05] logo offset 0x000008400000, size 0x000002000000 [32 MB], code
[mmcblk0p06] CE_FLASH offset 0x00000a400000, size 0x000020000000 [512 MB], data
[mmcblk0p07] CE_STORAGE offset 0x00002a400000, size 0x000379a00000 [14234 MB], data
Used space of '/flash': 225MB
Used space of '/storage': 177MB
There is enough free space on eMMC for installation!
Install CoreELEC on eMMC.
Continue? [y]: y
Error dtb magic: "!
Could not remove node '/partitions' from dtb0!
Failed to write the new partition table to eMMC!Thanks - will do - so I am looking here - https://relkai.coreelec.org/?dir=ce-19 - for a nightly dated 8/3 or later I guess?
About performance with an S905x with 1GB ram, does Matrix need more processing compared to Leia?
I am not sure if it is the skin but I find running Matrix hang the box if I scan the video too quickly. The caching of the background/posters does not load as quickly and causes hangups.
Any comments on the performance?
If I’m not mistaken, there are plenty of posts that recommend to retire the 1/8 Gig GXL and to upgrade to real ng-device with at least 2 Gig RAM. Now you know why. On the other hand, maybe it’s a slow SD-Card or USB-Stick. An original ng device cost around 30 €, it could be money well spent.
Hi
i am trying to take my MS8 II device on to stable but am facing some issues. if i try to download full image for a clean install, i dont see a ‘generic’ s905x device to choose. i do see a specific entry for M8s II, but if i select that and click download i get ‘not found’ and nothing downloads.
i tried doing an update from in the gui using manual and selecting 9.0.3 (i was running the nightly from 5th March at the time) it updated but CE does not start. i get message that dtb is not supported suggestin to uipdate dtb to a supported version and counts down from 60s then reboots and this carries on in a loop. i cant get in with smb to drop a nightly in to get it going again.
i looked in the device tree folder on the SD and there is only a few dtb in there (odroid and lepotato) nothing for s905x.
i tried copying a working dtb from one of my other ce 19 s905x boxes running the nightly, but still get the same message about unsupported dtb
is support for s905x being dropped from ‘stable’ or did i miss a step or something?
Thanks
Thanks - can download now.
is direct update from nightly to stable from in the gui not supported, and fresh install a requirement, or was i just unlucky and something went awry when i updated?
Are we sure this nightly includes the fix? I don’t see any message at the bottom of the downloads pages as @Portisch mentioned (or perhaps it was someone else?
I ask because unfortunately there is no change in the behaviour - the 25hz file plays at 60hz…