miguelcmran 2 Posted July 31, 2018 Share Posted July 31, 2018 He probado tanto la versión del Repositorio Estable como del Repositorio Beta en Kodi 17.6 para Windows 10 y Kodi 17.6 para Raspberry Pi 3B y en ambos en cuanto instalo el plugin y añado la colección de Emby en Kodi, la CPU empieza a subir y se mantiene entre un 70 y 95 % tanto en Windows como en Raspberry. En cuanto desinstalo el plugin de Emby y elimino la colección el consumo de CPU por parte del proceso de Kodi vuelve a la normalidad a un 5-10%. Link to comment Share on other sites More sharing options...
Luke 37063 Posted July 31, 2018 Share Posted July 31, 2018 @@Angelblue05, he's saying the emby for kodi add-on results in high cpu usage on the kodi process. Thanks. Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted July 31, 2018 Share Posted July 31, 2018 (edited) ¿Puedes proporcionar tu registro de Kodi? In case translation is nonsense: Can you provide your Kodi log? Edited July 31, 2018 by Angelblue05 Link to comment Share on other sites More sharing options...
miguelcmran 2 Posted August 1, 2018 Author Share Posted August 1, 2018 Adjunto mi log de Kodi, hoy he probado a realizar una instalación limpia de Kodi instalando el addon de Emby para descartar que fuera problema de otro addon o del skin STVA para Kodi del que hago uso , y al terminar de realizar el escaneo de la biblioteca este ha sido el resultado: Uso la última versión de Emby para Linux, la 3.5.2.0. Si sirve como pista tanto esta versión como la 3.5.0.0 y la 3.5.1.0 tengo problemas con el proceso de Emby que se cae al tener el DLNA activado. La última versión que he tenido 100% estable de Emby para mi Raspberry era la 3.4.1.0 la cual nunca se me moría el proceso de Emby ni con el DLNA activado. kodi.log Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted August 1, 2018 Share Posted August 1, 2018 Es normal que la sincronización inicial use la CPU porque está importando todo su contenido a Kodi. ¿Tiene el mismo problema después de que se completa la sincronización? No voy a arreglar esto ahora mismo. Ya estoy trabajando en una nueva versión, pero necesito tiempo para terminar. Gracias por su paciencia. Link to comment Share on other sites More sharing options...
miguelcmran 2 Posted August 3, 2018 Author Share Posted August 3, 2018 (edited) Parece que ahora está estable el consumo de CPU de Kodi con el addon de Emby funcionando, por lo que lo doy por solucionado, no obstante como comento desde la versión 3.5.0.0 a la 3.5.2.0 tengo problemas con el proceso Emby en el que se cae o se queda al 100% uno de los núcleos del procesador, y me toca levantar el servidor por comando "sudo service emby-server start" o reiniciarlo para que el procesador recupere la normalidad. Siempre que entro en el log veo cosas relacionadas con el DLNA, el cual tengo desactivado pero aún así sale este error cada minuto: Error Dlna: Error in BeginListeningForBroadcasts *** Error Report *** Version: 3.5.2.0 Command line: /opt/emby-server/system/EmbyServer.dll -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_armhf.deb Operating system: Unix 4.14.58.7 64-Bit OS: False 64-Bit Process: False User Interactive: True Processor count: 4 Program data path: /var/lib/emby Application directory: /opt/emby-server/system System.Net.Sockets.SocketException (98): Address already in use at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at Emby.Server.Implementations.Net.UdpSocket..ctor(Socket socket, Int32 localPort, IPAddress ip) at Emby.Server.Implementations.Net.SocketFactory.CreateUdpMulticastSocket(String ipAddress, Int32 multicastTimeToLive, Int32 localPort) at Rssdp.Infrastructure.SsdpCommunicationsServer.ListenForBroadcastsAsync() at Rssdp.Infrastructure.SsdpCommunicationsServer.BeginListeningForBroadcasts() System.Net.Sockets.SocketException at System.Net.Sockets.Socket.UpdateStatusAfterSocketErrorAndThrowException(SocketError error, String callerName) at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) at Emby.Server.Implementations.Net.UdpSocket..ctor(Socket socket, Int32 localPort, IPAddress ip) at Emby.Server.Implementations.Net.SocketFactory.CreateUdpMulticastSocket(String ipAddress, Int32 multicastTimeToLive, Int32 localPort) at Rssdp.Infrastructure.SsdpCommunicationsServer.ListenForBroadcastsAsync() at Rssdp.Infrastructure.SsdpCommunicationsServer.BeginListeningForBroadcasts() Con la versión 3.4.1.0 tenía estabilidad total con DLNA activado. Edited August 3, 2018 by miguelcmran 1 Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted August 3, 2018 Share Posted August 3, 2018 @@Luke He's saying he disabled DLNA but he keeps getting errors regarding DLNA in his log. Original issue has been resolved. Link to comment Share on other sites More sharing options...
Luke 37063 Posted August 4, 2018 Share Posted August 4, 2018 We're looking that particular one. Thanks. 1 Link to comment Share on other sites More sharing options...
miguelcmran 2 Posted September 8, 2018 Author Share Posted September 8, 2018 (edited) Hola, sigo con los mismos problemas, os cuento. Tengo una Raspberry por cable de red conectada al router, donde tengo conectados dos discos y tengo instalado Emby Server con toda la biblioteca de peliculas y series de esos dos discos. Ademas tengo instalado Kodi con el addon Emby en la misma Raspberry que me sincroniza la biblioteca de Emby Server con Kodi. En esta Raspberry el consumo de CPU es correcto, entre 10-20% Luego tengo una segunda Raspberry por Wifi donde he probado tanto Libreelec como OSMC que recien instalados tienen un consumo correcto, pero que en cuanto instalo el addon de Emby para Kodi y sincronizo la base de datos de Emby con Kodi la CPU me sube a un 100% constante. Si deshabilito el addon de Emby para Kodi y purgo la base de datos de Kodi myvideos107.db automáticamente el consumo vuelve a un 10%, por lo que me da que el problema del consumo de CPU está relacionado con que el Emby Server está en la otra Raspberry y el acceso remoto no sé si es que genera latencia o que, pero la Raspberry esta en un constante 100% de CPU. He probado a cambiar parámetros de los ajustes del addon de Emby pero no soluciona el problema sólo soy capaz de solucionarlo purgando la base de datos de Kodi, pero me quedo sin la biblioteca de Emby en mi Raspberry. Edited September 8, 2018 by miguelcmran Link to comment Share on other sites More sharing options...
Luke 37063 Posted September 9, 2018 Share Posted September 9, 2018 Emby para Kodi tiene un proceso de sincronización y esto siempre requerirá algo de CPU. ¿Por qué no pruebas Emby Theatre para Kodi? No hay proceso de sincronización y es muy rápido: https://emby.media/community/index.php?/topic/42868-emby-theater-for-linux Por favor, háganos saber si esto ayuda. Gracias ! Link to comment Share on other sites More sharing options...
miguelcmran 2 Posted September 9, 2018 Author Share Posted September 9, 2018 Esto qué es? Un Addon que sustituye al Addon Emby de Kodi o una aplicación completa que sustituye al Emby Server? Porque yo actualmente el Emby Server lo tengo totalmente configurado con todas las categorías, películas y series y sería muy engorroso tener que volver a configurar todo desde cero. Gracias. Link to comment Share on other sites More sharing options...
Luke 37063 Posted September 9, 2018 Share Posted September 9, 2018 It is a new client application that you can use with Emby server. Link to comment Share on other sites More sharing options...
miguelcmran 2 Posted September 9, 2018 Author Share Posted September 9, 2018 I have read in the forum that with this parameter you can reduce the CPU consumption in the Kodi client: Any waitForAbort(5) are sleeps to limit cpu usage. Replace them with xbmc.sleep(1000) instead. Do you know in what file is this line? Would like to be able to have my Emby library synchronized with Kodi through the Emby addon, since the synchronization of the library is done well, with the logical CPU consumption, but it is later, when everything is synchronized, when the CPU goes up 100% without having anything to synchronize, and remains 100% constant without downloading at any time, unless you purge the myvideos107.db database. If I have the synchronization well done I would not have to consume that CPU constantly. Link to comment Share on other sites More sharing options...
Luke 37063 Posted September 9, 2018 Share Posted September 9, 2018 I've never heard of that but @@Angelblue05 may know. Link to comment Share on other sites More sharing options...
miguelcmran 2 Posted September 25, 2018 Author Share Posted September 25, 2018 He abierto un caso en el foro de Kodi por el consumo de CPU y me han pedido el log de Kodi, y esta ha sido la respuesta: The log file is full of messages like: 17:06:18.505 T:1554781040 DEBUG: CAddonSettings[plugin.video.emby]: failed to find definition for setting LastIncrementalSync. Creating a setting on-the-fly...17:06:18.505 T:1554781040 DEBUG: CSettingsManager: requested setting (SyncInstallRunDone) was not found.17:06:18.505 T:1554781040 DEBUG: CAddonSettings[plugin.video.emby]: failed to find definition for setting SyncInstallRunDone. Creating a setting on-the-fly...17:06:18.505 T:1554781040 DEBUG: CSettingsManager: requested setting (serverId) was not found.17:06:18.506 T:1554781040 DEBUG: CAddonSettings[plugin.video.emby]: failed to find definition for setting serverId. Creating a setting on-the-fly...17:06:18.506 T:1554781040 DEBUG: CSettingsManager: requested setting (token) was not found.17:06:18.506 T:1554781040 DEBUG: CAddonSettings[plugin.video.emby]: failed to find definition for setting token. Creating a setting on-the-fly...17:06:18.506 T:1554781040 DEBUG: CSettingsManager: requested setting (userId) was not found.17:06:18.506 T:1554781040 DEBUG: CAddonSettings[plugin.video.emby]: failed to find definition for setting userId. Creating a setting on-the-fly... I think you'd be better off asking in an Emby thread. Looks like a problem with the plugin. El caso es que cada vez que sincronizo la biblioteca de Kodi con Emby a través del plugin de Emby la CPU de la Raspberry se pone al 340-360% (85-90% por core de CPU) Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted September 25, 2018 Share Posted September 25, 2018 (edited) So you are saying that Kodi's own workaround for creating settings on the fly in Leia is causing the high cpu usage? I do have those messages too, but my cpu usage remains below 0.5% I however will look into the settings and hopefully that will help figure out if it was the issue or not. Edited September 25, 2018 by Angelblue05 Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted September 25, 2018 Share Posted September 25, 2018 I have read in the forum that with this parameter you can reduce the CPU consumption in the Kodi client: Any waitForAbort(5) are sleeps to limit cpu usage. Replace them with xbmc.sleep(1000) instead. I don't know where you read that but it's wrong? xbmc.sleep does not react to Kodi shut downs so that would cause Kodi to hang if anything was to happen during that time. Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted September 25, 2018 Share Posted September 25, 2018 So you are saying that Kodi's own workaround for creating settings on the fly in Leia is causing the high cpu usage? I do have those messages too, but my cpu usage remains below 0.5% I however will look into the settings and hopefully that will help figure out if it was the issue or not. Looks like settings.xml was changed for Leia. This is painful because it is a big change and it's not documented. This will have to wait for now. Link to comment Share on other sites More sharing options...
miguelcmran 2 Posted October 1, 2018 Author Share Posted October 1, 2018 (edited) Finally I found out that the CPU consumption was due to a Kodi addon (script.skin.helper.service) that apparently in Raspberry generates those consumptions. It had nothing to do with Emby's addon and not with Kodi's library having a lot of content. Edited October 1, 2018 by miguelcmran 1 Link to comment Share on other sites More sharing options...
Luke 37063 Posted October 1, 2018 Share Posted October 1, 2018 Well done. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now