I was a very happy Infuse user until I switched from having files hosted on my local network (via SMB) to RealDebrid-based hosting via WebDAV.
I’ve followed the instructions in Library Scanning & Indexing – Firecore Support to minimize library indexing time (for a Library-based browse, which I prefer). I’ve also to tried the default settings where more work is performed during indexing to see if it alleviated my spinning beachball issue described below.
A few other symptoms, in case it helps:
Large files in 2160p (~5-20 gb per hour of content) hosted on RealDebrid
Around 200 files in my library
I get a lot of spinning beachball moments, sometimes on indexing but frequently on attempting to play videos. I’ve had to force-close the app a few times. It seems the UI thread is blocked/ locked up by something
When videos do successfully play (~95% of the time), with or without spinning beachball happenings, it takes a very long time before the playback starts
My only reference point is playing the same videos, and indexing the same library in VidHub, which appeared a lot faster to me.
I did some quick testing Infuse v VidHub when it comes to playing videos (at this point with my library pre-indexed in both Infuse and VidHub).
Tried playing a 2h long 40 gb 2160p video via WebDAV. Infuse was ~1s faster than VidHub
Tried to play another 2160p video, 1h and maybe 5 gb: VidHub was ~1s faster than VidHub
So I was wrong. VidHub does not play faster than Infuse. It may appear faster since they are quicker to provide UX feedback once you press play (there’s a download speed indicator). Or, perhaps when I previously tried it was while Infuse was indexing, which may also has caused some slowdowns.
By default, Infuse uses a read-ahead disk cache for playback which is very useful in fluctuating network conditions, like Wi-Fi.
This can result in more requests to the server during certain periods of time and it’s possible some servers may not like this.
You can try adjusting the ‘Streaming Cache’ option found Infuse > Settings > Playback. Trying either Memory Only or Legacy may provide a better experience when streaming from this particular source.
I noticed you’ve been active on a few other posts — which is great to see! If you have a moment, I’d really appreciate it if you could take a look at my post regarding WebDAV playback issues. I’m hoping to get some insight from your end, especially since it might help clarify whether this is something Infuse-related or not.
I’ll be the one sitting patiently on the beach chair, watching the waves… and refreshing the thread.
Thanks in advance — looking forward to hearing your thoughts!
