# MetaGrid Pro 2 Is in the Works

**URL:** <https://forum.metagrid.app/t/metagrid-pro-2-is-in-the-works/1639>\
**Category:** 🧑‍💻From the Devs' Lab\
**Created:** [September 24, 2026, 8:12am UTC](https://forum.metagrid.app/t/metagrid-pro-2-is-in-the-works/1639 "2026-09-24T08:12:05Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![MetaGrid\_Admin](https://yyz1.discourse-cdn.com/flex009/user_avatar/forum.metagrid.app/metagrid_admin/32/21_2.png) [@MetaGrid\_Admin](https://forum.metagrid.app/u/MetaGrid_Admin)\
**Post date:** [September 28, 2026, 3:11pm UTC](https://forum.metagrid.app/t/metagrid-pro-2-is-in-the-works/1639/8 "2026-09-28T15:11:46Z")

</div>

Brett, I’m sorry you’re still having to restart MetaServer and recreate the Cubase control surface. We already have your [earlier report](https://forum.metagrid.app/t/1610/1) and the support package you sent privately, so there’s no need to resend that package.

Could you confirm your current **MetaServer Windows version and build**? The next time the problem occurs, **before restarting MetaServer or re-adding the control surface** , please check:

- Are the **MetaGrid, Cubase and Cubase Sync MIDI ports** visible in Cubase’s MIDI port list?
- Is the **MetaGrid MIDI Remote surface** still listed but disconnected, or has it disappeared entirely?

Please also capture a **fresh MetaServer support package while the failure is present** , before restarting MetaServer, Cubase or Windows MIDI Services. Send it in our **existing private conversation** , along with the **approximate time of the failure** , so we can match your observations to the logs.

---

_[View the full topic](https://forum.metagrid.app/t/metagrid-pro-2-is-in-the-works/1639)._