Dear VSL,

Would you mind telling us if you plan to migrate all of your software to the new Apple Silicon platform and if you have an estimated timeline?

Thanks in advance

Hello,

Martin, I just saw your answer about this subject: I've made an answer about it here, please don't hesitate to correct it.

Regards,

Gil.

Originally Posted by: Eulenauge66

Also waiting for this. Bought the M1 MacBook Pro and can't wait to test it with VEP.

I did it, and it works pretty well. I tested network on ethernet and Thunderbolt 3 both working very well.

The power of the actual unsupported and casual Rosetta2 adaptation is amazing, and competing already in performance with i9 top CPU. Then if software issues will be fixed and we get stable native version of the VSL software, I'm expecting some interesting result, let's say equal or better performance of the "actual one" should result already in an amazing quality/price rate for the Macmini M1, and good forecast for successors.

Originally Posted by: samphony

How did you got it working?

I am running a Mac mini m1 as DAW Mac and an i7 Mac mini as VEP server.
The moment I open the server plugin in my daw its window stays empty. 

I can manually enter the server IP address but am unable to select the specific instance from the plugin window!

I simply connected it and it was working, without manual IP input, just the instance was showing up!

But I had a similar problem with my old macs (a Mac Pro 2013 and a Mac Book Pro 2019) in Catalina/Mojave:

- automatic list of instances not happening, and even manual IP connection impossible if they were on different channels of the router... I realized they have to be all on the very same network, including the channel of the router (e.g. 2.4 vs. 5Ghz, subnetworks etc. etc.)

- still automatic detection impossible despite the correct network, but then manual IP connection perfectly working and saved in the file (so it happens again when you close it and reopen it later)

For that reason I suspect there is some issue in network detection caused by the last versions of the macOS, disregarding the M1 or BigSure updates. In my case I was so happy to get back the automatic connection between the M1 and the MacBook Pro both running BigSure 11.1

I recommend you carefully check the network set-up to ensure both the machines are in the very same channel/subnetwork, then if it doesn't fix at least the manual IP connectivity, then double check software versions. Can't say more than this sorry.