*fiddling around
Virtual JV: free Roland JV-880 emulation
-
- KVRAF
- Topic Starter
- 1725 posts since 17 Jul, 2001 from Milan, Italy
Following up on this thread — I did a proper A/B comparison between a hardware JV-880 and Virtual JV using the original sysex patches.
No processing, just straight comparison.
Sharing it here in case it’s useful to anyone evaluating the plugin:
No processing, just straight comparison.
Sharing it here in case it’s useful to anyone evaluating the plugin:
-
- KVRist
- 285 posts since 1 Nov, 2008
The VirtualJV plugin is awesome! But, it seems to use a lot of CPU when idle in Ableton 12. Windows 11, 5700x Processor, 32Gigs of ram.
CPU usage when idle is around 14-16%! I submitted the issue on the github, but wanted to know if anyone else was having that issue.
CPU usage when idle is around 14-16%! I submitted the issue on the github, but wanted to know if anyone else was having that issue.
-
- KVRAF
- 1714 posts since 15 Aug, 2003 from Indianapolis
In Fender Studio Pro, I get about the same...15%, but even maxing out polyphony, it never gets above 20%.
Certainly, there is room for improvement, but it's not horrible.
My biggest issue is sample rate related. In my experience, it has to be run at 44.1K. If I try to run it at 48K, I get clicks and pops. Haven't tried higher sample rates.
Certainly, there is room for improvement, but it's not horrible.
My biggest issue is sample rate related. In my experience, it has to be run at 44.1K. If I try to run it at 48K, I get clicks and pops. Haven't tried higher sample rates.
-
- KVRAF
- 24451 posts since 7 Jan, 2009 from Croatia
This is normal, the original synth ran its DSPs all the time even if no voices were playing.HydrogenHuman wrote: Mon Mar 16, 2026 1:01 am The VirtualJV plugin is awesome! But, it seems to use a lot of CPU when idle in Ableton 12. Windows 11, 5700x Processor, 32Gigs of ram.
CPU usage when idle is around 14-16%! I submitted the issue on the github, but wanted to know if anyone else was having that issue.
-
- KVRAF
- 9929 posts since 15 Sep, 2005 from East Coast of the USA
I don't use Reaper, but I have the latest version of the plugin and it works here in Sonar on Win11. I guess it’s just a Reaper issue?Midiman10 wrote: Sat May 16, 2026 5:44 am Win 11, same problem. R click on road, open with Reaper in instrument panel, but then cant load vst.
-
- KVRer
- 4 posts since 29 Dec, 2024
I can't get it to recognise the rom files whatever I try. I've tried the stand alone, I've tried the VST (Cubase on Mac), neither recognise the rom files. I've got the rom files from the usual source and I've tried files from two alternative sources. I've read through this entire thread but nothing has worked. It's frustrating because I actually own a hardware 880 which I love but it stopped working a year ago and I was hopeing I'd be able to get it back. 
-
- KVRian
- 548 posts since 22 May, 2009 from Portugal,Azores (faial island)
Windows 10
Check Data Location: Your plugin data should be located at %APPDATA%\JV880 (path: C:\Users\"your name"\AppData\Roaming\JV880).
Verify Cache: Ensure there is a Cache folder inside the JV880 directory. This is where the plugin descrambles and stores waveform ROMs during the first run.
Permissions & Attributes: Right-click the JV880 folder, select Properties, and ensure "Read-only" is unchecked. Apply this to all subfolders and files.
Avoid OneDrive: Do not host the plugin or its data folders within a OneDrive-synced folder, as this often causes access conflicts.
Dependencies: Ensure you have the latest Microsoft Visual C++ Redistributable installed or repaired.
Antivirus & Admin: Temporarily disable your antivirus to rule it out, and try launching Cubase as an Administrator (Right-click Cubase icon > Run as administrator).
ROM Validation: Use a checksum utility to verify that your ROM dumps match the required hashes in the source documentation.
macOS
Check Data Location: The data directory is located at ~/Library/Application Support/JV880. If the folder is missing, the plugin likely lacks permission to create it.
Remove Quarantine Flag: If macOS blocks the plugin, open Terminal and run the following command (replace <yourusername>):
sudo xattr -rd com.apple.quarantine /Users/<yourusername>/Library/Audio/Plug-Ins/Components/jv880.component
Alternatively, type xattr -cr (with a space), drag the plugin file into the Terminal window, and press Enter.
Grant Full Disk Access:
Go to System Settings > Privacy & Security > Full Disk Access.
Click the + icon and add Cubase to the list, ensuring the switch is toggled ON.
Rescan in Cubase:
In Cubase, go to Studio > VST Plug-in Manager.
Click the Rescan icon (or settings cog) to force Cubase to re-evaluate the plugin.
Always use the VST Plug-in Manager in Cubase to verify that the plugin is not in the "Blacklist." If it is, select it and click "Reactivate".
Permissions: Ensure Cubase has full permission to read/write to your user AppData (Windows) or Library (macOS) folders.
tell me if this helps.
Check Data Location: Your plugin data should be located at %APPDATA%\JV880 (path: C:\Users\"your name"\AppData\Roaming\JV880).
Verify Cache: Ensure there is a Cache folder inside the JV880 directory. This is where the plugin descrambles and stores waveform ROMs during the first run.
Permissions & Attributes: Right-click the JV880 folder, select Properties, and ensure "Read-only" is unchecked. Apply this to all subfolders and files.
Avoid OneDrive: Do not host the plugin or its data folders within a OneDrive-synced folder, as this often causes access conflicts.
Dependencies: Ensure you have the latest Microsoft Visual C++ Redistributable installed or repaired.
Antivirus & Admin: Temporarily disable your antivirus to rule it out, and try launching Cubase as an Administrator (Right-click Cubase icon > Run as administrator).
ROM Validation: Use a checksum utility to verify that your ROM dumps match the required hashes in the source documentation.
macOS
Check Data Location: The data directory is located at ~/Library/Application Support/JV880. If the folder is missing, the plugin likely lacks permission to create it.
Remove Quarantine Flag: If macOS blocks the plugin, open Terminal and run the following command (replace <yourusername>):
sudo xattr -rd com.apple.quarantine /Users/<yourusername>/Library/Audio/Plug-Ins/Components/jv880.component
Alternatively, type xattr -cr (with a space), drag the plugin file into the Terminal window, and press Enter.
Grant Full Disk Access:
Go to System Settings > Privacy & Security > Full Disk Access.
Click the + icon and add Cubase to the list, ensuring the switch is toggled ON.
Rescan in Cubase:
In Cubase, go to Studio > VST Plug-in Manager.
Click the Rescan icon (or settings cog) to force Cubase to re-evaluate the plugin.
Always use the VST Plug-in Manager in Cubase to verify that the plugin is not in the "Blacklist." If it is, select it and click "Reactivate".
Permissions: Ensure Cubase has full permission to read/write to your user AppData (Windows) or Library (macOS) folders.
tell me if this helps.
...want to know how to program great synth sounds,check my video tutorials: http://www.youtube.com/user/sergiofrias25
-
- KVRer
- 4 posts since 29 Dec, 2024
Thanks for this. Unfortunately it doesn't help.
It creates the JV880 folder in a different location than you've put above here: ~/Library/JV880
It has permission to write to this folder as it also creates a cash folder here. The plugin launches fine in cubase, it just doesn't recognise the rom files even though they are in the directory it specifies (the plugin even opens the directory for you which is how I know they are in the right location.
It creates the JV880 folder in a different location than you've put above here: ~/Library/JV880
It has permission to write to this folder as it also creates a cash folder here. The plugin launches fine in cubase, it just doesn't recognise the rom files even though they are in the directory it specifies (the plugin even opens the directory for you which is how I know they are in the right location.