Hello, I downloaded the most recent version and seem to have dropouts in the waveform; This did not happen in a previous version though.
I would like to use the most recent version because it can be resized unlike the ones before. Does anybody have the same issue?

This is the most recent version 1.1.0 vst3 (same happens with vst2)


This is the old version and how it should look

 

Affirmative. They managed to f-it up. If you feed a test sine signal and switch to Spectrum tab, you'll see lots of upper harmonics instead of that single sine fundamental. Sadly the entire thing is non-functional, and it was a really smart oscilloscope

 

Get the free version from Computer Music magazine archive on File Silo then. It's the same thing. I'm not sure what their "update" even did, probably support for newest operating systems?

The CM version was in issue #216. Link for pc/mac: https://www.filesilo.co.uk/software/vengeance-sound-scope/

 

Last edited: Aug 3, 2025 at 12:46 PM

Thanks for linking this version, the legacy VPS Scope was the only plugin left that required my eLicenser USB dongle. Now I can retire the eLicenser alltogether.

 

Have you tried this one?

FREE Scope

a free analyser plug-in with scope, screctral and stereo field analyse capabilities!
This plugin is free for all.
available in VST,VST3, AAX and AU format.
Version 1.0.4.
www.vengeance-sound.com/plugins.php?sub=FREE%20Scope

 

I'm already using 1.0.4 from CM, I made the thread to know if there was a fix for the most recent version

 

I can't find any error, are you sure the error isn't yours?

Spoiler: Source: ChatGPT KI

It appears that very few users have reported issues with VPS Scope 1.1.0—especially not any global reports of waveform dropouts or audio glitches. On KVR, version 1.1.0 is confirmed as the latest release and widely adopted, with no widespread bug mentions tied to waveform interruptions KVR Audio+1KVR Audio+1. The earlier 1.0.4 version is similarly documented, but again no direct notes of dropout issues in official changelogs or forum posts KVR Audio+1AudioSEX - Professional Audio Forum+1.

What You Can Try
1. Check for Known Host-Specific Issues
VPS Scope is often used in DAWs like Cubase, Reaper, Studio One, etc. Other Vengeance plugins have had host-specific quirks, such as GUI display overlap or automation issues—but no specific dropout issues with Scope have been flagged so far support.slatedigital.comvengeance-sound.com. It’s possible your DAW/plugin host is introducing latency or processing glitches.

2. Test in Different DAWs or Session Contexts

• Try loading Scope 1.1.0 in a clean project/session in another DAW (or offline render mode) to see whether the waveform dropouts still occur.
  
  
• Disable any other plugins around it to check if CPU load or plugin chaining is causing interference.

3. Compare Side‑by‑Side with 1.0.4
You already mentioned that 1.0.4 doesn't show dropouts—try loading both versions in the exact same session or audio source, with identical routing and buffer settings. That will isolate whether it's truly an issue with the new version or its interaction with your system/config.

4. Buffer Size and Resampling Settings
If 1.1.0 adds resizing flexibility, it might interact differently with your buffer or screen-scaler. Try changing your host’s audio buffer size (e.g. switching between 128 samples vs. 512) or monitor resampling/zoom settings.

5. Report the Issue
Since there doesn't seem to be a general report yet, it would help if you can provide details to Vengeance Sound directly:

• Your OS and DAW host (Windows/macOS, DAW version, VST‑host).
  
  
• CPU spec and usage.
  
  
• Buffer size and latency settings.
  
  
• Step-by-step reproducible behavior (e.g. zoom adjustable waveform and then playing back).
  Record a short video or GIF if you can.

Summary

• No known wide‑scale reports of waveform dropouts in VPS Scope 1.1.0.
  
  
• The issue may be tied to your DAW, CPU load, buffer settings, or GPU scaling interactions.
  
  
• Testing in other hosts, comparing versions side‑by‑side, and lowering load can help isolate the cause.
  
  
• Sharing detailed repro steps with Vengeance or on their forums may help catch a niche bug that slipped through.

If you capture a more detailed log or can reproduce this across clean sessions, I'd recommend posting it in the official Vengeance support forum or emailing their support team. Let me know your DAW and system specs if you’d like help tweaking settings or preparing diagnostic info!

 

Last edited: Aug 4, 2025 at 9:32 AM