So will it send me PCM 2.0 if I read TrueHD, even if my support is AC3 compatible?
IF RPi input: HD sound
THEN RPi output: nothing
Keep in mind that A/V has to stay in-sync when pass-through a device. Merging all the data needs compatible hardware.
Posts by Da Flex
-
-
Good. Keep in mind that your hardware is quite exotic. If you combine this with special version requests, you maybe get nothing from escalade.
-
Don't recall why I never did the 9x which I think Leia is. But I remember something off I didn't like.
If it was about an illegal add-on, then we don't support it. I'm just saying to not run into cat and mouse games. Most low-version guys do those games here.
-
Have a look at kodi.old.log, too, to see the shutdown part. You probably already know how to activate log level 1.
-
In theory this should work. But I wana take a backup from existing libre krypton which i think is 8.2.5 and put it on this.
Why not upgrading your existing Kypton, and then backup from there?
-
Is there anything I can do to 'capture' this issue?
Sure, have a look at kodi.log after a bad reboot.
-
PS: If one device on the transmission chain can't do pass-through for an (HD) audio format, then audio is simply lost at this point.
-
So if I have a track with TrueHD, will it send me the AC3 in 5.1 if I check compatible AV receiver AC3?
Same for DTS-HD?
I don't think so. Non of the devices on the transmission chain will do a conversion to a lower audio format.
-
To auto-scan posts for Chinese characters might help.
-
Since (as I have written above) Kodi is not running at all, this log file is not available. Also I'm not sure if kodi.log contains what I need.Can you confirm that kodi.log would contain messages from the kernel about tuner card drivers?
If you just need an add-on of Kodi, then you'll see the errors, warnings etc. generated by that add-on. You can run LE non-headless for testing, if no kodi.log appears headless - I'm not sure about it.
-
Really?
Yes, read here.
-
HD sound pass-through is not supported by LE on RPi (was already mentioned in another thread). You need more processing speed to pass-through that much data, it's not just "copy and paste".
-
Kodi has an own log system, which is different to standard Linux.
The kodi.log is the replacement for kern.log, and it's located (when is logging activated) at /storage/.kodi/temp.
There are different log levels. Log level 1 should fit your needs.
Activate logging at level 1 by creating the file /storage/.kodi/userdata/advancedsettings.xml with this content:
Code<advancedsettings> <loglevel>1</loglevel> </advancedsettings> -
I don't see any nightly builds for 9.0.2, too. It takes time to implement Kodi 18.2. The LE 9.0.x branch is still alive.
-
Update: I changed the volume name of the drive and now its working again as intended. Thanks for the relpys
What volume name do you use now? Knowing the name conventions could help other people.
-
To my knowledge they currently build LE 9.0.2, which implements Kodi 18.2. 9.0-devel should be the nightly builds for that version.
A good logic is (don't know if they do so):
LE 9.0.x implements Kodi 18.x
LE 9.1.x implements Kodi 19.x
-
-
I was not using HDhomerun. Was using it for my private library to watch movies
Sorry for my wrong interpretation.
Where are your videos stored? (internal SSD, external hard disk, NAS)
I know you have a large library. How long is the list you are scrolling through?
Does it freeze forever, or just for some time?
