How To

How to Set Up Automated VJ

Setup steps and a first-night checklist

The fastest way to test automated VJ is not to enable everything at once. Start with output, audio, network, and staff control in that order to reduce operational risk. This guide goes beyond the minimum "pixels on screen" baseline into the real production-ready checks that separate a stable venue setup from a flaky demo, with concrete numbers and common failure modes.

Setup time
30 to 45 min
Reading time
About 9 min
Difficulty
Beginner (1/3)
For
Owners and managers of DJ bars, lounges, and smaller venues
You will need
PC, screen, mic, Wi-Fi, latest Chrome
How to Set Up Automated VJ

Who this guide is for

This guide is written for owners and managers of DJ bars, lounges, and smaller venues who want a reliable visual layer every night without hiring a dedicated VJ every time. It treats automated VJ as a baseline for ordinary operating hours, not as a replacement for live visual performance.

The hardware you need is minimal: one PC with HDMI output (Mac or Windows), a screen or projector already installed in the room, a mic that can hear the speakers, either wired Ethernet or a 5GHz Wi-Fi network, and the latest Chrome. No additional purchases are required. Budget roughly 30 to 45 minutes of focused time for the initial setup and first test.

Core setup steps

  1. Choose the playback computer

    Use the machine that feeds your venue screens and confirm that browser playback stays stable. If this step is shaky, nothing that follows will save you.

    What to do
    Install the latest Chrome on the Mac or Windows machine you already use at the venue. Open app.autovj.club, switch to fullscreen, and watch the output for 30 seconds.
    Success check
    CPU usage stays under 50 percent, fullscreen playback keeps a stable framerate, and the laptop is on AC power rather than battery saver mode.
    Common pitfall
    Older MacBook Airs and low-end laptops with integrated graphics often fall back to SwiftShader (CPU WebGL) and drop to single-digit FPS in fullscreen. Do not walk into a night with a "runs but stutters" machine. A cheap mini PC like an Intel NUC is usually the faster fix than trying to tune an old laptop.
  2. Verify the display path

    Confirm resolution, fullscreen behavior, HDMI routing, and any switcher in the venue chain. Display issues are hard to fix during service, so catch them before the doors open.

    What to do
    Turn off mirroring, add the venue screen as an extended display, move the browser window to that display, and go fullscreen. Then disable sleep, screensaver, and any auto-restart schedules on the PC.
    Success check
    The aspect ratio looks correct, the resolution matches the native value of the screen (often 1920x1080), and after 10 minutes of idle time, no sleep or screensaver has kicked in.
    Common pitfall
    HDMI matrices and cheap switchers can trigger HDCP warnings or black screens in unpredictable ways. Always test through the exact same routing you will use on the night. On macOS, double-check the battery-saver sleep settings — they are often separate from the main sleep config.
  3. Make sure the system can hear the room

    If you plan to use song recognition or audio-reactive behavior, mic placement is the most important single setting. It directly controls recognition accuracy.

    What to do
    Use the built-in mic to test quickly, but ideally connect a USB mic near the DJ booth. Grant mic permission in the browser, then watch the Level Meter on the control panel while music plays at normal volume.
    Success check
    With typical DJ levels, the Level Meter sits between -20dB and -6dB steadily without clipping. With Auto Identify at its default 60-second interval, recognition succeeds on more than 70 percent of tracks.
    Common pitfall
    A mic far from the speakers or close to an HVAC vent will cripple recognition. Shortening the Auto Identify interval below 60 seconds rarely improves hit rate but multiplies ACRCloud costs, so avoid it.
  4. Test the network

    Confirm that video retrieval, song metadata, and lyrics calls all work reliably on your actual venue connection. Shared networks are the most common cause of mid-night visual dropouts.

    What to do
    Run fast.com and confirm at least 10Mbps downstream. Prefer wired Ethernet. If that is not possible, set up a venue-only 5GHz SSID separate from the customer Wi-Fi.
    Success check
    Ten minutes of continuous music-video playback runs without buffering. Now Playing and lyrics updates appear within two seconds of a track change.
    Common pitfall
    Sharing bandwidth with a packed customer Wi-Fi is a recipe for the screen freezing on a busy night. Always separate venue and customer networks, and keep a mobile hotspot ready as an emergency fallback.
  5. Create a safe default preset

    Set restrained defaults for brightness, overlays, lyrics, and Now Playing that fit normal service. Time spent here pays back every subsequent night.

    What to do
    Keep brightness and contrast moderate (around 60 to 70 percent of the display), keep lyrics off, place the logo small in the lower-left, and show Now Playing only on track change for four seconds. Save the configuration via Settings > Export as JSON.
    Success check
    After two hours of continuous playback, neither staff nor guests complain about brightness or distraction. The visuals never pull focus from conversation or service.
    Common pitfall
    Reusing an event preset for normal operation overwhelms the room. Always keep a "daily" preset and an "event" preset in separate files, and make switching between them a one-tap action.
  6. Confirm mobile control

    Make sure the staff member on shift can reach the control surface from the same network, with a minimal set of controls exposed.

    What to do
    On a phone connected to the venue Wi-Fi, open app.autovj.club/control and sign in with the same Google account as the main display. Expose only three to five controls such as brightness, logo toggle, lyrics toggle, and Now Playing toggle.
    Success check
    Each action reflects on the main display within one to two seconds. Locking the phone and unlocking it again restores the connection automatically.
    Common pitfall
    Exposing every control to staff invites accidental full-effect chaos on the floor. Keep the mobile view deliberately small. And remember: if the main display and the controller use different Google accounts, cross-device sync will not work at all.

First-test checklist

These checkboxes save to your browser locally. Run through them in order during your first test, and only go live once every item is checked.

Common pitfalls and how to handle them

Fullscreen playback stutters
Integrated-GPU laptops and older Macs sometimes fall back to SwiftShader (CPU WebGL), which tanks framerate. Open chrome://gpu and confirm that Graphics Feature Status shows Hardware acceleration as Enabled. If it is not, a cheap HDMI-capable mini PC (Intel NUC, Beelink, etc.) is usually the most direct solution.
Song recognition hit rate is low
Mic placement is almost always the real issue. Mount the mic within 1 to 2 meters of a speaker, and avoid HVAC airflow. Keeping Auto Identify at the 60-second default is important too — shorter intervals barely improve hit rate but multiply ACRCloud spend roughly four times over.
Phone controls do not reflect on the main display
Verify that both surfaces are signed in with the same Google account. Without login, sync is limited to the BroadcastChannel within a single browser and will not cross devices. If login is correct but sync still fails, reload both tabs to re-establish the link.
YouTube keeps refusing to play videos
Embed-disabled videos (common for official J-POP music videos) return error codes 101/150, and the system automatically skips them. Adjust the MV section's region setting or toggle anime mode to widen the candidate pool. For full control, switch to a self-curated YouTube playlist.
When visuals freeze during service
Step 1: reload the browser (Cmd/Ctrl + R). Step 2: close and reopen the tab. Step 3: reboot the PC. Share this three-step recovery with staff in advance. If the person on shift is not technical, print the steps and tape them next to the PC — it is the fastest way to recover.