• Content Count

  • Joined

  • Last visited

About zendnez

  • Rank
    New User

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I started a thread here in November of last year asking about explicit support for M1 Macs. Everyone on this thread is already well aware that we haven't seen or heard anything since that time. In fact, the last Mac release (2.72) was motivated by another Mac issue I reported which made it impossible to sync a Photos Library on Big Sur. Resilio continues to function on M1 Macs but it stands out as a high consumer of both CPU and battery. I rarely see it drop below 4% CPU, and it's often using much more CPU than that. This is when there is no disk activity whatsoever in any of the fol
  2. You're being generous when you speak about this as an event that might occur. It's not clear that it hasn't happened already. Resilio is a great product but the prosumer/hobbyist niche that it fits into must be small and it's possible there's not enough market demand to generate the volume necessary to fund support and development.
  3. @jdrch - I don't understand what horse you have I this race but you are digging in on mis-informative posts. I started this thread with the intent of asking about the timeline for an M1 build. Your suggestion to run the iOS build isn't helpful. Not only is such an option not available (Resilio hasn't published a Catalyst based build to the App Store) but it's just not going to behave the right way. So please stop promoting the notion that it's an option. It's not. As @muse points out above, the few diagnostics we have to help us understand how the Intel / Rosetta version runs suggest
  4. They need to build a Universal Binary using Xcode 12. So, minimally, an Xcode update, build config changes, and a recompile. Could be more complex depending on their dependencies, how many binaries they produce, any x64-specific hand-coded optimizations. Essentially, though, it's this: https://developer.apple.com/documentation/xcode/building_a_universal_macos_binary
  5. Thanks for the response. I addition to the outstanding question about if/when we can anticipate a universal binary from Resilio, you bring up a bunch of fun topics. The comparisons to WOW/Wow64 aren't quite accurate, though they did both address a similar scenario in which an operating system and/or processor architecture evolved and app compatibility was maintained. WOW/WOW64 were thin layers that did things like shim OS API calls, fiddle without pointers, and flip the OS (in some cases) between 32-bit and 64-bit mode since X64 processors were designed with that capability. Rosetta
  6. I'm not clear if you are representing Resilio on this or just sharing an opinion. Can you clarify, please? We don't yet have clear benchmarks regarding battery consumption of emulated apps vs native apps. On my machines, Resilio tends to use a consistent 0.7% CPU. That's not a huge amount and I'm not in a position to claim definitively that a native app will use less, but power management is certainly one of the reasons that apps will go native over time. In any case, I'd love to hear from the source.
  7. Apple's M1 (Arm) based Macs hit the streets today. Is Resilio planning on releasing a "universal" version with native Arm support? Any idea when? Thanks!
  8. @davidmarshalljr - were you able to get this working? Any chance you've submitted a bug / support request on it? I have but just received a boilerplate request for logs. I'd like to see this get fixed.
  9. I've pretty conclusively determined that @davidmarshalljr is close to correct about the issue he's reporting. This capability broke with the 2.7 release. The difference in security bits between 2.64 and 2.7 is that the "Hardened" bit has been set in the 2.7 release. With 2.64, when I attempt to set up Resilio to sync a Pictures library on a clean install, I'm prompted to grant Resilio access to Photos (by MacOS). Once permission is granted, Resilio works fine. With 2.7 on a clean install, no prompt is seen and Resilio starts spewing permissions errors into its Activity history.