[SoulReaver]

So pass through seems to be working for me with Dolby Digital and DD+ (Atmos) content. Any chance of TrueHD support coming down the line?

No it is a hardware limitation.

If I start watching content that has audio which can passthrough then after stopping that content no PCM audio will play.

This does not happen for me. That being said, it might be because the PCM device is opened too early since in passthrough mode audio playback will be exclusively passthrough only. Debug logs might be useful here to check when the passthrough device is disposed and the ALSA device is opened again. Do you have the option keep audio device enabled?

Thank you for the reply. I have an opportunity to test on another tv and sound system today so I’ll do that and see if the same thing happens and I’ll try the “keep audio device alive” option as well to see if it makes any difference. I could not make the ALSA device open again it seems using Kodi no matter what content was playing after having used passthrough once, so I think you are on to something here. I even tried switching to Pulse Audio and back to ALSA and turning off pass through option entirely but no GUI sounds returned.

[matthew6870]

Alternative youtube by webosbrew group supports this feature when it is recognized as eligible input next to HDMI,LiveTV etc

 
luna-send-pub -n 1 'luna://com.webos.service.eim/addDevice' '{"appId":"org.xbmc.kodi","pigImage":"","mvpdIcon":""}'

When I try with kodi's appId it does not work, Kodi is not recognized as input. Is appId wrong or does Kodi for webOs miss some API support?

Advantage of this is:

1. If Kodi was the last selected input, it will be automatically launched when turning on the TV
   
2. Faster startup performance, since it will be runnning constantly in the background
   

[matthew6870]

^^just found out this is not official API 

https://www.webosbrew.org/pages/luna-ser...ceeim.html

[matthew6870]

I meant "not public"

[SoulReaver]

@sundermann Update for you. So I tested on another TV but same model CX with a different sound system and the exact same issue happens where if passthrough audio is triggered once then it stays in that mode until I play something else on the tv outside of the Kodi app that will trigger PCM mode on the receiver and then GUI sounds return when going back to the Kodi app and playback of non-passthrough Opus and AAC tracks in the YouTube Kodi addon will have audio working again. The "keep audio device alive" setting made no difference in this case so I guess some tv models or AVRs may need a slightly increased delay before trying to open the ALSA device again as I did actually get 2 out of 50 attempts to actually succeed in re-opening the ALSA device after stopping passthrough content.

[falk42]

It is for youtube, then I do beleive DRM is required. Then I can stop my try.
Thank you for the information

Just FYI. Inputstream.adaptive works fine for YouTube on webOS if you compile it yourself and install from zip. Using it right now.

@SoulReaver Interesting! Compiled inputstream-adaptive as per the instructions and installed the .zip on the latest version (using a LG CS here). The addon shows as installed and the settings can be changed, but neither YouTube nor other addons play any videos and show an "inputstream-adaptive not working" error instead. Am I overlooking the obvious (is inputstream-ffmpeg also needed?) or did you change any specific settings?

[SoulReaver]

It is for youtube, then I do beleive DRM is required. Then I can stop my try.
Thank you for the information

Just FYI. Inputstream.adaptive works fine for YouTube on webOS if you compile it yourself and install from zip. Using it right now.

@SoulReaver Interesting! Compiled inputstream-adaptive as per the instructions and installed the .zip on the latest version (using a LG CS here). The addon shows as installed and the settings can be changed, but neither YouTube nor other addons play any videos and show an "inputstream-adaptive not working" error instead. Am I overlooking the obvious (is inputstream-ffmpeg also needed?) or did you change any specific settings?

I used these webOS specific instructions and ran this command:

Code:

make -j$(getconf _NPROCESSORS_ONLN) -C tools/depends/target/binary-addons PREFIX=$HOME/kodi/build/tools/webOS/packaging ADDONS="inputstream.adaptive"

and then just manually zipped the inputstream.adaptive folder and installed from zip in Kodi.

[matthew6870]

Hello.
I am trying to build Kodi according to https://github.com/xbmc/xbmc/blob/master...E.webOS.md

I am stuck at the:

Code:


./configure --prefix=$HOME/kodi-deps --host=arm-webos-linux-gnueabi \--with-toolchain=$HOME/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot \--enable-debug=no


with error

Code:


checking whether the C compiler works... no
configure: error: in `/home/ubuntu/kodi/tools/depends':
configure: error: C compiler cannot create executables


Can you help me?

[falk42]

Just FYI. Inputstream.adaptive works fine for YouTube on webOS if you compile it yourself and install from zip. Using it right now.

@SoulReaver Interesting! Compiled inputstream-adaptive as per the instructions and installed the .zip on the latest version (using a LG CS here). The addon shows as installed and the settings can be changed, but neither YouTube nor other addons play any videos and show an "inputstream-adaptive not working" error instead. Am I overlooking the obvious (is inputstream-ffmpeg also needed?) or did you change any specific settings?

I used these webOS specific instructions and ran this command:

Code:

make -j$(getconf _NPROCESSORS_ONLN) -C tools/depends/target/binary-addons PREFIX=$HOME/kodi/build/tools/webOS/packaging ADDONS="inputstream.adaptive"

and then just manually zipped the inputstream.adaptive folder and installed from zip in Kodi.

Thank you, I followed the tutorial from scratch (not actually building Kodi completely though) and that did the trick! Turns out that I did indeed miss the obvious by not building the inputstream.adaptive addon for the correct platform ...

[SoulReaver]

@SoulReaver Interesting! Compiled inputstream-adaptive as per the instructions and installed the .zip on the latest version (using a LG CS here). The addon shows as installed and the settings can be changed, but neither YouTube nor other addons play any videos and show an "inputstream-adaptive not working" error instead. Am I overlooking the obvious (is inputstream-ffmpeg also needed?) or did you change any specific settings?

I used these webOS specific instructions and ran this command:

Code:

make -j$(getconf _NPROCESSORS_ONLN) -C tools/depends/target/binary-addons PREFIX=$HOME/kodi/build/tools/webOS/packaging ADDONS="inputstream.adaptive"

and then just manually zipped the inputstream.adaptive folder and installed from zip in Kodi.

Thank you, I followed the tutorial from scratch (not actually building Kodi completely though) and that did the trick! Turns out that I did indeed miss the obvious by not building the inputstream.adaptive addon for the correct platform ...

Glad to hear it worked

[SoulReaver]

Hello.
I am trying to build Kodi according to https://github.com/xbmc/xbmc/blob/master...E.webOS.md

I am stuck at the:

Code:


./configure --prefix=$HOME/kodi-deps --host=arm-webos-linux-gnueabi \--with-toolchain=$HOME/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot \--enable-debug=no


with error

Code:


checking whether the C compiler works... no
configure: error: in `/home/ubuntu/kodi/tools/depends':
configure: error: C compiler cannot create executables


Can you help me?

I think you may be missing some required packages to build Kodi in general. Check this page and try again.

[sundermann]

When I try with kodi's appId it does not work, Kodi is not recognized as input. Is appId wrong or does Kodi for webOs miss some API support?

It needs supportGIP: true in appinfo.json though we might run into trouble when submitting it to the official app store when we set this unofficial flag

Can you help me?

Make sure you have set the toolchain path correctly. It seems it does not find the compiler.

@SoulReaver can you create a debug log including your PCM playback issue?

[SoulReaver]

@SoulReaver can you create a debug log including your PCM playback issue?

Sure thing. I have some time tomorrow where I’ll try and capture it in the debug log including maybe if I’m lucky one successful attempt at re-opening the ALSA device so we can see what’s actually happening.

@sundermann Here is the debug log.

[matthew6870]

@SoulReaver thank you, but that did not helped

@sundermann toolchain path is correct

these are the logs from config.log

Code:


configure:4923: checking for arm-webos-linux-gnueabi-g++
configure:4946: found /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-g++
configure:4958: result: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-g++
configure:5058: checking for arm-webos-linux-gnueabi-gcc
configure:5090: result: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc
configure:5488: checking for C compiler version
configure:5497: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc --version >&5
./configure: line 5499: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc: cannot execute binary file: Exec format error
configure:5508: $? = 126
configure:5497: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc -v >&5
./configure: line 5499: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc: cannot execute binary file: Exec format error
configure:5508: $? = 126
configure:5497: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc -V >&5
./configure: line 5499: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc: cannot execute binary file: Exec format error
configure:5508: $? = 126
configure:5497: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc -qversion >&5
./configure: line 5499: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc: cannot execute binary file: Exec format error
configure:5508: $? = 126
configure:5497: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc -version >&5
./configure: line 5499: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc: cannot execute binary file: Exec format error
configure:5508: $? = 126
configure:5528: checking whether the C compiler works
configure:5550: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc conftest.c >&5
./configure: line 5552: /home/ubuntu/kodi-dev/arm-webos-linux-gnueabi_sdk-buildroot/usr/bin/arm-webos-linux-gnueabi-gcc: cannot execute binary file: Exec format error
configure:5554: $? = 126
configure:5594: result: no


[izprtxqkft]

Exec format error

probably wrong architecture executable

https://www.cyberithub.com/solved-cannot...mat-error/