MIXVIBES Dj Community old forum

When the graphical drivers are updated while the video plugin is active this results in a white videobox within the GUI and the external screen not working no more.

As a change in number of monitors is detected and warned for, this might be something to give a warning for to, or a way to have the plugin adapt to the situation without having to restart.

(even though updating in live situations is never recommended)

But why would you choose to update your graphic cards drivers whilst using the plugin or any other program that needs to use your graphics card

That's a recipe for disaster if you as me

That's why I put it in the suggestion forum.
I Agree that not changing things while performing is the best.

However videodrivers, as many other applications, are updating more frequent. Most updates nowadays can be run on the fly, without a reboot. I have not seen an other application having problems with the on the fly update of the video driver (likely these are not as dependent on graphical quality).

Updates may come 'any moment' (after reboot, after being downloaded, upon activating a WIFI, at fixed day/week/month, company policy, etc.....). Finding out updates one by one and doing them by hand is really time consuming so automatic updates is getting more and more common...

To my opinion the issue is not so much 'why would you do that' but more 'how can it be resolved when it happens'.

All Nvidia and AMD Updates require a reboot....

I am not sure where it comes from, just trying to report a new situation that appears to influence Cross. The update does not ask for a reboot of the PC. Also restarting Cross is sufficient. I do know that Nvidia has developped a new update program.

You can also have a notification about available update and not an auto-install one.
Updating drivers on the fly is like swapping device while using the application : risky !

The intention was just to put some information to development on this 'new' issue.

The only thing new with 'on the fly' updates is that starting with W8 it has come available for all users.
In e.g. high availablity environments this is common for more than a decade (also Windows); usually at high service costs.
Additionaly in the version logs Nvidia reports driver upgrade problems as being bugs for W8. Some of which they cannot control; likely Cross is one of these.