Thanks, I’ve just created my own API with that little tutorial. Hopefully I can see some API hits tomorrow. Will update later.
@BinsonBuzz: I’ve moved from a 200/20 to a 500/500 so I expected at least some more speed, so it’s weird to me. I will try your advise for the changed buffer!
For the rclone rc command, do you run it as a standalone snippet right after the mount or is it integrated in a longer string?
Currently I’m not testing with Plex but with Emby, since previously I had better results with that. My library scan just finished on Emby so I will test some more tomorrow. Then I will also compare it to Plex with your throttle buffer setting.
I think I didn’t do it right yesterday with my own API, didn’t get any hits. So I created the API and deleted my rclone mount and tried to reconfigured. So I go through the rclone wizard, with client ID filled it from my dashboard. Then I get the 0auth screen and paste in the code. Then I get the following error:
2018/11/06 09:59:38 Failed to configure token: failed to get token: oauth2: cannot fetch token: 401 Unauthorized
Response: {
“error”: “invalid_client”,
“error_description”: “Unauthorized”
}
So could it be that my 0auth hasn’t been processed by Google yet, or am I doing something wrong? I only got asked for the Client ID during rclone config, not for the client password.
EDIT: just went through the Rclone config for the 5th time and this time it did ask for my client secret from the start. So now I’ve got this configured. Hopefully I will get api hits now.
I’ve put this code behind my mount but it gives me the following error:
Failed to rc: connection failed: Post http://localhost:5572/vfs/refresh: dial tcp 127.0.0.1:5572: connect: connection refused
My code looks like this now:
rclone mount --allow-other --dir-cache-time 72h --vfs-read-chunk-size 128M --vfs-read-chunk-size-limit off --buffer-size 100M --log-level INFO gdrive_crypt: /mnt/user/mount_rclone/Gdrive --stats 1m &
Sorry for dirtying up the thread. I’ve got the API working and the performance now is amazing! Startup times are within 5 seconds for my short tests with Emby Will also try Plex, see how it goes there. This feels like my previous performance again. Really amazing how big of a difference this makes!
Now if I could get that RC working then I’m pretty much set again I hope :).
hmm just checked my logs and I have the same - it was working before. Will investigate tonight.
Glad it’s working - basically it’s about the same as spinning up a local disk
I’ve got 80% of my media on gdrive now and I only really keep some of my 4K stuff local just to remove the bandwidth requirements, not because rclone can’t cope
Sorry, I meant vfs-read-chunk-size 64M Vs your vfs-read-chunk-size 128M
I went with 64M as I was trying to get faster start times, but I might test again with 128M as I got upgraded last month from 200/200 to 300/300, so it might be a bit faster.
I saw you somewhere post your Plex settings to stop analyzing. I browsed through your posts, but can’t find it anymore. Would you mind sharing it here again? I’m noticing Emby performs quite a lot better than Plex, which shouldn’t happen.
Thanks! That made me change some settings (not a lot). So I will test a bit with the read chunk size to see if that speeds up playing time. But I think it doesn’t make much a problem. At this point the mediaplayer device is probably the only limitation.
The IP address he is used is more related to his environment.
If you plan to run the rc commands from the same box, you can just use --rc and it’ll bind to the local loopback, which means only that box can access it.