Rclone 1.53 release

Hi, I noticed in 1.53 it no longer says "Setting your own (client id) is recommended" and leaving that value blank is the default.

Whats the reason for the change? Will we have better performance if we don't use our own own API key?

Looks like an awesome release btw, super excited to use the new cache feature. Thanks so much!

1 Like

Using the default rclone would be bad as it's shared and over subscribed. Not sure what changed that.

1 Like

Brilliant, again.

I switched over to cmount on an iMac running MacOS 10.14.6

Running two mounts on separate teamdrives side by side, cmount is substantially faster at showing folders/files in Finder and also in initializing streams. Thank you!

Is there some basic info about cmount in the wiki, so I can point others to the feature (aside from rclone cmount --help ). I understand it takes time for the wiki to catch up with the new release/features. Asking only in case it is there and my small search-brain cannot find it :slight_smile:

1 Like

Oh, we unified the oauth config for all the backends. I forgot the drive backend had a special message.

I made an issue #4555 about this.

1 Like

Great :slight_smile:

rclone cmount should be almost 100% compatible with rclone mount. There are some differences in the -o options but other than that it works identically to rclone mount.

In 1.54 it will become the implementation when you type rclone mount.

1 Like

I confirm that error is harmless, but annoying!

I've made a fix for that here which I'll stick in 1.53.1 at some point.

v1.54.0-beta.4745.27b9ae4fc on branch master (uploaded in 15-30 mins)

Any chance we get some love for more bandwidth controls and rclone serve too ? <3

Bandwidth controls are in progress - I just didn't have time for 1.53 to finish them!

Is it bandwidth for serve that you are interested in?

I want to be able to set very high chunks to reduce API hits but without increasing bandwidth usage with that!

@ncw The rc docs formatting seems to be broken for me after the core/command section @ https://rclone.org/rc/#core-command.

Update: Found the issue and sent a PR: https://github.com/rclone/rclone/pull/4557

I've fixed that now - sorry I didn't see your PR update until after I've fixed it!

1 Like

Note that I'll be putting updates to the stable branch here (there will be one there in 15 mins or so!)

https://beta.rclone.org/branch/v1.53-stable/

Think of these as release candidates for 1.53.1 - they should all be stable

Thanks again for a great update. Can i check I understand the vfs-cache-mode full change please.

  1. I currently use vfs-cache-mode writes - so in 1.5.3 I don't lose any streaming performance e.g. start-up times or playback smoothness, but any old reads will now be stored in the buffer so repeat access times could be even faster (and no data transfer)?

  2. I have buffer-size 256M in my mount command, but I previously thought this was per stream, not for the full mount? E.g. 4 streams = max buffer of 4x256MB. Am I wrong, and it's for the whole mount and isn't affected by the number of streams and to benefit from the new full functionality, I might benefit from increasing the size of this?

Thanks in advance.

This replaces the cache backend from before and you can use vfs-cache-mode full instead and it'll keep a cache of the files on disk. It works with files, not chunks though. To be exact, they are kept on disk (cache) and the buffer is a different setting.

Best to just use the defaults rather than making changes and go from there.

thanks to all for v1.53.0

i noticed that on https://rclone.org/downloads/
the version number is v1.53.1 , not v1.53.0

image

@ncw is prepping a point release to hit a few things.

How do I control the location of this cache?

I'm trying to understand though what this buffer is as I think I've got it wrong now - is this different to the new cache, and is it per stream or for the whole mount?

--cache-dir /some/location

--buffer-size is per file opened and has not changed. Having a big buffer makes no sense since the files are on disk anyway with the full mode so it's best to leave it at the default.

1 Like

Thx - will try out 1.5.3

Edit: lol just seen --vfs-read-ahead as well. If I'm using the mount 99% to play files from Plex, how high do I go with this? To be honest, my current playback is pretty good in terms of startup times, but it'd be nice if this helps with e.g. skipping forwards

I've fixed that now. I made a mistake updating the website for the point release version number! :blush: