Vimu Engine V2 — Failed 2021

Each user gets their own cursor and can simultaneously work on the same Windows desktop. Configure each individual pointer device (acceleration, cursor theme, wheel and button behaviour etc) independently. Collaboration was never so easy!

Download (Or read some more on what features we have)
December 2025 - New Beta Release
RustDesk + MouseMux = Multi-user Remote Desktop

Major updates to MouseMux! We now support RustDesk for multi-user remote desktop collaboration. This BETA includes new collaborative apps (Multi Paint, Team Vote, Whiteboard), smarter keyboard remapping, performance optimizations with cursor caching and high-DPI mouse support, a new Web SDK, and many bug fixes. As this is a beta release, you may encounter small inconsistencies. Your feedback is highly appreciated!

Get the New Beta!

Simple collaboration

Our goal is to make working together as intuitive and simple as possible. Just add some extra pointer devices (mice, pens, touchpads) and (optional) keyboards and MouseMux will transform your PC into a realtime multi-user system. Each user can work in their own document, annotate on the screen, drag or resize windows or interact with different programs - all at the same time on the same windows desktop. Simple annotations allow each user to highlight parts of the screen. Concurrently interacting with different apps on the same desktop creates new and interesting ways to work together; collaborate by taking over certain actions, type together, draw together - all at the same time without interfering others.

$features.alt

For teams

Use it for pair programming, collaborative designing, in the class or meeting room (so all can interact and have a presence on the screen). Join forces on editing documents, or in the control room so each operator can see where the others are. vimu engine v2 failed

For individuals

Use it to customize your mouse (or pen, touch or tablet) interaction; custom acceleration, assigned buttons, themes or wheel behavior - for each individual pointer device. Let any pointer device act as any other (mouse, pen, touch, etc). Record macro's and play them back to automate tasks, even in a multi cursor scenario. Having a cursor for each mouse means you can quickly interact with individual applications because cursors can be localized or dedicated to one program - the restriction of moving one cursor all over the screen and refocusing on a specific application is lifted. The screen's realastate becomes much more manageable. If you are using external apps like TiviMate

For industry

In Industrial processes including manufacturing, process control, power generation, fabrication, and refining, and facility processes, including buildings, airports, ships, and space stations where multiple operators work in SCADA like situations safe multiuser operation is vital. MouseMux can manage individual users and can store historical data of any interaction. Assigning a supervisor and overriding actions by other operators is now possible - SCADA programs can integrate with our SDK so true simultaneous interaction becomes possible. Try toggling "Hardware Acceleration" off to see if

Vimu Engine V2 — Failed 2021

If you are using external apps like TiviMate or Stremio to call Vimu, the handoff can fail if the device's RAM is overloaded.

Based on an older version of ExoPlayer, this is often more compatible with older devices or specific file types that struggle with modern decoders.

: Reducing the stream buffer size can prevent crashes on weaker devices.

Try toggling "Hardware Acceleration" off to see if software decoding works, or change the "Hardware Decoder" type. 3. Clear Cache and Force Stop Residual data can cause engine initialization failures.

Are you still seeing the "Engine V2 Failed" message after trying these steps? Let us know your and firmware version in the comments!

Engine V2 closely links video rendering with audio syncing. If Vimu attempts to output a raw audio track (like DTS-HD or TrueHD) to a device that doesn't support it, Engine V2 will fail to initialize the video track. Inside Vimu, open . Go to Audio settings. Locate Audio Passthrough (AC3/DTS/EAC3). Turn passthrough Off or switch it to Software Decoding .

If the error persists after all the above, consider that your device’s GPU may be incompatible with Engine V2. Here are three zero-cost alternatives that handle the same streams without the error:

The video file uses a profile (like 10-bit HEVC or Dolby Vision) that your hardware or the V2 engine cannot process.

As the Vimu team regroups to work on Project V3, the industry watches with bated breath. They have promised a return to monolithic simplicity. Whether users will give them a second chance, however, remains to be seen.

, there are three primary ways to resolve the "Engine v2 Failed" error: Revert to Engine v1 (Legacy) : In many cases, switching the playback engine from v1 (Legacy)

FAQ

If you are using external apps like TiviMate or Stremio to call Vimu, the handoff can fail if the device's RAM is overloaded.

Based on an older version of ExoPlayer, this is often more compatible with older devices or specific file types that struggle with modern decoders.

: Reducing the stream buffer size can prevent crashes on weaker devices.

Try toggling "Hardware Acceleration" off to see if software decoding works, or change the "Hardware Decoder" type. 3. Clear Cache and Force Stop Residual data can cause engine initialization failures.

Are you still seeing the "Engine V2 Failed" message after trying these steps? Let us know your and firmware version in the comments!

Engine V2 closely links video rendering with audio syncing. If Vimu attempts to output a raw audio track (like DTS-HD or TrueHD) to a device that doesn't support it, Engine V2 will fail to initialize the video track. Inside Vimu, open . Go to Audio settings. Locate Audio Passthrough (AC3/DTS/EAC3). Turn passthrough Off or switch it to Software Decoding .

If the error persists after all the above, consider that your device’s GPU may be incompatible with Engine V2. Here are three zero-cost alternatives that handle the same streams without the error:

The video file uses a profile (like 10-bit HEVC or Dolby Vision) that your hardware or the V2 engine cannot process.

As the Vimu team regroups to work on Project V3, the industry watches with bated breath. They have promised a return to monolithic simplicity. Whether users will give them a second chance, however, remains to be seen.

, there are three primary ways to resolve the "Engine v2 Failed" error: Revert to Engine v1 (Legacy) : In many cases, switching the playback engine from v1 (Legacy)

These companies, among other, use & trust MouseMux

Proudly serving our clients! Let us know if you need a customized/branded version for specific corporate or industrial use.

ABB - Global leader in industrial automation and power technologies
BMW - Premium automotive manufacturer
UFA - University of Alberta
NHS - National Health Service UK
ROAV7 - Regional Operations Air Vehicle 7
RUAG - Swiss aerospace and defense technology company
Micronav - Navigation and positioning technology solutions
Amgen - Biotechnology company
Avio Aero - Aerospace manufacturing company
Bosch - Global engineering and technology company
Schiphol - Amsterdam Airport Schiphol
Vector - Embedded systems and software tools provider

Contact

Address
Moreelsepark 65, 3511 EP Utrecht, the Netherlands
Email

Love MouseMux? Join Us!

We're looking for a passionate MouseMux enthusiast to help spread the word! If you love creating content (videos, tutorials, demos), engaging with communities, or just can't stop talking about multi-cursor collaboration, we want to hear from you.

We love people who think outside the box and can spot new opportunities where MouseMux could flourish - whether that's creative use cases, new markets, or ways to reach people who haven't discovered multi-cursor collaboration yet.

Interested? Email us