PolarWeasel Do you have pass-through activated at the audio settings?
Posts by Da Flex
-
-
Usage of banned add-ons means no support.
ThreadForum Rules
General Conduct- Be polite and respectful to forum staff and other users
- Be polite and respectful towards this project and other projects
- Be patient, user and staff are spread all over the world, an answer may take time
Posting- One topic per thread
- Posts should be written in English (add text in your native language if needed)
- Be as descriptive and detailed as possible. We are not mind readers!
- Do not cross-post or double-post
- Do not post or promote external URL links to products, a name
newphreakMarch 15, 2016 at 1:02 AM -
Would there be information elsewhere that would be useful?
No. At this point we are only digging in the dirt. You can try two other things:
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
The part where the stream is broken - related to audio somehow?
TV signals aren't always consistent. So maybe your setup is fine, and the stream gets interrupted by a short interrupt of the TV signal. It would be interesting, how TVHeadend handles such interruptions. Does it create a new recording file? Does it have a setting for such situations?
Other than that, no idea. You're already at log level 2, and no better explanation for creating a new recording file.
-
I think that's when the stream gets interrupted:
Code2024-03-31 14:31:57.930 T:957 error <general>: CAESinkALSA - snd_pcm_writei(-32) Broken pipe - trying to recover 2024-03-31 14:31:57.930 T:994 debug <general>: UpdateInProgressSize: Updating recordings size 2024-03-31 14:31:57.930 T:1951 debug <general>: Thread JobWorker 3595555456 terminating (autodelete) 2024-03-31 14:31:57.930 T:990 debug <general>: AddOnLog: pvr.hts: new connection requested
Can you update your NAS from NFS 3 to NFS 4?
-
Check your NTP settings.
CodeMar 30 02:59:01.277963 PiKodi nmbd[901]: [2024/03/30 02:59:01.277774, 0] ../../source3/nmbd/nmbd_namequery.c:109(query_name_response) Mar 30 02:59:01.277982 PiKodi nmbd[901]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.31.101 for name LANGCLAN<1d>. Mar 30 02:59:01.278020 PiKodi nmbd[901]: This response was from IP 192.168.31.123, reporting an IP address of 192.168.31.123. Mar 30 02:59:47.922456 PiKodi connmand[588]: ntp: adjust (slew): -0.023922 sec Mar 30 03:02:02.004453 PiKodi tvheadend[1388]: epgdb: snapshot start Mar 30 03:02:02.155433 PiKodi tvheadend[1388]: epgdb: queued to save (size 7908898) Mar 30 03:02:02.155525 PiKodi tvheadend[1388]: epgdb: broadcasts 20339 Mar 30 03:02:02.155551 PiKodi tvheadend[1388]: epgdb: save start Mar 30 03:02:02.412209 PiKodi tvheadend[1388]: epgdb: stored (size 1727297)
-
LeVraiRoiDHyrule Ask at the Kodi forum. We have a pinned post on top for our repo issues.
-
-
This usually happens when piracy add-ons are in use. We don't support such systems. Otherwise...
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
I was rather hoping I could configure this to set the Pi NOT to boot until the button was pressed on initial power on...
I'm not familiar with that SHIM. I assume when you plug in the PSU, it will always boot, no matter what's in the scripts.
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Just a small hint: Users love to know what a wizard does under the hood. Something like a visual checklist would be nice.
-
What do I save this as (filename and filetype) is it autostart.sh or as it's a python script is it whatever.py ?
Both. Call the Python script from this /storage/.config/autostart.sh:
Create the script folder: mkdir /storage/.kodi/userdata/scripts
Copy whatever.py into /storage/.kodi/userdata/scripts.
Make both files executable:
chmod +x /storage/.config/autostart.sh
chmod +x /storage/.kodi/userdata/scripts/whatever.pyCan I create both of these files directly on the SD card when its in my local machine or is it best to do so via SSH using nano?
Doesn't matter.
-
enabled passthrough DISPLAYPORT and output on displayport (NUC8i3) doesnt have a displayport.
buy it worked anyway from hdmi
That's because your NUC uses DisplayPort protocol internally, and then it's converted to HDMI by an LSPCon chip. LSPCon issues are unsolvable by us, so you're lucky. I think the HDMI firmware update was the real fix.
-
On TV's people can usually select different color schemes for HDMI input (I did so for my RPi). Maybe you'll find such an option for the projector, too.
-
Can you provide a log on Generic? Then we know which HDMI modes the projector is offering. Maybe a hi-contrast RGB mode is available, but not in use.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
ain't that for RGB limited ?
I think so. I suggest to play with xrandr options, before you invest serious time by compiling your kernel. I don't know how exactly HDMI negotiation works, but there is a chance that you can enforce an HDMI mode, which has better contrast on RGB. So update to Generic-Legacy, and go back to Generic, if it doesn't work.