I am on a Raspberry Pi 3B, so probably ARM?
You need to update both
Posts by awiouy
-
-
The latest binary releases are available here
I have updated my pull request.
On what LibreELEC project (aarch64/arm/x86_64) would you like to test Emby 3.5.0.0?
-
The latest version of Emby has just been released. You should be able to update the .Net Core release of Emby Server to 3.5.0.0
I will update as soon as it is released here Releases · MediaBrowser/Emby · GitHub
-
How can you end up reinstalling LibreELEC ?
I do not understand your question.
Addons do not require reinstalling LibreELEC: simply delete addon configuration directory and reinstall the addon.
-
As for Emby for .Net Core:
The latest release of Emby for .Net Core is still 3.4.1.0, which was released on May 7th, 2018.
.Net Core runtime 2.1.2 has been released in the meantime.
I will submit updated .Net Core runtime (>= 2.1.2) and Emby addons as soon as Emby 3.4.2.0 is released.
This might take some time, because Emby seems under heavy rework.
As for ffmpeg:
Since Milhouse 18 #0628 ffmpeg has been removed from the LibreELEC image, and ffmpegx has been renamed ffmpeg in revision 102 of the FFmpeg Tools addon.
For Emby to use ffmpeg rather than ffmpegx unset Use dedicated ffmpeg/ffprobe in the Emby addon settings.
-
Hello, excuse the question, maybe a little stupid, but how can I tell WebGrab to start the EPG scan every time you turn on the box and to find the programming for several days?
I noticed that if I turn off the box in the evening, in the morning I have no more EPG and I have to manually restart the scan.
The box is a WetekPlay 2 with LibreELEC 8.2.3.1 of kszaq
`—on-active` setting defines how many seconds after start of the service the epg is dowloaded.
`—on-calendar` setting defines a schedule at which epg is dowloaded. See earlier posts for syntax.
The service creates ˋguide.xml` in `/storage/.kodi/userdata/addon_data/service.webgrabplus`. You can define a `after.sh` script in the same directory to copy the ˋguide.xml` somewhere else after it is updated by the service.
-
I did the steps above, but the issue persists. I didn’t have SSH enabled so I couldn’t log it, but I will try to get a log next time.
I’m not sure what causes it exactly, but it keeps happening. I can still use the Kodi web interface to reboot, and everything goes back to normal.
Log is also available at smb://libreelec.local/userdata/addon_data/http://service.emby/logs/embyserver.txt
-
I was on a beta version of Emby before, so that’s probably why the stable version of Emby on the .Net Core version is behaving weirdly. I wanted to install it fresh, because I’ve also messed around with some of the files on the Mono release before I installed the .Net Core release.
I will, however, provide the log so you can better analyse what might be going on.
Uninstall Emby and delete /storage/.kodi/userdata/addon_data/service.emby
Then reinstall Emby.
That should be enough
-
So far the experience has been better than with the Mono releases, but I am facing an issue where the Emby server will shut down or won’t be able to connect randomly. The only way to fix is to reboot, and then it takes a bit of time to get back online. I’m not sure if the issue is because of LibreELEC 9, or because of the experimental nature of this addon.
I will probably end up reinstalling LibreELEC completely and installing this addon from scratch to see if the result is any different.
No need to reinstall LibreELEC: simply install Emby from the LibreELEC Add-ons repository and you will be using the latest Emby and Mono without losing your settings.
Before you do that, please provide a log of Emby for .Net Core runtime, to help determining where the issue lies.
One way of displaying the log after a crash is the command journalctl -u service.emby.
Thank you for your feedback.
-
In the Kodi audio settings I can switch to ALSA: AML-M8AUDIO, HDMI.
Then it seems to work, at least during the first tests. Good!
I am not sure what is the difference between the 'ALSA: AML-M8AUDIO, HDMI' and the 'ALSA: Default (AML-M8AUDIO Analog), PCM' it was set to previously. It is not going over HDMI, only. I still hear it over the optical out and my audio receiver.
Good if it works for you...
-
I think it looks similar to LE8
Hm... Not sure Kodi and Librespot can share the same ALSA device.
This was why I added the Kodi output.
ALSA dmix might be an option for sharing the device.
But I have never used it.
Maybe someone here can help.
-
Really it was the size. It says maximal size 2MB and I was below that (around 1MB). But reduced it works.
The third screenshot is from the librespot settings. There it shows nothing in Playback devices (also after using the configuration wizard), but I assume this is a minor problem.
Configuration wizard does not copy the selected device to Playback device anymore, because the behaviour of Kodi changed.
I should try to fix that.
In the meantime, you must fill in Playback device manually.
What is displayed if you select configuration wizard?
-
I just wanted to append the screenshots (.png, around 1MB), here, but always get an unkown error on upload.Any idea?
Too large?
-
Display More
librespot plugin does not run satisfactorily on CoreELEC 8.90.3 (Wetek Play 2).
I wrote the issues also in a thread at CoreELEC, but because it seems unclear if the issue is CoreELEC, Leia or librespot specific, I want to inform you as well.
The issue depends on the used audio system:
1) ALSA
* If librespot is active playing, the Kodi GUI is not working anymore
* If I stop the playing and try to use Kodi again, it crashes
* last lines of kodi_crash.log:
15:04:48.020 T:4064277360 INFO: CActiveAESink::OpenSink - initialize sink
15:04:48.020 T:4064277360 DEBUG: CActiveAESink::OpenSink - trying to open device ALSA:default
15:04:48.020 T:4064277360 INFO: CAESinkALSA::Initialize - Requested layout: FL, FR
15:04:48.021 T:4064277360 INFO: CAESinkALSA::Initialize - set digital_codec 0
15:04:48.021 T:4064277360 INFO: CAESinkALSA::Initialize - Attempting to open device "default"
15:04:48.024 T:4064277360 INFO: CAESinkALSA - Unable to open device "default" for playback
15:04:48.024 T:4064277360 ERROR: CAESinkALSA::Initialize - failed to initialize device "default"
15:04:48.025 T:4064277360 DEBUG: CActiveAESink::OpenSink - trying to open device ALSA:default
15:04:48.025 T:4064277360 INFO: CAESinkALSA::Initialize - Requested layout: FL, FR
15:04:48.025 T:4064277360 INFO: CAESinkALSA::Initialize - set digital_codec 0
15:04:48.025 T:4064277360 INFO: CAESinkALSA::Initialize - Attempting to open device "default"
15:04:48.029 T:4064277360 INFO: CAESinkALSA - Unable to open device "default" for playback
15:04:48.029 T:4064277360 ERROR: CAESinkALSA::Initialize - failed to initialize device "default"
15:04:48.029 T:4064277360 ERROR: CActiveAESink::OpenSink - no sink was returned
It seems Kodi is not able to get back the ALSA sink.
2) Kodi
I can switch between the use of librespot and Kodi without crashes. But sometimes (maybe after librespot was restarted) the audio output is stuttering.
I will try to address the ALSA issue first. But I have no clue about the differences between CoreELEC and LibreELEC, and I do not have hardware to test.
Can you send me a screen shot of the Kodi sound settings on CoreELEC.
-
Install the FFmpeg Tools addon, and use ffmpegx instead of ffmpeg to (try to) transcode.
-
Hi, Librespot work only with account spotify premium?
Thanks
Yes
-
Was anyone here able to run Webgrab+Plus with .Net Core runtime (on any operating system)?
If so, how?
Thank you in advance.
-
An addon for .Net Core runtime 2.1.0 should be available soon from the LibreELEC Add-ons repository.
In the meantime, you can download a preview of the addon attached to this post.
To run the .Net Core runtime, install the addon and type `le_dotnet` at the console.
Emby will be switched from Mono to .Net Core.
You can download a preview of the Emby (3.4.1.0) for .Net Core addon attached to this post.
To run the Emby addon, first install the dotnet-runtime addon, then the Emby addon.
Emby listens at libreelec.local:8096.
Enjoy!
