I’ve just solved a problem with my Korg Kronos not being recognised by Cubase 12 (running on Windows 11) - despite it working perfectly for the last 2 years or so. With help this problem was solved (it was to do a corrupt driver in the midi device slots)…I also reinstalled the Steinberg UR22 driver and since then my cubase/Korg system is working fine, but I keep getting this ‘missing ports’ message every time I open a project. (Or start a new one). I can’t seem to work out why this is happening. I’ve been going round and round in circles for hours. Any help appreciated.
take a look in VST Connections
When that “Missing Ports” dialog pops up, don’t just click “OK” or "Map Always.
Look at the Mapped Port column.Manually select your current audio interface output (e.g., “Stereo Out” or “Analog 1/2”).
Check the box that says “Map Always” to try and force Cubase to remember this translation for future old projects.
or maybe in Studio Setup
Go to Studio > Studio Setup.
Select Audio System in the left sidebar.
Ensure the correct ASIO Driver for your interface is selected.
Click on the driver name underneath “Audio System” and ensure your ports are listed as “Active.”
If your driver is correct but the ports are still “missing,” your Input/Output definitions are likely the culprit.
Go to Studio > Audio Connections (or press F4).
Go to the Outputs tab.
If you see “Missing” in red, click the Device Port column and re-assign it to your interface.
Thank you for offering solutions - when I tried your first suggestion my usual audio interface output wasn’t showing up…yet all seems ok in audio connections. One thing I don’t understand that may offer a clue to what’s happening is the selection I usually make for the metronome doesn’t appear in the drop down. I’m mystified, and frustrated, sat here most of the day trying to solve it. But many thanks for your time, it is really appreciated.
It seems this is really about a MIDI port, Glenn. Look at the 5-pin-DIN symbol.
Thanks for trying to help - I have, somehow, resolvd the issue - the problem lay with corrupt drivers and - when this was working trying to clear up the mess I’d made trying to fix the original issue.