Interesting article about trying to make the M1 gpu work under Linux.
I can confirm the rendering increase from 3.2 Beta to 3.3 Alpha. I started running the 3.3 alpha a couple of days ago and tried my trusty benchmark file; and indeed Iām consistently get an 8 secs increase with the 3.3 alpha on a 68 sec frame versus with 3.2 beta. Also feel like my animation playback is a little snappier.
Tested with the M1 Mini 16GB. You will probably see higher gains on the higher end machines? Looks like the promised performance is trickling in. Looks like the bigger performance commit is still in the works from the Apple team.
3.2 Beta: 68 secs
3.3 Alpha: 60 secs
Edited times from 108secs vs 100secs to 68 vs 60.
Brain was stuck on seconds when describing (1) minute, lol.
Correct times are above now. Not a big change but it raises the percentage of improvement by a few points.
I wonder if this is an ARM optimization or a general Metal optimization?
Good question, Iām kind of lumping the two together right now. I would guess both optimizations are happening in tandem; ARM base code clean up and changes needed for the Metal implementation?
Sorry had to edit my original comment you replied to after rereading. 60 secs (1 Minute) versus 68 secs (1:08) Not sure why I wrote 100 seconds, maybe had 1 minute in my head. lol
Nice, thatās about 12% decrease in render times
Iām all for metric time!
Iāve been pushing my m1 max a little harder with a scene with linked assets. Iām getting A LOT of weird errors though, and at least once my entire system locked up and I had to hard reset. 3.1.2 official, anyone else running into any errors like this?
Not yet the only thing that has been annoying me a lot recently with 3.1.2 is the blender window flickering, that bad that I save and reopen blender to make it stop.
Well and having changed my desk setup I am noticing the fans of the 14ā in clamshell mode
Fans seem to be about 1000 rpm higher then open, which made them audible, only reason I noticed.
Yeah thermals are the main reason Iāve never attempted using any laptops in clamshell mode. I guess M1 machines would be as well suited as any for it, but Iāve become spoiled by the generally silent operation.
Interesting note about all these glitches. They are almost always fixed by restarting blender; and I just did a lengthy animation render of the sequence and it didnāt glitch out. But it seems if Iām actively working on the scene I can run into glitches every few minutes.
My 16ā M1 max at work (well I donāt own that one), does not have the issue but I did put it in a vertical stand, it does more 2D work too. Fans never turn on however.
There are other differences like the screen at work is not even 4k and I home I drive 2 4k screens at the moment. So who knows.
I agree now when I hear fan noise I go like aaah no what is that . I can never go back to a PC
Especially now after nearly 2 years of M1s.
I found this interesting
I wonder if this update has any improvements for our needs?
Well, if you have a Studio Display and are annoyed about the
quality of the webcam, which works otherwise quite well in an
external iPhone, you may now profit from looking better in
your video calls.
(AFAIK youtubers werenāt that sure if it got better by the new
firmware - or just different)
I personally didnāt notice any difference during 12.4 open beta.
But as Apple is always shy of explaining update details, there is
hope of some magic included.
I am already looking forward to test macOS 13 with moderate
excitement. Or more iPadOS 16 - if there is really a macOS option.
So maybe Blender on iPad in autumn ?
(Unfortunately iPadOS 15 will be the last OS on my iPad Air2,
so I would have to get a new one to profit)
Not that I noticed been using the RC release which is the same as the final version.
Not sure if itās just an automated message that doesnāt really imply anything more than that ā but Blender for an iOS device would be pretty game-changing and definitely get the entire user base to stop and take notice. I would assume that in that case, Blender for Android wouldnāt be too far behindā¦but it would be cool to have a head start for a change!
Iāll tell you what it is: a giant tease.
Though I think this is something we shouldnāt get our hopes up over. Unless the BF intends to release Blender as-is, requiring a mouse and keyboard to work (which wouldnāt pass Appleās standards for iOS apps), theyād have to do tons upon tons of work on the UI to make it touch friendly. Developing such would require a tremendous amount of resources the BF would probably deem better used elsewhere.
Plus, all the supposed and alleged license incompatibilities and whatnot. I wonāt say itāll never happen, but Iām thinking itād be a very, very long shot.
Unless Apple is actively involved in making it happen.
I took me a second to see it. At first I was thinking, what is Steve grasping at? āThe Freedom to Createā means iPad? Then I saw itā¦
And yes, I see the āyet.ā There is no reason for it to be there grammatically, unless it needs to be there grammatically.
Hmmm this is interesting.
M1 iPad Pro comes to mind and the recent article/patent I saw with connecting an iPad to a physical keyboard base like the MS Surface Book.
To me it seems with the iPadPro doing what it does and the M1 mac Mini sharing a lot of the hardware one might start to ask is it logical to keep having iPad OS and Mac OS ?