Hey Guys,
I bought an Intech PO16 controller to use it with VCV Rack 2 and faced a serious problem with VCV rack constantly crashing.
Configuration:
Intech PO16 via USB C connected
VCV Rack 2.5 or also 2.4.1 testet
VCV Rack default patch
Intel Mac Book Pro 16 Zoll 2019 mit Intel core i7
VCV Rack crashes immediately after connecting the PO16, independent of the patch loaded. Connecting the PO16 to the Mac when VCV Rack runs lead to the same crash. The PO16 is working on the Mac in general in other software or MIDI monitoring tools. Interestingly connecting the PO16 to another Mac and using the MIDI tools of the Mac over a network session allows to use the PO16 in VCV rack. Using it over another Mac is possible but very unusable for me.
Does anybody experience the same or even have an idea how to solve it?
Hey Paul,
I also pluged it in before running VCV with the same outcome. Connecting another MIDI Source to the running VCV Rack, than connecting the PO16 or closing VCV with a connected MIDI Source and connecting PO16 and then starting VCV Rack gives the same crushing of the software.
I will post the crash log as well.
The problem is VCV works with other midi controller and the intech works in other software with the described set-up. It must be something special with the PO16 compared to other MIDI controllers. It also happend on another Intel Mac with VCV Rack first installed in the same manner.
I meant the Rack log (log.txt in the Rack user folder. Open folder from the Rack help menu) although vcvrack support will appreciate the system crash dump.
I’m had a similar problem with the Intech Studio PBF4.
The crash does not happen if I enable the “Input Monitoring” permission for VCV Rack 2 app in my macOS system preferences. I don’t know why Rack would ask for this permission, but I denied it initially, and that seemed to cause the crash. I know that this particular MIDI controller can act as a computer keyboard, so maybe that has something to do with the app asking for the permission.
SOLUTION: Uninstalling VCV Rack and removing the “Input Monitoring” permission. Then reinstalling and giving the Input monitoring permission again and it works nicely. Seems like the given “Input monitoring” permission coming from previous Versions of VCV Rack (< 2.5) was the problem. It also worked on my other Mac (an old Intel iMac).