8 hours ago
Hello, I don't know if this has been addressed before, I didn't see anything in a quick search of this forum.
I have the latest NextPVR running on a RPi 5 using Raspberry Pi OS, and I have a Mac mini running macOS Sequoia 15.7.1 (I'm not quite ready to go to 26 but I will soon). I've installed Kodi (21.2 Omega according to the file I downloaded) and the NextPVR client add-on (21.3.2) on the Mac. When I open Kodi after setting this up everything works fine. If I reboot the RPi, Kodi on the Mac continues to work just fine. But if I reboot the Mac, when I open Kodi and go to 'TV,' I'll see a screen where it shows a message saying something like "PVR manager starting up" with a little spinning circle, and it just spins and spins and spins. In order to get the NextPVR client add-on to work again I have to reinstall Kodi from the downloaded file over the existing Kodi. Then the NextPVR client is right there when I open Kodi, without me having to re-add the add-on.
Is this a known problem with a solution or workaround? I don't know if I have the same problem after the Mac goes to sleep; I haven't worked that out yet.
Thank you
I have the latest NextPVR running on a RPi 5 using Raspberry Pi OS, and I have a Mac mini running macOS Sequoia 15.7.1 (I'm not quite ready to go to 26 but I will soon). I've installed Kodi (21.2 Omega according to the file I downloaded) and the NextPVR client add-on (21.3.2) on the Mac. When I open Kodi after setting this up everything works fine. If I reboot the RPi, Kodi on the Mac continues to work just fine. But if I reboot the Mac, when I open Kodi and go to 'TV,' I'll see a screen where it shows a message saying something like "PVR manager starting up" with a little spinning circle, and it just spins and spins and spins. In order to get the NextPVR client add-on to work again I have to reinstall Kodi from the downloaded file over the existing Kodi. Then the NextPVR client is right there when I open Kodi, without me having to re-add the add-on.
Is this a known problem with a solution or workaround? I don't know if I have the same problem after the Mac goes to sleep; I haven't worked that out yet.
Thank you