When will this project, or at least 1 of the current applications, get native support for Apple Silicon MacOS chips/devices?

Given that the development of new applications, and any work at fixing up the bugs with the existing applications has been stalled for 6 months now, it would say never.

---

Grant
Darwin NT

I have a 16gb/256gb M4 Mac Mini and a 16gb 1tb M1 MBP and both of them can chew through Rosetta Beta 6.00 tasks in 3 to 4 hours on average. Even though they aren't Apple Silicon apps, they still preform extremely well!

I have a 16gb/256gb M4 Mac Mini and a 16gb 1tb M1 MBP and both of them can chew through Rosetta Beta 6.00 tasks in 3 to 4 hours on average. Even though they aren't Apple Silicon apps, they still perform extremely well!

I hope you don't mind me asking, but why do you only run tasks for 3hrs?
The default is 8hrs so if you force the runtime to only be 3hrs you only do 3/8ths of the work and get 3/8ths of the credit.
You're not completing a full task in 3/8ths of the time - that's not how it works at Rosetta.
More importantly, you churn through more tasks, that then aren't available for you or anyone else to run and fresh batches of work last less long.
I see you run a lot of projects, so correcting your runtime here may impact on meeting deadlines, depending on your offline cache size.
It would definitely help if you could make this adjustment - either to "Not selected" or an explicit 8hrs, as you prefer.

---

I have a 16gb/256gb M4 Mac Mini and a 16gb 1tb M1 MBP and both of them can chew through Rosetta Beta 6.00 tasks in 3 to 4 hours on average. Even though they aren't Apple Silicon apps, they still perform extremely well!

I hope you don't mind me asking, but why do you only run tasks for 3hrs?
The default is 8hrs so if you force the runtime to only be 3hrs you only do 3/8ths of the work and get 3/8ths of the credit.
You're not completing a full task in 3/8ths of the time - that's not how it works at Rosetta.
More importantly, you churn through more tasks, that then aren't available for you or anyone else to run and fresh batches of work last less long.
I see you run a lot of projects, so correcting your runtime here may impact on meeting deadlines, depending on your offline cache size.
It would definitely help if you could make this adjustment - either to "Not selected" or an explicit 8hrs, as you prefer.

My default is set to default / 8 hours and all of my v4.20 tasks are running for that time.

The majority of my tasks, however, are v6.06 beta and they, without exception, run for 3 hours - not my choice, I presume it’s a setting within the task.

How would I make this change? I have everything set to default, both on Rosetta's web end and on BOINC's end 4.20 tasks are running for eight hours on both my Apple Silicon and my Desktops. On my desktops, the 4.20 tasks run for a full 8 hours.

How would I make this change? I have everything set to default, both on Rosetta's web end and on BOINC's end 4.20 tasks are running for eight hours on both my Apple Silicon and my Desktops. On my desktops, the 4.20 tasks run for a full 8 hours.

In your account- Preferences, Preferences for this project- Rosetta@home preferences, Target CPU run time.

You can change it, but personally i just leave it at the default "Not selected".
If the Project wants it to run for 8 hours, it does. If they are happy with 3 hours, then it does 3 hours. If they want it to go for 12 hours, then it will. It's their data and application, so i let them choose whatever processing time they decide will be appropriate.

---

Grant
Darwin NT

I have a 16gb/256gb M4 Mac Mini and a 16gb 1tb M1 MBP and both of them can chew through Rosetta Beta 6.00 tasks in 3 to 4 hours on average. Even though they aren't Apple Silicon apps, they still perform extremely well!

It would definitely help if you could make this adjustment - either to "Not selected" or an explicit 8hrs, as you prefer.

My default is set to default / 8 hours and all of my v4.20 tasks are running for that time.

The majority of my tasks, however, are v6.06 beta and they, without exception, run for 3 hours - not my choice, I presume it’s a setting within the task.

Is that still happening? I thought they corrected that.
Yes, it is within the task for some reason. It seems like a mistake to me, but there may be a reason we're not aware of.
This is the difference between chosing "Not selected", which may change as Grant says, and selecting a specific runtime.
I select 12hrs for everything, so I'm unaware it still happens. Longer runtimes don't have any of the same issues attached as long as deadlines are still met - imo

---

Is that still happening? I thought they corrected that.

There have been some batches that run for 8 hours, but 95%+ run for 3 hours (if they don't error out first).

---

Grant
Darwin NT

Is that still happening? I thought they corrected that.

There have been some batches that run for 8 hours, but 95%+ run for 3 hours (if they don't error out first).

I had no idea. I thought it was a one-off mistake that they corrected and assumed it didn't come back.
While I agree with you that runtimes should be set at "Not Selected", the fact this 3hr thing still happens makes me think people wanting to run default times should set it to 8hrs explicitly.
In the absence of a known reason why those tasks run for 3hrs, I'm still inclined to believe it's a silly mistake that's slipped through.
But that's just me - others can take their own view and, I repeat, I do accept that "Not Selected" should be the preferred runtime setting.

---