I'm trying out the VirtualJV vst3 plugin and I'm getting extremely noticeable sound artifacts on pretty much every instrument. I thought maybe it's a problem with my latency settings, but there are no latency settings for this plugin and it plays the pops and cracks identically each time I play the identical notes - that means they're baked in somewhere and not coming from my side.

Has anyone else experienced this? Been able to fix it?

 

EDIT FORGET THIS:
3. Strange ground hum issue with JV-880
- It might be picking up magnetically induced hum from something nearby with a big mains transformer.
- Identify what that might be, and move your JV far away from it.

Please read all the comments: www.soundonsound.com/forum/viewtopic.php?t=85189

 

Last edited: May 19, 2026

@Meteo Xavier

What host (DAW) do you use?

 

Huh?! The OP is talking about a plugin, not a real piece of hardware. The plugin is even called "VirtualJV". He doesn't have a real JV880.

VirtualJV can have some issues with it's internal resampling - the hardware (and therefore also the emulation) runs at 32KHz, which needs to be resampled to your host's native sample rate. It's easier to resample to 48KHz than 44.1KHz, so there seem to be fewer resampling artifacts at 48KHz - if you're running at 44.1KHz, try switching to 48KHz, and seeing whether that is the issue.

The resampling algos will get improved when the plugin ultimately gets rewritten, for now it's a sort of prototype thing - it is what it is, but it's certainly useable enough here.

 

Pulsewave doesn't know how to communicate without having an LLM think for them. which is why you will regularly see them chiming in with comments that are void of context of the thread in question, or any old bollocks really. they might as well be a ChatGPT, Gemini, Claude symbiote at this point. who is parasitically feeding of whom though. has Pulsewave been infected by the LLM mind virus, or has their mundanity actually infected the LLM. it could go either way

 

the last "answer" #3 could be blamed on using an LLM, but the first two are suggestions because he assumes the crackling noise is caused by too low of a buffer setting or missing windows dependency. Don't blame AI for that, even though it is probably wrong too.

The OP basically spells out it is not clicking and crackling caused by buffer, because that kind of artifacts are never predictable. The JV880 was basically a rompler, which would point you to either the original sample having that noise in it, or a problem between the rom->emulator->DAW as @dkny already suggested. The problem is almost never actually an AI related issue. It's because he doesn't read the original post.

 

Hello @Meteo Xavier, have you installed this latest version yet?
Giulio Zausa VirtualJV (Roland JV-880 Emulator) + ROMS v1.0.0 (05.12) WiN Mac [FREE]
05/12 Fix clipping

The error likely lies not with you, but with the plugin; it is still in the testing phase. You can, of course, change your sample rate and see if that helps. One user wrote that they switched from 48 kHz to 41 kHz.

NOTE (Windows): If you are having troubles with Windows 10, it's possible you need to install the Visual C++ 2022 Redistributable.
www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/

 

Last edited: May 19, 2026

AI would have given the correct answer though. that is the main difference.

 

No, not noticed any issues.

 

Try one of these combinations of sample rate & buffer size and see if that fixes it for you:

44100: 16
44100: 128
44100: 256
44100: 512
48000: 16
48000: 64
48000: 256
48000: 1024
48000: 4096
88200: 16
88200: 32
88200: 256
88200: 512
88200: 1024
96000: 32
96000: 128
96000: 512
96000: 2048
96000: 8192

(Trying one of these is enough, either they all work or none of them work)

 

Well, I tried different sample rates and buffers like you suggested and no improvement. Again, it plays the cracks and pops identically every time I play it.

Interestingly, though, when I actually export an example of it, the artifacts are not there in the MP3. I'm guessing it's just a glitch or something it does for my particular system (I had an inverse problem with an Omnisphere patch a few months ago, so I know these things happen), so maybe I just need to ignore them in the DAW when they won't show up in the track other people (might) hear.

 

Not really safe to assume that. MP3 export can easily hide short clicks / HF artifacts depending on encoder + masking. Also no idea what bitrate it was or if it’s realtime vs offline bounce.

Better test is to print it to WAV in the DAW and zoom right in on the waveform, or stick an oscilloscope on it. If it’s still there in the WAV, then it’s actually in the signal. VPS free scope is decent enough for this if you don't have one: https://www.vengeance-sound.com/plugins.php?sub=FREE Scope

 

That came to mind shortly after exporting it and I'll try a .WAV at a later point to see if there is a difference, but I feel like if this rendered version has no audible artifacts in it, that's most likely because they're gone. Don't know the how and why, but I'm old and experienced enough to know by now all's well that ends well in music production. My first five years in doing DAW music I had to learn how to tolerate listening to latency issues in playback that would come out fine in the render, so this wouldn't really be that bad.

And, yes, I use FL Studio 2024, lbnv.

 

lbnv?
I got it
Indiana Nevada

 

Last edited: May 22, 2026

..error

 

Then just do what I have written. The problem is solved.

 

Confirmed to have removed audible artifacts. Marked as best answer for future generations. Thanks lbnv!