The VFS options donât do anything if you are using cache so you can safely remove them.
The cache has itâs own buffer so setting it to 32M is not needed/wasteful on memory.
Moving the drive-chunk size that low makes transfers slower -> https://www.chpc.utah.edu/documentation/software/rclone.php
The buffering seems to be more player specific rather than setting specific from what Iâve tested. I can play without an issue with or without using the cache.
I find the cache to be slower starts slower than without.
Thanks, I removed buffer-size and both vfs options, didnât notice much of a difference, itâs still fast.
I donât see slow transfer with small chunk size? I tried from 32M in chunk size down to 4 and donât notice any speed difference, this on 1Gbit fiber up and down.
anyone having issues where an rclone mount is not being able to read the files in plex? The âvideoâ, âAudioâ section on plex show as ânoneâ and the playback wonât work, even though the rclone mount properly shows all the files listed in explorer and properly mounted. Iâm not able to play the file directly in explorer either (even smaller, 200mb MKVs file, let alone 50GB+ 4K files).
Is this related to heavy download and upload / 24 hour google ban?
Really nice post (and btw first hit on google when searching âbest rclone config plexâ). I based my config on these settings and am happy with the result so far.
Although I have one question:
Your current setup:
Plex > Encryption > Cache > Cloudsource.
Wouldnât it work (better) if you would build it this way:
Plex > Cache > Encryption > Cloudsource
Because then the cache contains decrypted files right? Not really experienced so there could be a flaw in my reasoning.
Iâve got my new updated plex server doing really well but I need to configure a cache now to stream 4k.
Going to test and see if I can push my server abit harder
NB https://rclone.org/cache/
From the Docs above it appears that you might have had it right to start with
âDuring testing, I experienced a lot of bans with the remotes in this order. I suspect it might be related to how crypt opens files on the cloud provider which makes it think weâre downloading the full file instead of small chunks. Organizing the remotes in this order yelds better results: cloud remote -> cache -> cryptâ