Skip to main content
All CollectionsStreamingStreaming Tips
Troubleshooting Buffering Issues While Streaming on ViGram

Troubleshooting Buffering Issues While Streaming on ViGram

Sergey Manvelyan avatar
Written by Sergey Manvelyan
Updated yesterday

Troubleshooting Buffering Issues While Streaming on ViGram

Buffering issues during streaming can be frustrating—for both you and your audience. Here’s how to fix the most common causes of buffering when streaming to ViGram.


✅ Step 1: Check Your Internet Connection

  • Use a wired (Ethernet) connection whenever possible. Wi-Fi can be unstable, especially for high-resolution streaming.

  • Run a speed test. We recommend:

    • Upload speed: At least 6 Mbps for 1080p

    • For 4K or high-frame-rate: 15 Mbps or more

  • Avoid sharing your connection with other bandwidth-heavy applications (e.g., online games, cloud backups, Zoom calls).


✅ Step 2: Optimize Your Stream Settings

If your internet speed is limited, adjusting your settings helps reduce buffering.

  • Resolution: Lower from 1080p to 720p if needed.

  • Frame Rate: Lowering from 60 FPS to 30 FPS can help reduce bandwidth usage.

  • ViGram Bitrate Recommendations:

    • 30 FPS: Set bitrate to 5000 Kbps

    • 60 FPS: Set bitrate to 7000 Kbps

In OBS:

  • Go to Settings → Output and adjust the Video Bitrate

  • Under Settings → Video, adjust:

    • Base/Output Resolution

    • Common FPS Value


✅ Step 3: Double Check Your ViGram Server and Stream Key

Make sure you’ve entered the correct streaming details from your ViGram dashboard:

  • Server URL

  • Stream key (make sure there are no extra spaces when pasting)


✅ Step 4: Reduce System Load

  • Close any unnecessary programs or browser tabs

  • Disable sync apps like Google Drive, OneDrive, or Dropbox during streaming

  • A fresh reboot before you go live helps ensure a clean slate


✅ Step 5: Monitor Stream Health in OBS

  • OBS shows a status bar at the bottom:

    • Green = Good

    • Yellow = Caution

    • Red = Trouble (dropped frames or network issue)

  • Go to View → Stats in OBS to check frame drops, CPU usage, and network stability


Still having issues?
📩 Contact ViGram Support and include your OBS log file and speed test results so we can help troubleshoot.


Fixing Common OBS Encoder Problems for ViGram Streaming

OBS is a fantastic (and free) streaming tool—but it can throw some confusing errors if your setup isn't just right. Here's how to solve the most common encoder problems when streaming to ViGram.


🔧 Error: “Encoder Overloaded! Consider turning down video settings…”

What it means: Your computer can’t handle the current settings and is struggling to encode video in real-time.

Here’s how to fix it:

  1. Lower your Output Resolution
    OBS → Settings → Video → Output (Scaled) Resolution → Try 1280x720

  2. Reduce the FPS
    OBS → Settings → Video → Common FPS → Drop from 60 to 30

  3. Use Hardware Encoder if supported
    OBS → Settings → Output → Encoder → Choose NVENC, Apple VT, or AMD, instead of x264

Recommended Bitrate Settings for ViGram:

  • 30 FPS: 5000 Kbps

  • 60 FPS: 7000 Kbps


🔧 Error: “Failed to Start Streaming” or “Invalid Output Settings”

  1. Double-check the server URL and stream key provided by ViGram.

  2. In OBS, go to Settings → Output and verify:

    • Output Mode: Advanced

    • Bitrate: Use ViGram recommendations

    • Keyframe interval: 2

    • Profile: Main

    • Tune: (optional) zerolatency


🔧 Laggy or Stuttering Stream in OBS

  • Check OBS stats:
    View → Stats → Look for "Skipped frames due to encoding lag" or "Dropped frames due to network"

  • Try switching from Software (x264) to Hardware Encoder (NVENC, AMD, or Apple VT)

  • Remove unnecessary overlays, filters, or high-resolution sources


🔧 Audio Out of Sync?

  • Use Advanced Audio Properties in OBS to set a sync offset (typically around ±200ms)

  • Confirm the sample rate matches system and OBS settings (either 44.1kHz or 48kHz across both)


🛠 Pro Tip: Keep OBS up to date! New releases fix bugs and improve encoder compatibility.

Did this answer your question?