[hdmkv]

Great, thanks for all the suggestions. With Fire Cube 3, SMB/NFS performing less than ideally has been my one complaint. And the cluttered UI w/ads, but that's a different story .

[xnappo]

Never done HTTP streaming. Only NFS & SMB. I see mention of Plex & Emby. Possible with Kodi? If so, how does one set this up? I see this wiki guide, but can a share be added just like with SMB/NFS? Wondering if one also needs to do something on the NAS side to allow this.

If you have a Synology NAS, you can install WebDAV Server on it and configure it.

You can then add an HTTP source to Kodi in the same way that you would add an SMB/NFS source. Just make sure you add the port number that you configure in WebDAV to the URL.

Thanks for this - I never noticed WebDAV was directly supported.  Even though I am happy using Emby to serve stuff - I do like being able to browse the real file system.  It was incredibly easy to install Apache and enable WebDAV on my Windows server!

[hdmkv]

What am I doing wrong? I got a can't connect error in Kodi, add it anyway?

[izprtxqkft]

What am I doing wrong?

first, what are you doing?

there's a lot of posts leading up to this one, not sure which one you are attempting

[xnappo]

What am I doing wrong? I got a can't connect error in Kodi, add it anyway?

If it doesn't connect, no point adding because it won't work.

What are you using as the server?  I am using Windows and Apache.

All I had to do was:
1. Download Apache from here: https://www.apachelounge.com/download/
2. Unzip to c:\apache24
3. Edit C:\Apache24\httpd.con
  Uncomment these lines:

Code:

  LoadModule alias_module modules/mod_alias.so
  LoadModule auth_digest_module modules/mod_auth_digest.so
  LoadModule authn_file_module modules/mod_authn_file.so
  LoadModule dav_module modules/mod_dav.so
  LoadModule dav_fs_module modules/mod_dav_fs.so
  LoadModule dav_lock_module modules/mod_dav_lock.so
  LoadModule setenvif_module modules/mod_setenvif.so
  Include conf/extra/httpd-dav.conf

4. Edit c:\apache24\conf\extra\httpd-dav.conf, add directories like this:

Code:

Alias /T "T:/"
<Directory "T:/">
    Dav On
    Options Indexes FollowSymLinks
    AllowOverride None
    Require all granted
</Directory>

Then run c:\apache24\bin\httpd.exe

Check it works in a web browser.

Then add WebDAV-HTTP in Kodi.

I also changed the port and added a password later, see here: https://mkyong.com/apache/how-to-enable-...x-windows/

You can install as a service using: .\httpd -k install

If you get stuck, ChatGPT can probably help.

[hdmkv]

Using Synology. As @MrMagic suggested, installed WebDAV Server package on my Synology. Opened it & enabled both HTTP & HTTPS. Left the two port values you see above as default. Then, went into Kodi & tried to add the HTTPS one as a network share.

[xnappo]

Using Synology. As @MrMagic suggested, installed WebDAV Server package on my Synology. Opened it & enabled both HTTP & HTTPS. Left the two port values you see above as default. Then, went into Kodi & tried to add the HTTPS one as a network share.

Use HTTP not HTTPS.  You almost certainly don't have a certificate.  Also you might click the anonymous box for now at least.

[hdmkv]

Ah, thanks much, HTTP works! Definitely snappier than SMB or NFS on FTV Cube 3. It almost feels like a mounted share like on nVidia Shield.

[maxcovergold]

Considering replacing my Vero 4k+ with Cube 3 for main TV to benefit from Dolby Vision and stumbled onto this thread.

My Kodi MySQL DB and media is on a Synology. With everything being shared by SMB. I've got Kodi on half a dozen devices around the house pointing at this.

If I wanted to go from SMB to http, could I just do a search and replace on the various SQL tables to change the protocol after enabling http on the Synology? Or is there a better or more correct way?

[maxcovergold]

EDIT - managed to get source working via WebDAV, scrapping and flawless remux playback over WiFi of my largest file.

Waiting for a USB>Ethernet adapter and will see whether can get acceptable performance on that over SMB before going down the rabbit hole of migrating my SMB MySQL library to DAV.  Though welcome feeback from anyone who's gone through something similar.

[blunden]

Now that chunk size changes actually take effect, it seems to work much better over SMBv3 after reapplying most of my old cache settings in the new GUI settings. I haven't done too much testing yet, but watched the Blu-ray remux I usually use for testing all the way though without issue. It didn't seem to cache very far ahead based on the progress bar, but played without any stuttering. Burst bitrate from the Wifi client did appear to be higher than efter before a few times.

For more details, I might check with the debug OSD later if I end up having issues in the future. Hopefully won't be needed though.

[Cris_]

Just a hint: Switch the Wifi band from 2.4Ghz to 5Ghz AP mode.

I have a RPi5 and it was connected via 2.4Ghz AP mode and got only 72Mbit/s which can be result in fps drops and stuttering for 4k/HDR, doesn't matter if i use the cache or chunk size options or SMB/NFS!

After switching to the 5Ghz AP mode i get 388Mbit/s and now problems anymore with empty player cache.

Router is a modern FRITZ!Box 7530 AX (EU, Germany)

[blunden]

Just a hint: Switch the Wifi band from 2.4Ghz to 5Ghz AP mode.

I have a RPi5 and it was connected via 2.4Ghz AP mode and got only 72Mbit/s which can be result in fps drops and stuttering for 4k/HDR, doesn't matter if i use the cache or chunk size options or SMB/NFS!

After switching to the 5Ghz AP mode i get 388Mbit/s and now problems anymore with empty player cache.

Router is a modern FRITZ!Box 7530 AX (EU, Germany)

I naturally ensured adequate network throughput (running on 5 GHz) before tweaking settings. It was never a problem with network throughput for me though, although I can see how 72 Mbit/s would cause issues.

Previously, with the default caching and prefetch behavior for SMB sources, it would cache very little and hardly use more bandwidth than the bitrate of the file. These settings were optimized for wired networking where latency and overall network performance tends to be very consistent so only very limited caching is needed.

On WiFi on the other hand, it's a shared half-duplex medium where every device has to wait its turn to transmit data. If you have other networks (from neighbors) on the same or closely adjacent frequencies (channels), you have interference from having to contend with the devices of that network too. All of this leads to variable latency and unpredictable network performance due to retransmissions. That's why you need to buffer a lot more to smooth over the variable network performance. Others had the same issue and improved the caching code and generally made it easier to tweak these settings, so what you find if you test it now is dramatically improved over how it behaved back in 2021/2022 when the thread was started. It now normally works well even with high bitrate content if you tweak the caching settings in the GUI, including content that was completely unplayable before.