RcloneView uses ALL System/Network Resources when uploading

First time using RcloneView, I’m trying to Copy/Paste files into a Folder on pCloud, I’m using RcloneView’s Encryption on that folder. However, I have a big problem.RcloneView literally uses every single system or network bandwidth on my system that I literally can’t even open a “browser page” with Edge.The turkey….? I’ve never seen such a thing except like 20 years ago…Now, I know I can “limit” the Network usage, so I’ll try that next.But I’ve also tried adding these codes to the “Global Rclone Flags”, and none of them work.

–no-check-certificate;–ftp-no-check-certificate;–s3-directory-markers;–transfers 2;–checkers 2;–bwlimit 10M;–tpslimit 4;–low-level-retries 1;–rc;–rc-no-auth

I have like “10” or something Transfers trying to occur at the same time, so I’m trying to “limit” the number.
I’ve tried the above, I’ve tried –transfers=2, etc. etc.
Nothing seems to work.

I haven’t tried using “Add Job” yet…. I’ve just tried copy and pasting the files over.
I’ve read that maybe that doesn’t work yet, I have to use Add Job instead?

Anyway, I’ve never seen such a thing with ANY program that it literally takes over ALL Resources. Even other Download programs when set to as fast as possible still don’t USE EVERYTHING the computer has. I can STILL use my browser etc.
So, there seems to be some problems here….

  1. Is Limiting the Bandwidth the only solution?
  2. Do I “have” to use “Add Job” to get the Transfer settings to work?
  3. How do I properly get the Transfers to work?

Thanks…. Happy to see this program. Was worried I might have to use Mountain Duck, seems to be the ONLY other program that will Encrypt files etc.

Thanks for the detailed write-up, and welcome to the forum.

We’ve logged this on our side and it’s being looked into — both parts of it: transfers saturating your system and network, and the Global Rclone Flags not taking effect for copy/paste transfers.

A couple of things would help us narrow it down:

  • Your OS and RcloneView version (and whether the pCloud target is going through a Crypt remote in every case)

In the meantime, it’s worth running the same transfer through Add Job and seeing whether the transfer settings behave differently there. That comparison is useful for us as well, so let us know what you see.

We’ll follow up here once we have something concrete.

Hi, thank you so much for the Reply… I’ll get back to you as soon as I can with the Test Results.
What I have now…

  1. Windows 10
  2. I didn’t try “Non-Encrypted” Copy/Paste Transfers yet. But will do so. So yes, every attempt has so far been trying to upload to a Remote Crypt.
  3. Will try the “Add Job” option…
  4. Using last Rclone version 1.5.10 (oh I see it’s been updated since last week)

Recommended Improvements….

  • We need “Stop” and “Resume” Transfer buttons. Might be good to put them next to the “Trash” icon above the Transfer window?
    When I was having the above issues, I actually couldn’t “stop” the Transfers most of the time using the “X” in the program, nor trying to use the “Exit” in the right-click Taskbar Manager Icon.
    I had to go to “Task Manager” and End Task both the program and Rclone.

Thanks, :slight_smile:

Hi @leeuniverse — thanks for the detailed report, and sorry for the rough first impression. You found a real bug, and it turned out to be two separate problems stacked on top of each other.

1. Copy/Paste ignored --transfers and --checkers. This one is on us. When you paste files in the explorer, RcloneView was starting a separate rclone job for every single file. rclone’s --transfers limits how many files move in parallel within one job — it has no say over how many jobs run at once. So selecting 10 files always meant 10 simultaneous transfers, no matter what you put in Global Rclone Flags. That is exactly the “10 or something Transfers” you saw.

We’ve fixed it: a paste, drag-drop, upload or download now runs as a single rclone job covering everything you selected, so --transfers, --checkers and --bwlimit all apply the way you’d expect. Measured on our side with --transfers 2: it went from 10 concurrent transfers down to 2. The fix is on a branch now and will ship in an upcoming release — I’ll follow up here when it’s out.

2. Your flags may not have been applied at all — please check the dashes. In the list you posted, the flags start with an en dash (–) rather than two ASCII hyphens (--). It may just be the forum’s editor auto-converting them, but if that’s what’s actually in the settings box, it matters: rclone refuses to start with an unrecognised argument, and RcloneView then restarts it with all global flags removed. That would mean none of your flags took effect — including --bwlimit, which does work correctly today.

Could you check the Global Rclone Flags box and confirm whether the characters are -- or –? Retyping the line by hand (rather than pasting) is the quickest way to be sure. We’re also going to add a validation warning so a bad character can’t silently wipe the whole list.

Two other answers to your questions:

  • Is bandwidth limiting the only option? No — but --bwlimit 10M is genuinely your best lever today, because it’s enforced globally by the rclone daemon and isn’t affected by bug #1 (closed). If you retype the flags with proper -- hyphens, it should take effect immediately, without waiting for the fix.
  • Do you have to use Add Job? Until the fix ships, yes — that’s the reliable workaround. The Add Job path has its own transfer settings and honours them correctly. Once the fix is released, Copy/Paste will behave the same way.

One note about --rc and --rc-no-auth: RcloneView already runs rclone in remote-control mode itself, so those two aren’t needed and are best left out.

Thanks again — this was a good catch, and it also led us to find a couple of related issues we’d otherwise have missed.

Thanks — and the part about not being able to stop it is the most important thing in your reply. That’s arguably worse than the original bug, so let me answer it directly.

Why X didn’t stop anything. By default the X button doesn’t quit RcloneView — it hides it to the system tray, and rclone keeps running behind it with the transfers still going. You can change that with Settings → “Quit on close”. We’re also rethinking that default, precisely because it lets a runaway transfer keep running behind an apparently-closed app.

Why you couldn’t cancel your way out. There’s no “cancel everything” button — only per-transfer cancel in the Transfers tab, each behind its own confirmation dialog. With ten separate transfers on an already-saturated machine, that isn’t a usable escape hatch. You’re right, and we’ve opened a ticket for a Cancel All button in the transfer window, next to the trash icon exactly where you suggested.

Stop vs Resume. Stop is straightforward and is in that ticket. Resume needs a caveat: rclone has no true pause/resume. We can stop and then re-run, and since rclone skips files it already copied, that behaves like resuming — only the one file that was mid-flight starts over. Better to say that now than ship a “Resume” button that quietly means something else.

Your version. You’re on RcloneView 1.5.10 and the current Windows release is 1.5.29, so there’s a fair bit of unrelated fixing in between worth picking up. To be clear though, the Copy/Paste fix isn’t in any release yet — I’ll post here when it ships.

Crypt. Worth flagging, but the bug isn’t Crypt-specific — it’s about how many transfers we start at once, so a plain remote hits it too. Crypt just makes it hurt more, since every transfer is also doing encryption on your CPU. Your non-encrypted test will likely still show too many simultaneous transfers, with less CPU burn. Still a useful data point.

No rush on any of it. If you only get to one thing, the dash question from my last message is the one that matters — it decides whether your --bwlimit was ever active.

  1. No worry’s, I’m just happy your program exists and you’re doing great work supporting it. Growing pains are okay. :slight_smile:
  2. Great to hear you fixed the Copy/Paste :slight_smile:
  3. Ya, the Forum put the 2 dashes into 1 single dash. I was following the format you have in the “Global Rclone Flags”. The improvements sound great. :slight_smile:
  4. Ya, the rc and rc no auth I was just trying different things to make it work. Will leave out. :slight_smile:
  5. Ya, the X I just put that in, couldn’t remember at the time. So, yes, I couldn’t exit out the program from the Taskbar either.
  6. Great to hear about Stop Transfer. :slight_smile:
  7. Ah, maybe the “Resume Transfer” Button could do it as you say, and then maybe you can add a Hover “Note” that says how it actually works, that it restarts “Incomplete” File Transfers?
  8. When I have the Updated version I’ll fully test things, cause then I can do my Uploads, and then let you know if any issues. So, I’ll wait for the moment to do the various Transfer Tests, and then we can know for sure how well things are working. I don’t want pCloud to have a spaz attack if I’m trying to upload so many files at once LOL. :slight_smile:
  9. Yes, my “dashes” were correct…. It’s just the Forum that changed them. Though, “Formating” otherwise was a question, if I needed to uses “spaces” or an = Equals sign?

Thank you so much for your work…. Happy to help something good that’s needed.
You’re fitting a “niche” we were definately needing.

Also, I haven’t checked everything yet with your program, but is there a way to “decrypt” our files like with Cryptomater or something if we ever don’t have access to your program, like we can with Mountain Duck?
Thanks again… :slight_smile:

Good news: the Copy/Paste fix is out.

It went in at 1.5.30, and the current Windows download is 1.5.32 (macOS is 1.5.35), so it’s live now. You’re on 1.5.10, so updating picks this up along with everything in between.

What changed: a paste, drag-drop, upload or download now runs as a single rclone job covering your whole selection, instead of one job per file. --transfers, --checkers and --bwlimit from Global Rclone Flags now apply to explorer transfers the way you’d expect. In our test case, --transfers 2 took it from 10 concurrent transfers down to 2.

One caveat so you don’t get caught out: this fix covers the explorer path (paste, drag-drop, upload, download). If you use Add Job, set the transfer options in the job’s own settings, because Global Rclone Flags don’t yet carry through to jobs in 1.5.32. That’s a separate bug, it’s fixed on our side, and it will land in the next release.

Your formatting question: spaces or =?

Both work. Use whichever you prefer:

--transfers 2 --checkers 2 --bwlimit 10M
--transfers=2 --checkers=2 --bwlimit=10M

Separators can be spaces or semicolons, and you can mix them. Quotes group a value that contains spaces, e.g. --exclude "My Folder/**".

The one thing that genuinely breaks it is the character we discussed: a non-ASCII dash. rclone refuses to start on an unrecognised argument, and RcloneView then restarts it with all global flags dropped. To be straight with you, the input validation warning I mentioned isn’t built yet, so until it is, typing the flags rather than pasting them is still the safe habit.

Decrypting without RcloneView

Yes, and there’s nothing to migrate. RcloneView doesn’t use a proprietary container. When you set up encryption it writes a standard rclone crypt remote into an ordinary rclone.conf (its path is shown in Settings). That means:

  • The plain rclone CLI reads the same config and decrypts the same files: rclone copy secret:folder /local/path
  • Any other rclone-based tool can do the same
  • What’s sitting on pCloud is standard rclone crypt, a documented open format, not something only we can read

Worth keeping a backup copy of rclone.conf somewhere safe. That file plus the rclone binary is everything you need to get your data back, with or without us. Treat it like a password file though: rclone obscures the crypt password in there rather than encrypting it, so anyone holding the file can decrypt your data.

Cancel All / Stop

Tracked, not built yet, and I’d rather say so than let it sound done. The batching fix removes most of what got you into that corner (one paste is now one cancellable job instead of ten), but there’s still no one-click “cancel everything”. Same for the Quit on close default, which we’re still thinking about. In the meantime, Settings → Quit on close makes the X button actually exit instead of hiding to the tray.

If you do get around to your upload tests, I’d be glad to hear how pCloud holds up.

Wonderful… Will get to doing a full test, and digesting your info likely this weekend, or as soon as I can. Have gotten into watching BYU games with my sons, so I’m trying to figure out the best cheap way to do it, since they show them on different channels, ESPN+, Fox, CBS, etc., so that’s taking up some of my time. I used to just mostly watch game Highlights. LOL

Sounds great, take your time! Enjoy watching the BYU games with your sons…that sounds like a fun way to spend time together. Hope you find a cheap streaming option soon!

Hi there… Okay, I’ve finally been able to start doing my uploads, testing the program.
Here are my initial Observations and thoughts….

1. So, I was just doing Copy/Paste/Drag & Drop, seeing it if was working well, seemed to go well for both the Vault and regular pCloud folder upload. I haven’t done any “Syncing” etc. yet. Once everything is uploaded I will, and I’m sure I’ll use the Add Job option.

2. I did add the “Flags” we talked about… and they worked.
–transfers=2 --checkers=2 --bwlimit=10M
Now, I don’t know I didn’t test, but do you have these as “hidden”, or did I need to add them to work? I would actually recommend you have them as “Default” showing in the field, so if we want to change or remove etc. we can.
I think this would be a good “default” setting, do you think?

3. You likely know this already, it would be ideal if the Individual Transfers that are part of a Group, if they showed as “Completed” instead of Running still, when they’ve actually completed.

4. I noticed there were some Transfers which showed as 183% or 102% when they were completed. Is this a bug?

5. It would be good if we had a “Setting” in which we could choose if ALL files are shown in the Transfer Window, or just the “Group”. I would prefer to see just the Group Transfer. I know I can manually change it. But, I would rather have that as “Default”, and then if I need to “expand” to see ALL the files, or deal with individual files that are transferring I can still do so.

6. In relation to “Stop/Start” buttons….
It would be good if we had simple Stop/Start Buttons (or a single button which Starts/Stops, and it shows a Play Arrow for Resuming, and a Stop Square for stopping) for the entire Transfer Window that Starts/Stops ALL Transfers.

Then, it would be good if we also were able to “Right Click” on both a Transfer Group, as well as Individual Transfers and Stop/Start them.
I think this might be the best way to put in these functions?

I noticed you had a “Cancel” “X”…. If that stops a transfer, you might want to get rid of it and do the above and below methods instead?
So, just canceled a Drag/Drop Transfer (aka Copy), and I discovered I can’t “Restart it”. I have to try to “remember” the files I had previously tried to Transfer, and do them again.
So, we definitely need the functionality of above and below to work better with the Transfers, to be able to Start/Stop them.

You might also want to add the ability to “Highlight/Select” a particular Transfer, and the main Stop/Start button/s will actually stop/start that individual or group transfer. However, if none are highlighted, then everything in the Transfer window starts/stops.
Just some ideas… :slight_smile:

7. I would recommend we also have a “Setting” which is set by Default to NOT show “Protected System Files”, such as the RECYCLE Bin of a Drive, or System Volume Information etc. folders or other files. These folders and files are in the way.

8. Could we get a “Sound” to let us know that All Transfers have completed?

9. Could we get like a “Gif” image over the Taskbar Icon, which shows “Transferring” of files, like other Download/Upload programs do?

Those are my initial observations with using the program and it working as it should.
Thank you for working on this program…. I’ve purchased it. I like what you’ve done, and your work ethic. Look forward to giving more thoughts as I use it and get more familiar with it.

Thanks again… :slight_smile:

I guess I can’t “edit” my previous post….?

#7 I’ve used a “Workaround” adding exceptions to my “Jobs” to prevent at least the Hidden Windows files I know about to not be copied over. A “Setting” would still be good in program for those and other files we might not know about or see which are still being transferred.
The Exceptions Rules also aren’t helpful if we are doing Copy/Paste aka Drag & Drop. Though, there might be such a section also in the “General Settings”, I need to check.

#8 I see when we’ve set a “Job” we DO get a “Windows Notification” on Transfer completion.
But, a Completion “Sound” would likely still be good to add, especially for the cases when we are doing Copy/Paste aka Drag & Drop Transfers.

Or, I guess actually adding the “Windows Notification” for ALSO those Transfers Completions is something we need. There WAS a sound with the Windows Notification if I recall? So, just adding it for also Copy/Paste is likely all we need.

I’ve added a big Feature change request to the “Features” section of the Forum. Hope you like the idea? :slight_smile:
Thanks again for everything…. Loving the program. :slight_smile:

Good news: the Copy/Paste fix is out.

It went in at 1.5.30, and the current Windows download is 1.5.32 (macOS is 1.5.35), so it’s live now. You’re on 1.5.10, so updating picks this up along with everything in between.

What changed: a paste, drag-drop, upload or download now runs as a single rclone job covering your whole selection, instead of one job per file. --transfers, --checkers and --bwlimit from Global Rclone Flags now apply to explorer transfers the way you’d expect. In our test case, --transfers 2 took it from 10 concurrent transfers down to 2.

One caveat so you don’t get caught out: this fix covers the explorer path (paste, drag-drop, upload, download). If you use Add Job, set the transfer options in the job’s own settings, because Global Rclone Flags don’t yet carry through to jobs in 1.5.32. That’s a separate bug, it’s fixed on our side, and it will land in the next release.

Your formatting question: spaces or =?

Both work. Use whichever you prefer:

--transfers 2 --checkers 2 --bwlimit 10M
--transfers=2 --checkers=2 --bwlimit=10M

Separators can be spaces or semicolons, and you can mix them. Quotes group a value that contains spaces, e.g. --exclude "My Folder/**".

The one thing that genuinely breaks it is the character we discussed: a non-ASCII dash. rclone refuses to start on an unrecognised argument, and RcloneView then restarts it with all global flags dropped. To be straight with you, the input validation warning I mentioned isn’t built yet, so until it is, typing the flags rather than pasting them is still the safe habit.

Decrypting without RcloneView

Yes, and there’s nothing to migrate. RcloneView doesn’t use a proprietary container. When you set up encryption it writes a standard rclone crypt remote into an ordinary rclone.conf (its path is shown in Settings). That means:

  • The plain rclone CLI reads the same config and decrypts the same files: rclone copy secret:folder /local/path
  • Any other rclone-based tool can do the same
  • What’s sitting on pCloud is standard rclone crypt, a documented open format, not something only we can read

Worth keeping a backup copy of rclone.conf somewhere safe. That file plus the rclone binary is everything you need to get your data back, with or without us. Treat it like a password file though: rclone obscures the crypt password in there rather than encrypting it, so anyone holding the file can decrypt your data.

Cancel All / Stop

Tracked, not built yet, and I’d rather say so than let it sound done. The batching fix removes most of what got you into that corner (one paste is now one cancellable job instead of ten), but there’s still no one-click “cancel everything”. Same for the Quit on close default, which we’re still thinking about. In the meantime, Settings → Quit on close makes the X button actually exit instead of hiding to the tray.

If you do get around to your upload tests, I’d be glad to hear how pCloud holds up.

Thanks again for taking the time to share your feedback and report this issue—it really helps us improve!

LOL… You posted this previous already and I responded to it also.
My prior two posts were updating you that I had finally been able to “Test” the new Copy/Paste, and it all worked well.
And then I gave you my “Initial Impressions” of things I noticed finally able to properly use the program the way I was trying.
So, I have a “List” of suggestions…. I posted above.

FYI…. Thank you much. :slight_smile:

Sorry about my last reply. That was an earlier message posted again by mistake, not an answer to your list. Here’s the actual answer.

One correction to that old message: Global Rclone Flags now carry through to Jobs too, as of 1.6.6. Leave a Job’s Transfers and Checkers empty and it uses your global values; fill them in to override them for that Job.

Thanks for the thorough test run, and for buying a license. Good to hear copy/paste and drag & drop now behave on both the Vault and the plain pCloud folder.

I checked all nine points against the code. Short version: 3 and 4 are one real bug (the Vault, explained below). It’s already fixed, and the fix is in 1.6.6, which is out now. 6 turned up a real gap, and the rest are good ideas that are now on our list for our next development cycle. I’ll post here as pieces ship.

2. Were those flags hidden defaults?

No, they only took effect because you added them. The field ships with three unrelated flags (certificate checks and an S3 setting). With nothing else in it, rclone’s own defaults apply: 4 transfers, 8 checkers, no bandwidth limit.

I’d rather not make 2 / 2 / 10M the default for everyone, because on a fast connection or with S3 it would slow people down a lot. What we will do is show what’s actually in effect right in that field, with an example, the way the Job editor already does for its transfer settings. Keep your line as it is.

3 and 4. “Running” after completion, and 183% / 102%

Same bug, and the Vault is the cause. When rclone uploads through encryption, it counts the encrypted bytes, and an encrypted file is slightly bigger than the original: 32 bytes of header plus 16 bytes per 64 KB block. RcloneView only marked a file “Completed” when the byte count matched the file size exactly, so every Vault file stayed on “Running”. The percentage had no cap either.

The numbers you saw fit exactly. A 58-byte file becomes 106 bytes encrypted, which is 183%. A 2.4 KB file gains 48 bytes, which is 102%. I reproduced both. It’s display only, and your files upload correctly. Uploads to the plain (non-Vault) folder don’t hit this.

It’s fixed now. RcloneView no longer does byte arithmetic to decide a file is done: it uses rclone’s own list of finished transfers, so Vault files now show “Success” when they’re done, and the percentage stops at 100%. I checked it with 58-byte, 2.4 KB and 40 MB files, during the transfer, after the group finished, and after restarting the app. The fix is in 1.6.6.

5. Show only the group by default

Agreed, and it’s logged as a setting. While checking this I found a bug that makes it worse: whenever a transfer finishes, every group you had expanded collapses again. That gets fixed along with it.

6. Stop / Start

  • Restarting after Cancel: you hit a real gap. RcloneView already remembers what was in a drag & drop or paste, so it can run it again, but it only offers Retry for transfers that failed, not ones you cancelled. We’ll offer it for cancelled ones too. That’s effectively the “Resume” we talked about: files that already made it are skipped, and only the file that was mid-flight starts over.
  • Stop all / Start all, right-click on a group, select-then-stop: added to the existing ticket for the stop-everything button.
  • One limit: a single paste or drag & drop is one rclone job, and rclone can’t pause or drop a single file inside a running job. So Stop/Start will work per group, not per individual file.
  • We’ll keep the X until its replacement exists, so you’re never left without a way to stop something.

7. Protected system files

Agreed. One wrinkle: rclone can’t see Windows’ “hidden” or “system” attributes, so it has to go by name ($RECYCLE.BIN, System Volume Information, desktop.ini, Thumbs.db and the like). What we have in mind is a setting, on by default, that hides these in the file list and leaves them out of copy/paste and drag & drop.

To answer your follow-up: there’s no global exclusion section in General Settings today, so you’re right that Job exclusions don’t help with copy/paste. For Jobs, your exclusion rules are still the right approach until then.

8. Completion sound

I think your own conclusion is the right one: send the same Windows notification (which brings the sound with it) when copy/paste and drag & drop transfers finish, not just Jobs. Most likely once when everything has finished, rather than a ping for every paste, with a switch to turn it off.

9. Taskbar progress

Logged. Windows’ own way of showing this is the green progress fill behind the taskbar icon, so that’s what we’d use rather than an animated GIF.

I’ll answer your Dry Run vs Compare idea in that thread.

Absolutely ASTOUNDING…. I just love your attention to detail, skills, and work in all this.
It’s much appreciated to see some real quality happening.
Thank you for that…. Everything looks great and understandable in what you’ve stated. :slight_smile:

Hi leeuniverse,

Thank you again for the detailed suggestions in this thread. The three items from your October 3–4 posts are implemented and will be in the next RcloneView release.

1. Restarting a canceled transfer: Canceled copy, move, upload and download transfers in the Transfer window now show a Retry button, the same as failed ones. Retrying skips the files that were already copied and sends the rest; the file that was in progress when you canceled is sent again from the start. A tooltip on the button explains this. Note: Retry is available for transfers from the current session. After RcloneView is restarted, older entries loaded from history cannot be retried. Also, a transfer canceled while it was still checking files is now shown as “Canceled” instead of “No Changes” or “Success”.

2. Showing only the transfer group: There is a new setting: Settings › Interface › “Show transfer groups collapsed”. When it is on, new and past transfers start with only the group row visible, and you can still expand a group to see or manage individual files. We also fixed the behavior where groups you had expanded collapsed again by themselves whenever another transfer finished or the filter changed.

3. Hiding protected system files: There is a new setting “Hide system files”, on by default. When it is on:

  • The file explorer no longer lists $RECYCLE.BIN, System Volume Information, desktop.ini, Thumbs.db, pagefile.sys, hiberfil.sys, swapfile.sys, and on macOS .DS_Store, .Spotlight-V100, .Trashes, .fseventsd.
  • Copy/paste, drag & drop, upload and download from the explorer skip these files, so you no longer need workarounds for those transfers.

For Jobs, existing Jobs are not changed. In the Job filter settings there is a new “System files” preset you can tick to exclude the same list, instead of adding the exceptions by hand.

Please let us know how these work for you once you have updated.

Best regards,
RcloneView Team

Great to see the continued development…. Will do.

So, after using RcloneView full-time for all my Transfers, I’ve encountered some issues.

  1. I’ve discovered when simply changing a “Folder Name”, the ENTIRE Folder is Deleted and then “re-uploaded”. This was a surprising thing with a file-transfer program, something default with Rclone. I was expecting a short Transfer job, because I re-named the folders of 3 huge game folders, and I thought some bug was happening, and realized I was re-uploading 3 huge 60-100GB folders again. UGH. When searching for the issue, I discovered it’s an rclone limitation.

    Apparently by adding “- -track-renames” to the Flags of the job, rclone will “check” for folder name changes first? Though, the instructions says “may”…. So, I don’t know yet if this is actually working, need to test further still.

    This is a BIG issue…. I noticed you didn’t include that Flag as one of the "options” in the “Batch Job” Flags section we could “check” to use as part of a job, but you included a ton of other flags we could use. Could you add that one?

    Of course, the “true fix” for this issue is can you try to get the rclone Developers to ADD Folder/File Name changing as an ability of rclone by default? Just weird to me it would have that limitation, that simply changing the name of a folder and I guess also file, the entire folder/file is reuploaded.

  2. I also discovered I had to add “- -buffer-size 64M” to my Flags, as well under “Transfer” set to 2 Transfers, 4 Checkers, and 16M Bandwidth, cause I was getting I/O Errors even with rclone/rcloneview when transferring those large files to my NAS. Not sure why I all of a sudden was getting those errors. So, I’m trying things to prevent the issue from occur, such as this Flag.
    Also, you might want to add this Flag to the “checked flags” options in the Batch Job Flags section, it’s not there? Don’t know if this will prevent the issues, just trying it.

  3. I don’t understand why when we’ve created a “Batch Job” and RUN it that you pop-up a “separate window” showing the Job activity….?
    I see in the background the Jobs ARE STILL showing in the standard Transfer Window.

    I think you should “get rid of” this extra Window that shows each batch completion. It seems pointless…. The normal Transfer area shows us the Transfers already still.
    It also prevents us from “Minimizing” the program to the Notification area like we can normally do with the program. We can only do a regular minimize.

  4. It would be nice to have a “Date/Time” column in the Transfer window that shows “when” a Transfer was completed.

These are the things off the top of my head as I’ve been fully using the program now that I see need to be fixed.

Thank you again for your all’s work…. in making a great program. :slight_smile:

Hi leeuniverse,

Thanks for reporting these from real day-to-day use. I went through each point against the code, and tested the rename one with the rclone version that ships with RcloneView.

1. Renamed folders being uploaded again

You found the right flag. rclone doesn’t keep a record of past transfers. On each run it compares the source and destination listings, so a renamed folder looks like a set of new files plus a set of files that no longer exist. Without --track-renames, it uploads the new ones and deletes the old ones.

The “may” in the docs is the catch. --track-renames is only used when certain conditions are met. When they aren’t, rclone writes a single error line to its log and goes ahead with the normal delete and re-upload. The Job still finishes as successful, so in RcloneView you can’t tell that the flag was skipped. In our tests it was skipped in two cases:

  • In a Copy job (or Move). It only works with Sync.
  • When the source and destination don’t share a checksum type, which is how it matches files by default. Your plain pCloud folder does share one with your local disk, so --track-renames on its own works there. The pCloud Vault doesn’t, because encrypted remotes have no checksums, and neither does a NAS added as an SMB remote.

What works for all three destinations is telling rclone to match files by name, size and modification time instead of by checksum. Put both flags in the Custom flags of a Sync job:

–track-renames --track-renames-strategy modtime,leaf

In a Job that’s Advanced Settings › Custom flags. In a Batch Job, it’s the Sync step’s Custom Flags › Additional flags.

We tested this by renaming a folder that had subfolders, with an encrypted remote as the destination. The files were moved on the remote and nothing was uploaded. With --track-renames alone, everything was uploaded again. rclone moves the files inside the renamed folder one by one on the server. If you turn on rclone logging with Log level set to INFO (Settings › General settings › Embedded Rclone, then Restart Rclone Now), the log shows a “Renamed from” line for each file. It treats a file with the same name, size and modification time as the same file, which is exactly what a folder rename leaves you with.

One thing to watch: in a Batch Sync step, don’t tick --delete-before together with it. rclone refuses to run that combination.

About adding it as a checkbox: a checkbox alone would still be skipped silently on the Vault, the NAS and Copy jobs, so we built a more complete version. It will be in the next release. Sync jobs get a “Detect renamed files” option. When the source and destination share no checksum, it switches to matching by modification time and name by itself, so it works for the Vault and the NAS too. If you add --track-renames to a Copy job, RcloneView now warns that it only works with Sync. In a Batch Sync step, it warns when --delete-before is ticked together with it. Until then, the Custom flags above do the same thing.

About asking the rclone developers: rclone already has this, as --track-renames, and it isn’t on by default. It uses extra memory, checksum matching has to read the renamed files to compare them, and it only works where the destination can move files on the server. So we think the better fix is on our side: making it easy to turn on, and showing you whether it worked.

2. --buffer-size 64M and the I/O errors

–buffer-size does reach rclone from Custom flags. It’s the memory rclone uses to read ahead from the source file, per transfer (16M by default), so with 2 transfers, 64M uses up to about 128 MB. It affects reading, not writing to the NAS, so on its own I wouldn’t expect it to stop write errors. Leaving it in does no harm, and for now Custom flags is the place for it.

To find the cause we need the error itself. Could you post:

  1. The exact error lines. If a step failed, the Batch window’s log shows its error. For full detail, turn on Settings › General settings › Embedded Rclone › Enable rclone Logging, click Restart Rclone Now, and run the transfer again. rclone.log is in your Documents folder by default.
  2. How the NAS is added in RcloneView: as an SMB remote, or as a drive letter or network path?

3. The Batch Job window

You’re right, and it’s worse than pointless. While a Batch Job runs, that window blocks the whole app, including the buttons in RcloneView’s own title bar. That’s why X (hide to the notification area) doesn’t respond and only the taskbar minimize works. The window can’t be closed until the batch finishes or you cancel it.

This is fixed for the next release. The window now has a “Run in background” button. It closes the window while the batch keeps running, and you can follow it in the Transfer window. When the batch finishes, RcloneView shows a notice. If you click Run on the same Batch Job while it is still running, the progress window opens again instead of starting a second run. We kept the window because it shows the step-by-step progress and log that the Transfer window doesn’t. Scheduled Batch Jobs already run without this window.

4. A date/time column in the Transfer window

The next release adds “Started at” and “Completed at” columns to the Transfer window. The finish time is now saved too, so both stay after you restart the app. Until then, the start time and each file’s completion time are only shown in the Job details window, which opens from the “See details” button on a Job’s completion notification.

Thanks again for running everything through RcloneView and telling us where it rubs.

Best regards,
RcloneView Team

Hey, thanks much again for your work and detailed responses…. :slight_smile:

  1. So, yes, I just ran the Batch Sync to my NAS and even with –track-renames it STILL uploaded Two folders worth some 200GB’s of files simply because I renamed them.
    See pic below…. So this absolutely NEEDS to be fixed. Will try what you say the FLAGS should be, to see if that helps, and also upload to pCloud to see what happens.

I don’t do “Checksum” transfers as of yet…. But, I’ll add your additional Flags to see if that fixes the problem. Will do a test also…

This is really frustrating…. I have to add so many Flags and CMD’s whatever to make sure things are working right. Of course, looks like I’ll eventually fix things.
But, whatever you can do to prevent some of these things…. It should be just “Default” to me that whole folders aren’t deleted and reuploaded for a simple Name change, as well to prevent I/O errors, among other things I’ve had to change.

UPDATE… Changing the Flags to what you indicated seems to have worked, the File name change occurred without having to entirely reupload the file contents. Thank you, will further monitor. Made changes to the Conf file too, and seems to have worked with pCloud, though haven’t verified the VAULT yet.

  1. Sorry, I should have taken screenshots when I got those I/O Errors… Although, I think I had one, but for some reason it’s corrupted and nothing will repair it.
    Anyway, so far, adding the “64M” seems to have fixed it…. But I’m in the middle of my NAS transfer still, so I will update you if I get the errors again.
    I’ll try to update you with the I/O Error issues, and the info you requested when I can.

  2. So, I get that it might seem like a nice idea to have that “Batch Job Window” but, I honestly don’t see the point, because you could show each batch job as “Separate Transfers” or “Grouped Transfers” in the standard Transfer Window like normal.
    I mean, it’s good you added a “Minimize” link now, but still, seems weird….?

A thought on that further…. What you could maybe do instead is have a “Universal Transfer Window” eventually, because I know you’re wanting to add a “Completion Window” with full details at some point. Maybe you could have this window for all Transfers, and then it shows the full “Completion” Details once the Transfers are done?

The main Transfer window could then end up being like essentially a “Log” showing Transfers, rather than the main window we work with for showing the Transfers and the Completed Transfers?

This might be a better way to eventually do things….? What do you think about that? So, that way things are more universal and streamlined instead of having Transfers and Completion results being different from each other?

Thanks much again… :slight_smile: Will further test… and let you know.