Behind the Scenes: I just ran Isadora natively on an Apple Silicon M1 ;-)

bonemap

I mean compatibility with things like OpenNi depth cameras, Artnet, DMX, Javascript, GLSL, serial devices and any other devices and systems that might be disrupted by lagging compatibility with Apple.

Best Wishes

Russell

mark

@bonemap said:

I mean compatibility with things like OpenNi depth cameras, Artnet, DMX, Javascript, GLSL, serial devices and any other devices and systems that might be disrupted by lagging compatibility with Apple.

Of these, only the skeleton tracking OpenNI system should be affected, because that subsystems of OpenNI cannot be recompiled for Apple Silicon. (Receiving aa depth map reception should, in theory, still work.) But really I want to find an AI empowered replacements for that technology anyway.

Everything else you mention is either C++ code that can be recompiled for Apple Silicon, or subsystems that will work the same way under that the new chip (e.g., serial communications.)

Best Wishes,
Mark

bonemap

@mark

Hi Mark,

Thanks for the insight.

Best wishes

Russell

Armando

@mark

Wow.

What about performances, MarK I don't want to take a lot of time from you but did you see some performance boosts as everyone says ?

mark

@armando said:

I don't want to take a lot of time from you but did you see some performance boosts as everyone says ?

I just got Isadora to work on the M1 two days ago, so I cannot say yet. I'm still dealing with stuff like getting all the plugins to compile.

That said, we're a quick and dirty comparison: playing 4 x Apple Pro Res 422 1920x1080. Here are the results from activity monitor. (Remember, you can have CPU usage higher than 100% for the individual component measurements below because of multiple cores.)

Mac Book Pro i7:

Isadora CPU Usage: 42%
Background Movie Player CPU Usage: 20%
Apple Pro Res Decode Service CPU Usage: 300%
Overall System CPU Usage: 32% (User CPU Usage from Activity Monitor)
Isadora LOAD indicator: About 2.1%

Apple miniMac M1:

Isadora CPU Usage: 13%
Background Movie Player CPU Usage: approx 30%
Apple Pro Res Decode Service CPU Usage: approx 200%
Overall System CPU Usage: 33% (User CPU Usage from Activity Monitor)
Isadora LOAD indicator: About 1.9%

So while the Intel numbers are a bit higher for the individual components, the overall system usage is about the same. In the end, I don't really know how to evaluate this simple test. Of course, the minMac is 1/4 the price of my Mac Book Pro, so one could argue you're getting equivalent performance for a much lower price.

For the moment I think it's critical to keep this one limitation in mind: the current M1 devices only support one display output in addition to their main display. I suppose this limitation could be overcome with a Quad Head 2 Go, DataPath FX 4, etc. But in terms of hooking things up directly, that would make it a no go for my own use in performances.

Finally, I will mention that someone I am acquainted with did a DaVinci Resolve file using 8K raw files and several layers. Then he rendered this out both on an Intel based MacBook Pro and an Apple Silicon M1 based miniMac to compare the results. (DaVinci was running native M1 version on Apple Silicon.)

Here's what he said: "Finally did a [DaVinci] Resolve speed test. 3840x3840px (ie ~5k) with 20 secondaries. M1 mini = 9:21. 16” MBP intel = 4:33. Over 2x slower! Big disappointment."

This conflicts with other DaVinci Resolve tests I've seen posted on the web, but this guy is a video editor and I am giving this test some credence.

I think there is a lot of hype around this chip. Once we can get M1 machines for the team, we can start evaluating performance. But right now I am cautious about the many claims made on the internet about how amazing these chips are.

Best Wishes,
Mark

Armando

@mark

And I had a chance to test the 308 b41 on an M1 (through emulation) and it works too !!!! ;)

Cheers

mark

@armando said:

And I had a chance to test the 308 b41 on an M1 (through emulation) and it works too !!!! ;)

Good to hear. But it will be good to use the native version. ;-)

Best Wishes,
Mark

crystalhorizon

Excited. Have my eyes on a new basic MacMini M1. Seems to smoke a lot of machines out there...

mark

@crystalhorizon said:

Seems to smoke a lot of machines out there...

Maybe. Read what I posted above about a film editor's experience regarding performance.

Best Wishes,
Mark

Clement

[EDIT by Mark: Adapters of this kind probably will not work with Isadora, or any OpenGL/Metal enhanced application; see my comments below.]

Hi everyone !

I just found this video where an apple M1 owner succeeded to connect 6 displays on a new Mac Mini.

But be careful, apple M1 devices don't seem to be compatible with eGPU for now, and there are other problems mentioned above.

Best Wishes. Clement

Armando

@mark Sure. But it is good news.

mark

@clement said:

I just found this video where an apple M1 owner succeeded to connect 6 displays on a new Mac Mini.

Unfortunately, this are USB to HDMI/Display Port adapters. These almost certainly do not support OpenGL, and thus are likely useless for Isadora or any other GPU backed app.

As it says in this article from 2016 about USB adapters of this kind, "Being able to connect additional displays to a MacBook, MacBook Pro, or MacBook Air sounds fantastic, but it still is important to be aware of the limitations of the technology. The bandwidth provided by USB is insufficient to "fully support" OpenGL 3D hardware acceleration, and as a result, there is a lag time." (emphasis mine.)

Best Wishes,
Mark

Clement

@mark

Thank you for making a clarification about USB Display adapters, we have to be careful about technology specifications in these times of USB4 release.

Best whishes.

CitizenJoe

@mark

Does USB4 change the bandwidth problem?

Cheers,

Hugh

mark

@citizenjoe said:

Does USB4 change the bandwidth problem?

Unlikely. You would need a full GPU on the adapter.

Best Wishes,
Mark

DusX

@mark said:

full GPU on the adapter

Sounds like a nightmare moving textures back and forth. NO

alfiek

@mark is this anywhere near releasing now? I would love to use on my new M1!

mark

@alfiek said:

is this anywhere near releasing now? I would love to use on my new M1!

In terms of an official release of an M1 native version, it's going to take some time -- though a beta may be available far sooner. Before putting our "stamp of approval" on this, we need to purchase M1 machines for the entire team (happening next week), given them a build, and do complete regression test of the entire program. If there are bugs or incompatibilities, those have to be addressed and then we have to retest. So it's coming, but it will take some time.

I will not make a prediction yet as to how long it will be before a native M1 version is released, because we need to get the Big Sur release out. (Very very soon.) Then we can progress to the M1.

In the mean time, we anticipate that the Big Sur compatible version will run in Intel emulation mode on the M1 once we get it out.

Best Wishes,
Mark