Basically, yes. I have similar issues with DL Quad 2 and DL HDMI Quad Capture. But it was claimed that only 64gig-models are affected. (It always was, especially with random black images in previous versions than 12.2) - So now there are also issues with the 32-gig-model?
And… When I reconfigured the DL-Ins in mimoLive, I had to save and re-open the document to see the content of the live capturing. Basically the same problem as with 12.2 and 12.3, but it was only temporary.
Honestly. I’d not use M1-max for pro productions, until there is a release version of mimoLive. (Even not on Monterey 12.0.1) With MacBook Air (M1) I have promising results, also with MacBookProM1-13 inch. But even with these, I just do experiments.
I finished my tests. I can exclude BMD drivers as an issue. (At least for Decklink Quad 2, HDMI Quad Recorder, UltraStudio 3G TB3-mini-Recorder and UltraStudio 3G TB3-mini-Monitor.) - I tested some 3rd party tools. (Native, also Rosetta 2). No issues at all, except the–in comparison–lame performance we know from other apps.
It seems to be that the problem is caused by a very specific situation, which uncovered a bug in macOS (more concrete at the so called METAL framework). The bug is exlusivly related to M1-max SoCs (mainly the 64-gb-model), and was firstly introduced in macOS 12.2. - However, there were some instabilities related to this bug in earlier versions of macOS Monterey, and with version 12.2 it bricked completely. Now it seems to be that finally Apple has to solve the bug in Metal.
I’m sure that there could be a way to workaround this bug anyhow. But certainly on what cost? I assume it would be on the cost of loosing the outstanding performance that makes mimoLive so unique and on which I’m so keen on. There is still lots of riddle and guesses in my post, but now I think to understand the whole situation much better.
Apple should solve this bug–in their own interest–as soon as possible. At their upcoming event in March, new hardware might be introduced, which will never be (officially) compatible with a macOS version earlier than the soon published 12.3.
In my experiences: about -60% - BUT:
It should work, that you save and reopen the document. By reconfiguring the sources while live, this phenomenon appears.
Try to configure the BMD-ins, save the document and reopen it. It should be fine afterwards.