Thank you for the feedback, riverside70.
Indeed, neither LE, nor spotify-connect-web store the state of ALSA devices. The volume is therefore sometimes maxed out when a device is started.
I am testing workarounds to the issue.
Thank you for the feedback, riverside70.
Indeed, neither LE, nor spotify-connect-web store the state of ALSA devices. The volume is therefore sometimes maxed out when a device is started.
I am testing workarounds to the issue.
Send a log
Hello Marciano,
I have no Odroid C2 to work on, and Docker is not yet available in LibreELEC.
However, if someone brings Docker to Odroid C2, and creates an image for Mono, then I will adapt the addon to use it.
As for native Mono in aarch64, my bug tickets are still pending.
You just need to enable "Show hidden files and directories" from Kodi "Setttings\Appearance\File Lists".
Make sure "Settings Level" is at least "Standard".
Then you can point to "/storage/.kodi/userdata/addon_data/service.webgrabplus/guide.xml" in TV Guide Fullscreen.
Thank you for sharing!
Display MoreThanks. All Answered.
I had a good look at service.webgrabplus and tested out compatability with Webgrab+Plus Configurator.
It seems to work fine for me as long as the filename and folders are set up right.The filename has to be guide_wgp.xml to enable the postprocessing, as you mention,
and the folder has to be /storage/.kodi/userdata/addon_data/service.webgrabplusI checked your code and it only copies new ini files if they don't exist.
That's good for me as I copy the necessary ini files into the config folder.I accessed the guide.xml on LibreELEC from Windows and everything was fine. So SMB seems ok.
One more cheeky question which you don't need to answer if it is against LibreELEC rules:
Have you tried to run the webgrab exe on android with mono?
I didn't want to start trying to compile mono for android if it already exists somewhere.
WGP should run on any OS providing the required version of Mono.
The LE addon however requires LE features (system.d and system.d automatic service activation).
Display More
Hi. A couple of issues have come up with Webgrab+Plus Configurator.I thought I read somewhere here about the addon's addon_data folder being restricted between addons. I might have been dreaming.
It works ok at the moment.
Is there going to be any problems with copying the config file output from my addon to yours?Someone is having problems with access the xmltv file from smb.
Could you help solve that for us. I suggested it might be an smb user permission issue.
TV Guide Fullscreen - possibly the most powerful TV Guide in the world. ;)Right now I copy out the necessary ini files into the folder that has the webgrab config file and then copy all of them over to your addon's folder.
Your addon also has a siteini folder.
What is the best way to make sure we are using the right set of ini files?
Addons can access all the data, users cannot access special://userdata from the Kodi user interface.
If a user has an SMB problem, then he should open a specific thread in the forum, and provide a log. I this specific instance, I think he has already done, and it is addressed.
There should be no problem copying the files, as long as WGP produces guide_wgp.xml, which is expected by the next processing step.
The service uses the siteini.pack in its home folder. If the date of siteini.pack in the home folder is earlier than that provided with the addon, the service updates siteini.pack in the home folder.
I hope to have answered all of your qurstions.
Display More
Hi,Everything is working as expected !!
I configured Emby server (used Chromium add-on for web browser), accessed it at local address on port 8096.
I was earlier confused because the "configure" and "run" buttons are disabled when adding the Emby server add-on. So I thought may be we need to configure within Kodi.Then I added (official) Emby add-on for Kodi, and could get all the library contents in Kodi.
I also was able to stream to my iPhoneThanks to awiouy for this Emby server add-on !! Also, to im85288 and other persons at Emby for the Kodi add-on to access the server !!
Just another Noob question ... why is "Mono" add-on needed for this? It is automatically installed and enabled while installing Emby server.
Best,
Sanjay
Hello Sanjay,
Thank you for the positive feedback!
The official Emby addon needs an Emby server as a back end.
The LibreELEC Emby addon runs an Emby server on LibreELEC.
The Emby server is a .NET program that needs Mono to run on Linux.
Requests is not yet available for Kodi 17, see here
I have updated my addon a bit:
- the erroneous bit rate setting should be solved;
- the wizard should now handle device:CARD=card,DEV=n PCMs
The addon is said to work on S805, Wetek Play and Wetek Core, but I do not own such boxes.
Would anyone here be so kind to verify this for me?
As for the sound quality, I would not know where the problem comes from.
I add a link to alsamixer built for LE8 to inspect/modify your card's settings.
I have submitted a pull request to add alsamixer to the multimedia-tools addon.
Spotify Connect Web 101 for LE7
Spotify Connect Web 101 for LE8
alsamixer for LE8
[hr]
I installed spotify connect before on the musicbox OS, the sound was ok. But now on Libreelec I have problems with the sound, and tried several settings in the addon. I use my pi over an AV Receiver with hdmi.
Hello riverside70,
To help you I would need you to provide me with the following information:
- what version of LibreELEC you are using
- what version of the addon you are using
- what settings you have tried
- what your problems with the sound are? If you think it is overmodulated, have you tried to reduce the volume with your Spotify app?
- a log, to assess the problems you have with the sound, as well as those caused by the VPN
Always handy, built-in pastebinit support
If none of the below work, I am at my wits' end
hdmi:CARD=HDMI,DEV=0
hdmi:CARD=HDMI,DEV=1
hdmi:CARD=HDMI,DEV=2
default:CARD=PCH
sysdefault:CARD=PCH
front:CARD=PCH,DEV=0
surround21:CARD=PCH,DEV=0
surround40:CARD=PCH,DEV=0
surround41:CARD=PCH,DEV=0
surround50:CARD=PCH,DEV=0
surround51:CARD=PCH,DEV=0
surround71:CARD=PCH,DEV=0
It was aplay -L (uppercase)
Have you tried hw:0,0 hw:0,3 hw:0,8 and hw:1,0 ?
To display the state of your cards, use the following commands:
amixer -c 0 contents
amixer -c 1 contents
Anyone got moonlight addon x64 working with alsa? If so how? Ive tried hw:0,3 which is the correct alsa soundcard and it doesnt work. Picture, and controller work but zero sound. sysdefault do nothing as does changing the soundcard to hw:0,0 like suggest by the addon creator.
I do not know moonlight, but I might help with ALSA.
To know what PCMs are active, use the command cat /proc/asound/pcm.
If that file does not exist or is empty, no PCM is active.
If that file exists, it contains a list of available PCMs, eg
00-00: bcm2835 ALSA : bcm2835 ALSA : playback 8
00-01: bcm2835 ALSA : bcm2835 IEC958/HDMI : playback 1
In the example above, you could try using hw:0,0 or hw:0,1.
It might also be possible to use the names provided by aplay -L, eg
null
Discard all samples (playback) or generate zero samples (capture)
default:CARD=ALSA
bcm2835 ALSA, bcm2835 ALSA
Default Audio Device
sysdefault:CARD=ALSA
bcm2835 ALSA, bcm2835 ALSA
Default Audio Device
In the example above, default:CARD=ALSA or sysdefault:CARD=ALSA.
If they work, prefer names to addresses.
I would personally prefer to be able to set specific time that the guide is updated and for my usage case run routine once a day. Additionally don't particularly want job to run everytime I re-boot the device, when busy doing other boot up activities..(although I have not noticed any issues)
Settings option "config file" that allowed me to specify time/frequency per week. (i.e. 04:00 everyday of the week) would be great.
If I would know how to this implement this feature on LE, I gladly would.
Moreover, I gather from your reply the addon works for you, even without this feature.
I therefore keep this feature on my to-do list, but with a very low priority
Sounds great in sense before.sh and after.sh should cover multitude of user needs, any more thought on allowing external user control of frequency of EPG update requests if I remember correctly routine currently automatially runs every six hours.
(once at a re-boot, then every six hours after re-boot)
Hello MikeKL,
If you could change the frequency, to what value would you set it?
Display MoreFirst of all - great idea with "configuration wizard", very user friendly
I have tested with my Trust 5.1 USB soundcard and I was now able to control the volume, using the following device/mixer combinations:
- Device: default:CARD=Device + Mixer "Speaker"
- Device: sysdefault:CARD=Device + "Mixer "Speaker"
Mixer "Line" didn't work for both of them - no sound output, at least for my soundcard cabling.BUT: the sound was blurred - not a problem of overmodulation, rather it looks like as if the channels are not adressed properly. Within in Kodi you can choose the channel configuration (e.g. 2.1) - maybe the same needs to be done too here in the config.
Another comment, that may help during bugfixing - I got an UI popup add-on error, when I choose one of the following items as device:front:CARD=Device,DEV=0
surround21:CARD=Device,DEV=0
surround40:CARD=Device,DEV=0
surround41:CARD=Device,DEV=0
surround50:CARD=Device,DEV=0
surround51:CARD=Device,DEV=0
surround71:CARD=Device,DEV=0
iec958:CARD=Device,DEV=0The error log for the above error is as follows:
PythonAug 09 18:37:11 LibreELEC sh[9443]: Starting spotify-connect-webAug 09 18:37:14 LibreELEC sh[9443]: Loading Spotify library...Aug 09 18:37:14 LibreELEC sh[9443]: Traceback (most recent call last):Aug 09 18:37:14 LibreELEC sh[9443]: File "loader.py", line 3, in <module>Aug 09 18:37:14 LibreELEC sh[9443]: File "runpy.py", line 180, in run_moduleAug 09 18:37:14 LibreELEC sh[9443]: File "runpy.py", line 72, in _run_codeAug 09 18:37:14 LibreELEC sh[9443]: File "/storage/.kodi/addons/service.spotify-connect-web/main.py", line 14, in <module>Aug 09 18:37:14 LibreELEC sh[9443]: from connect import ConnectAug 09 18:37:14 LibreELEC sh[9443]: File "/storage/.kodi/addons/service.spotify-connect-web/connect.py", line 9, in <module>Aug 09 18:37:14 LibreELEC sh[9443]: from console_callbacks import audio_arg_parser, mixer, error_callback, connection_callbacks, debug_callbacks, playback_callbacks, playback_setupAug 09 18:37:14 LibreELEC sh[9443]: File "/storage/.kodi/addons/service.spotify-connect-web/console_callbacks.py", line 104, in <module>Aug 09 18:37:14 LibreELEC sh[9443]: mixer = alsa.Mixer(args.mixer, **mixer_card_arg)Aug 09 18:37:14 LibreELEC sh[9443]: alsaaudio.ALSAAudioError: Unable to find mixer control Mixer,0 [hw:1]Aug 09 18:37:14 LibreELEC sh[9443]: Failed to execute script loaderAug 09 18:37:14 LibreELEC systemd[1]: service.spotify-connect-web.service: Main process exited, code=exited, status=255/n/aAug 09 18:37:14 LibreELEC systemd[1]: service.spotify-connect-web.service: Unit entered failed state.Aug 09 18:37:14 LibreELEC systemd[1]: service.spotify-connect-web.service: Failed with result 'exit-code'.Aug 09 18:37:14 LibreELEC systemd[1]: service.spotify-connect-web.service: Service hold-off time over, scheduling restart.Aug 09 18:37:14 LibreELEC systemd[1]: Stopped spotify-connect-web.Aug 09 18:37:14 LibreELEC systemd[1]: Started spotify-connect-web.Aug 09 18:37:14 LibreELEC sh[9466]: The hw:d,s device specification is unreliable. Use names instead
I hope this helps.
Cheers
Chunki
Thank you for the feedback!
As for the sound quality, it may be due to the fact that the cards are not configured properly. Addinhg a mixer interface to the addon is however not within the scope I had given to the addon, and well beyond my league. I nevertheless consider bundling alsamixer with the addon.
As for the error, it looks like the listed PCMs do not have a mixer. I will review my code.
Hello all,
I have submitted a pull request to add user defined pre/post-processing to the service.
The principle is simple: the service calls shell scripts before.sh and after.sh, if they exist in the addon home folder.
You could use this, eg to copy the guides locally and/or remotely, update siteini.pack, etc.
What do you say?
Display More
Hi,I was using OpenElec and now trying out LibreElec.
I downloaded and successfully installed LibreElec 7.02 (X86_64).
My hardware is a NUC box.I was especially interested in "Emby".
I downloaded the add-on from the repository and also installed successfully.
I also got a message that "Mono" add-on is also enabled.However, when I "opened" the Emby add-on, both the "Run" and "Configure" buttons are disabled.
So I do not know what I should do next. (I have tried Emby earlier on my laptop, so I have a fair idea how to configure Emby normally).What I wanted was something like this:
When I was running OpenElec, I used an add-on (by "hugepants") for Plex Media Server, so that both OpenElec and Plex Media Server are running on the same machine. Then, using another add-on PlexBMC, I am able to use Kodi (Jarvis) as front-end and Plex Media Server as backend. In this way, I was able to stream to my other devices such as iPhone and iPad.I want a similar configuration with Emby and LibreElec. I want to know whether we can run both LibreElec and Emby in the same machine, similar to how I used PMS and OpenElec on the same machine as above.
If it is possible, why are the "Run" button and "Configure" button disabled?
I tried the same on LibreElec 8.0 preview (alfa) but the status seems to be exactly the same.Maybe I am missing something very basic? Please let me know if I need to provide any additional information.
Please help
Thanks
Sanjay
Hello Sanjay
The Emby addon only runs Emby on LibreELEC, it does not configure Kodi to access Emby.
You can access/configure Emby with your browser, usually at libreelec.local:8096.
You must configure Kodi to access Emby, which may involve an additional addon.