Troubleshooting

For more assistance or bug reporting send an email to support@visualvibes.io

This page will be update regularly with more information, better guides, video tutorials, and FAQs, so check back soon.

ViVi Freezes when operating?

Cause: Too Much Power Through ViVi

LEDs turn red, animation stops

This is caused by drawing too much current through ViVi.  ViVi can only pass-through a maximum of 5 amps of continuous current. If this is exceeded a protective circuit shuts down the controller and any lit LEDs should turn red and the animation will freeze.

To reset unplug the power and wait 30 seconds, then plug back in. If ViVi sets the LEDs red and freezes too quickly, remove some LED strips before restoring power. Follow the guidelines below for creating a setup that does not exceed the power limits.

LED POWER SUPPLY GUIDELINES (amps per 100 LEDs at 5V):
1A per 100 LEDs – Music reactive animations, 100% brightness
2A per 100 LEDs – Constant on, all LEDs, assorted colors, 100% brightness
3A per 100 LEDs – Constant on, all LEDs, white, 100% brightness
Power consumption drops in relation to brightness, power consumption decreases faster than brightness, so, for example, LEDs set to 70% brightness will use 60% of the power compared to LEDs at 100% brightness.

To avoid this issue you can reduce brightness to use less power or you can add additional power directly to the LEDs (see 5V Power Guide).

Cause: Power Supply Voltage Dropped Below 2.7V

Animation stops, LEDs remain colored

This is caused by the power supply voltage dropping too low.  Below 2.7V the main processor can create errors and corrupt the memory, ViVi automatically stops if this voltage is reached for even a fraction of a second.

This is a symptom of having an undersized power supply.  This is most common when using a USB power source, but could occur with any undersized supply.  See the guidelines below and ensure your power supply is rated for the number of amps your setup requires, if not, you can reduce the brightness to reduce power usage or buy a bigger power supply.

LED POWER SUPPLY GUIDELINES (amps per 100 LEDs at 5V):
1A per 100 LEDs – Music reactive animations, 100% brightness
2A per 100 LEDs – Constant on, all LEDs, assorted colors, 100% brightness
3A per 100 LEDs – Constant on, all LEDs, white, 100% brightness
Power consumption drops in relation to brightness, power consumption decreases faster than brightness, so, for example, LEDs set to 70% brightness will use 60% of the power compared to LEDs at 100% brightness.

Unable to Connect to App?

App crashes upon connection

Noise Filter is set to 1

There is a potential bug that can cause the app to crash upon connection when the Noise Filter is set to 1.  Multiple repeated attempts should result in a successful connection.  This is due to some byte being missed during the initial settings upload and should be patched in the latest app versions.  This affected both Android and iOS.

All outputs have animation set to a Constant or Off AND each has >200 LEDs in settings

The underlying cause is unknown and this only affects the iOS app.  When all outputs have 200 or more LEDs and each output has a animation near the bottom of the selection list (a Constant animation or set to OFF) then the iOS app will crash shortly after connecting.  This was discovered in September 2019 and is expected to be patched soon.

To resolve this an Android phone can be used to connect and change the settings so that the iOS app will no longer crash when connecting.  Another possible solution is to let the controller run for approximately one minute and if “auto-animation change” was checked on any of the outputs the animation should change to a music reactive animation and then the iOS app can be connected.

App shows white screen or blank list when opened

Check that ViVi has power

ViVi will only show up on the list if powered is connected.

 

Ensure app has location permissions

ViVi VibeLink needs location permissions to be able to scan for BLE devices.  This can potentially reveal your location by using BLE beacons that show up in a scan to compare against a list of BLE beacons with known locations.  ViVi VibeLink only uses BLE scanning to find BLE devices (which ViVi is one) so you can connect to ViVi without pairing in advance, it does not attempt to estimate your location.

Ensure phone “Location” is on

Some phones have an option to turn off “Location” which is separate from GPS.  Turning “Location” off will also disable BLE scanning and even if ViVi VibeLink has location permissions and your phone’s Bluetooth is on it will block the app from scanning for BLE devices.  GPS does not need to be on for the app to work, so that can be disabled directly without any issue.

A way to test if this is location permissions or “Location” being off is the issue is to open your phone’s Bluetooth menu which will show a list of nearby Bluetooth devices.  If ViVi shows up in this list, but not in the VibeLink app, then the phone is preventing the app from scanning for BLE devices due to either permissions or if the phones “Location” is currently off.

Other devices, but not ViVi, show up in app list

Bluetooth Name may have changed to “RigCom”

RigCom is the default BLE module name and in a few rare cases the module has defaulted back to that name for unknown reasons.  You can connect the same as usual by selecting RigCom.  If you wish to change the name back please contact support@visualvibes.io for assistance.  NOTE: the name RigDfu will show up for approximately 1 second when ViVi is powered on, this cannot be connected to.

Check that ViVi has power

ViVi will not broadcast it’s BLE name unless it is powered on.  We did not include a power indication LED (oops) so you can check by plugging in an LED strip and inputting audio to cause it to animate.  Alternatively you can carefully put multimeter probes into the bottom two squares of any LED output to check for 5V (left is +5V, right is GND), or check the circuits/connectors of cables or LEDs plugged into ViVi.

ViVi Not Responding to Music?

Cause: Audio Cable Connection is Bad

Messing the with audio cables causes erratic response

Sometimes cables break, sometimes you just need to push the connector in a bit more.

For pre-orders from Kickstarter and Indiegogo we discovered a later batch of 3.5mm extensions and splitters had quality control issues; to resolve you need to pull the extension plug slightly out from the splitter, creating a ~1/8″ gap, rather than being fully inserted.  This is most likely to affect orders shipped during May and June.

Cause: Audio Source Volume is Not Optimal

ViVi is triggering almost constantly, but with the music (volume too high), or ViVi very rarely triggers, only on very loud sounds (volume too low)

For most audio sources (phone, computer, etc.) the best volume setting is between 50% – 90% to give ViVi a clear signal to evaluate.  Try to adjust the audio signal source to this range and then adjust your speakers amplifier separately to get the volume you want to hear.

Too low of volume makes sounds less defined and harder to differentiate from each other and any static on the line.

Too high of volume can sometimes distort the audio signal and cause many of the loudest (but different) sounds to all hit the same max output level rather than allowing more variation as the original recording intended.  This is a rare issue that is unlikely to occur from an aux port on a phone or computer.

Cause: Sound Level is Too Quiet for the Microphone

You are using the microphone but ViVi is not responding to the music playing.

The microphone on ViVi require the sound level at the microphone to be about 75dB, which is loud enough to make you need to raise your voice to hold a conversation, but not have to yell. 

 

If the volume is too quiet you can try placing the microphone closer to a speaker, even directly in front of it will be fine.  Or turn up the volume!

Cause: Microphone is being Moved or Hit

ViVi reacts, but not to the sound.

If the microphone is touched or moved along a surface it can create very loud sounds in the wind guard that ViVi detects, ViVi will then not respond to the quieter sounds detected that are actually the music (it will again after about 30 seconds of no touching).

 

Make sure the microphone is placed in a location where it will not be bumped into or moved.  Having it dangling in the air would be better than moving against a surface.  If you are wearing the microphone place it somewhere clothing or limbs will not brush against it, like the center of your chest or top of your head.


Bug Tracking

These issues are known and being worked on:

(1) Sparkle Explosion animation won’t display beyond 255 LEDs.
— –Sparkle Explosion causes the software to freeze when generated for more than 255 LEDs, the display length limit is a temporary fix to prevent freezing. If your strip is more than 255 LEDs only the first 255 will animate when this is the active animation.
— — The underlying issue was resolved and will be implemented on new controllers starting in November 2019. Previous controllers will receive a firmware patch when the first firmware update is released in late Fall 2019.

(2) [iOS Only] app may crash upon connection if all outputs are set to Constant animations, or OFF, and all outputs have 200 or more LEDs.
— –This was discovered in September 2019, cause is unknown and only affects iOS app.  A controller with settings causing iOS crash may be connected to and adjusted with the Android app and after the settings are changed it will work with iOS again.  We expect this bug to be fixed quickly.

(3) If Noise Filter is set to 1, attempts to connect to ViVi VibeLink app may fail.
— —  After a year of random issues with this bug we discovered the cause was some bytes being missed in the initial connection settings upload.  The series of bytes created when NF=1 was much more likely to cause a missed byte.  This issue should be patched in the latest app versions.

(4) [iOS Only] LED count +/- button adjustment for bass output changes mid output LED count instead.
— —  The +/- buttons for the bass output LED count setting make adjustments to the mid range LED count instead.  The bass slider still works to adjust the bass LED count (going over the desired value by 5 LEDs looks fine, the slider can be tricky to get exact).  This bug was discovered in September 2019 and will be patched soon.