Mouse error on Profile Console!

[soundarchitect]

Hope anybody has an idea about the following:

Today a friend of mine had a mysterious error on the Profile console he's been touring with for three months. He couldn't use his mouse in the plug-in window anymore! To be more specific: the mouse functioned everywhere in the console, including the plug-in rack. But when he wanted to alter any specific plugin itself the mouse didn't react on any clicks or whatsoever.

All the plugins are loaded fine and could be adjusted via the console controls, but this is not how it should be. Everything else seems to be normal.

Has anybody encountered this before? Advise or help appreciated.

Regards,
Dennis

[Sheldon Radford]

Hi,

Sorry to hear about the troubles. One thing to try if this happens again is to hold the keyboard ALT key and press TAB (Alt+Tab) while the Plug-Ins screen is displayed, as this may restore the window focus to the plug-in interface and allow the mouse to control parameters again. If it happens consistently please contact customer service so we can get a copy of the show file and see if the problem can be reproduced.

Also, ensure the latest versions of all plug-ins are in use. On the Options > Plug-Ins page select each plug-in from the right hand "Installed" list and examine the Info pane to see if an alert indicating the plug-in needs to be updated is displayed. You can also export the system info file to a USB key (Options>System, click on the info button) in order to see a full list of plug-ins, including those which have updates available.

Sheldon

[C Hawk]

Ive had that issue with one kind of logitec Trackball and to fix it i just replaced the mouse and rebooted the console.

i think the mouse confuses the mouse driver in windows coz if you enter windows you have no control of the mouse aswell

[soundarchitect]

Thanks for the replies and help.

To keep you informed: when the Profile console was restarted the next day (!) everything worked normally. The only thing different with the day before was the power being completely disconnected from the racks.

One of the very few bugs/errors we've encountered the last few years...

Cheers,
Dennis