Sigh.
Unfortunately I do have to object here:
Starlight mini only partly works well on AppleSilicon based machines in the last pre-Studio beta (7.2.0.3b) and the first Studio Version (1.0) - which isn’t really surprising considering the fact that the first Studio release is said to have gotten the unchanged beta model.
The subsequent releases (maybe except for 1.0.1 as I never tested that) all have bigger issues with the RGB bug in the 1.0.4 only being the icing on the cake / being the most obvious and embarrassing one (as it’s quite unbelievable how something like that could really be in a non-beta release - at least not if just one single person had ever tried it before release). And no, it wasn’t just a “small subset of systems” but occurred on M1, M2 and at least one M4 system with that bug.
So, the majority if not all Apple silicon systems were affected. It’s not as if you could vary the hardware much with Apple, you know… (which should be a dream for any developer).
And, the resolution bug together with quality issues is still there. According to my tests SL mini now always seems to do the 2x model and then (sometimes) simply lanczos scales to the final resolution.
So, selecting 1x, 2x and 4x always give the same quality and also run at similar speed. Selecting by the factor often gives a wrong output size different from that shown in the export window. Selecting custom resolution gives the correct output size but not the correct quality as it’s simply “faking” the resolution by a plain upscale. Any video player does that in real-time, so this is simply blowing up file-size without any use.
In the earlier SL mini model there was a MAJOR difference in1x/2x/4x renderings (concerning both quality and speed).
