Posts by awiouy

Hello escalade,

I progressed a little:
- in LE:
- fbset -g 1920 1080 1920 1080 32 (to enable the frame buffer device)
- systemctl stop kodi (to stop Kodi)
- in the Docker container
- apt install firefox xorg -y (to install Firefox and X.org)
- startx -- :0 & (to start X.org)
- DISPLAY=:0 firefox (to start Firefox)

Firefox displays on the screen.
I however had stop stop Kodi to display Firefox on the screen.
I had copied the /etc/X11/xorg.conf.d/10-inputs.conf you provide, but the keyboard remained unresponsive.

Had you managed to display Firefox on top of Kodi? Do you remember how?
As for the keyboard, I have a feeling that a link is missing between LE and the container. What do you think.

Thank you for any help further.

Quote from beardedgeek

Got this working first time with no issue. It's working seamlessly with three different Spotify accounts at home.

Thank you for all the time spent getting it working, it's very cool to finally have!

Thank you for the kind words. Enjoy!

No, the other way around: if you change the LibreELEC host name, the display name of the service will change accordingly

Jdiesel,

Here is the addon for LE8 (should also work one Milhouse's test builds).
Here is the corresponding code.

Please report if it makes (and maybe share how you use it) or if it breaks.

Hello Gerben,

At the moment the service uses the host name as the display name.
Therefore, in order to permanently change the display name, you must change the host name.

I'll have a try at creating a package/addon. I do however not have a system to test it.

Volunteers please provide your LE release.

Thanks

Hey escalade!

I am trying to run Firefox on my Pi with the information you provide.
I am however new to Docker, and I have a hard time filling the gaps, eg:
- the ubuntu/armhf image does not ship xorg and firefox, you have to install them
- how should xorg and firefox be started
- fbset.service is absent from LibreELEC and Ubuntu
- etc

Thank you in advance for any help

Hello sesc,

Thank you for the feedback. I am glad your are able to use the addon.

Do not forget you can plug the jack of your Pi to an audio system, and route Spotify playback via the jack

Cheers

Hello lewham,

x11vnc is work in progress.
It however flickers badly.

We welcome any suggestion on how to fix the issue, here or on github.

Here you go!
Please report it it makes or breaks.
Thank you in advance.

Hi sesc!

Sorry to read you are struggling with the addon.

First, the addon home folder is /storage/.kodi/userdata/addon_data/service.spotify-connect-web (also smb://http://libreelec.tv/userdata/addon…ify-connect-web).
There is no need to reinstall LibreELEC or the addon, deleting settings.xml in the addon home folder is enough to reset the addon.

Then, the service will only activate onboard audio if no other sound device is active or if the service is configured to use onboard audio.
It sounds complicated, but the intention is to avoid activating onboard audio, because it might interfere with operation of other/unknown audio devices.

In summary, the service (probably) does not start onboard audio because your USB device is active when the service starts

To enable onboard audio:

• dtparam audio=on at the console or in config.txt
• restart the wizard to use onboard

Hope this will help you use onboard audio.
We will assess your USB device when this is done.

Keep cool

Quote from zosky

i leave it up to yall if you want to make this an addon,
bundle it into one of the system tool packages
or maybe there's someone willing to compile it for rpi2 and share

Hi zosky!

I submitted pull requests to add inotify-tools to the system-tools addon:
system-tools: add inotify-tools, mc by awiouy · Pull Request #700 · LibreELEC/LibreELEC.tv · GitHub
Backport of #700 by awiouy · Pull Request #702 · LibreELEC/LibreELEC.tv · GitHub
If you tell me which release of LibreELEC you are running, I could send you the corresponding inotifywait and inotifywatch.

Cheers

The log you provide does not enable me to assess.
My first impression is that the device is not ready when the service starts.

According to me the problem lies here:

Sep 08 22:28:04 openelecpi sh[12021]: Unable to acquire device:  Device or resource busy [surround21:CARD=Aureon51MkII,DEV=0]

I gather that Kodi and Spotify Connect Web can not share the device.

To verify that this is the case:
- set Kodi to use another device, eg PI:HDMI,
- set Spotify Connect Web to use the device, and
- restart Spotify Connect Web (eg by re-running the wizard and then confirming the settings with OK)

If Spotify Connect Web plays, you will unfortunately have to decide which of Kodi or Spotify Connect Web will use the device.

A similar problem was discussed here, and solved with DMIX.

I will assess if DMIX may be applied to LibreELEC, but it looks daunting and device specific.
Do therefore not expect this to happen soon.

I will nevertheless submit the current fix if you confirm it enables Spotify Connect Web to use your audio device.

Hello sesc,

Thank you for reporting this bug, which lies with the addon (spotify-connect-web.start does not handle a PCM specified as x:CARD=c,DEV=d), and should be quite easy to fix.

Please install this updated version of the addon (for LE7/RPi2), and report whether or not it fixes the problem.

Thank you in advance.

This could help you further: Setting up pHAT DAC on your Raspberry Pi Zero - Pimoroni Yarr-niversity

In terminal:
dtoverlay hifiberry-dac

If it works, add that command to config.txt: Config.txt - LibreELEC

Quote from poelzi

i intalled v7.90.005 on my Raspberry pi ... but cannot get past FFmpeg setup ... no matter what option i choose

By default, Emby donwloads its own copy of ffmpeg/ffprobe, which are not optimized for LibreELEC, and which do not support transcoding on arm (eg RPi).

Emby 8.0.104 enables h264 omx support on Raspberry Pi.
To try this out:

• In the settings of the addon, enable 'Use dedicated ffmpeg/ffprobe (experimental)'
• In the Emby web UI, under Manage Server/Playback/Transcoding, set Hardware Acceleration to OpenMAX OMX
• Restart Emby or LibreELEC.

No further configuration is required.

With these settings, Emby happily transcodes H264 1080p to lower resolutions on my Raspberry Pi 3 (200-250% CPU out of 400%, without overclocking).

However, there is an issue: the transcoded stream is displayed on the screen. This bug lies with ffmpeg.