Troubleshooting

I can't access MiruSuite in my browser ("Your connection is not private").

If you see this or a similar error message, click on Advanced and Proceed to localhost (unsafe).

Why is this necessary? All modern browsers impose a limit of a maximum of six streams per website. Since MiruSuite makes heavy use of streams (camera feeds, predictions, GUI updates), we often require more than six streams. This is only possible using HTTP/2. All modern browsers only allow HTTP/2 with TSL encryption (HTTPS). Although encrypting traffic to localhost is entirely useless, this unfortunate constraint forces MiruSuite to do just that using a self-signed HTTPS certificate, which will not be recognized by any browser. Thus, there is no better option than to skip this warning.

Do I have to do this every time? Fortunately, no. After you have skipped the warning for the first time, most modern browsers will not show it again for a long time.

I cannot reach MiruSuite via the local network.

If you want to access MiruSuite from another device on your local network (e.g., to control it remotely or view the web interface from a tablet), you might need to configure your firewall to allow incoming connections. MiruSuite uses port 8443 for HTTPS and port 8080 for HTTP connections, unless you have configured different ports in the launcher settings.

Read about how to configure your firewall in the Remote Access guide.

Security Notice

Only allow incoming connections from trusted devices on your local network. If you need to access MiruSuite over the internet, use a VPN or other secure connection method.

I can't see any tracking boxes around people.

To enable tracking, make sure a Director component and a Person tracker component are added and enabled.

The tracking is losing the target person too quickly.

There are multiple reasons why this could happen:

• If the input delay is too high, MiruSuite cannot react quickly enough to the target person's movements. Try to connect your camera using a connection with a smaller delay. The smallest delays are usually reached using USB capture cards. NDI® has moderate delays, MJPEG streams usually have the highest.
• The director's sensitivity can be too low. Try increasing the sensitivity slightly.
• Smaller shot sizes (close-ups and extreme close-ups) are more difficult to track, especially if the person is moving around a lot. Try changing the shot size towards a wider shot.
• If the lighting conditions are too difficult, the tracking can be less reliable. Try improve the lighting of your shots.

The tracking is overreacting or oscillating on sudden movements.

There can be several reasons why the tracking could be too sensitive:

• The director's sensitivity can be too high. Try decreasing the sensitivity slightly.
• If the target person is so close to the camera that quick movements are required, the PTZ camera might be too slow to keep the target person in frame, leading to overcompensation. Try increasing the distance between target person and camera.
• Smaller shot sizes (close-ups and extreme close-ups) are more difficult to track, especially if the person is moving around a lot. Try changing the shot size towards a wider shot.
• If the input delay is too high, MiruSuite cannot react quickly enough to the target person's movements. Try to connect your camera using a connection with a smaller delay. The smallest delays are usually reached using USB capture cards. NDI® has moderate delays, MJPEG streams usually have the highest.
• You are using an unsupported PTZ camera. If the tracking behavior seems odd, reach out to our support team at supportmirusuite.de.

Feedback

We are always happy about your feedback when the tracking works well or when it fails. You can send us feedback or demo videos to infomirusuite.de.

(Windows) I can't find any NDI sources.

If you can't see a NDI source, make sure it is turned on and in the same network. If you still can't see the source in MiruSuite, the Windows firewall might block ingoing network traffic. Look for dialogs from Windows Firewall that ask for network permissions for MiruSuite. If there aren't any, check your firewall settings:

1. Search for and open the Windows Defender Firewall with Advanced Security.
2. Go to the Inbound Rules. Look for any rules for miruServer.exe:
3. If you find any, double-click it and make sure network traffic is allowed:

(Windows) When starting MiruSuite, I get an error message that says "The code execution cannot proceed because VCRUNTIME140.dll was not found". (or msvcp140.dll)

This error message indicates that the Microsoft Visual C++ Redistributables are not installed on your system, which are standard libraries needed for running MiruSuite and many other programs. You can download them from the Microsoft website. Install the correct version and try to start MiruSuite again.

(Windows) CUDA was disabled because of a critical failure during initialization. Please check that you have a compatible GPU and your installation is not corrupted.

This error message indicates that MiruSuite could not access your NVIDIA GPU using CUDA. Possible reasons are:

• You do not have an NVIDIA GPU installed. MiruSuite requires an NVIDIA GPU for fast AI computations.
• Your NVIDIA drivers are not installed correctly or are outdated. Make sure to install the latest drivers from the NVIDIA website.
• Your NVIDIA GPU is not supported. MiruSuite requires a GPU with compute capability 5.2 or higher.

After you have checked these points, try running the following command in a terminal:

nvidia-smi

If you can see your graphics card, open MiruSuite and click reactivate and restart MiruSuite.

(Windows) MiruSuite crashes after enabling person tracking.

This issue is probably caused by incompatible NVIDIA drivers. Please make sure to install the latest drivers from the NVIDIA website and see the previous question for more information.

MiruSuiteStarter is not able to start MiruSuite.

Maybe there is still an instance of MiruSuite running. Check your task manager and kill the process if necessary. If this does not help, try to restart your computer.

The video feed is black even though the NDI® Studio Monitor works.

In rare cases, certain PTZ cameras (e.g. Sony BRC-X400) may output their NDI® signal (often via NDI®|HX / NDI®-HX style encoding) using a codec or bitrate configuration that prevents decoding in MiruSuite, while the NDI® Studio Monitor works correctly. As a result, the NDI® source appears in MiruSuite but the preview image remains black.

Check the video codec / NDI® encoding profile settings in the camera configuration:

1. Open the camera's web interface.
2. Navigate to the Video Codec / Streaming settings.
3. Review the available encoding or NDI®|HX / NDI®-HX profiles for the NDI® output.
4. Try adjusting the following settings (if your camera exposes them for its NDI® output):
   • Switch the codec within the available profiles (e.g. between H.264 and H.265).
   • Change the bitrate mode (CBR vs VBR).
   • Reduce the bitrate if necessary.

Some cameras allow multiple encoding profiles for their NDI®|HX / NDI®-HX output; selecting a different one can resolve the issue immediately.

After applying the new codec or profile settings, restart the stream if required and reconnect the NDI® source in MiruSuite.

INFO

MiruSuite uses the standard NDI® libraries for video decoding. However, some cameras only support certain NDI®|HX / NDI®-HX or encoding profile configurations for external decoders, so specific codec/bitrate combinations may not work reliably in MiruSuite.

My auto tracking stops working after a while.

Maybe your computer turns off the display or goes to sleep. Check your power settings and disable automatic display sleep as this can cause the video feed to pause.

My preview video feeds stop after a while.

This is a known frontend issue, usually due to a slow connection between your browser and the MiruSuite server or due to high load of your browser. Stopping the video feeds is the browser's choice so we cannot detect or circumvent it. We recommend just refreshing the page/visiting another view to resume the video feeds. Don't worry, MiruSuite will continue to work fine. Tracking quality is not affected.

My audio device is not detected.

Due to driver limitations, new audio devices can only be detected on startup. To discover newly connected devices, a restart of MiruSuite is required.

My UI is looking broken or some features are not working.

Make sure you are using a supported browser. We recommend using the latest version of Google Chrome for the best experience.