Please provide a Kodi debug log.
Posts by chewitt
-
-
I've recently been migrating Tvheadend documentation over to a new Docs/Wiki site https://docs.tvheadend.org and one of the text blocks I've moved talks about how multi-tuner setups on Raspberry Pi hardware can be troublesome. The issues flagged are power; as often you need to run tuners from a powered hub to ensure the current draw is handled instead of being directly connected to the Pi board, and bandwidth as this arrangement results in the tuners being connected to a single USB port. Then for extra credit it mentions that RPi 0/1/2/3/4 boards are sharing USB with Ethernet. RPi5 runs Ethernet from a proper PCI bus which should eliminate the latter issue, but the other issues are still possible.
What happens with one tuner connected directly and other tuners connected via the hub? (experiment with different combinations)
-
Please post the entire debug log else you eliminate all the useful background technical info on your setup, and all the useful info on the media being played. Just run "pastekodi" and share the URL.
-
The last official WP2 image with support for the internal tuner is LE 9.0 and there's a community image for LE 9.2. The newer AMLGX image has no support for the tuner cards and S905 is from 2015 so I really wouldn't waste $50 on WP2 as an upgrade. If the WP1 is working for you as a DVB-C receiver I would continue to use it as a network tuner-only device and invest the $50 in a new client box or board. RPi5 is my go-to recommendation but probably needs a few more pennies than $50 saved.
-
You probably need to enable pass-through audio, to avoid the inherent decode/conversion incurred with PCM.
-
Allwinner devices should be used in Direct-to-Plane mode, so you found an issue, but not the (correct) solution. Start with sharing a proper Kodi debug log playing something that shows the issue.
-
Please try again with https://chewitt.libreelec.tv/testing/LibreE…inix-u9h.img.gz which has a fix for the resize issue included https://github.com/LibreELEC/LibreELEC.tv/pull/8845 - it would be good to confirm this resolves the problem.
-
where is disable password auth?
only see in the services panel
ssh enable
password disable
Err, what you think "password disable" does?
-
Hello, what about DVB addons?
No change. There's been increasingly long delays between LE bumping to a new kernel and crazycat sources being available, which complicated our update cycles, and then upstream stopped maintaining the forward-porting mechanism required for dvb-latest. I'm not sure the team ever formally disussed abandoning all dvb-addon maintenance, but those add-ons incur a continual drip-feed of user complaints so over time we've exhausted the list of willing (and unwilling) volunteers. The best option is to find some hardware you can dedicate to an ancient LE or Ubuntu/Debian + modified kernel version and run cards/server end separate from a Kodi client running latest LE. And in the future, vote with your wallet and use hardware that either has upstream support or runs as a network appliance and avoid all driver shenanigans. Sorry for the lame/wrong answer
-
You need to install an Arial font that supports Arabic characters to /storage/.kodi/media/Fonts/Arial.ttf and reboot, then select this from Kodi Settings > Interface > Skin > Fonts > Arial based.
-
It's known and not something that can easily (or will be) fixed. The settings add-on is an independent background service. It doesn't run through Kodi and thus isn't part of the skin and cannot be skinned and cannot inherit properties of the skin. We've made it look like default Estuary to suit a percentage of users, but that's all we can do.
-
This thread is known to devs but since none of them have an afflicted AVR themselves it's not something that's easily tested. If the current investigation comes up with anything (nothing yet, and it's unlikely to be quick) then we'll flag the change and have you all test something to see if the issues are related. In short:
-
You can script kodi-send commands from the console to run/open the add-on, see https://kodi.wiki/view/List_of_built-in_functions but that will only work if the add-on automatically starts playing the stream when opened. If it presents any kind of menu/list of things to play the only option would be to include "keyboard" navigation too. That's possible via JSON-RPC, which is what phone-remote apps are using to drive the GUI, but the best place to ask for that advice would be the Kodi forum.
-
The architecture change means there are no e.g. RPi4 'arm' images to download hence nothing shows up in the list. We could fake the files to make GUI update simple, but that's also a bad idea since additional things like widevine libs and docker containers must be removed and reinstalled when changing arch and users need to be aware of this.
NB: I'll update the main release post on the website to give some instruction.
-
Code
AddOnLog: pvr.iptvsimple: pvr.iptvsimple - LoadPlayList - Loaded 84480 channels.There is no legitimate IPTV service with that number of channels so we don't really need to investigate further. You are reminded of our forum rules.
-
How can I use LibreELEC to access these drives via Ethernet connection
Share the drives to the network using Windows, then configure sources for them in Kodi. You will need to use authentication as on the Windows side you either share to a specific user (that you must authenticate as) or if "guest" shares are still a thing it means "any username/password can access" but you still need to access and authenticate using a username/password. I personally find it easiest to do this from the SSH console (editing /storage/.kodi/userdata/sources.xml and passwords.xml). Go read the Kodi wiki, it has all the "how to use Kodi" help you need.
-
Use "video=HDMI-A-1:1280x720M@60" not your odd resolution. Better or no difference?
-
Update to LE12 and retest. Any difference?
