Jump to content

thomas.rehberg

Membres
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

0 Neutral

About thomas.rehberg

  • Rank
    Qnapeur fidèle

Profile Information

  • Matériel
    Futur Qnapeur

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. thomas.rehberg

    Kodi Leia

    in the Kodi18 directory you should be able to find a file called ".list". Think here the installation process is listing all files that have been installed. in my case this file has a size of 794.2kB, and is in fact documenting all files I have in the Kodi18 installation folder. I´m attaching this file here, maybe you can check if there are files missing in your installation? .list
  2. thomas.rehberg

    Kodi Leia

    the mykodi versions are pretty old I‘m afraid, I would not use them any longer. The only reasons to use them is if you need to stick to the legacy volumes, but this is not your issue. Your case is really strange, obviously there is no kodi.log as the app never started. In Qnapclub there are also two more packages you can try, one is Kodi 18.6, the other is Kodi 19. Can you try these first in order to overcome your issue?
  3. thomas.rehberg

    Kodi Leia

    I have no idea, we need to ask the author. I have installed the 19 version in parallel, from the same source, just for to do some compatibility checks, and I haven´t spotted anything that I´m missing.
  4. thomas.rehberg

    Kodi Leia

    Hi Chris, look into Qnapstore.eu, there is a 18.6 package. I have not tested it yet but you´ll find it under https://www.qnapclub.eu/de/qpkg/873 BR, Thomas
  5. thomas.rehberg

    Kodi Leia

    normally you should see kind of indication which HDMI is connected as the end device. I also see "SAMSUNG" (as I also have this brand) in the name of the HDMI connected. My setup is that the NAS is connected to one input of a SAMSUNG receiver, and the output of this receiver goes to the SAMSUNG TV. Originally I have had the NAS connected to the TV directly, but this will limit your audio to 2channels only (stupidly).
  6. thomas.rehberg

    Kodi Leia

    with this logging you absolutely need to check your audio config first. Passthrough is routing the audio stream directly to the ALSA device, and it looks like this HDMI related sound config has a problem. If you have more than one HDMI in your Kodi config page, try to use another device.
  7. thomas.rehberg

    Kodi Leia

    Try to look what PlayerDebug Info (STRG SHIFT O) is telling you: If there is a constant rise of VsynchOFF values then you know your problem. I might be that in passtrough you face an audio clock that is in deviating from the video clock constantly, and after a while it needs to skip frames to get back on sync. Otherwise you need to try the option "sync audio to video" in the Player options, but then you loose passthrough because of resampling. In my case this even does not help, but for others it does. Also, try to disable all motion improver in the TV, as in my case the "LED MOTION PLUS" was the reason (black frame injection, not frame rate doubling, this is something different), this is what I discovered yesterday . Not easy to find, but don´t give up
  8. thomas.rehberg

    Kodi Leia

    very strange indeed. Maybe they have changed some requirements meanwhile, remember that I had to open a ticket and worked with the R&D directly in order to find this out. But I never regretted having done the shift, the NAS works better than compared with the legacy volumes.
  9. thomas.rehberg

    Kodi Leia

    you are sure that you are running on the the new storagepool filesystem ? If not then make sure you migrate to it, as Kodi 18 will NOT start when on legacy volumes.
  10. thomas.rehberg

    Kodi Leia

    there should be also some other directories in the temp directory, is it totally empty ? I have a "archive_cache", "scrapers" and another "temp" in it, additionally to the logfiles. Are you sure having logging enabled ? Should be enabled by default, however. If you cannot start Kodi then you need to study "https://kodi.wiki/view/Log_file/Advanced" as you cannot go via the GUI like described in "https://kodi.wiki/view/Log_file/Easy". I´m afraid there is no other way for you as first make sure you get a logfile providing information what is (not) happening at startup of Kodi.
  11. thomas.rehberg

    Kodi Leia

    for to get the kodi.log in your QNAP server you need to login via SSH into your NAS. Then the path to your logfile is: "/share/CACHEDEV1_DATA/.qpkg/Kodi18/opt/.kodi/temp/kodi.log" there also is a kodi.log.old at the same place, which is the logfile from your last start of Kodi.
  12. thomas.rehberg

    Kodi Leia

    will do later today when back home, don´t know out of my head. Path is a bit depending on your platform, eg the Raid level you run.
  13. thomas.rehberg

    Kodi Leia

    Nico13, you should first look into your kodi.log to see what is recorded there, it normally should provide some indication. Otherwise this is pretty much a blind flight.
  14. thomas.rehberg

    Kodi Leia

    Friends, as chrisvdb said already: Look to my posts done earlier in this thread. You absolutely need to move away from the legacy filesystem and introduce the storage pools. Then it will work out of the box. I have invested a lot of effort with QNAP R&D (!) in order to get to that finding. Unfortunately this asks for a complete reinstallation of the NAS, there is no other migration, so be cautious and backup your data !
  15. thomas.rehberg

    Kodi Leia

    FINALLY: I can confirm now to the forum that the measure to walk away from legacy filesystem, and migrate to a thick-volume, does solve the problem with Kodi 18.3 on the Hybrid Station 4.03. Got it working now, and I think indeed this was the reason why for some folks it worked out of the box, whilst others (including me) where facing trouble big time ... I will talk back to QNAP Support that they should be very explicit in their compatibiliy statements when it comes to legacy volumes support, or simply drop it completely. At least it has to be part of regression testing. So I hope these efforts have been of some use to the community, at least at my end I'm happy now looking into Kodi back again
×