Lights with Vista M1 Console & Vista 3 Flash Off

Hi everyone,

Been having a problem recently with the lights seemingly going dark almost like a blackout button has been hit and then a few seconds later come back on. Happens randomly every few minutes or so.

We are using the Vista M1 Console with Vista 3. Everything works perfectly fine and scenes are all working and everything. We just have this one random glitch that keeps happening. Cant seem to be able to find an answer anywhere.

Thanks!

What operating system are you using?

Sounds like your dongle is not plugged in, drivers not working or it is broken.

We are using Mac Mojave 10.14.6

Dongle is plugged in and everything is working normal, just occasional black outs and jump back on. Never says “disconnected” or anything.

The only thing that would happen if it is the dongle is it would say “blackout” in the main title bar.

Pess “help > about Vista”. How many available channels does it say you have ? 0?

I am using Vista Chroma Q EX console with Vista 3 and the same thing is happening to me. Very frustrating!!

Hi Christine,

The answer will likely be the same. You are either missing the physical dongle or the dongle driver.

What version of Vista are you using? If you are not using Vista 3 R3 I would recommend installing this. This included updated drivers.

If you still have issues, submit a support request.

The main info we will need to know is the Vista version you are using and the Operating System.

Jack

Also, why does the lights brighten up when I switch from one fader to another?

Any solution to this?

I am having the same problem at my church… M1 Console, vista 3 latest release, Mac pro that’s updated. One thing I have noticed is that if I switch usb ports of the dongle and the M1 and reboot, this problem goes away… No real solution so far since it’s happened a few times in the last couple months. No idea when this will strike. Help!

Did you check your lincense/channel count before you switched usb port/ reboot like @jack.moorhouse said?

I did not check that before the reboot. I will when this happens again because as it stands there seems to be no solution to this error.

Two things, first make sure you are on the latest build.

Second, if you are and the problem persists then fill out a support ticket.