Multiple users/mice on one desktop

Nothing special. Just plug in some spare mice, pens, tablets or touchscreens and/or keyboards. MouseMux will detect the newly plugged in devices and automatically add them. Generally what people do is buy a USB hub and use that to plug in more mice and keyboards. Theoretically you can add unlimited devices, we tested up to 32 simultaneous users (64 input devices).

Occasionally a virus scanner will flag MouseMux as unsafe - under the hood MouseMux has lots of complex behavior and emulates part of the input layer of windows, some virus scanners will find that behavior suspect and will raise the alarm. We're in continuous contact with manufacturers of security tools to keep MouseMux white-listed. Please drop us a line if your virus scanner flags MouseMux as suspect.

Yes. The business edition has a 'capture device' which will capture mouse input injected by (most) remote desktop programs - so the remote user will become a separate MouseMux user/cursor. You can try out this functionality in trial mode to see how it works. The mouse cursors are rendered in such a way that remote deskop programs will show the cursors on the remote screen too. See the manual for further explanation.

Yes. The business edition has a 'capture device' which will capture mouse input injected by (most) auto-clicker/macro/robo-clicker programs - so the clicker will control a separate MouseMux user/cursor. You can try out this functionality in trial mode to see how it works. See the manual for further explanation.

Some high precision touchpads inject their input into the Windows subsystem; to catch that input you have to enable the 'capture device' - once enabled you will be able to use your touchpad as normally. This option is only available in the business edition of MouseMux (but you can test it for free in trial mode). See the manual for further explanation.

The Logitech unifying receiver acts as generic USB HID device and as such MouseMux will work fine and detect both mouse and keyboard input. It will however not be able to separate between devices during saving and loading because the receiver (re)creates device ID's - so settings for each mouse will get lost unfortunately.

When MouseMux starts it will try to minimize required CPU resources to play nice with your system but this may also result in laggy cursors - to fix this you can enable 'High priority threading' in the settings dialog, also try to move the 'Main loop speed' all the way to the left to speed it up a bit more. For multiplex mode there is also a 'high priority multiplexing' option that optimizes the code paths for multiplex mode.

Try enabling 'Force hardware dragging' in the output tab of the user, this will force MouseMux to use hardware dragging for that user and will fix a number of issues with dragging, painting, etc. You can additionally enable 'Force hardware motion' to force any motion through the hardware layer.

MouseMux generates telemetry to help us understand how it behaves on various systems. All data is anonymized, no personal data is sent to our servers. No interaction data is sent, so no keystrokes, no titles of windows you clicked, etc. We’re mainly gathering which features are being used, how long some operations take and what warnings are generated during a MouseMux session. We’ve built a list of all specific data that is sent to our servers – find it at https://mousemux.com/pages/telemetry - feel free to contact us if you have any questions or concerns!

All windows versions are supported, from Window XP up to Windows 10, including all the server editions. The program comes in both 32bit and 64bit versions and will automatically select for the appropriate architecture. There is initial support for Windows Apps (UWP) and this will be updated in the coming period. Windows 11 now has initial support.

Keyboard pairing means linking a keyboard to a mouse – together they represent a (virtual) user. Pairing is simple: move a mouse and hit a key on the keyboard that you want to pair. You will see both the mouse and keyboard light up orange in the row of your user number. Working with paired keyboards may feel unintuitive at first; here’s a use case to explain why. User A and B sit behind the same computer, there are two mice attached and one single keyboard. Both users are interacting with the desktop with their own mouse. User A pairs his mouse to the keyboard. User A clicks on notepad and starts typing. User B takes over and types on the same keyboard. Now user B clicks on some other window and expects to start typing in that window – but since the keyboard is paired with user A, and user A did not click on any other window user B will keep typing in notepad! Practically speaking; user B does not have a keyboard – he/she just follows what the focus window is of user A. This may feel unintuitive because generally you expect to be able to type in a window once you click on it. For this scenario we added an option to synchronize all keyboards (even if it’s just one) to all users – that means mice can operate independently but the keyboard is shared for all users. You can uncheck the Multi Keyboard option in the main UI to disable per-user keyboard pairing – when this option is switched off the keyboard(s) will work just like in normal windows – follow the window with focus to send key data to. Of course, if you have two keyboards and two mice and user A and B are both working on the desktop we suggest to keep the Multi Keyboard option checked and pair each keyboards to an individual mouse so that both A and B can work independently with each a mouse and keyboard.

Yes! MouseMux will route each device to a 'user' - so your pen is a 'user', your touch screen and your mouse are other 'users'. So touching your screen will just move the 'touch screen user' while your mouse will move a different user/cursor. Screen real estate is much more easier to manage and navigate! You can even blank the cursor to completely remove any visual effects that may be annoying during touch.

Yes! MouseMux can convert any source device type to any target device type; MouseMux will read an input device and build a generic input event from that - inside MouseMux these events can be manipulated (adding pressure or rotation data, inverting an axis or translating coordinates from absolute to relative for example) and then be outputted as any device - so you can mimic pen behavior with a mouse or use your pen as a touch device or mouse for example. Multi touch is also availabe, you could for example use two mice devices to mimic multi touch interactions.

Yes, we have two SDK's available in beta. They allow MouseMux to run in the background (hidden) and perform various actions. SDK one can create virtual mouse pointers and users via API calls while the other SDK can 'filter' mouse events and change them on the go. Please note that these SDK's are still very much in beta and are only distributed to collaborating parties. Please drop us a line for more information.

Yes! MouseMux development is very active and the program is continually being updated (and will update on your computer automatically). Once you buy MouseMux you are entitled to all updates for free.