If you are trying to "browse" the Windows network from LE it will not show anything because LE (and Win10) no longer use the SMB1 protocol which supported a network browse service. We now use SMB2 or SMB3 which do not. Microsoft also recently deprecated the homegroup function in the latest creators update.
Posts by chewitt
-
-
As someone already said earlier.. You need to go find someone who's more computer literate to help.
-
The best place to ask for support would be the plugin author's support thread in the Kodi forum. "Connection reset by peer" looks like a network issue; typically something being blocked.
-
Accessing LibreELEC [LibreELEC.wiki]
Use PuTTY to access the box over SSH, run "nano /storage/.kodi/userdata/sources.xml" and edit the sources to have valid URL's, then save (Ctrl+O) and exit (Ctrl+X) and reboot the box.
-
Stop using \\ and \ in the servername, don't append \ to the folder name, don't use an IP unless the Win10 box is on a static address (or static DHCP lease).
-
Kodi normally builds ffmpeg as an internal dependency to control the ffmpeg version and apply specific patches. LE builds its own 'external' ffmpeg but applies the same patches. We also have an 'ffmpegx' package in our build-system because Tvheadend also needs ffmpeg but it needs more features enabled than the quite minimal Kodi version.
I would not invest too much time/effort in the Amlogic 3.14 codebase. It's full of low quality kernel code and unresolvable issues. In the next couple of months we will have a mainline kernel/uboot with V4L2/mem2mem hardware video decode.
-
The "Kodi" user needs to have a password. Then you need to edit the existing 'sources' in Kodi to use that username/password (credential) when accessing the shares on the Win10 box. That can be done in the GUI (edit source). It can also be done manually by accessing the LE box over SSH and editing /storage/.kodi/userdata/sources.xml in a text editor (nano). As scary as that might sound it's often the quicker and easier way to edit things. The URL's in sources.xml need to be in smb://user:pass@server/path format.
-
The "git reset --hard" isn't necessary because you already checked-out the repo at a specific tag, and IMAGE_SUFFIX=v825 isn't required as the 8.2.5 version is part of the release image filename. Also be aware that the repo-tool script will download the sources for all packages in the build system; whereas if you allow them to be downloaded at build-time you only download sources for the packages used in the image you create. Apart from that (and one typo, which I corrected) all looks fine.
If you plan to build/rebuild things I'd recommend moving the 'sources' folder somewhere outside the main git folder and then creating a symlink to it. This allows you to nuke the git folders and re-clone (or share sources between multiple git folders) without having to re-download or duplicate all the sources. If you're a git novice it's kind of inevitable that at some point things get screwed up and the easiest way forwards is to nuke/clone again, and downloading sources adds time to the build process. NB: It takes a while to get the hang of git and everyone makes mistakes at first (nobody ever stops learning).
-
No harm in trying..
-
If there is no "just scan" option on the TV you can calibrate the screen in Kodi settings > system > display > calibrate. You need to calibrate for each refresh rate that your media requires.
-
Kodi is written around ffmpeg (some of the Kodi developers are ffmpeg developers, none are gstreamer fans) so anything that forces another player app into the codebase is always going to be an ugly hack that is hard to maintain. It would be long-term better to think about enhancing ffmpeg capabiltiies in Kodi and contributing improvements, not hacking gstreamer support.
Can you point me to your GitHub repo?
-
I can ask, but I don't recall seeing a lot of particularly useful info there that's not already duplicated between general technical info on the Compute Module (on the Pi Foundation site) and posts here.
-
wget or curl from an LE box, you cannot download in a browser
-
Kodi evaluates what to use at start, so turning the display off after Kodi starts won't result in Kodi dynamically reconfiguring itself. Stop Kodi, run the command, start Kodi again and it should only detect the active panel. If that works we can script it at startup.
-
-
The Amlogic change that happens in v19 is removal of the proprietary 'amcodec' interface in Kodi. Devices which are stuck on 3.10/3.14 kernels will not be able to run Kodi after this time. Devices which can run a mainline kernel will be able to use the next-generation video decoding and rendering pipeline that supersedes amcodec. Currently S905 devices and newer (excluding S912) can be supported on a mainline kernel. Anything older (and S912) is missing important kernel or driver code and is not supportable.
Kodi is written around ffmpeg and you will not be able to "swap" ffmpeg for gstreamer. Qt now has V4L2 support though, which should allow you to write a Qt app that runs with the next-generation V4L2/mem2mem video pipeline. V4L2 support was added to Qt by a Plex employee who is also an LE team member .. because Plex uses LE as the OS base for their "Plex Embedded" distro.
On Amlogic devices running a mainline kernel there is only /dev/fb0
-
We never allow/disallow something on the grounds of legality because the law of a specific country have little meaning to an internet based project with a global audience. Decisions are based on project policy which is formed from general morals.
-
Nope. There is no audio input/mic support in LE (or Kodi) to capture voice and send it somewhere for processing. You need to use an external device like a Google Home or Amazon Echo .. which is what the other poster is doing.