MacBook Air intel. Sequoia 15.7.8 only - no crash in windows 11
Note: No USB I/O device connected
Edit: checked with a usb device connected - same result
Recipe:
New Project
Add a Layer
Set output to a VM MIDI Port - defined or not doesn’t matter.
if port not defined VSTL asks for a name for the port: Cancel or OK - crashes.
If port is defined VSTL - crashes immediately port is selected.
Tried to reproduce with MacBook Air M4 Tahoe 26.5.2 - no crash.
Just me then - weird, unless it’s an intel thing. Thanks for checking it out.
On Intel or Silicone to test (still have both)
… do you have a crash log? Can you please check if a log was created?
Sorry Michael - I already checked and there is no crash log
/Users/YourUserName/Library/Logs/DiagnosticReports
… nothing? 
Ah! Hidden folder - bear with me…
There you go…
vstlive-2026-07-30-180226.ips (84.8 KB)
vstlive-2026-07-30-180305.ips (83.8 KB)
One for each version
… yeah, thank you. Your project must running a “event-recursion”. I can reproduce it with
New Project
Add Layer
Select “Virtual MIDI In 1” for “MIDI Input”
Select “Virtual MIDI Out 1” for “Instrument”
Select TRACKS
Add MIDI Track
Select “Virtual MIDI IN 1” for Output
Add Clip and open Clip in Lower Zone
Click to the Keyboard to generate a MIDI Event
Crash. The same event is sent repeatedly in an endless loop …
We’ll fix that, but meanwhile you could check your “faulty” connection?
See you,
Michael.
I’m not adding any tracks.
Just new Project, add layer, set output to VM1 - crash
Maybe your “default part” contains a layer.
No default Part.
I do have my default Layer instrument set to ARP Odyssey but changing that to Halion and then to VM1 still crashes.
I just noticed - if I set the output to VM2 there is no crash.
Every new project contains one default song with one default part.
And the default part is empty in my setup which I equate to “no default part”, never even saved a default part.
Maybe thats also a difference. My default part contains one stack (microphone) and one layer (Halion).
Are you using an Intel MacBook?
No, I wrote above thats an M4
I just read back up to that - as I said originally it works fine on Windows, and you said it’s fine on MacBook M4 so it appears peculiar to Intel MacBook.