08:24 <benoliver999> Having issues scanning for new content, I think since upgrading to 9.2. I have turned logs on but it says nothing much. Starting scan, then

08:24 <benoliver999> VideoInfoScanner: Finished scan. Scanning for video info took 00:02

08:24 <benoliver999> My databse is over a shared MySql if that counts for anything

08:24 <benoliver999> Current entries in the DB play just fine

08:25 <benoliver999> I notice that there are a couple of " Process directory XXX does not exist" for stuff I deleted, which shouldn't be there because I ran Clean Library

08:25 <benoliver999> Again, dunno if that is related

08:26 <benoliver999> Naming seems ok, no different from before

08:38 <benoliver999> Agh it's weird, if I use the 'missing movies' add on, the movie is located

08:51 <benoliver999> Ah I think I have it, the content type got un-set

17:01 <Temparcota> Hello, is it possible to setup libreelec so if I download a file through torrent client that it gets saved to the pi? Currently I download a file and then ftp it to the pi. Trying to avoid this extra step.

17:05 <pragmaticenigma> Temparcota: LibreElec, and more specifically, KODI have had the ability to access remote file shares for a very long time. You can setup your sources with the "smb://remote_computer" for Windows/Samba File Shares for example. See the Kodi documentation https://kodi.wiki/view/Adding_video_sources#Adding_Remote_sources for more information.

17:06 <Temparcota> Thank you, I just started using LibreElec but I've used kdo for a while now. The reason with ftp is that device is in an area where I don't have it wired so all the content buffers.

17:07 <Temparcota> So everything on that specific device has to be stored locally. I grabbed a larger microSD just for that reason.

17:11 <Temparcota> I did try SMB on this unit before but even 25 feet away and it buffers a lot.

17:11 <pragmaticenigma> Some torrent clients have the ability to perform a task after the torrent completes downloading. You would have to consult the documentation on the client. As for hosting the files that you are torrenting on the RPi, that would not be recommended

17:12 <Temparcota> Oh no I wasn't trying to host the files from there. Just download a file using my torrent client but instead of the file downloading to this PC I wanted it to download directly to the pi device.

17:13 <pragmaticenigma> Temparcota: That's what I mean not recommended

17:13 <Temparcota> Is there a way to setup the rpi as a network drive so when I select save as location I can choose the pi in my torrent client?

17:15 <pragmaticenigma> Temparcota: You already expressed that your Rpi is located in a place where getting a stable network connection is hard. Adding to the mix of trying to "save" the file over the network directly is going cause a lot of issues, both in your overall network performance and your torrent client. Torrent clients do not handle network shares disappearing due to dropped connections very well, and will either lead to the torrent client

17:15 <pragmaticenigma> crashing, or the torrent client redownloading the entire file

17:16 <pragmaticenigma> Also, while you download a torrent file, the pieces you already have obtained are being shared with the swarm. Depending on the torrent tracker, your connection will quickly lose reputation and the admins of the tracker could ban you

17:17 <Temparcota> So what I'm doing now seems like my best bet. My only concern is the speed not sure why it takes22 mins to send over 4GB.

17:17 <pragmaticenigma> Temparcota: what you are doing now is recommended. Handle all the torrent activities on one computer, and then research into having your torrent client copy the file to the RPi, or at least a "completed" folder for another system task to check and sync over to the Rpi

17:18 <Temparcota> Alright thanks.