For the past two years I have been running three remotes: drive, cache, and crypt. Today, I dropped the cache remote to go full vfs. After the switch, I direct streamed a video file with 12.7 MB bitrate and experienced visual blockiness in moving areas. When I streamed this file last night before the switch there was no blocking, and I'm wondering if I need to purge the cache. Also, when I transcode the video to the same bitrate (not direct stream), there is no blockiness, so I do not believe it is speed or bandwidth related.
for that, need to use --vfs-cache-mode full, which is different from --vfs-cache-mode writes, when it comes to using sparse files and the way it downloads just the chunks needed to stream a media file.
--fast-list does nothing on a mount.
for what it is worth, for streaming media from cloud using a rclone mount, myself and other rcloners do not use --vfs-cache-mode
You can compare this to the old service file in my top post, if needed. They are both there.
My concern is with any items that may still be cached after I removed the deprecated cache remote from the config. Could this be causing bad data to stream?
Edit: My mount command: systemctl --user enable --now rclone-vfs
if your rclone mount command no longer uses the old cache remote, then rclone no longer using the cache remote.
so just delete those files from your local storage and be done with it.
Oh, I'm familiar, thanks I learned quite a bit from looking at Animosity's scripts when I set this up a couple years ago. My problem is that my carrier restricts the use of certain service files, since I have a slot in a shared environment.
Glad to hear the old cache remote files aren't being accessed at all anymore, thank you.
Still troubleshooting why direct streaming the same video file worked better with the cache remote than without.