Skip to main content

Editor: Known issues

OS-independent issues​

Grid Editor Issues​

How to import locally saved profile .JSON files into the Profile Cloud​

If you have old .JSON Grid configuration profile files saved somewhere on your computer here's how you can import into the modern profile cloud interface:

  1. Make sure Editor in not running.
  2. Go to your ...\grid-userdata\ folder.
  3. Create a new folder inside ...\grid-userdata\ named profiles.
  4. Copy and paste all your old legacy profile .JSON files into the folder named profiles.
  5. Start Editor and you should see your old profiles appear in Profile Cloud converted to the new system. After this if you check the folder named profiles should have disappeared.

Grid configurations are all stored in ...\grid-userdata\configs\ in new Editor versions and the above process will migrate your old configurations there as well.

Grid module is stuck in a bootloop caused by an uploaded faulty configuration, how to fix it​

Reset your controller to the defaults by following the instructions highlighted here

OS-Specific Issues​

Windows System Issues​

List of possible windows issues and their resolution.

Windows 7 does not recognize your device​

caution

Windows 7 is not supported by Grid Editor.

Using Windows 7 today is brave! It can be that you will need to install a serial driver to get started using Grid Editor. Link is on our Github below:

Download the Drivers

Mac OS Issues​

List of possible Mac OS issues and their resolution.

Grid does not show up as MIDI device​

Your system may have specific MIDI routing or configuration set up with your existing devices. In the Audio MIDI Setup application you can try to add Intech Studio: AC as a MIDI device for your config.

See the Apple Documentation

Grid interfering with Vodafone ZTE/Huawei driver​

Your system may have existing preference, configurations, drivers or other software installed which blocks serial device enumeration for Grid.

For debugging sessions: kextfind -report -b -loaded | sort |grep yes |grep -v com.apple will show you the loaded kernel extensions that are not from apple, whereas e.g. pkgutil --pkgs | grep -i novamedia followed by pkgutil --files de.novamedia.driver.pkg will show you the list of files to delete (when installed through a .pkg). After deleting stuff manually, remember to pkgutil --forget de.novamedia.driver.pkg to remove it from the list of installed packages after you finish.

Extensions are located in /System/Library/Extensions or /Library/Extensions. Go there and e.g. kextunload /System/Library/Extensions/de.novamedia.driver.NMUSBCDCACMData.kext before deleting the .kext directory.

Linux Issues​

List of possible Mac OS issues and their resolution.

User has no access to serial ports, and therefore to serial devices like Grid | Grid not visible in Editor on Linux​

If you're using a Linux system, it might be possible you have no access to serial ports and this is why when connecting a Grid module to your system it still isn't visible in Grid Editor.

To enable serial access, try the following steps:

  • Close Grid Editor if you still have it open.
  • Open up terminal and type in the following command: sudo adduser $whoami dialout
  • This will add the current user to the dialout group which you'll need to have access to serial ports on Linux.
  • Log out and the log in again.
  • Relaunch Grid Editor and the module should be showing up now.

Firmware Issues for Intech Studio devices​

List of possible firmware update issues and their resolution.

Black LEDs after starting Grid​

LEDs are black and Grid doesn't send MIDI data, neither is it visible in Editor.

You're most likely experiencing a firmware crash. This can be caused by a corrupted firmware upload or an outdated bootloader. If you're using an older Grid module purchased before May of 2023, with a white logo on the front visit the bootloader update article that might resolve your issue.

Otherwise with a firmware crash it's best to send a mail to support@intech.studio!

Device does not show up as removable device​

Reboot your computer. Make sure you connect your module directly to your computer. Check if the utility side button moves freely and it is not stuck. For each time you connect the module, wait 5 seconds to see the device showing up. Repeat the connection step based on the firmware update document multiple times, it can be that it will show up after a couple tries. Try a different computer.