322 replies to this topic

[ntj]

 

 

 

Indeed it is this one.

Thank you for confirming this.

BUT since i was using it and have no sound, maybe Dragnan can comment if he does something more/different?

Are the alsa Oss plugins in the correct folder?
Try to install alsa tools and play a wav file using the aplay command. Then write the output here.

 

Tried aplay and an wav-file and got this (but could not hear any sound)

 

Playing WAVE '/media/error.wav' : Signed 16 bit Little Endian, Rate 11025 Hz, Mono

 

Then opened KODI and tried alsa playing when KODI was running and got this:

 

ALSA lib ../../alsa-plugins-1.1.9/oss/pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp

aplay: main:828: audio open error: Device or resource busy

.

So ALSA seems to think it is playing and also alarms if i try to do things in parallell

 

 

 

This is logical, you can't run Kodi and aplay at the same time, they both claim the ALSA device.

Yes, that was my point

 

Tested some more with aplay and playing a wav file works partly, as i found out that the sound works on optical out (S-PDIF)  on my Ultimo4k but not on HDMI out

Sadly no sound on any output in KODI

[rantanplan]

I'm a little confused about the discussion.
Nothing is changed in version 8.
Changes have been made in the develop.
Seen in this way, version 8 no longer leads to a meaningful result.
What is more important is the question of what errors still happen in an application from the development?
So if you want to watch Kodi, you should try the image from the develop branch directly.
Kodi from version 8 does not work. This is known and will not be fixed in version 8, but rather in the subsequent version.

[Piterek79]

In my vusolo4k very strange.

 

Kodi is up and running . No sound from kodi despite this crackles

 

root@vusolo4k:/hdd/music# ps | grep kodi

13643 root      6712 S    /bin/sh -c unset PYTHONPATH;kodi;kodiext -T

13644 root      6844 S    {kodi} /bin/sh /usr/bin/kodi

13652 root      789m S    /usr/lib/kodi/kodi-stb

13744 root      2656 S    grep kodi

 

Aplay is working fine

 

root@vusolo4k:/hdd/music# aplay captcha.wav

Playing WAVE 'captcha.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono

root@vusolo4k:/hdd/music# aplay captcha.wav

 

Regards, 

[dragnan]

I'm a little confused about the discussion.
Nothing is changed in version 8.
Changes have been made in the develop.
Seen in this way, version 8 no longer leads to a meaningful result.
What is more important is the question of what errors still happen in an application from the development?
So if you want to watch Kodi, you should try the image from the develop branch directly.
Kodi from version 8 does not work. This is known and will not be fixed in version 8, but rather in the subsequent version.

Yeah, all my testing is on development image.

[ntj]

 

You had the dsp enabled but we never understand how. Did you use OpenMultiboot on your box with another image installed?
Because for me those devices are never available nor on the Solo4K nor on the Duo4K.
So now you are also back to the "normal" situation.
And as already explained it is VU+ that needs to fix this. Vu+ enable Kodi in there BSP but we have no sound at all making it totally useless.

 

I never could have imagined, this could be the reason - but thanks for that hint.

 

I actually did have OMB installed - and OpenSPA - but I never imagined, there could be any connection between the two images. So I just tested it. If I install OMB and boot to OpenSPA - then turn off, remove  the USB Key and boot again, /dev/dsp is enabled and can be used for sound in Kodi.

 

So what makes this difference? I am aware, that the OpenPli team is not willing to do the manual adaptations - but is it possible to somehow hack this as a "normal" user? I really hate all the other images due to UI modifications. OpenPli is super clean and easy to use - the best image of them all. 

 

 

 

 

I'm a little confused about the discussion.
Nothing is changed in version 8.
Changes have been made in the develop.
Seen in this way, version 8 no longer leads to a meaningful result.
What is more important is the question of what errors still happen in an application from the development?
So if you want to watch Kodi, you should try the image from the develop branch directly.
Kodi from version 8 does not work. This is known and will not be fixed in version 8, but rather in the subsequent version.

Yeah, all my testing is on development image.

 

Testad now with latest dev with the "special" arrangement tested by Dragnan with multiboot  with openspa. (Ulimo4k)

Have now sound in KODI but only works with "audio downmix" and it is a choppy sound a little bit out of sync.

So exept missing "dev/dsp" from standard openpli dev, install there must be something more to give this choppy sound.

[Pr2]

Please don't trust the dragnan test he was using OpenATV as main image and OpenPLi with OpenMultiboot so he was using the OpenATV kernel that is patched to enable those device.
So you I can just confirm that it has never worked in OpenPLi.

[dragnan]

Please don't trust the dragnan test he was using OpenATV as main image and OpenPLi with OpenMultiboot so he was using the OpenATV kernel that is patched to enable those device.
So you I can just confirm that it has never worked in OpenPLi.

Well - no. Openpli Dev is main image. Just the kernel is openSpa. OpenAtv is not being used at all.

The choppy, out of sync sound is on my setup too - but when I stop playback and start it again, the sound is no longer choppy. I watched a movie on Viaplay on Sunday using Kodi on openpli 8 Dev with the Viaplay plugin - worked fine. Also Netflix, German tvnow and some other plugins work acceptable using the stop start workaround and the openSpa kernel

[murphys_law]

I am running into trouble compiling the feed for Kodi to try out the sound issues on my vusolo4k. Recently changes were made to move downloads from archive.vuplus.com to code.vuplus.com. See this commit:

https://github.com/vu-plus/meta-vuplus/commit/8dbde44fe617b22c9a4ffcf8a7c910e46668ae4c

However the file

http://code.vuplus.com/download/release/kodi/KodiGLESPL_vusolo4k_20180124p0.tar.gz

doesn't exist, leading to an error in do_fetch:

--2021-03-26 16:26:06--  http://code.vuplus.com/download/release/kodi/KodiGLESPL_vusolo4k_20180124p0.tar.gz
Resolving code.vuplus.com (code.vuplus.com)... 13.209.0.12
Connecting to code.vuplus.com (code.vuplus.com)|13.209.0.12|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2021-03-26 16:26:07 ERROR 404: Not Found.

Does anyone have the file handy so I can put it in place manually? I don't know what license this thing is though.

 

Or can we use kodi instead of kodiegl?

 

Thanks!
 

 

[blzr]

in vu repo package date has been changed:

http://code.vuplus.c...8ca7e6b;hb=HEAD

PKGDATE="20190124p1"

so I assume you need to adjust acccordingly in "our" vuplus bsp,

should help

Edited by blzr, 26 March 2021 - 21:31.

[WanWizard]

It has disappeared for all boxes.

 

Appearently we miss all the updates from http://code.vuplus.c...af8e4becbd73411.

 

I've asked VU+ to update the BSP.

[murphys_law]

Thanks guys. It compiles now, will report if it works.

 

in vu repo package date has been changed:

...

PKGDATE="20190124p1"

so I assume you need to adjust acccordingly in "our" vuplus bsp,

should help

 

It has disappeared for all boxes.

 

[murphys_law]

 

Thanks guys. It compiles now, will report if it works.

 

in vu repo package date has been changed:

...

PKGDATE="20190124p1"

so I assume you need to adjust acccordingly in "our" vuplus bsp,

should help

 

It has disappeared for all boxes.

 

No workie in dev branch. Retrying in stable branch.

Edited by murphys_law, 27 March 2021 - 15:52.

[A.A.]

Just for info, I found this thread about kodi 18.x sound issues and more (OpenATV).

 

https://www.opena.tv...idevine-34.html

 

I was looking for widevine cdm for mips which cannot be found.

Iirc kodilite did not ask for this or did provide it for mips...

 

A.A.

Edited by A.A., 9 May 2021 - 07:50.

[WanWizard]

Widevine provides DRM support, I can't imagine that it is needed to solve sound issues...

[A.A.]

Widevine provides DRM support, I can't imagine that it is needed to solve sound issues...

heh, nope

It was just a valid google match

[A.A.]

@WanWizard

 

what's the roadmap now?

I'd move to kodi 19.1 which iirc needs only python3.

 

Do you plan to keep 18.9 in 8.0 release?

 

Cheers

A.A.

[WanWizard]

I want to get 8.1-release out the door in the next week or two, and keep any big changes till after then.

 

Python 3 is quite a big change, it might not be a bad idea to have a seperate branch for it, as Enigma itself also needs to be readied for Py3 (so ideally we don't need both Py2 and Py3 installed).

[A.A.]

ok, let's do this way: I'll split the kodi 18.9 stb-patchset in chunks and recommit it.

 

I hope someone would review that because there are parts apparently unnecessary but I am probably wrong

 

Let's keep kodi 19.x for 8.1 then, which also has less patches.

Cheers

 

A.A.

[A.A.]

One more thing: do you plan to add any mali stb?

 

We only have one line, commented:

#SRC_URI_append_gbtrio4k     = " file://egl/EGLNativeTypeMali.patch"

 

Which stb will have kodi in the feeds?

 

Greets

A.A.
 

[ntj]

@WanWizard

 

what's the roadmap now?

I'd move to kodi 19.1 which iirc needs only python3.

 

Do you plan to keep 18.9 in 8.0 release?

 

Cheers

A.A.

 

 

I want to get 8.1-release out the door in the next week or two, and keep any big changes till after then.

 

Python 3 is quite a big change, it might not be a bad idea to have a seperate branch for it, as Enigma itself also needs to be readied for Py3 (so ideally we don't need both Py2 and Py3 installed).

Is it possible now after the work done by A.A. to put KODI 18.9 for mips in the plugin feed (develop) to try out ?