322 replies to this topic

[dragnan]

This problem must be fixed by VU+ itself there is nothing Kodi can do about it. VU+ enable Kodi in the BSP but there is no sound.
VU+ needs to properly enable the ALSA support on there side and provide the audio devices in the kernel.

Some months ago, the dev/dsp device was added to vuultimo4k development branch. At that time, sound worked fine using alsa Oss plugin. Unfortunately the dev/dsp has been removed again. I just hope, it will be re enabled - but I have no clue how...

[WanWizard]

Nothing has been removed, at least not consciously.

 

The only relevant commits I see are the ones from blzr on the 6th and 7th of February, with attempts to fix alsa on vu+.

[Pr2]

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.

[littlesat]

I just checked for Kodi on vu still manual adaptions are mandatory.... without you do not have good audio... so it seems alsa is not solved... the attempt did not help...

Edited by littlesat, 21 March 2021 - 08:47.

[dragnan]

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. 

[blzr]

I'm pretty sure the difference is oss emulation enabled in VU+ kernels in OE-A

https://forums.openp...-5#entry1308250

 

It's quite easy to check, if one only:
a) knows how to compile/build custom kernel/image
b] has the necessary hardware to test it
I unfortunately lack the later ;-)

Edited by blzr, 21 March 2021 - 12:25.

[littlesat]

That is in the bsp from vu...

[blzr]

sure, but if we'd have tested this and confirm it works, submitting PR to vu's bsp wouldn't be a problem, right?

[littlesat]

When they merge it... it should not be a problem..:

[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. 

 

 

Have tried this today and can confirm that dev/dsp and dev/mixer shows up after power down and boot wihtout usb-stick as in Dragmans text.

 

However i will NOT have sound in KODI.

 

My test is with Openpli release from 20210315 on Ultimo4k

 

installed "opkg install libasound*" Have checked that i have alsa files in /usr/lib/alsa-lib and in /usr/share/alsa (as in openspa)

 

asound.conf also modified and looks correct

 

Have also tried with or without audio downmix

 

Tried bouth HDMI and Optical output.

 

Am i missing something compared what Dragman has done?

[Pr2]

 

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. 

 

 

The difference is that OpenMultiboot is not a true multiboot because you are using the kernel from the "main" image, so when you install another image into OpenMultiboot it just change some "directories" (kind of symbolic link).

So you were testing OpenPLi Kodi with the kernel build for OpentSPA (kernel that is patched to have such /dev/dsp ... devices).

So you can never conclude anything about an image when you are testing it with OpenMultiboot.

 

Only boxes that support true multiboot (boot managed by the bootloader) fully boot on the image you are choosing.

[Pr2]

 

 

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 them. 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. 

 

 

Have tried this today and can confirm that dev/dsp and dev/mixer shows up after power down and boot wihtout usb-stick as in Dragmans text.

 

However i will NOT have sound in KODI.

 

My test is with Openpli release from 20210315 on Ultimo4k

 

installed "opkg install libasound*" Have checked that i have alsa files in /usr/lib/alsa-lib and in /usr/share/alsa (as in openspa)

 

asound.conf also modified and looks correct

 

Have also tried with or without audio downmix

 

Tried bouth HDMI and Optical output.

 

Am i missing something compared what Dragman has done?

 

 

Dragnan changed the default sound configuration file to force Kodi to use those devices files. By default it is not using them. Please read the thread to find the exact file name and parameters to set in it.

Edited by Pr2, 21 March 2021 - 16:08.

[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 them. 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. 

 

 

Have tried this today and can confirm that dev/dsp and dev/mixer shows up after power down and boot wihtout usb-stick as in Dragmans text.

 

However i will NOT have sound in KODI.

 

My test is with Openpli release from 20210315 on Ultimo4k

 

installed "opkg install libasound*" Have checked that i have alsa files in /usr/lib/alsa-lib and in /usr/share/alsa (as in openspa)

 

asound.conf also modified and looks correct

 

Have also tried with or without audio downmix

 

Tried bouth HDMI and Optical output.

 

Am i missing something compared what Dragman has done?

 

 

Dragnan changed the default sound configuration file to force Kodi to use those devices files. By default it is not using them. Please read the thread to find the exact file name and parameters to set in it.

 

 

Do you mean this one?

 

 /etc/asound.conf 

 

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

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

 

This is the one i have used.

Or are you writing about a different config?

[Pr2]

Indeed it is this one.

[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?

[Piterek79]

Hi, posted on kodi forum in https://forum.kodi.t...php?tid=361496 

 

"They package Kodi and probably modify it in order to run on their exotic hardware and software stack thus they are the ones who should support their shit.

By looking at your log snippet one might think that alsa is somehow broken on your system, this is not Kodi problem but OS problem or even kernel problem, hard to tell without having the same hardware and software handy.
As I've already said before - refer to the people you get your software from for support."

 

Who should fix this finally ?

[dragnan]

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.

[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.

 

From my earlier post:

Have tried this today and can confirm that dev/dsp and dev/mixer shows up after power down and boot wihtout usb-stick as in Dragmans text.

 

However i will NOT have sound in KODI.

 

My test is with Openpli release from 20210315 on Ultimo4k

 

installed "opkg install libasound*" Have checked that i have alsa files in /usr/lib/alsa-lib and in /usr/share/alsa (as in openspa)

 

asound.conf also modified and looks correct

 

Have also tried with or without audio downmix

 

Tried bouth HDMI and Optical output.

 

-------------

Dragnan wrote:

 

Are the alsa Oss plugins in the correct folder?

 

Do you mean something more than these folders with that question?

 

installed "opkg install libasound*" Have checked that i have alsa files in /usr/lib/alsa-lib and in /usr/share/alsa (as in openspa)

 

asound.conf also modified and looks correct

[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

[WanWizard]

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