benwiggy

New Members
  • Posts

    13
  • Joined

  • Last visited

benwiggy's Achievements

Member

Member (2/3)

  1. I find that quitting RS and restarting it seems to improve the energy usage, for a while.
  2. I've been running Resilio Sync on an M1 16" MBP for a few months now; and like others, I've seen rampant CPU usage from time to time. However, this now seems to have stopped for me. Possibly because I'm on the release candidate of MacOS 12.3, which will go public next week, but also I recently noticed that the version you can download from the main site has a date stamp that is a few hours later than the version you can download from this forum. https://download-cdn.resilio.com/stable/osx/cc/2501/Resilio-Sync.dmg (The date stamp here is 13:00 on 28 May 2021; where the version on this forum is 09:35.) It is slightly larger, by a matter of Kb. It is build 1975, as opposed to 1971. I've no idea whether either or both of these things has had an effect, but Resilio Sync seems to be behaving very well for me now.
  3. Resilio Sync works perfectly on Monterey, from what I can tell. Also running native ARM on my M1 MBP.
  4. MacOS will use the Unix Executable icon for any file that has the executable 'x' attributes set, and which is not identified as any other file type. As T1 fonts don't have file extensions, MacOS doesn't easily know what they are. However, it may not matter that the printer file shows as an executable. Make sure that your suitcase has the file extension .suit. Make sure that com.apple.ResourceFork and com.apple.FinderInfo are in your StreamsList file. My T1 fonts seem to be synching OK. However, Apple now describes T1 PostScript as 'legacy fonts'. Adobe have already stopped supporting them in Photoshop, and will not recognise them in all their apps from 2023. Resource forks were deprecated on macOS as far back as Lion. https://helpx.adobe.com/uk/fonts/kb/postscript-type-1-fonts-end-of-support.html
  5. Now, when I try to add the folder to my Home folder level, it says that it can't add it as the destination includes a folder that is currently syncing, even though I've deleted all the previous attempts.
  6. I'm trying to sync my $Home/Documents folder on two Macs. But I'm having an absolute nightmare trying to select the right folder. I either get a Documents folder inside my Documents folder, or I get the contents of my Documents folder splurging all over the Home folder level. I dragged the Documents folder onto Resilio on one Mac, and the other comes up with "Save to location: ~/Documents/Documents". I've already nearly trashed two computers setting this up, as it started to interfere with Dropbox. Argh. Any advice?
  7. It seems to happen regardless of any syncing in progress. Do you mean "indexing" added to the filename? No, not seen that.
  8. Thanks. Yes, this works well. It now runs at about 3%, though runs up to 18% every 20 seconds for 2 seconds. But much better.
  9. Sync on my Mac is running very hard, and driving down my battery life. It's using between 99% and 125% CPU (100% = 1 core) permanently. I'm using the Sierra public beta, but I seem to remember it was doing this before, but only about 20%, which was better, though still not optimal.
  10. You've lost me with a subscription model. I really liked BTS, and I recommended it to everyone. Now I'm doing the opposite. I'm now looking at other apps that do the same thing. There are others -- even on the Mac App Store -- for a one-time payment.
  11. I got the dialog that a new version of BTS was available, and that I should install it. OK. Woah! No simple upgrade-the-app-and-carry-on-as-before. Straight into click-through wizards about setting up identities, using PRO, with no way "Go back" button for the faint-hearted. I find the new version far too complicated, and I don't way to pay a sub. I'll happily pay a one-time fee to run V2 -- I'll even pay again for a major update. But at a time of my choosing. I don't want a metered clock. I looked at all kinds of sync products, and the only one that did what I wanted was BTS. Loved it. Simple, elegant. For the time-being, I've gone back to 1.4, as I need to read up on all the changes and how everything works now. I'll also wait to see if the backlash causes any revisions.