322 replies to this topic

[dudule22]

I read all this post, i saw sound problem on Kodi but no way to install Kodi on DUO4K.

[Pr2]

No Kodi doesn't start on Duo 4K with OpenPLi image, with a derivated image it starts but no sound.

[dragnan]

sound is back! 

 

I use the devellopment image for the last week or so - and after todays update (that wiped my tuxbox/satellites.xml) - the /dev/dsp and /dev/mixer are back. After reinstalling the libasound modules and changing asound.conf, sound in kodi is back

[dragnan]

I have the netflix plugin running in Kodi. But the audio hast strange delays - and video resolution seems to be lower than full HD. In Other plugins (like DR TV and SVT Play, I can choose to use "E2Player" instead of Videoplayer which results in the known issue: no RC input works, but video quality is flawless and I can press Exit in OpenWebIf to return to Kodi. But in Netflix Plugin, when I select E2Player, it doesn't play. Instead it just halts for a couple of seconds and then returns to the netflix plugin. The before mentioned "playercorefactory" change doesn't fix anything - and it doesn't matter whether ServiceApp is setup for exteplayer3 or gstplayer - both settings make the use of E2Player for netflix halt and exit. Is there any way to get exteplayer3 work with the netflix plugin?

[Pr2]

On which box do you have the sound working?

 

I have tested on the Solo4K after a fresh develop install and the libasound installation and still no trace of  /dev/dsp nor /dev/mixer  so still no sound.

[dragnan]

On which box do you have the sound working?

I have tested on the Solo4K after a fresh develop install and the libasound installation and still no trace of /dev/dsp nor /dev/mixer so still no sound.

Ultimo 4k

[dragnan]

I just got 111 new packages with today's development image update. What did you do to Kodi sound? It is perfect. No delays in sound at all anymore. It is way better than any of the other images I tested. Good job �

[WanWizard]

There was a gstreamer and ffmpeg update yesterday.

[Aliraza63]

Just for the knowledge Which plugins mostly dont have sound in kodi 

I have tried in solo4k and dou4k 

repository.tempest-0.0.5

repository.temptv-0.0.5

repository.temptv-0.0.5

repository.covenant-0.1

plugin.video.uwc-1.2.42

plugin.video.filmon-4.6.8

plugin.video.videodevil-1.8.7

Just for the testing purpose installed and working flawlessly. 

image installed Openpli development .

[marto]

I just got 111 new packages with today's development image update. What did you do to Kodi sound? It is perfect. No delays in sound at all anymore. It is way better than any of the other images I tested. Good job �

 

 

There was a gstreamer and ffmpeg update yesterday.

So, is it works on OpenPLi 8.0 - Stable release image as well, or only on develop?

Edited by marto, 4 February 2021 - 19:14.

[WanWizard]

I can't comment. I haven't tested anything.

 

But in general stable images aren't updated, develop will become the basis for OpenPLi 8.1.

[blzr]

I just got 111 new packages with today's development image update. What did you do to Kodi sound? It is perfect. No delays in sound at all anymore. It is way better than any of the other images I tested. Good job �

one question, you have alsa-plugins still installed (all these libasound packages)? or sound appeared just with a 'clean' develop image?

[dragnan]

I just got 111 new packages with today's development image update. What did you do to Kodi sound? It is perfect. No delays in sound at all anymore. It is way better than any of the other images I tested. Good job �

one question, you have alsa-plugins still installed (all these libasound packages)? or sound appeared just with a 'clean' develop image?

I installed them again

[WanWizard]

Which exactly? On which image?

 

I see only

root@vuduo4k:~# opkg list | grep libasound
libasound-dbg - 1.1.9-r0.1 - ALSA sound library - Debugging files
libasound-dev - 1.1.9-r0.1 - ALSA sound library - Development files
libasound2 - 1.1.9-r0.1 - ALSA sound library

on a standard develop image.
 

[A.A.]

Which exactly? On which image?

 

I see only

root@vuduo4k:~# opkg list | grep libasound
libasound-dbg - 1.1.9-r0.1 - ALSA sound library - Debugging files
libasound-dev - 1.1.9-r0.1 - ALSA sound library - Development files
libasound2 - 1.1.9-r0.1 - ALSA sound library

on a standard develop image.
 

 

It seems not consistent between devices:

 

root@vuduo2:~# opkg list | grep libasound
libasound2 - 1.1.9-r0
root@vuduo2:~#

 

root@vuduo2:~# cat /etc/issue
openpli homebuild \n \l

root@vuduo2:~#
 

I'll go working on sound once I get GLES2 on vuxxo2...

Cheers

A.A.

[WanWizard]

Whether or not you have dev and dbg ipk's depends on how you build what.

 

My buildserver has the same setup as our "production" servers, and does produce them.

 

I've checked the feed, none of the boxes in our standard build have any of the libasound-module-* packages mentioned a few pages back.

[dragnan]

Which exactly? On which image?

 

I see only

root@vuduo4k:~# opkg list | grep libasound
libasound-dbg - 1.1.9-r0.1 - ALSA sound library - Debugging files
libasound-dev - 1.1.9-r0.1 - ALSA sound library - Development files
libasound2 - 1.1.9-r0.1 - ALSA sound library

on a standard develop image.
 

 

 

 

 

Has the kodi sound problem been solved because I still have no sound on VU + Uno 4K SE kodi?

Some are writing that this is the solution, but it is not working for me, but you can try if it works for you.

 

Ok, if someone want to test (I don't have any vu receiver here), please try as below:

1) install alsa-plugins - attached (they're not available in the feed (yet), these are from my home build)

opkg install libasound*

2) change content /etc/asound.conf to

pcm.!default {
    type oss
    device /dev/dsp
}

ctl.!default {
    type oss
    device /dev/mixer
}

3) make sure that multi-chanell audio downmix is ON

4) run kodi, check if you hear anything, give feedback ;-)

//oh, and just in case, this is only for the (all) vu*4k* arm receivers, not for older 1st / 2nd generation mips boxes...

 

 

the libasound modules provided by blzr earlier.

libasound-module-ctl-arcam-av_1.1.9-r0.0_armv7ahf-neon.ipk

libasound-module-ctl-oss_1.1.9-r0.0_armv7ahf-neon.ipk

libasound-module-pcm-oss_1.1.9-r0.0_armv7ahf-neon.ipk

libasound-module-pcm-speex_1.1.9-r0.0_armv7ahf-neon.ipk

libasound-module-pcm-upmix_1.1.9-r0.0_armv7ahf-neon.ipk

libasound-module-pcm-usb-stream_1.1.9-r0.0_armv7ahf-neon.ipk

libasound-module-pcm-vdownmix_1.1.9-r0.0_armv7ahf-neon.ipk

libasound-module-rate-samplerate_1.1.9-r0.0_armv7ahf-neon.ipk

libasound-module-rate-speexrate_1.1.9-r0.0_armv7ahf-neon.ipk

[littlesat]

Bsp layer?

[WanWizard]

Might be handy if blzr would create a PR so these can be build in the image.

[blzr]

sure, I can submit PR probably later today (or you can use attached patch alternatively?)

this was just a blind test on my side /no hardware to test myself/ based only on clear differences in oe-a kodi implementation for vu boxes, and the feedback was not completely clear - in fact only @dragnan confirmed that worked for him, and others reported it did not help, but the pool of testers was small (looking at the numbr of downloads)
anyway, we can add alsa-plugins and vuplus specific asound.conf -  does not harm at all the other brands, and we'll see, I assume more users test develop images (I somehow suspect taht defconfig changes will be still necessary too though)

Attached Files

•  0001-vuplus4k-trying-to-fix-kodi-sound.patch   3.91KB   43 downloads