Drivers Licence Keyboard Notes

[Athina Dollison]

Ihave recently purchased the above secondhand and have transferrd the licence arranged with the original owner. Everything works fine and have followed all the setup instructions. But it is hit and miss if I can navigate my DAW using the midi controls to move around cubase. If I restart windows maybe several times it will work.

Not sure if this will help but in my experience these simple uninstall - reinstall procedures work in 90% of cases. If it does not (or you are that original poster and this was your question) that will at least remove the biggest possibility and help narrow the solution.

Just spotted something. After a reboot the midi manager needs to be clear to get this to work - see below.

image933499 19.2 KB

So now that it is currently working how do I clear away the earlier midi devices when it shows up again (which I use with Maschine) Do I just hit reset and connect them back when I want?

Yes you are right it does make a difference to start the keyboard first for better reliability. Unfortunately when you turn the keyboard off (because you want to take a break and save power) then turn back on you lose connection again to use keyboard to control Cubase.

Here is the batch file (text file with a .bat file extension) I use (Windows 10). It simply prompts me with a text message and pauses until I press a key. Then it launches Cubase. I replaced my Cubase shortcut with this because I kept forgetting to turn things on first.

Release notes for the most recent versions of the Solstice host (Pod) software and related apps can be found below, with the most recent release first. Use the links below to find release notes for older Solstice releases.

Mersive strongly recommends upgrading Pods to software version 6.1.2 to benefit from the latest security updates and important performance enhancements. Read this Mersive Support article if you are upgrading Solstice version 4.4 or earlier to Solstice version 5.5 or higher.

Mersive found that an upgrade to the software used by Gen3 Solstice Pods to display the user interface, which was included in Solstice 6.1.1 and improved digital signage stability, also caused the Solstice welcome screen to freeze randomly. This update has been rolled back for Solstice 6.1.2, but Mersive plans to resolve the welcome screen issue and include the update in a following release.

Visit mersive.com/download/ to access updates. A current Solstice Subscription is required to upgrade Solstice Pods to the latest version. You can schedule the latest software update for your Solstice Pods using Solstice Cloud. For optimal compatibility and performance, Mersive recommends using the same version of the Mersive Solstice app to connect to a Solstice Pod as the version of Solstice running on that Pod.

The first time a Solstice Pod is plugged in out of the box (or after a factory reset), a new series of screens will launch on the connected HDMI monitor. This tool walks through checking connections to a network, the internet, and the Solstice Cloud management portal that are needed to fully deploy a Solstice Pod, as well as provides tips for resolving common issues and links to further resources.

Solstice fully supports current versions of macOS 14.X Sonoma for in-room content sharing starting in version 6.1. Solstice video conferencing is fully supported on macOS 14.0. See Known Issues regarding Solstice video conferencing support on macOS 14.1.

Mersive tested the most popular AV peripherals devices for use with Solstice 6.1 to identify those providing the best room audio and video resources when connected to a Solstice Pod. Organizations using the Room Camera + Mic functionality in the Mersive Solstice app for video conferences should view the updated list and details.

An issue on newer Gen3 Solstice Pods that made sharing appear in Dual - Mirror mode rather than Dual - Extend or Dual - Seamless Extend mode (Display Options in Welcome Screen configuration) has been fixed in Solstice 6.1.1 (6.1.36718). Extend mode settings may need to be reapplied after upgrading a Pod to take effect.

An incompatibility between virtual cameras on macOS 13.X Ventura running on Intel processors and Room Camera + Mic functions in the Mersive Solstice app, which caused other applications to close when they requested access to any installed video cameras, has been resolved in macOS Sonoma.

Factory resetting a Solstice Pod previously re-enabled room calendar integration features, which in some cases caused random crashes. Room calendar integration settings are now disabled by default after a factory reset of a Pod.

Users can successfully connect using Miracast to a Solstice Pod with a screen key and Miracast over existing network infrastructure enabled ('Enable Miracast Infrastructure' in Features configuration).

Mersive is investigating issues that occur when devices connected to a Solstice Pod with the Mersive Solstice app for Windows are in use in video conferences. High Windows CPU load can cause camera and mic devices to not be detected in the Mersive Solstice app and audio issues such as crackling and cut-outs. Plugging in a power cord or turning on a high-performance power mode can help work around these issues in some cases.

Mersive strongly recommends upgrading Pods to software version 6.1 to benefit from the latest security updates and important performance enhancements. Read this Mersive Support article if you are upgrading Solstice version 4.4 or earlier to Solstice version 5.5 or higher.

A rapid HDMI-In port disconnect/reconnect signal could incorrectly result in the disabling of the HDMI-In port, resolved previously by sending an API command to re-enable the port or with a Pod restart.

Visit mersive.com/download/ to access updates. A current Solstice Subscription is required to upgrade Solstice Pods to the latest version. You can schedule the latest software update for your Solstice Pods using Solstice Cloud.

Mersive strongly recommends upgrading Pods to software version 6.0 to benefit from the latest security updates and important performance enhancements. Read this Mersive Support article if you are upgrading Solstice version 4.4 or earlier to Solstice version 5.5 or higher.

- Users on a laptop can access a completely redesigned Solstice web app by going to share.mersive.com in a web browser to share content (browser tab, window, or entire screen) to Solstice. This makes sharing content to a Solstice Pod easier for users and helps administrators support Solstice content sharing without the installation, maintenance, and load of additional apps on laptop devices.

Notes: The Enable Web Sharing setting (Solstice Cloud > Features template settings) must be turned on for the Solstice Pod. Android and iOS devices are not supported. Audio sharing may be limited by laptop OS and browser. The Mersive Solstice app for Windows or macOS is currently required for full layout controls and Room Camera + Mic connections. Learn more.

Updated digital signage capabilities in Solstice 6.0 can be used to display webpages with interactive and responsive elements whenever a Solstice Pod is not in use for content sharing or video conferencing. Custom HTML and JavaScript programming can interact with and dynamically respond to the Pod and attached devices, such as occupancy sensors. Learn more.

The first time a Solstice Pod running Solstice 6.0 is plugged in out of the box (or after a factory reset), a new series of screens will launch on the connected HDMI monitor. This tool walks through checking connections to a network, the internet, and the Solstice Cloud management portal that are needed to fully deploy a Solstice Pod. It provides tips for resolving common issues, QR codes linking to further resources, and information about other available services.

Windows installers for the Mersive Solstice app now automatically add exceptions to Windows Defender Firewall for program files required for the application to communicate over the connected network. Exceptions may need to be added manually for other firewalls. Learn more.

Starting in Solstice 6.0, daily reboots scheduled for Solstice Pods will be performed within 10 minutes of the configured Daily Reboot Time (Solstice Cloud > Advanced template configuration). This allows restarts of large numbers of Pods configured for the same reboot time to be better managed.

Starting in Solstice 6.0, Solstice Pods will validate their licenses against a new licensing service hosted in Solstice Cloud. This increases Pod reliability by preventing third-party license issues from disabling devices with active licenses. Note: Connections must be allowed to kepler-backend.mersive.com to validate Solstice Pod licenses, including for Pod deployments not managed in Solstice Cloud.

- To streamline deployment, Mersive will no longer provide Quick Connect versions of the Mersive Solstice app, either downloaded directly from the Solstice Pod or from mersive.com/download/. Related options have been removed from Solstice Cloud and Pod local configuration settings.

- Windows MSI/SCCM and macOS DMG versions of the Mersive Solstice app will still be available at mersive.com/download/. Users will be referred to the downloads page when a newer version of the app is available, but the app will no longer auto-update upon connecting to a Solstice Pod.

The Solstice Location Service and associated features have been disabled. Settings related to this service were removed from Solstice Cloud and the Mersive Solstice app and will be automatically turned off in Solstice Dashboard.

Mersive now offers support for a range of devices from certified peripheral partners. These devices provide the best room audio and video resources for video conferences connected to a Solstice Pod. Organizations utilizing the Room Camera + Mic functionality in the Mersive Solstice app are encouraged to view the full list and details. Solstice 6.0 adds support for the following devices:

3a8082e126