Posts by awiouy

Quote from Loggio

Working now, It was indeed set to 30005. Set to 320 works fine now.

Also, if this addon requires docker, then it should be downloaded as a dependencey for this addon.

Thanks!

Awesomeness

I am glad the addon works for you now.
The problem obviously lies in the transition from preview release 90 to a later release, as already reported by Dom4Jack in the other thread.
I will update the first post to instruct uninstalling preview release 90 before installing release 100 or later.

This addon does not require Docker, yet, but that may change in the future.

Thank you for your feedback

Quote from Loggio

Sorry this is not working...

8.0.90 worked fine... Ever since the submission to libreelec repo, the addon updated to 8.0.100 and now I cannot see the device available from my iPhone spotify app.

Hello Loggio,

I am sorry to read that it is not working for you, and glad you could find a solution.
I could maybe help you fix the problem if you provide me with more details.

Would you please be so kind to uninstall the addon and then reinstall it from the repository.
Then check the bit rate in the settings: it should be blank, 90, 160 or 320, but not 30005.
If the addon from the repository still does not work, could you please send me a log, edited to remove userid and password, by private mail.
To produce a log in the downloads folder, type the following command at the console:

journalctl -u service.spotify-connect-web > /storage/downloads/scw.log

Thank you in advance

The Spotify Connect Web addon is now available from the LibreELEC repository.

Support is for the addon available here

See you there!

Spotify Connect Web is replaced by Librespot, and is not further maintained.

Team LibreELEC is pleased to announce that Spotify Connect Web is available as an addon from the LibreELEC repository.

Unfortunately, the spotify-connect-web project, on which the addon is based, does not run on every LibreELEC project, and overcoming this limitation lies with the spotify-connect-web project. As a consequence thereof, Spotify Connect is only available for Raspberry Pi 2 and 3, Wetek Core and Wetek Play.

Operation
1. Install the addon
2. Get your spotify_appkey.key from here
3. Place the spotify_appkey.key in the addon home folder, usually smb://libreelec.local/userdata/addon_data/service.spotify-connect-web
4. Optionally enter your Spotify username and password
5. Configure ALSA with the wizard
6. Save the settings
7. Check the service with the web interface at port 4000
8. Play Spotify through the service, using a Spotify app as a remote
9. Enjoy!

Further Reading
spotify-connect-web README.md
Spotify Connect forum thread

Feedback
Please share your feedback on this thread.

Enjoy!

Quote from topix

Hello awiouy.
This is what my raspberry told me:

Code

LibreELEC (community) Version: 7.90.003
LibreELEC:~ # cat /flash/config.txt
################################################################################
#      This file is part of LibreELEC - http://www.libreelec.tv
#      Copyright (C) 2016 Team LibreELEC
#
#  LibreELEC is free software: you can redistribute it and/or modify
#  it under the terms of the GNU General Public License as published by
#  the Free Software Foundation, either version 2 of the License, or
#  (at your option) any later version.
#
#  LibreELEC is distributed in the hope that it will be useful,
#  but WITHOUT ANY WARRANTY; without even the implied warranty of
#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#  GNU General Public License for more details.
#
#  You should have received a copy of the GNU General Public License
#  along with LibreELEC.  If not, see <http://www.gnu.org/licenses/>.
################################################################################
# Bootloader configuration - config.txt
################################################################################


################################################################################
# Memory (System/GPU configuration )
################################################################################


# Default GPU memory split (do not change if you do not know what you are doing)
  gpu_mem=128


# Configure GPU memory based on SDRAM size - overrides above setting
  gpu_mem_256=112
  gpu_mem_512=160
  gpu_mem_1024=256


################################################################################
# For overclocking and various other settings, see:
# https://www.raspberrypi.org/documentation/configuration/config-txt.md
################################################################################
# Set 'force_turbo=1' to disable dynamic overclocking and enable overclocking always.
force_turbo=0


# Make display smaller to stop text spilling off the screen
#
# Note that the overscan settings only affect the splash screen and not Kodi.
#
# If you experience overscan/underscan issues the best solution is to adjust
# your TV settings ("full pixel", "1-1 pixel" etc.). Alternatively, there is a
# calibration menu in the Kodi GUI.
# disable_overscan=1


# Force HDMI even if unplugged or powered off
# hdmi_force_hotplug=1


# Doesn't sent initial active source message.
# Avoids bringing CEC (enabled TV) out of standby and channel switch when
# rebooting.
hdmi_ignore_cec_init=1


################################################################################
# License keys to enable GPU hardware decoding for various codecs
# to obtain keys visit the shop at http://www.raspberrypi.com
################################################################################


# decode_MPG2=0x00000000
# decode_WVC1=0x00000000


################################################################################
# End of default configuration
################################################################################


################################################################################
# Include distribution specific config file if it exists.
################################################################################
[all]
include distroconfig.txt
dtoverlay=hifiberry-digi
dtdebug=1
LibreELEC:~ # aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HifiBerry Digi HiFi wm8804-spdif-0
  Subdevices: 1/1
  Subdevice #0: subdevice #0
LibreELEC:~ # aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
default:CARD=sndrpihifiberry
    snd_rpi_hifiberry_digi,
    Default Audio Device
sysdefault:CARD=sndrpihifiberry
    snd_rpi_hifiberry_digi,
    Default Audio Device
LibreELEC:~ # dtoverlay hifiberry-digi
LibreELEC:~ # aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HifiBerry Digi HiFi wm8804-spdif-0
  Subdevices: 1/1
  Subdevice #0: subdevice #0
LibreELEC:~ # aplay -L
null
    Discard all samples (playback) or generate zero samples (capture)
default:CARD=sndrpihifiberry
    snd_rpi_hifiberry_digi,
    Default Audio Device
sysdefault:CARD=sndrpihifiberry
    snd_rpi_hifiberry_digi,
    Default Audio Device
LibreELEC:~ #

Display More

Thanks for your help.

The bitrates offered by the plugin are: 320, 160, 90, blank.

According to your output, playback device should be hw:0,0

Incidentally, your output also shows that the addon did not reach the point where it enable the onboard alsa interface.
The addon expects a spotify_appkey.key in its home folder.
Could you check that this is indeed the case.
To consult the addon's log: journalctl -u service.spotify-connect-web.

As for the mixer, I am trying to find it out.
I have acquired a hifiberry DAC+. I managed to have it play, but I have not been able to set the volume, yet

Thank you for the bit rates
[hr]

Quote from DomJ4ck

No Problem mate. We have to thank you for making Spotify Connect available via an addon. It's so simple for endusers. Thank you very much.

320kbit is working great!

Hello Dom4Jack,

topix could not reproduce your problem, either.
Maybe unistalling/reinstalling the addon will fix it.
Incidentally, release 100 is available from the LibreELEC repository.

Let me know.

Quote from tecko

Hello,

I would like to use Libreelec on Raspberry pi 3 wiht official 7" screen. It is working fine except one thing. When I shutdown Libreelec the screen does not turn off. It continues to fade out in cycles. It is connected via DSI port and powered from GPIO pins. I also tested seperate power supply for the screen but it does the same.

Is there a way how to shut the screen down completely through the shutdown commnad? Power on/off button is not an option because I want to use delayed/scheduled shutdown.

Thanks

Hello tecko,

You might find a way to turn off the screen here, and how to customize shutdown here.

Quote from topix

Thank you for creating this plugin, i have been waiting for this for a long time
I use Libreelec v7 with kodi kyrpton. Additionally i installed a hifiberry digi+.
Unfortunately i get no sound when i connect to libreelec. Neither via the hifiberry nor hdmi or headphone jack.

Is there anything i have to write in the mixer or hw field?

Thank you in advance.

Hello topix,

I have no hifiberry device, so I can't experiment myself.
I therefore need you to provide me the output of the following console commands commands:
1. cat /flash/config.txt
2. aplay -l
3. aplay -L
4. dtoverlay hifiberry-digi
5. aplay -l
6. aplay -L

Incidentally, to assess another issue mentioned by Dom4Jack, would you be so kind to tell me what bit rates are available in the addon settings (blank, 90, 160, 320 or 30005, 90, 160, 320).

Thank you in advance

Quote from DomJ4ck

Yes i've downloaded your zip file and installed this via Kodi addons-menu (from the zip)
I've uploaded a photo for you. You can see the "30005-Bitrate" on it. This was directly after updating. If i'm using the down-arrow the next bitrate is 320, 160, 90 (but not blank).
With 30005 set up the server isn't starting.
I think labels are correct.

Foto 04.08.16, 09 33 27.jpg - directupload.net

I can't reproduce this problem.
I will address it if it remains with release 100, which should soon be available from the LibreELEC repository.
Thank you for your patience.

Quote from nickr

Thanks, downloading now. Will test and advise...
[hr]
OK installed that, have "run xdotool" switched on (.kodi/userdata/browser.chromium/settings.xml confirms).

However when chromium starts via netflix, xdotool doesn't seem to start.

unclutter does start. but ps ax|grep xdotool reveals nothing.

xdotool will run from the command line, and xdotool key alt+F4 closes chromium. However the lines in the startup script

if [ "$RUN_XDOTOOL" == "true" ]
then
xdotool &
XDOTOOL_PID=$!
fi

don't seem to be doing anything.
[hr]
Ahhh enlightenment

xdotool will not background like xdotool &.

In fact it needs to be run per keypress. So having it there and runnable should be enough and those lines won't be needed in the chromium startup script.

flix2kodi has a script:

/storage/.kodi/addons/plugin.video.flix2kodi/resources/scripts/keysender/linux/chromium.sh

It is effectivley a big if, then else case statement with stanzas like:

if [ "$1" = "close" ];
then
CMD="alt+F4"

I am trying to work out what feeds into this script.

Display More

Thank you for testing.
Waiting for further feedback.

Hello nickr,
Here is chromium with xdotool for LE7.
Do not forget to enable "Run xdotool" in the addon settings when you test.

Quote from Marciano

So when will this addon be avaible for odroid C2?

Hello Marciano,

I am sorry to have to disapoint you.

WebGrab+Plus is not available for Odroid C2, because it requires Mono, and I have not been able to build Mono for the aarch64 architecture, ie the Odroid C2 project.

In summary: the versions of Mono that support aarch64 do not cross compile for LE; bug tickets have been submitted, but to no avail.

Moreover, Odroid C2 does not provide docker, so that is not an alternative.

If I could bring Mono to Odroid C2, I gladly would.

Hi nickr,
I had overlooked you are building for LE7.
I have managed to build the PR for LE8, after adding the xdotool dependency to chromium (I updated the PR accordingly).
I will try to build the PR for LE7 during the night, to see if I can reproduce your issue.
If not, I will post the addon on this thread.
Just in case you can runtime test on LE8, here is chromium with xdotool for LE8.
Thank you for your patience.

Quote from DomJ4ck

So here's my Feedback.

After the Update the Bitrate in Settings was set to 30005 (?). The server won't come up so you don't see it in the Spotify Apps. When i change it to 320 then it appears and i can play music.

So: it's working great. I cannot validate, if the stream is really 320kbit. (i don't know how to do it. using the -bitrate 320 don't mean that 320kbit is used, probably)

My Setup:
Raspberry Pi 2 Model B
HDMI Connection to Pioneer AVR (setup with Audio passthrough in Kodi Settings)

btw: i'm not a developer, no clue what a docker image is
But i think you know what you're doing
And what is ALSA?

Cheers

Display More

DomJ4ck,

I was unable to reproduce your problem.
You are installing the addon via Kodi install from zip file, right?
If you go to the addon settings in the Kodi GUI, are the labels correctly displayed? What are the available bit rates (should be blank, 90, 160 and 320)?

ALSA is Advanced Linux Sound Architecture, used by some applications, but not by Kodi on LibreELEC

Quote from cyberden

Do I have to modify my config.txt to enable alsa to make the addon work?

Hello cyberden,

No, the addon takes care of enabling alsa. Just make sure that the volume (set from your Spotify app) is high enough: spotify-connect-web becomes inaudible even at a relatively high volume.

Quote from DomJ4ck

Hey awiouy,

Amazing, thank you for your work.

I'll try it out in the evening today!

Will this addon be integrated in the Libreelec Repo? There are already addons which were created by you

I'll give you feedback.

I am looking foward to your feedback.

I have submitted a pull request for the addon. Let's see if it makes it.

I however think that the pull request will stand a better chance if it provides for more projects than just RPi2, eg RPi and other arm projects. I have therefore created a docker image (about 50 MB) for that purpose. I should have the time to test it soon.

If it works, I will simply replace the current binary wrapped in the addon by that docker container.

It might have something to do with the latest commits. I will have a look at it tonight.

I have updated the preview addons, see my updated post above.
I hope they will work for you.

My next steps:
1. create a small Alpine based docker image to run spotify-connect-web on all LibreELEC arm projets
2. offload ALSA configuration (common to spotify-connect-web, squeezelite, etc) to a dedicated addon

Quote from nickr

Yeah I don't know of another use except to drive a browser. If you want to include it in chromium, thats great. I will learn from what you do!

Hello nickr!

This builds:

PKG_NAME="xdotool"
PKG_VERSION="2.20110530.1"
PKG_REV="1"
PKG_ARCH=""
PKG_LICENSE="GPL"
PKG_SITE="http://www.semicomplete.com/projects/xdotool/"
PKG_URL="http://semicomplete.googlecode.com/files/${PKG_NAME}-${PKG_VERSION}.tar.gz"
PKG_DEPENDS_TARGET="toolchain libX11 libXext libXinerama libXtst"
PKG_PRIORITY="optional"
PKG_SECTION="x11/app"
PKG_SHORTDESC="This tool lets you simulate keyboard input and mouse activity, move and resize windows, etc.."
PKG_LONGDESC="This tool lets you simulate keyboard input and mouse activity, move and resize windows, etc.."


PKG_IS_ADDON="no"
PKG_AUTORECONF="no"


PKG_MAINTAINER="vpeter4 ([email protected])"


pre_configure_target() {
  export LDFLAGS="$LDFLAGS -lXext"
}


make_target() {
  make xdotool.static
  mv xdotool.static xdotool
}


makeinstall_target() {
  : # nothing to do here
}

I will add it to chromium, the same way as I added unclutter.
I might not have the time to do it tonight, though.
[hr]
Hello nickr,

This is how I suggest to add xdotool to chromium.
Would you please be so kind to build and runtime test it.
Thank you in advance.